Solutions
-
Jimbo.Automates's post in Version 3.0.13 on store but labeled as 3.0.12 was marked as the answerLooks good now. I hadn't announced this version yet since I am testing on my production system and wanted to make sure there were no issues first.
-
Jimbo.Automates's post in PG3 ELK node server 3.5.5 fails with error: cannot import name 'FunctionKeys' was marked as the answerOh, that explains it. You need to do an "Upgrade Modules" to get the latest python:
[admin@polisy-dev ~]$ python3 -V
Python 3.9.14
-
Jimbo.Automates's post in Deleting Elk Lighting was marked as the answerHow to handle lighting is still under discussion between @Michel Kohanim and myself. I didn't realize if you imported all from ISY that it would then make them show up. I guess I need to add a configuration option in what lights to import. If you delete on the nodes tab they will come back on restart. So not much you can do besides delete them all from the ELK, setting the show option may work but I'm not sure. I'd need to test that when I have time later this week.
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in Temp in version 3.5.0 was marked as the answerYeah, it's a timing issue with the startup of PG3 so eventually on the next report it will get fixed. 3.5.2 fixed the initialization value so it shouldn't toggle on startup like you noticed. You can always check for new versions manually by going to the store page and click the update button.
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in CAO Tags Battery Life was marked as the answerYou can disable motion detection completely which should help battery life, and in special options set "Buffer multiple" so they push out temp/hum updates less often, and change "Receiver Mode" to "Lower Power Mode".
-
Jimbo.Automates's post in Unable to upgrade from v3.0.8 to v3.0.9 was marked as the answerI confirmed that I missed updating a file, so even though it displays 3.0.8 you are actually on 3.0.9. I'll fix with next release.
-
Jimbo.Automates's post in Current Power used does not match device state was marked as the answerFixed in 3.0.10
-
Jimbo.Automates's post in New LED Light Strip Issue was marked as the answerThanks, the PM showed the issue. That device doesn't have color temperature control. Issue fixed in 3.1.10.
-
Jimbo.Automates's post in HE on PG3 v3.0.54 Status was marked as the answerThere should not be errors in NS logs... This error was the issue that 3.0.54 was supposed to fix. Try changing the log level to something different. like Debug, then restart and hopefully it works. Then change level back to warning or error.
-
Jimbo.Automates's post in Character Issue was marked as the answerYep, there's an issue already for that
https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/4
Sent from my Pixel 6 Pro using Tapatalk