Jimbo.Automates

That's possible, I was a little distracted at the beginning of the call. Sent from my Pixel 6 Pro using Tapatalk

Most of the time was geared towards hub users, which is understandable to give those people a little confidence. ISY was mentioned many times by Steve, in a good light, and said the Hub will never be as good as the ISY, just that the Hub user is a more simple user. Ken said shipments of products are arriving soon and will be in the on line store, wouldn't say which ones. Ken said many times that they want to be different and work closer with 3rd parties, like UDI. But they only took question submissions thru the Zoom ask questions interface and I put all questions asked here out there and nothing was said about PLM plans, improving failures, or a public API.

That's odd because those errors are from PG3 itself, not the Node server so unsure how any could be working. Near the very end of the PG3 log it shows errors contacting the ISY: /20/2022, 20:14:30 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:00:ef:c2_2] {"shortPoll":{}} 9/20/2022, 20:14:30 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:00:ef:c2_2 to broker pg3_broker 9/20/2022, 20:14:30 [pg3] error: No code in error response 9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 1] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 11.024519ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection 9/20/2022, 20:14:30 [pg3] error: No code in error response 9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 2] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 6.935924ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection 9/20/2022, 20:14:30 [pg3] error: No code in error response 9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 3] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 9.455622ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection 9/20/2022, 20:14:30 [pg3] debug: ISY Response: [Try: 1] [00:21:b9:00:ef:c2] :: [200] :: 56.488285ms - http://192.168.0.33:1026/rest/profiles/ns/0/connection 9/20/2022, 20:14:30 [pg3] error: No code in error response 9/20/2022, 20:14:30 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 18.126119ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection 9/20/2022, 20:14:30 [pg3] info: ISY node server configuration update required 9/20/2022, 20:14:30 [pg3] debug: Scheduling http://192.168.0.33:1026/rest/profiles/ns/2/connection/set/network?ip=192.168.0.48&baseurl=%2Fns%2F00%3A21%3Ab9%3A00%3Aef%3Ac2_2&name=Hue&nsuser=00%3A21%3Ab9%3A00%3Aef%3Ac2&nspwd=Fx8VH%3FXivE05leIS&isyusernum=0&port=3000&timeout=0&ssl=true&enabled=true&sni=true to group system 9/20/2022, 20:14:30 [pg3] error: Error: GET http://192.168.0.48:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 9/20/2022, 20:14:30 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/isy/system.js:91:13) at runNextTicks (node:internal/process/task_queues:60:5) at listOnTimeout (node:internal/timers:533:9) at process.processTimers (node:internal/timers:507:7) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) 9/20/2022, 20:14:30 [pg3] warn: verifyNodeServers (00:0d:b9:53:2b:bc) :: ISY has no node servers installed, skipping 9/20/2022, 20:14:30 [pg3] debug: ISY Response: [Try: 1] [00:21:b9:00:ef:c2] :: [200] :: 114.915795ms - http://192.168.0.33:1026/rest/profiles/ns/2/connection/set/network?ip=192.168.0.48&baseurl=%2Fns%2F00%3A21%3Ab9%3A00%3Aef%3Ac2_2&name=Hue&nsuser=xxx&nspwd=xxx&isyusernum=0&port=3000&timeout=0&ssl=true&enabled=true&sni=true 9/20/2022, 20:14:30 [pg3] info: [00:21:b9:00:ef:c2_2] 'Hue' installed into ISY successfully... 9/20/2022, 20:14:30 [pg3] debug: >>>>>>> Got isy ready event >>>>>> That is a problem, change the emulated hue to a different port when using IoP. It doesn't matter what as long as it's greater than 1000 but just use something like 8081. I need to change the NS default since IoP decided to use the port that I was using as a default. And you never answered @bpwwer Make sure you are on the latest version of PG3 which is at 3.1.10 now.

There are tons of errors in the PG3 log about permissions communicating with the ISY: 9/20/2022, 20:14:30 [pg3] error: Error: GET http://192.168.0.48:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 9/20/2022, 20:14:30 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/isy/system.js:91:13) at runNextTicks (node:internal/process/task_queues:60:5) at listOnTimeout (node:internal/timers:533:9) at process.processTimers (node:internal/timers:507:7) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) 9/20/2022, 20:14:30 [pg3] warn: verifyNodeServers (00:0d:b9:53:2b:bc) :: ISY has no node servers installed, skipping

It goes to where ever your browser is configured to place downloads. Yes, I saw that error in your post, but that doesn't help, I need to see the PG3 log, not the NS log to see what happened before that error.

For either issue "Download Log Package" and PM it to me.

Easiest way to send log is download log package from node server log page and PM that zip file.

Log into Polisy and: sudo tail -f /var/udx/logs/log Then in AC do a Upgrade Modules and see what it says. Mine is showing a weird error that Michel is looking into.

Yes, it's possible, will try to make time to add it sometime. https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/9

Need help from @bpwwer for this.

It will only discover devices if broadcasts can go across vlans, otherwise you would have to manually add them, but the NS doesn't currently support that. Sent from my SM-X808U using Tapatalk

I noticed this as well, but you don't have to copy, just update a line and save. I think thus was mentioned in the transition post somewhere? Sent from my SM-X808U using Tapatalk

This node server automatically detects devices assigned a new IP, and that seemed to work for your 'Basement Hallway" device. 2022-08-31 02:05:04,586 Thread-6 udi_interface WARNING Controller:discover_new_add_device: Updating 'Basement Hallway' host from 192.168.1.43 to 192.168.1.42 But the discover is not seeing another device. Did you check the Kasa app to see if that device is available there?

My Kasa devices are very reliable. When the node server says they are disconnected can you check the Kasa app and see what it says? I'm very busy this week and weekend but can try to review the log when I have time. Sent from my Pixel 6 Pro using Tapatalk

You should not be using pkg upgrade, only use Upgrade Packages in the admin console. Send a support ticket using the URL Michel has in his signature. Sent from my Pixel 6 Pro using Tapatalk

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.

That usually means I forgot to update a file and you are likely running 3.0.9, I'll take a look when I get a chance. Sent from my Pixel 6 Pro using Tapatalk

Yes, and that info will help me add support https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/65 Sent from my Pixel 6 Pro using Tapatalk

Both issues fixed in 3.4.9. Thanks for reporting.

Thanks, that is benign, I'll add an ignore. That message means the system was sending an alarm report to central station and can not be used by 3rd party applications like this.

Please go to log page and download log package and send PM it to me. Sent from my Pixel 6 Pro using Tapatalk

Confirm your on 3.4.8 and restart the NS and it won't show up again. Sent from my Pixel 6 Pro using Tapatalk

Fixed in 3.4.8, thanks for reporting.

That's odd, I'll take a look tonight. Sent from my Pixel 6 Pro using Tapatalk

Yes, what @lilyoyo1 said. Since we have to poll the Ecobee servers to get status I never felt it was very useful to integrate. It could be added to the list, but honestly not much motivation to work on it since I already have over 60 issues that need attention at some point for all my node servers. Most people would opt for Insteon or Z-Wave sensors, I have a few I would give away since I now have wired ELK sensors.