jkosharek

Mine is disconnected after the update, tried deleting, re-installing, and re-configuring, log shows this: 2023-01-03 19:51:49 info: NS: Starting Node Server 2023-01-03 19:51:49 info: POLY: Interface starting 2023-01-03 19:51:49 info: POLY: Getting config from environment

PG3x version 3.1.17 resolved this

Migrated my POLISY to the EISY, bought a new KASA License for the EISY and KASA starts but fill the log with this: 2022-12-31 16:39:53,929 MainThread udi_interface ERROR udi_interface:write: No module named 'kasa' 2022-12-31 16:39:55,096 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-31 16:39:55,479 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-31 16:39:55,481 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-12-31 16:39:55,481 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/kasa-poly.py", line 12, in <module> 2022-12-31 16:39:55,481 MainThread udi_interface ERROR udi_interface:write: from nodes import Controller 2022-12-31 16:39:55,482 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/__init__.py", line 8, in <module> 2022-12-31 16:39:55,482 MainThread udi_interface ERROR udi_interface:write: from .SmartDeviceNode import SmartDeviceNode 2022-12-31 16:39:55,482 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/SmartDeviceNode.py", line 8, in <module> 2022-12-31 16:39:55,482 MainThread udi_interface ERROR udi_interface:write: from kasa import SmartDeviceException 2022-12-31 16:39:55,482 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-12-31 16:39:55,483 MainThread udi_interface ERROR udi_interface:write: : 2022-12-31 16:39:55,483 MainThread udi_interface ERROR udi_interface:write: No module named 'kasa' 2022-12-31 16:39:56,654 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-12-31 16:39:57,034 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2022-12-31 16:39:57,035 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-12-31 16:39:57,035 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/kasa-poly.py", line 12, in <module> 2022-12-31 16:39:57,036 MainThread udi_interface ERROR udi_interface:write: from nodes import Controller 2022-12-31 16:39:57,036 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/__init__.py", line 8, in <module> 2022-12-31 16:39:57,036 MainThread udi_interface ERROR udi_interface:write: from .SmartDeviceNode import SmartDeviceNode 2022-12-31 16:39:57,036 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/SmartDeviceNode.py", line 8, in <module> 2022-12-31 16:39:57,036 MainThread udi_interface ERROR udi_interface:write: from kasa import SmartDeviceException 2022-12-31 16:39:57,037 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-12-31 16:39:57,037 MainThread udi_interface ERROR udi_interface:write: :

Might have been the 5.4.5 IoX update needing a reboot. Seems to have picked up the new device.

Kasa TP-Link Node Server on 3.0.16 won't load a new device that is discovered. Device is added to the Kasa App and is controllable via the app, but getting errors in when I hit discover. Error log fills with this: 2022-11-22 19:05:26,048 Thread-92864 udi_interface WARNING SmartDeviceNode:handler_poll: TP-LITTER: Node not ready to poll Then this: 2022-11-22 19:05:26,048 Thread-8 udi_interface ERROR Controller:discover_new_add_device: Problem adding device Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/Controller.py", line 178, in discover_new_add_device self.add_node(dev=dev) File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/Controller.py", line 248, in add_node self.poly.addNode(SmartPlugNode(self, parent.address, cfg['address'], cfg['name'], dev=dev, cfg=cfg)) File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/SmartPlugNode.py", line 34, in __init__ super().__init__(controller, primary, address, name, dev, cfg) File "/var/polyglot/pg3/ns/000db9560bc8_2/nodes/SmartDeviceNode.py", line 41, in __init__ controller.poly.subscribe(controller.poly.POLL, self.handler_poll) File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 277, in subscribe pub.subscribe(topic, callback, address) File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 97, in subscribe Thread(target=callback, args=item[2:]).start() File "/usr/local/lib/python3.9/threading.py", line 899, in start _start_new_thread(self._bootstrap, ()) RuntimeError: can't start new t hread Then continues with this again: 2022-11-22 19:05:39,377 Thread-92873 udi_interface WARNING SmartDeviceNode:handler_poll: TP-LITTER: Node not ready to poll

Great work bpwwer:

On PG3: Node 1 - Parent Node - 943cc64511f Node 2 - main - 943cc64511f_1 Node 3 - indoor - 943cc64511f_2 On IoP Admin: Node 2: Node 3:

Sent the logs and my API Key

Yes, hit load profile on the PG3 interface, restarted admin console, same node mismatch. Also stopped node and started, then restarted admin console, same node mismatch.

I setup AmbientWeather v2.0.6 on PG3 v3.1.13 on IoP v5.4.4. Put in the API Key and it created 3 nodes in PG3 and on IoP. In the AmbientWeather Node Server on PG3 web interface I see the following nodes: Node 1 - Weather Station - 1 property, just the name Node 2 - Main (outside array) 19 properties Node 3 - Indoor (inside array) 7 properties On IoP is see: Node 1 Node 2 - Main - 7 properties Node 3 - Indoor - 7 properties The properties and values on Node 2 and 3 are both from Node 3, The number of properties and values I see in PG3 for node 2 are not displayed in IoP at all. Also in Programs, Node 2 doesn't show up at all, only 1 and 3. bpwwer how do I get the Nodes displayed in PG3 to display correctly on the IoP??

