Jimbo.Automates

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.

1. Sorry, they are not, and currently not on the list to add. That would be a big effort. 2. Yes.

The Polyglot Version 3 Node server for ELK Security Version 3.4.7 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.

Also, make sure it's not trying to constantly write updates to wireless devices, that can make ISY very slow if there are a lot. I disable that option on each startup.

PG3 Camect node server 3.0.9 released. See Release Notes Make sure your ISY is running the latest version, which is 5.4.4 for IoP and 5.3.4 for ISY994i.