Light Status Graphics Settings

[brientim]

Hi Wim.

Currently the Slider Control has a range 1 to 100 whereby, 100 "fully dimmed" and 255 is On and this has been reflected in the Status Graphics. However, if you set the light to on, this will effectively result in the light be presented as Dim 100%.

It is my belief the the Status Graphics should be changed to reflect as displayed below.

Modify "0" (Zero) and add Status of "Off"
Range 1 - 99 and the prefix "Dim" be removed as the percentage in the range displays that it is dimmed.
Add new Single Value "100" and add Status of "On"
Modify "255" and add Status of "On" If desired for consistency

[George]

Hi Wim.

Currently the Slider Control has a range 1 to 100 whereby, 100 "fully dimmed" and 255 is On and this has been reflected in the Status Graphics. However, if you set the light to on, this will effectively result in the light be presented as Dim 100%.

It is my belief the the Status Graphics should be changed to reflect as displayed below.

Modify "0" (Zero) and add Status of "Off"
Range 1 - 99 and the prefix "Dim" be removed as the percentage in the range displays that it is dimmed.
Add new Single Value "100" and add Status of "On"
Modify "255" and add Status of "On" If desired for consistency

G'Day Mate! You sober yet?

Get back to breaking stuff! LOL

Hoo Roo,
George

[brientim]

Hey George,

Will do and I have been very good at achieving that goal.

Happy New Year mate.

Tim

[w.vuyk]

Hi Wim.

Currently the Slider Control has a range 1 to 100 whereby, 100 "fully dimmed" and 255 is On and this has been reflected in the Status Graphics. However, if you set the light to on, this will effectively result in the light be presented as Dim 100%.

It is my belief the the Status Graphics should be changed to reflect as displayed below.

Modify "0" (Zero) and add Status of "Off"
Range 1 - 99 and the prefix "Dim" be removed as the percentage in the range displays that it is dimmed.
Add new Single Value "100" and add Status of "On"
Modify "255" and add Status of "On" If desired for consistency

Tim,

Your suggestion is a good one, I will check how I could try to implement it. The challenge at this point is that many users have their events set (on devicevalues) and me changing those values might break events. Will let this sink in and work on it. Removing the Dim remark is a no brainer, so that part will be in the next version. The rest will be later.

Happy New Year

Wim

[brientim]

Tim,

Your suggestion is a good one, I will check how I could try to implement it. The challenge at this point is that many users have their events set (on devicevalues) and me changing those values might break events. Will let this sink in and work on it. Removing the Dim remark is a no brainer, so that part will be in the next version. The rest will be later.

Happy New Year

Wim

Hi Win,

Happy New Year and I hope you enjoyed the break...

WRT "The challenge at this point is that many users have their events set (on devicevalues)" This should not be impacted as that is the maintained in the Controls and that does not require any changes and the only changes are to the Status Graphics.

Current




Proposed Change to Status Graphics Only



Regards
Tim

[brientim]

Hello Wim,

Whilst you are looking at this, can you please "Hue" colour feature Control Use for coloured lights.
in testing the ZHome Plus app we noticed that when we set this Colour Control that the light would dim in % to the Colour selected on the slider.
This behaviour was previously raised by @lawkhawk, Dan the ZHome Plus developer in this thread
https://forums.homeseer.com/forum/hs...eature-control

On subsequent review, I noticed that the Control Use for the Feature is set to Dim whereby, I believe this should be set to ColorControl.
This would need to be changed for both individual lights and Group features.

Thanks in advance

Tim


Current Control Use


Proposed Change

[brientim]

Wim,

The next one is the RGB colour selector, when used it will override the light dim setting and either set to !% and/or subsequently send a second command to turn off the light.
Dan was intending to use this function in his app; however, this is currently not feasible due to the behaviour currently being observed.

https://www.youtube.com/watch?v=dkIi9oybT4o

Regards
Tim

[George]

Thanks for posting this, Tim

I know that this is one of the last few punch list items that Dan is holding up releasing the new 5.1 update for Z-Home+.

We've beat the code to death, as Dan can attest to with his lack of sleep and missing football games (sorry Dan). This would be great to take care of and add full Zigbee JowiHue support to the app. I'm getting myself into Zigbee and would be great if people can use this new support along with the other great features.

Cheers,
g

[lakehawk]

Wim,
The RGB selector feature is the one I would really like to use... but as Tim's video shows... whenever I set the color of the light using the controldevicebyindex JSON api then I end up with the light changing the brightness... usually down close to 0... when it was set at 100% before I request the color change. I have been working with Tim and have a new interface for devices controlled by your plug in and was hoping to present just a color wheel to the user... To me trying to explain to the layperson that you have to adjust the three controls of hue, saturation, and color temp, in order to produce the color they want is rather obtuse. It's like this 3 lever machine that you have to adjust all 3 levers at the same time to produce a color you want... and you only have two hands... where presenting them a color wheel and letting them just select that color and everything is set up would be great.

