SMorgan

It does appear to be working. I think the "not supported" indication was from the first instantiation of the node prior to turning it on and attempting to set the fan speed, which was successful when first attempted.

Debug log attached. Cycled through the fan speeds low, med, high, auto debug.log

Gotcha. I turned on my unit and set the fan level to low and it did report back successfully. Let me know if you need any logs to help determine the field names.

@bpwwer thanks again for providing those fixes so quickly. Just to follow up, the Sensibo node works fine in IoX, the only thing that looks amiss is the Fan Level which I personally don't use but thought you'd like to see it

Looks like that fixed it! After installing 2.0.5 I'm showing my one expected node now in Polyglot V3. I'll check it out in IoX later today when I have some time. Thanks again for the support.

Thanks for the response. Installed 2.0.4 with same results. New log attached debug - 2.0.4.txt

@bpwwer any ideas? edit: debug log attached with {api_key} and {UID} removed debug.log

I'm having a similar issue. Yesterday I was having problems with my IoX in general, it wouldn't control devices/scenes based on expected state changes or inputs, the mobile app failed to synchronize with error messages, and the programs tab in the iox interface would not load. I ended up rebooting the eisy which took forever to finish starting up. Today I noticed my Sensibo was not behaving as expected. In the IoX interface, I could not turn it on/off. No apparent issues in Polyglot so I uninstalled/reinstalled the node server, reconfigured the api key, and no nodes.

Same results on 5.8.3

I am on 5.8.0. I see 5.8.3 was posted yesterday. I'll give that a shot

I'm having the same issue. Did you get yours working?

Centralite by Ezlo Temperature and Humidity Sensor https://www.centralite.com/products/temp-and-humidity-sensor/ Temp and humidity readings

Here's a cable I've purchased before and verified correct angle of the micro USB end: https://www.amazon.com/dp/B0CF1ZBRF1

Thanks again for all the replies. I returned home and had two Insteon Motion Sensor II that were dead, which were working when we left last week. So it could have been these low battery devices creating that All On scenario. I do not have the All On option in the eISY interface. I plan to hard-wire the 5v USB power for the motion sensors that I can.

Thanks for the replies. The devices aren't members of any scenes. Siren is v.46 IOLinc is v.41 Sorry I don't have physical access to the devices at the moment to provide the other requested information. In the meantime I'll look into the circumstances that generate Random All On events