Jimbo.Automates

PG3 ELK Node Server 3.3.8 Released see the Release Notes

The latest Polisy updates seem to have broken the ELK Node server. I will try to get a fix out soon.

The Polyglot Version 3 Ecobee Node server 3.1.2 is released to production. This version supports the new Ecobee thermostat with Air Quality Sensor. See the README for more information, including information on moving from PG2 The Release Notes are also available.

Yes, it's each device, not the sensors in the device. On each poll it gets current data for all sensors in the device, but if the value is the same as previous then PG3 doesn't pass it on to the ISY. Sent from my Pixel 6 Pro using Tapatalk

Issue updated: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/13 Also updated config doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/CONFIG.md

I do not have this specific device, but I do have a power strip which uses the same exact code. I was able to see this happen one time, but I can not make it happen again. I added more debug code to try and pin down why this is happening, so if you can update to 3.0.11, make sure the NS Log is in Debug mode, then see if you can make it happen again. You can download the log and send it to me in a PM again and say which Node name was showing the issue. What I think is happening is the node server says to turn off the plug, then poll's the main device, because it can't poll the individual plug, and for some reason it is reporting the plug is still on. I can add a delay in between, but that's not really a robust solution.

Sorry about that, fixed in 3.3.7. You'll just have to go set it back to true where desired. I had noticed this last night for the use off node as well.

PG3 ELK Node Server 3.3.7 Released see the Release Notes

PG3 ELK Node Server 3.3.6 Released see the Release Notes

Fixed in 3.3.6, thanks for reporting.

Looks like the rate limit issue as well: 2022-07-16 00:03:04,512 Thread-16889 udi_interface ERROR pgSession:response: Unknown response 429: https://ext-api.airthings.com/v1//devices/2930024519/latest-samples {"error":"TOO_MANY_REQUESTS","error_description":"Rate limit on API exceeded","error_code":1070} Added info to issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/13

Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/13

Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/12

Sorry, just saw this. I need to confirm what that time value is. Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/11 It only polls once for all devices, so it shouldn't blow the rate limit.

There's no way to restart a NS from the ISY. Restarting from the PG3 interface should update all those values. Do a download log package and send that to me. I'll try to look later this week when I'm back home. Sent from my Pixel 6 Pro using Tapatalk

Yeah, I don't remember why I used 0-254 but I'll take a look, although probably can't change at this point.

Works fine for me Sent from my Pixel 6 Pro using Tapatalk

Thanks, I'll take a look when I'm home at the end of the week. Sent from my Pixel 6 Pro using Tapatalk

Issue filed: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/8 Will try to look at it when I'm back home the end of next week.

Yes, this looks like a bug. For some reason Polyglot thinks the last known value is 1 (Armed Away) so on restart that's what it's getting. The bug is that the NS should set it to the current value received from the ELK but it's not doing that. I'll have to fix that when I get home end of next week. But, if you change the ELK to another arm state, then back to disarmed that should fix it, right?

HSL is what Kasa natively uses, search Google and there's lots of info. I have one of those strips and last I tested it worked fine using any method. I can test again when I'm home at the end of next week. Are you using PG2 which is where this is posted, or PG3? Sent from my Pixel 6 Pro using Tapatalk

He was on: 2022-07-08 10:42:19,374 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.32 Starting... and now is on 2022-07-08 16:13:16,193 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting...

Weird, he was till on an older version, and pip3 command above fixed it.

Looks like your PG3 python interface is not up-to-date, not sure how that can happen. Please PM me the download log package file. You can ssh to your polisy and run this, then restart the node server: sudo -u polyglot pip3 install --upgrade udi_interface

Sorry, I'm asking @bpwwer who is the PG3 developer, not you. Sent from my Pixel 6 Pro using Tapatalk