I did try a hack where I would send the plug in the color hex string ... save the dim level that the light was at before I sent the color string... and then when I got a response back that the color was changed I would then submit back a request to take the dim level back to what it was... but with the lag between a request and how HST reports back to the app on when JowiHue has made a change... well it's just seemed a little heavy overall in performance to me.

If it's possible to get the plug in to not change the dimming level when requested to change the color via the hex string then that would be great. I could revisit using an actual color wheel not unlike what the latest Philips Hue App does now... They vastly improved their app in the past few months. I would like to be able to improve mine as well.

Thanks for your time and work. We all appreciate it.

Dan

[w.vuyk]

Hello Wim,

Whilst you are looking at this, can you please "Hue" colour feature Control Use for coloured lights.
in testing the ZHome Plus app we noticed that when we set this Colour Control that the light would dim in % to the Colour selected on the slider.
This behaviour was previously raised by @lawkhawk, Dan the ZHome Plus developer in this thread
https://forums.homeseer.com/forum/hs...eature-control

On subsequent review, I noticed that the Control Use for the Feature is set to Dim whereby, I believe this should be set to ColorControl.
This would need to be changed for both individual lights and Group features.

Thanks in advance

Tim

Tim and Dan,

The Control Use is not to be set on the Hue control as it is set on the RGB feature, this feature is the logical feature to hold the colorcontrol. The Hue device is not the logical place for this.

Also, as I tried to explain in the thread with Dan, the plugin does a conversion to the requested color through the RGB feature's color control wheel's result (which is a hex color setting) To reach the requested color all formula's used for this include setting the brightness. Not using the brightness will at the end not set the light in the requested color, but most of the time in a brighter/whiter version of that color.
It does not mean I do not understand what you want, that is why that option for not dimming on voice control is in the settings. I can check on this option why it does not respond as I expected (on any color hex command). I feel the plugin should basically work with the correct values (and thus dim or brighten lights if needed). I will check the option present in the settings and expand it to a general setting, so if a user wants to ignore the dim level for hex colors, it can be disabled.

I hope this would suffice for you both?

One challenge though, I am at this point choking in my time, at first there was the APIV2 changes for deCONZ and now also the Philips Hue APIV2 is comming available, so I am very occupied at the moment with these changes. And I still have changes waiting for the lock (I did not forget Tim )... so I am afraid it will take time before I can show a result...

Wim

[lakehawk]

Wim,
Yes I believe that would give me the functionality I'm looking for. I understand what you are saying about the mapping of a color including the brightness... but even Philips isn't staying true to that... if you go into their color wheel and change the color they do not factor in and change the brightness. I think this is what most users expectations are... change the color, not the brightness.

I understand completely all the API changes... I'm currently spending a lot of my time trying to learn and adopt a lot of the new iOS SDK API's as well that I believe will bring some real improvements.

Best regards,
Dan

[brientim]

Hello Guys,

Wim thank you for the detailed response and I appreciate the answer to Hue is not the correct place to set Color Control and this is best configured and controlled from the RGB feature.

[lakehawk]

Wim,
One question about the RGB control for the plug in on HS3. I can send a color hex string to the hue reference ID on HS3 using the controldevicebyIndex JSON api and I can get the light to change color .... and of course on HS4 there is a feature for this .... the color picker shows up on HS3 web interface for the hue "feature" for the light... and you can set color with it... but how do I get the hex string for the color of a light under HS3? I'm not sure how I get the hex string for the light on HS3. The web interface is showing the hex value for the color on HS3.. how is this value constructed?

Thank you,
Dan

[w.vuyk]

The hex string is the same as the RGB color, but transferred to its hex value per two bytes (red being #FF0000 / 255,0,0).

But I think I got confused somewhere here. I assumed you were talking about HS4 here as indeed the HS4 device has a RGB device, where HS3 has not. In the HS3 version of the plugin there is not yet a routing that converts the actual values of Hue/Sat (or x,y) and brightness to the RGB value, the HS4 version has this calculation. This is one of the many differences between both plugins that have grown over the past year and a half. So there is not a standard way to "get" the RGB value from a HS3 device, as it is only letting this value be set. Not sure if we can get this done, other then using HS4 devices.

[lakehawk]

Wim,
I just noticed on the Hue feature in HS3 that on the web page there is a color picker..... so I figured somewhere there must be some calculations going on. I'm trying to get this to work for both HS3 and HS4. One issue I'm having and see on the web page... is that when a light has its color changed that its not showing up on the web page at all... Sometimes a long, long time from now I may see some updates on HS4... but it's rare. I would think that when the color changes that it would push those out to HS4... I call to get the status on a light after a color change ... and it continues to show the old RGB value on HS4.

I don't think you are alone in confusion.. LOL. I'm starting to feel like I'm chasing my tail. It just shouldn't be this hard to change a color and then how that it changed.

Thanks,
Dan