I figured this out, the call back URL needs a /auth at the end: https://udi-honeywellhome-auth.azurewebsites.net/auth That got it working for me.

Went through the setup procedure here: https://github.com/dbarentine/udi-honeywellhome-poly/blob/master/README.md When I go to https://udi-honeywellhome-auth.azurewebsites.net/ and enter the client ID and secret I get this error: {"code":400, "message":"The redirect URL provided does not match the redirect URL registered for the app."} Checked the URL twice, deleted the app and recreated twice. Any ideas?

I am looking for smart switches to jump ship on Inseton and find a keypad link replacement, so I am testing some LiFX switches and Lights for our new home. I am running IoP and PG3, I installed LiFX controller and the node was created on IoP, selecting 'Re-Discover Bulbs' produces these messages in the logs: 2022-07-27 23:47:14,685 Thread-96 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2022-07-27 23:47:16,473 Thread-96 udi_interface INFO lifx-poly:_discovery_process: 0 bulbs found. Checking status and adding to ISY if necessary. 2022-07-27 23:47:16,475 Thread-96 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete. The devices are ping'able from the POLISY and I can run this command and lists the bulbs/switches. curl "https://api.lifx.com/v1/lights/all" \ -H "Authorization: Bearer YOUR_APP_TOKEN" On the LiFX controller node in IoP, if I press All On or All Off, it controls the LIFX Z light strip, but not the switch. Does the Node need an API Key created to auto-discover the bulbs and control them?

I have been using the KASA Node server to control come outlets and am looking for an inseton and keypad link replacement for a new home. Any plans to get the KASA node to work with KASA dimmers correctly and have them able to be controllers for scenes?

I am looking for smart switches to jump ship on Inseton and find a keypad link replacement, so I am testing some LiFX switches and Lights for our new home. I am running IoP and PG3, I installed LiFX controller and the node was created on IoP, selecting 'Re-Discover Bulbs' produces these messages in the logs: 2022-07-27 23:47:14,685 Thread-96 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2022-07-27 23:47:16,473 Thread-96 udi_interface INFO lifx-poly:_discovery_process: 0 bulbs found. Checking status and adding to ISY if necessary. 2022-07-27 23:47:16,475 Thread-96 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete. The devices are ping'able from the POLISY and I can run this command and lists the bulbs/switches. curl "https://api.lifx.com/v1/lights/all" \ -H "Authorization: Bearer YOUR_APP_TOKEN" On the LiFX controller node in IoP, if I press All On or All Off, it controls the LIFX Z light strip, but not the switch. Does the Node need an API Key created to auto-discover the bulbs and control them?

I’d put in a ticket, UD support is quite good. Were the keypads working before you converted to IoP?

I have about 20 keypads and they all work perfect. Maybe try a reboot of the ISY and power cycle the keypads, if that doesn’t work restore the PLM

Updated both POLISYs using 'sudo pkg update && sudo pkg upgrade && sudo service isy restart' My original OG POLISY is running my IoP and had the left LED fast blink, so I did the six tappy taps and it stopped blinking. My new POLISY (in the past month) runs my PG2, PG3, and a test IoP didn't have the left fast blink LED, I assume it is already UEFI. Both POLISY seem to be running great, console loaded lighting fast. I might have been the function of clearing java cache/deleting Admin Console and a fresh install. Although on my MacBook I cannot get the admin console to create the shortcut on the desktop or keep the launcher link in the dock. Everything on the POLISY and IoP seem to be functioning well, nice job UDI Team!

I have an original POLISY and it was blinking and pressed the reset 6 times and it updated or at least it stopped bliniing. I bought a new POLISY in the past month and it was already UEFI or not blinking after the upgrade.

That seems like a step backwards in PG3 to not have a mechanism as it is in PG2? This morning I work up to an alert for my HUE node (ISY Program configured to email when the node was not connected), so I looked at PG2 and needed to start the HUE node. Are you saying that wouldn't work if/when HUE gets migrated to PG3?

The Sonos PG3 version doesn't have a parent node. All nodes should have a parent node for status. I have program alerts set for all of my nodes, so if they go offline I get a notification. Michel Kohanim is there any requirement for nodes to have a parent or node status?

Part of my sleep timer program for my bedroom TV is turn on Sonos 'Speech Enhancement' and 'Night Mode' via a network resource to other node server (https://github.com/jishi/node-sonos-http-api). I would be willing to contribute to getting those functions added to the PGv3 Sonos Node!

Is a Serial PLM better than a USB PLM when moving from ISY to IoP? Is one faster than the other or more reliable?

Probably, I went ahead and picked up the EVL-4EZR and will play with the Honeywell panel and see how it works, then decide if I should upgrade to a DSC panel and keypads. Thank you for your help and work on the nodeserver.

I really only want to use the status of door & motion sensors to control other devices within the ISY or IoP ecosystem. So it sounds like I should look for a used DSC panel and get the EVL-4EZR. Do you know if the DUO™ IP/LTE (https://www.eyezon.com/duo.php) is the same thing as it relates to the HW EnvisaLink nodeserver?