UniversalDevicesInc/Polyglot

Hue hub connected status needs to be changed

Opened this issue · 4 comments

mjwesterhof commented

The current behavior of the connected status reflects only that the hub was previously "paired" with the node server -- but user expectations are that the status should reflect the current ability to communicate with the Hue Hub. Per user report on forum:

"Don't know if this has been discussed, but on the "Hue Hub" node on the ISY, it always seems to say "Connected = True", even when it isn't. I noticed that my Hue lights' status was not available, nor would they respond through the ISY commands, but the hub says it was connected in the ISY interface. After re-connecting (by pressing the button the hub and connect in the ISY), all is well again."

We need to move the current connected indicator to an additional field ("paired" or "authenticated" or "key obtained" or such), and add code to make the status reflect the current response or lack of response from the Hue Hub.

mkohanim commented

Hi mjwesterhof,

Wouldn't that be the Is Responding control? Doesn't get see a red ! next to the node?Also, in Programs, they can check against Responding.

This said, I agree that connected is not the right choice of word. I think it should be renamed to "commissioned".

With kind regards,
Michel

mjwesterhof commented

As far as I can tell, there is no explicit way for a node server to indicate that a node is in a "not responding" state. In this case, it is the Phillips Hue Hub that is not responding to the Node Server, but Polyglot will continue to respond to the ISY, so the ISY will not mark the node as "Not Responding, and therefore won't show the red exclamation point for that specific node.

mkohanim commented

Hi mjwesterhof,

Thank you. I think that's definitely an issue: node servers must report that the node is not responding. I'll ask Chris.

With kind regards,
Michel

mkohanim commented

Hi Guys,

This is the response from Chris:
"Sort of, but not one that will show the red exclamation mark. He can add an ‘ERR’ status to his nodedef and he can just update that (just like any other status). The user can then see the communication status and write programs based on it; the only thing they wouldn’t see is the red exclamation."

So, it seems that we can use the ERR status so that it can be used in programs but not exclamation marks next to nodes. This is something we will need to work on.

With kind regards,
Michel