Bumbershoot Posted June 28, 2022 Posted June 28, 2022 Here's the log: 2022-06-28 14:25:57,900 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-06-28 14:26:00,594 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting... 2022-06-28 14:26:00,600 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-06-28 14:26:00,601 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:3f:34_10/./lifx-poly.py", line 10, in <module> 2022-06-28 14:26:00,602 MainThread udi_interface ERROR udi_interface:write: import lifxlan 2022-06-28 14:26:00,603 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-06-28 14:26:00,604 MainThread udi_interface ERROR udi_interface:write: : 2022-06-28 14:26:00,604 MainThread udi_interface ERROR udi_interface:write: No module named 'lifxlan'
EricBarish Posted June 28, 2022 Posted June 28, 2022 I had the same problem had to open a ticket and Michel fixed all this afternoon. The cause was an error in updated Python library on the 27.
jwagner010 Posted June 28, 2022 Posted June 28, 2022 This was solution that worked for me. From Polisy Admin Console | Configuration tab | Upgrade Packages. Once you hear 4 beeps, reboot Polisy If that doesn’t fix it, SSH in and issue following commands sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx Reboot Polisy again
Bumbershoot Posted June 29, 2022 Author Posted June 29, 2022 13 hours ago, jwagner010 said: This was solution that worked for me. From Polisy Admin Console | Configuration tab | Upgrade Packages. Once you hear 4 beeps, reboot Polisy If that doesn’t fix it, SSH in and issue following commands sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx Reboot Polisy again It looks like the upgrade of the udx file to version 3.0.5 and a Polisy reboot solved this issue. I also unlinked pip3, but it looks like it got relinked properly to /usr/local/bin/pip-3.9, so I imagine that the udx upgrade made that new link. Probably not necessary to unlink it at the command line...
Recommended Posts