Jimbo.Automates

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

When removing the legacy server.json you must pass the version to the interface start call. I knew that but forgot. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/commit/4d3299aac70944c2548ef2a4107bdb74253e1dc3 Sent from my Pixel 6 Pro using Tapatalk

Version 3.8.1 released with the fix.

I know why now, I will fix in next release.

I manually did a sync purchases, then it showed the update. Now I have the 0.0.0 as well and log says: 2023-08-15 13:54:43,570 MainThread udi_interface.interface WARNING interface:_get_server_data: get_server_data: failed to read file server.json: [Errno 2] No such file or directory: 'server.json'

Not sure, I was going to test on mine, but just noticed PG3 isn't telling me an upgrade is available? I'm on 3.7 and 3.8 is out?

Please send the notification, then download log package from notification NS and email it to me.

I'm stumped... It's in your nodes list you sent me for sure <node flag="0" nodeDefId="e868e786c5_2"> <address>n002_e868e786c5_2</address> <name>Main Level</name> <family instance="2">10</family> <parent type="1">n002_e868e786c5</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n002_e868e786c5</pnode> </node>

That's odd. @bmercier any idea why it would show that? With this release I removed the old server.json so it should get the version the new way now.

Shouldn't be an issue. ELK creates a new nls on restart since it has to be customized for each person. Sent from my Pixel 6 Pro using Tapatalk

Not sure, will need help from @Javi

Just confirming, you did a resync of UDM after restarting IoX? Also, do the correct status names show up in the AC? Sent from my Pixel 6 Pro using Tapatalk

I'm trying this controller. I did a normal Z-Wave exclude/include and only got 3 nodes shown in the pic, none of which would control it. So I excluded again and included using smart add with UD Mobile then I got all the nodes I expected shown in the picture and could control it with ZY 013.1 Then powered down the device and power supplies, powered it back on then I could no longer control with IoX. I did a Z-Wave Synchronize Update with Interview, and all the nodes were deleted and back to just the 3 in the pic. bfecb926-2bca-48fc-9e72-c010c8f2458a.jfif

Great, glad it's working. You can ignore those pyisy.events errors, I'll turn that off in a future release. The node server API doesn't allow creating scenes, so I can't treat them any differently. I'll see if @bmercier can add that to PG3.

I'm not sure what you mean by this? Did you change your light_method to ELKALL and Save it?

But if they don't show up in the rest nodes then something weird is going on. Try reinstall the NS in the same slot? Sent from my Pixel 6 Pro using Tapatalk

Can you see the nodes in the Admin Console?

@William Olsen 3.8.0 Uploaded to the store with new light_method ELKALL which should work for what you want.

I don't. I could pull it out of git and release it but then you'd be stuck on an old version which would never get fixes or updates. I started looking at adding this back earlier today,.will try to work on it more this weekend if I have time. Sent from my Pixel 6 Pro using Tapatalk

I have asked Ecobee to allow the API to set Vacation mode but it hasn't happened yet. What I do is create my own "Comfort Setting" called "AwayExtended" or whatever you want to call it, then restart the node server and once it completes open the Admin console and your new comfort setting will be available. I prefer to have ISY control my vacation mode, when I arm my alarm in Vacation mode it sets the Ecobee as well.

The Polyglot Version 3 Ecobee Node server 3.1.5 is released to production. See the Release Notes for more information.

That's strange, the n002_e868e786c58b_2 looks to be a valid node, so not sure why it's not showing up. Can you delete it and type it in manually instead of being copied from the PG3 UI? @Michel Kohanim @bmercier or @Javi any other ideas?