-
Posts
4565 -
Joined
-
Last visited
Community Answers
-
Jimbo.Automates's post in Hue Emulator, ISY Connected is False was marked as the answer
For Polsiy & esiy set:
hue_port 8081
isy_port: 8080
and restart the node server.
-
Jimbo.Automates's post in Installed on eisy but not working was marked as the answer
Please update to the latest PG3, reinstall in the same slot and try again.
Sent from my SM-X808U using Tapatalk
-
Jimbo.Automates's post in 3.5.7 upgrade to 3.5.8 not working with restart was marked as the answer
That's a PG3 bug. Go to "Node Server Store" , Select ELK, Select "Install" of the Perpetual version. This will show in option "ELK is already installed in slot x, Reinstall here?". To be safe, I'd backup PG3 first, but I've not heard of this causing any issues.
-
Jimbo.Automates's post in Slow response to/from ELK NS was marked as the answer
Please update to 3.5.8 and let me know if that helps. I'm not home so I can't confirm.
-
Jimbo.Automates's post in 3.1.18 not Installing was marked as the answer
It's a PG3 bug. Please reinstall in the same slot. Don't delete and install, choose the reinstall option. Sorry, not at a computer to give the exact procedure...
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in Trying to install Flume Node Server was marked as the answer
Update to latest PG3 should resolve this.
Sent from my SM-X808U using Tapatalk
-
Jimbo.Automates's post in WeatherFlow on eisy PG3x was marked as the answer
I had initially enabled WiFi, but switched to Ethernet and kept having problems. I just reset networking with the 4 button pushes described in the user guide and it seems better so far. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Reset_Networking
-
Jimbo.Automates's post in Adding Hue to Harmony Hub was marked as the answer
Something else must be using port 8081? What other node servers or programs do you have running on your Polisy?
You can change it to something else, like 8082 and restart the node server.
-
Jimbo.Automates's post in Confirming your affiliate link for wireless tags was marked as the answer
Yes that's the correct link, thanks for checking. If you order after clicking the link it will be credited.
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in Zone Logical Status for Notifications? was marked as the answer
The doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#zone-node
Shows Logical Status driver:ST
If it's still showing the raw value try rebooting the ISY. It returns the correct for output because that uses a standard On/Off so a reboot is not required.
-
Jimbo.Automates's post in Unable to upgrade to version v1.0.6 from v1.0.5 was marked as the answer
This is a bug in PG3 where it doesn't properly recognize a new version of a node server that was previously released with a very old version of PG3.
But, do not delete and reinstall. You can reinstall in the same slot from the store or purchases page.
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in Rename feature question was marked as the answer
The nodes were deleted because you uninstalled the node server. That always deletes the nodes in PG3 and the ISY.
Sent from my Pixel 6 Pro using Tapatalk
-
Jimbo.Automates's post in Exception in thread using v1.0.0 was marked as the answer
Version 1.0.1 released to force an upgrade of the udi_interface which was out of date on your system.
-
Jimbo.Automates's post in UD Mobile Notifications support? was marked as the answer
It is released to beta @brians
-
Jimbo.Automates's post in Process for changing the name of a light? was marked as the answer
It pulls the name from what you define in the Kasa app when adding a new device, for existing devices if you want them to change to reflect a name in the Kasa app then set the change_node_names to true which I announced in the last release https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md#configuration-parameters
Then restart the node server.
-
Jimbo.Automates's post in Version 3.0.13 on store but labeled as 3.0.12 was marked as the answer
Looks 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 answer
Oh, 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 answer
How 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 answer
Yeah, 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 answer
You 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 answer
I 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 answer
Fixed in 3.0.10
-
Jimbo.Automates's post in New LED Light Strip Issue was marked as the answer
Thanks, 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 answer
There 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 answer
Yep, 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