Jimbo.Automates

That would cause it, if the Elk is sending out audio commands then the node server has no idea what to do with them so it spits out the error. I could just silence the error. Sent from my Pixel 6 Pro using Tapatalk

Which question above? This is answered here: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#zone-node This is available in the top post when you open this subforum. A CD is a command from the ELK to control Audio Equipment, you must be doing something on the ELK to trigger that?

I always have a featured post in the subforum with a pointer to the readme so I assumed that was there? Sent from my Pixel 6 Pro using Tapatalk

My ELK, Ecobee, and Kasa node servers never need to be restarted. When you see the issue with any of mine please dowloadl log package and PM it to me and let me know what time the issue started. Sent from my Pixel 6 Pro using Tapatalk

I think UD Mobile installs the Free version by default, right @Javi ? Sent from my Pixel 6 Pro using Tapatalk

Yes that is plausible with Notification NS. I forget what the default option was, but I think what is now standard change from the original default when the free version was created. Sent from my Pixel 6 Pro using Tapatalk

This looks like the PG3 issue they decided not to fix, you will need to upgraded to PG3x.

Yes, it should show that in the installed column @bmercier ? Sent from my Pixel 6 Pro using Tapatalk

I agree this is confusing, and by default should just update the one you selected to be updated, and another option to see the full list of choices.. But your last screenshot doesn't look right, the Installed column should say which slot you have it installed. Sent from my Pixel 6 Pro using Tapatalk

Added https://github.com/UniversalDevicesInc-PG3/udi-poly-ecobee/issues/7

@bmercier any idea why upgrade from free to standard didn't require payment? Sent from my Pixel 6 Pro using Tapatalk

Thanks. Fixed in 3.6.11 which just has a minor bug fix.

The KS225 is not confirmed as working but similar ones are: https://github.com/python-kasa/python-kasa/blob/master/README.md so not sure since it's not showing up in the discover. Some of the M devices work, but man do not since they use a new protocol. The developers of python-kasa have been looking into it but nothing released yet. This is the exact reason I gave notice that this uses an unsupported API and can break at any time.

That's a PG3 issue I've seen before. Will need @bmercier to look into it. Sent from my Pixel 6 Pro using Tapatalk

Thanks, no other issue I can see in the log besides what you showed 8/17/2023, 24:45:01 [pg3] error: createNS: Error: udx: /rest/pg3.install.ns returned error status 500 at call_udx (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/udx.js:70:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.UDXdeploy (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/udx.js:128:3) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/nodeservers.js:450:7) Probably best to upgrade modules so you are on the latest PG3x and try again, unless @bmercier has another suggestion?

I've heard that some of the M devices are working, but not that one specifically.

First one is a KP401, second one is a EP40 they should both be supported. I'll give the same answer as the previous post: Kasa devices sometimes don't respond initially, the NS does try to discover devices on each long poll so they may eventually show up. I can try increasing the timeout while looking for devices if possible. For the one that shows in PG3 but not ISY, it should be grouped underneath the controller by default, but if you still don't see it then set node server logging to debug, restart the node server, let it run for a few minutes then download log package and PM it to me.

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

What version of PG3x? Probably need @bmercier to help Sent from my Pixel 6 Pro using Tapatalk

What model number devices are these?

Thanks! Much appreciated. Funny that the zooz looks exactly like the Fibaro so I was wo if they were actually the same. Sent from my Pixel 6 Pro using Tapatalk

Kasa devices sometimes don't respond initially, the NS does try to discover devices on each long poll so they may eventually show up. I can try increasing the timeout while looking for devices if possible. Device status is only updated on short poll, Kasa doesn't allow immediate updates. Remember we are using an undocumented API. Some new devices use a new method which is not currently supported, not sure if yours is one of them. Sent from my Pixel 6 Pro using Tapatalk

So I guess nobody is using the Fibaro RGBW controller? Chris is looking into it, but Is there a Zwave RGBW controller that works with IoX? Sent from my Pixel 6 Pro using Tapatalk

FYI I tested a long node name like yours thru the notification node server and it worked fine. The $sys is parsed by the IoX before being passed to the NS so will likely need @Chris Jahn to look into it. Sent from my Pixel 6 Pro using Tapatalk

No idea where that came from. Was another node server in the same slot previously and it didn't get cleaned up? Sent from my Pixel 6 Pro using Tapatalk