Jimbo.Automates

Not required, this creates custom messages as described in the doc https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/POLYGLOT_CONFIG.md#messages New option to send notifications to UD Mobile app, I need to update the doc for this still. The opt1=val1 will cause and error, I guess you took that verbatim from the doc, it's meant to tell you to add your options and values, and all the options are described. https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#isy-network-resource The easiest way to send a message is with https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#short-custom-content Using "Send Sys Short" on your serivce node. Make sure to read both docs: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/POLYGLOT_CONFIG.md (This should be shown on the Configuration for the node server page, along with lots of hints about how to format your network resources. As to why the Node server still says Disconnected, that could be anything. Do a "Download Log Package" and PM that to me.

Something must be overriding it or setting it back because I use this method extensively at our Lake House. I created an "AwayExtended" Climate Type and have a program that sets it to that Cand Hold as Indefinite and it works great.

Yes, would be ideal to fix the source, and understand it can take a while. The slider works great on a dimmable light, haven't tried the Picker. I have no programs controlling these fans. Now the very odd thing is I just tried it again while not at home and it looks like it worked perfectly, I will test again when back home and connected to the LAN.

Ok, maybe I'll poll users of the Kasa NS to see if anyone objects to just change the it. Ok, bummer. Should it just be changed in the ISY source profile? Strange, I tried another Fanlinc and it had the same issue. They both respond file to KPL and RemoteLinc's.

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

@garybixler Try 3.5.2

The Polyglot Version 3 Node server for ELK Security Version 3.5.1 is released. See the Release Notes Please make sure your Polisy is up to date by running Upgrade Packages in the Admin Console -> Configuration -> System section. See the README for more information, including information on moving from PG2. If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

Great, glad it's kinda working. I don't have a zone with temperature so it's hard to test it thoroughly. I'm not sure if the zones need to be polled, of if temperature changes will be pushed. Please set log to "Debug + Modules" then query the node, wait for it to go back to -40 then download log package and PM that to me. Although I've heard that PM might be broken now on the forums, so you can email it to me, same as my user name here at gmail.

PG3 Node server for CAO Wireless Tags version 3.1.7 is released, see the Release Notes.

In ISY Systems settings do you have request status options enabled? Sent from my Pixel 6 Pro using Tapatalk

@Javi Great job on the widgets! Just started using them. Would it be possible for the slider to show the value as you slide it? The Kasa NS uses 0-255 for brightness which works fine in a slider, but maybe I should change it to use 0-100 so it shows percentage instead of the number? I'm not able to add the load button for an Insteon KPL. Can that be added? See pic. It works fine using the default type. I tried the picker for Insteon fan motor, which pulls up the off/low/medium/high but it doesn't actually change the device when I select one? UD Mobile.is now becoming a great app to control everything with IoP and Polyglot! Sent from my Pixel 6 Pro using Tapatalk

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.