bpwwer Posted September 5, 2022 Posted September 5, 2022 pushed out version 1.0.15, same drill. Fixes case where channel doesn't have a name (name == None) caused it to crash Fixes address for TotalUsage and Balance channels. @tazmanThe log shows the AC CT updating fine, the problem was the TotalUsage channel address was not getting validated properly, it should have been "31548_totalusa" but instead was "31548_", the same thing for the balance channel, it was also getting an address of "31548_" instead of "31548_balance"
Kevin Posted September 5, 2022 Posted September 5, 2022 looks great the only thing not there is the total and the difference. But I would not use that and I am not sure if anyone would? But if you want me to keep working with you on trying more things out I will be happy to.
tazman Posted September 5, 2022 Posted September 5, 2022 @bpwwerMy air conditioner (16) and Tesla charger (81882) will not go back down to zero they will fluctuate but will not go to zero after they are off. In the log file I'm attaching with the poll set to 10 seconds the A/C turned off around 2:30:30 and I turned the charger on I changed the charge rate some and turned the charger off at 2:32:30 and the values do not go to zero for either of them. VUE.zip
Kevin Posted September 5, 2022 Posted September 5, 2022 @tazman What dose it show I looked and it seems to be repoting 5w and at 240vac that is 5ma That could be just the cpu in the charger?
Kevin Posted September 5, 2022 Posted September 5, 2022 @tazman @bpwwer You are right it seems to not report a 0. if you suddenly turn off a device and it goes' to 0 it will stay at the last know kw reading. I tested it out on my ac and when I turned it off it stayed at 1.7519 kw
tazman Posted September 5, 2022 Posted September 5, 2022 @KevinThe car has not been charging since I did that test and the pic is what it is still showing.
Kevin Posted September 5, 2022 Posted September 5, 2022 (edited) @tazman Yes if a ct just drops to 0 it doesn't report it. But as soon as you start to draw power form it it works again . You could add a big loading resistor to the line so it never goes' to zero LOL. Edited September 5, 2022 by Kevin
TJF1960 Posted September 6, 2022 Author Posted September 6, 2022 (edited) Hi @bpwwer, Great job, thank you for all of your work on this. You have made tremendous progress, especially for not having a Vue2! I have the 16 sensor showing and data flowing, looks good with the quick peek I took. I also have 4 switches that populated nodes. All 4 report status of false with no data. Also, the on/off buttons do not work which is probably expected. Attached is the log. Thank you, Tim VueTest_9-5-2022_53224_PM.zip Edited September 6, 2022 by TJF1960 1
bpwwer Posted September 6, 2022 Posted September 6, 2022 18 hours ago, tazman said: @bpwwerMy air conditioner (16) and Tesla charger (81882) will not go back down to zero they will fluctuate but will not go to zero after they are off. In the log file I'm attaching with the poll set to 10 seconds the A/C turned off around 2:30:30 and I turned the charger on I changed the charge rate some and turned the charger off at 2:32:30 and the values do not go to zero for either of them. VUE.zip 24.55 kB · 1 download There is a bug in the code where it fails to report the value of zero. I'll get that fixed shortly.
bpwwer Posted September 6, 2022 Posted September 6, 2022 version 1.0.16 should now be in the store. Fixes not reporting usage when zero. Maybe fix outlet on/off Add some info to try and debug outlet power reporting 1
tmorse305 Posted September 6, 2022 Posted September 6, 2022 50 minutes ago, bpwwer said: version 1.0.16 should now be in the store Hi @bpwwer, I loaded 1.0.16 and initially the version shows 1.0.16 as the NS is booting up but then it drops back to 1.0.15 so I not sure what version I'm running. I deleted the NS and started over with 1.0.16 but the result is the same. The plugs still show a status of False and the KWatts don't drop back to 0 after the load is removed. Thank you for this fantastic enhancement to your NS!
bpwwer Posted September 6, 2022 Posted September 6, 2022 Sorry, I must have forgotten to push the 1.0.16 to the public repository. It's there now. A restart should re-install it and then show that 1.0.16 is running.
tmorse305 Posted September 6, 2022 Posted September 6, 2022 (edited) @bpwwer, thanks 1.0.16 does now load correctly. I can confirm the KWatts now drop to 0 when the load is removed. My plugs all still show up as False. I'd be happy to send you a plug if that would help your troubleshooting Thank you. Edit: I noticed in the log that the only error occurs when it tries to update the 'balance' node. It says its a scaling issue. When I look in the NS configuration it says there are 21 nodes but there is no balance node. I don't know if that helps but I thought I'd share the observation. Edited September 6, 2022 by tmorse305
Kevin Posted September 6, 2022 Posted September 6, 2022 just checked out 1.0.16 and it seems to be working good now for me. I kicked the ac on and then off and the compressor did go back to zero. I do not have any switches so I am no help to you there. Thanks so much for all your work
TJF1960 Posted September 7, 2022 Author Posted September 7, 2022 Hi @bpwwer, my findings are now exactly as @tmorse305 describes, switches report as false with no data, no balance node but everything else looks splendid! Log attached just in case you need it. VueTest_9-6-2022_45754_PM.zip
tazman Posted September 7, 2022 Posted September 7, 2022 @bpwwerAwesome job the numbers are working great for me. The charger supports on and off and changing the charge rate that shows up in the AC but does not work. I t would be nice if these items work but not a requirement and the only reason I ask is because the Tesla node server wakes the car up when it polls it. In the attached log file I tried to turn the car on with the AC then tried setting the charge rate twice then tried to turn it off. When the commands did not work from the AC I controlled it from the app hopping the log might pickup the commands in the log file. Charger.zip
bpwwer Posted September 7, 2022 Posted September 7, 2022 16 hours ago, TJF1960 said: Hi @bpwwer, my findings are now exactly as @tmorse305 describes, switches report as false with no data, no balance node but everything else looks splendid! Thanks! I had added some output to the log to get a better idea of what's going on with the outlets. It simply looks like the API call to get usage information is not including any information for the outlets. It's not a problem with the node server but with the reverse engineered library I'm using. I'll look at the library and see if I can spot anything that looks wrong or missing.
bpwwer Posted September 7, 2022 Posted September 7, 2022 Version 1.0.17 is in the store now. Refresh Store and restart to update. I fixed some bugs in the charger code so it should turn on/off and set the rate now. I also looked a bit more at the outlet code and added more log output to try and debug. From what I can tell, it should work. While searching for info on outlet support I did come a bit of info related to the library and Emporia API. The library was originally written for use with the Home Assistant package and Emporia reached out to the library developer asking them to optimize how it was being used as it seemed HA users were putting a strain on the Emporia cloud servers. They specifically asked that the number of calls to the API be restricted to no more than 2000 a day. With the current shortPoll interval of 1 second we're exceeding that by a large margin. Switching to a 1 minute shortPoll and getting the average use over that 1 minute is the only way to get that usage down. So my question is would 1 minute data be good enough? I.E. is anyone planning to try and trigger off small changes in power usage that would require better precision? 1
tazman Posted September 7, 2022 Posted September 7, 2022 @bpwwerIt is nice seeing the instantaneous readings but I think I should ok with the 1 minute intervals. I think if we keep the longer poll time maybe that will stop Emporia from changing something to cut everyone off. I will try the charger when I get home to see how that goes. To try and cut down on the data traffic would it make sense to delete some of the nodes I don't care about in PG3 or will they come back with a restart? Thanks for the great work!
bpwwer Posted September 7, 2022 Posted September 7, 2022 13 minutes ago, tazman said: To try and cut down on the data traffic would it make sense to delete some of the nodes I don't care about in PG3 or will they come back with a restart? Thanks for the great work! It polls for the other data at the longPoll interval and the hourly data is the only one that might make sense to poll more often, for weekly/monthly, once an hour would be fine and that's only 24 queries a day. So I guess the question applies somewhat to hourly data as well. Is there a use case for that and if so, how often should it be polled? To answer you question though, no, deleting the nodes won't change the node server polling at all.
TJF1960 Posted September 7, 2022 Author Posted September 7, 2022 Hi @bpwwer, I know that waiting 1 minute to see an update seems like an eternity sometimes. I would prefer 15 or 30 second polling but even at 30 second polling it puts us over 880 polls over their suggested 2k so... I defer to you guys. If polling can be adjusted, my vote would be 30sec and up Installed 10.0.17, switches still show disconnected and no data. Log attached Thank You! -tim VueTest_9-7-2022_123142_PM.zip
bpwwer Posted September 7, 2022 Posted September 7, 2022 Thanks @TJF1960for the log, it helps. I added some test code to try and output power data for the outlets and it worked, I see the data. Now I just need to figure out why it's not getting it when I update the nodes.
tazman Posted September 7, 2022 Posted September 7, 2022 With regards to what I plan to use it for I don't have any use for the hourly, weekly and monthly data at this time. Maybe make it so when it installs it updates the short poll every minute and the long pole every hour and put something in the instructions about the desired polling limitations then it is on each person on how they handle it. I know I would be good with it not polling while I'm sleeping but I know that is not how it works. I will set my polling accordingly to try and keep it under their desired limit.
tmorse305 Posted September 7, 2022 Posted September 7, 2022 (edited) 2 hours ago, bpwwer said: So my question is would 1 minute data be good enough? I've been using the Home Assistant integration, now I understand why the 1 minute poling limitation. It's the only thing HA is doing for me so I can't wait to shut it down. 1 min poling is fine for me. I am using it to alert me that the washer, dishwasher, dryer, etc is done. I also am using it to alert me when the oven and well pump have been on too long. Right now I don't have a need for anything but 1 minute data. Thanks again for your efforts to get this working! Edit: Additional note The person who authored the Integration for HA indicated that when Emporia is poled sometimes the data comes back as 'unavailable' or 0. I saw this happen and had to compensate for it in my programs to avoid false notifications. I don't know if this will happen to this NS but just a heads up in case it does. Edited September 7, 2022 by tmorse305
bpwwer Posted September 7, 2022 Posted September 7, 2022 1.0.18 in the store now. Changed the query from second to minute and also changed the default short poll time to 60 seconds. You can set the short poll shorter, but you'll still get readings that are averaged over a 1 minute interval. Changed the hour query to happen every 10 short poll intervals. So with the default value, that would be every 10 minutes Changed the default long poll to 1 hour (3600 seconds). The daily and monthly queries are done at this interval. After more investigation on outlet reporting, I think it was aborting the updates when it encountered a failure and it looks like it is failing to create the balance and totalusage nodes and fails when trying to update those. I re-worked the code so that it should just log an error now and keep going. If my assumption is right, outlets should start working now.
Recommended Posts