Light Status Graphics Settings

[w.vuyk]

I just checked on the RGB feature update on my system. The color change is calculated on the polling frequency of the Philips Hue bridge (normally once per few seconds) or on the deCONZ polling frequency (once per 90 seconds). I can see if I can update the frequency of the deCONZ lights as these are send through the webhook. For Philips I can update this in the near future when the APIV2 update is implemented which is not using a webhook but a notification once per second if needed. (working on this as we speak).

Wim

[lakehawk]

Hi Wim,
I’ve been sorting a lot of this out. One thing that has me confused and hopefully you can tell me if it’s something I’m not doing right or is there a problem somewhere. I notice if I change the dim level of a light from my app that Jowihue quickly has the light dim or brighten accordingly. If I’m watching the device on the HS web interface I see it update the dim level on the web page within the time of what I’ve set the polling parameter for Jowihue to poll the Hue bridge.

But if I send a color change to Jowihue on either HS 3 or HS 4 that it can be several minutes before we see an update to the web interface. Why is there such a difference between seeing an update for a dim level and seeing an actual color change status to show up?

Is there some setting or something I’m doing that causes this? I would have thought that when Jowihue sent a color change to the bridge that it would get back a success for that call, and then immediately tell HS the new state of the feature for the device.

Regards,
Dan

[w.vuyk]

There is no reason why a command send through an event, a json/txt command or an action on the device page would differ. All commands are handled the same way. I double checked here with my Philips Hue bride lights, all respond fine within 7 seconds (my polling frequency) with an update. I tested the Hue and the sat commands here and on HS4 the RGB device. I did not test the JSON/txt part, but cannot imagine it would differ? If the light responds on your commands in a responsive manner through the plugin, the update of HS devices walks the same path as any other command.

If the plugin sends a command, the new setting will return on the next polling cycle. So I do not have an idea where this could differ with other methods?

[lakehawk]

Hi Wim,
I don't understand this either.. as I said we see dim commands and changes on Hue or Sat almost immediately. It's when we make a change to the RGB that it sometimes can take minutes before we see an update appear on the web screen for HS. On HS3 web page we usually see the color picker displaying the wrong color on that web page from what was set on the device. But I'm focused mostly on trying to get the HS4 to be correct... but I have a lot of people who are adamant about staying on HS3. So like you I have to run multiple systems trying to keep up with everyones wants and needs.

When I make a call to the plug in on HS4 to do a color change I see the log reflect that a CAPI control was issued for RGB... and immediately after that I see the brightness request also processed. Right now since changing the color results in a dim level change we make the two calls... one to change the color and the second to restore the dim level to what it was set at. This gets me around the issue where the dim level was being reset with a color change.

I would have expected that when it see's the call to make the change that it should update the interface then or very shortly afterwards.. I've had it take up to 10 minutes to make a change on the web page for RGB change.

One thing I find troubling at times is that I'll see a status on a light that says "unreachable"... yet I can make a on / off or even color change on the light when it's showing that state and they work. I assume you get the "unreachable" state from the Hue bridge. I have to wonder what their criteria is for determining a light is "unreachable". Is this a polling on their part of individual lights?

Thanks,
Dan

[w.vuyk]

brientim Tim,

Statuses for lights are updated (you need to reset the status graphics - either on the JowiHue tab or through the settings)

lakehawk Dan,

Dim values should not change anymore with the no dim setting now and using a RGB command.

And more changes:

https://forums.homeseer.com/forum/hs...-for-hs4/page3

[brientim]

brientim Tim,

Statuses for lights are updated (you need to reset the status graphics - either on the JowiHue tab or through the settings)

lakehawk Dan,

Dim values should not change anymore with the no dim setting now and using a RGB command.

And more changes:

https://forums.homeseer.com/forum/hs...-for-hs4/page3

Wim,

Thank you for the update and effort.

Tim

[lakehawk]

Wim,
Yes thank you. These are all great changes. Have you given any thought to implementing the V2 event stream to get rid of polling? I wrote a small program to subscribe to the even steam and it looks really good... all the messages that come across also include the V1 id for each light or sensor. So with that it should be possible to make that the first thing implemented from V2 API and improve performance a great deal.

Thank you for your efforts.

Dan