Sensibo plugin won't find all nodes

[Minoaka System Admin]

Running an EISY with 5.8.4 firmware and Polyglot V3.

I'm trying to use the Sensibo plugin.  It's only finding two of the 5 nodes that I have.

I tried using a new API key to no avail, still only find 2 nodes. 

Any thoughts on how to troubleshoot?

Thanks!

[SMorgan]

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.

[SMorgan]

@bpwwer

any ideas?

edit: debug log attached with {api_key} and {UID} removed

debug.log

[bpwwer]

I can see what the problem is from the log, but I'm not sure what to do to fix it since I don't know anything about the sensibo devices.

It's failing to create a node because when it tries to update the node drivers initially (specifically the CLIMD (mode) node driver, it encounters an error.  It's trying to set the mode to 'auto' but 'auto' isn't defined as a valid mode for it to set.

The node defines 'cool', 'heat', 'fan', 'dry', and 'auto' as modes that can be sent to the sensibo to control it, but then it defines 'cool', 'heat',  and 'fan' as modes that the sensibo can return as the current set mode.  However, the sensibo is apparently returning the current mode as 'auto' which crashes the plug-in.

I would say the fix is to simply add 'auto' to the list of valid modes the sensibo can return.  But the control defines the modes as cool=0, heat=1, fan=2, dry=3, auto=4.  While the sensibo mode status is defined as cool=2, heat=1, fan=6(?).

So I think that things break if the sensibo ever sends a mode status of 'fan' since 6 isn't defined as a valid mode either.

I don't know if the mode status values should match the mode control values or if they really are different.  And if they're different, what should the mode status 'auto' be?

The API documentation is of no help as it doesn't define what's returned by the calls at all. 

So I made a guess and changed the mode status to match the mode control values.  I just pushed this change out as version 2.0.4 to the production store.  See if works.

[SMorgan]

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

debug - 2.0.4.txt

[bpwwer]

Actually, it's not the same error.  It's now failing on 'fanLevel' not 'auto' like it was before.

It looks like the code tried to handle the missing key 'fanLevel' but didn't do it right.  I've corrected it and released as 2.0.5

[SMorgan]

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.

[SMorgan]

@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

[bpwwer]

Your device isn't reporting any fan level so that value is correct.

That's what was causing the failures after the first fix I added.  The code was expecting a fan level and crashed if it didn't see one.

It's possible that the code has the field name wrong and that's why it doesn't see it, but there's no documentation on what the field names are so I have no way to check that.

[SMorgan]

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]

You can set the log level to debug and change the fan level.  It looks like the debug log might show what the device sends which would help.

[SMorgan]

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

debug.log

[bpwwer]

From the log, it appears to be working.

Successfully set {UID} :: CLIFRS to 0 UOM 25
Successfully set {UID} :: CLIFRS to 1 UOM 25
Successfully set {UID} :: CLIFRS to 2 UOM 25
Successfully set {UID} :: CLIFRS to 3 UOM 25

That shows it setting the fan value to low, medium, high, auto

There's nothing in that log that shows it setting the level to 'Not Supported' 

Based on what I see, the plug-in is working correctly.   Have you restarted the Admin Console?  If not, try that.

[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.

Edited October 20, 2024 by SMorgan