(04-20-2018, 08:54 AM)Dean Roddey Wrote: [ -> ]The color palette is just writing to the field same as you are. The color field is in HSV format. See the docs for the color palette widget for the form description. I think that the middle value being zero means completely unsaturated, which means basically white. If you wanted, say, full red, you'd do something like:
0 255 255
That's zero degrees, which is where red is, fully saturated, and full level. Try that and see how it does.
OK that is going to confuse me
.
shouldn't it be "0 100 100"
I see "360 255 255" works so that is odd.
Isn't HSV and HSB :   (degrees,percent,percent)
https://alloyui.com/examples/color-picker/hsv
http://colorizer.org/
Typically it's done as a byte each for the H and V, so 0 to 255. It could be anything of course, it's just a range. But I usually see it as a byte value. Z-Wave does it that way, and most painting programs seem to do it that way as well. And my underlying C++ HSV color class does it that way. So that's how it's exposed in the driver.
Of course you can use the color palette to find a color and just write it down, or use the IV editor's color palette to figure out the values for a given color.
It allows you to enter 360, which is the same as 0, since the colors just wrap around from 0 to 360, because they come from a sort of color wheel perspective and so are expressed in degrees around a circle.
Or, more specifically, because it's almost always done that way, the V2 CLGHT device class defines it that way, and hence the Z-Wave driver does it that way. The SetComp field, since it's not defined in any particular way out the in world, is just 0 to 100. So you can write "Red 50" to the set component field to set that one component to half intensity.
OK thanks.  I can deal knowing it is 360,255,255  Just wish there was a standard for percent on the web
.
Color picker makes it hard to pick the truest single color but it does work.
Reference for True colors values for Z-wave/Fibaro RGBW:
Red 0 255 255
Green 120 255 255
Blue 240 255 255
Cyan 180 255 255
Magenta 352 255 255       
Orange 24 255 255
Purple 280 255 255
Yellow 60 255 255
White 0 0 255
Yeh, RGB colors are going to be at 120 degree intervals from 0. Complementary colors will be at the 60 degree values between those basically.
I have a roughly functional IV widget palette now. Still some work to do, and it was a good bit of effort to implement the general purpose publish/subscribe stuff, but dang is that a lot easier now. I'm sure I'll find something where I'm failing to catch some change before it's ready to go. But the opportunities for such issues are vastly smaller than in the 4.x version of the widget palette.
It's a little painful because it required changes in one of the collection classes to add pub/sub support to it. That's a templatized class and visible to everything. So any changes means full rebuild time. I try to minimize that with unit tests of course, but they never catch everything.
Just checking to see if anyone has had the same symptoms with the new Z-wave driver(stick).
Seems after a day or two I have to remove and re-insert the new  zwave stick. Driver says it is ready but "???" in zwave devices status fields. I only have a couple test devices but will keep testing to see if I can reproduce the issue.
Today I just tried to pause driver and resume instead of removing/replacing the stick. After driver pause/resume it is now stuck in "Wait for commresources".(see log attached) could not get it to come back online. Once I stopped and started the CQC services from the tray monitor the Z-wave driver came back online but all devices stuck in "WaitApprove" on the driver client screen and missing from the driver screen.
Will look at it again tomorrow. 
Thanks
Kevin
Hmmm... It's like it couldn't re-open the serial port. Let me take a look at it. In the meantime, once you get it happy again, note the memory usage of CQCServer.exe on that machine. The next day, check it again to see if it's perhaps gotten really big or something. It doesn't seem too likely given that the rate of messages isn't high and they aren't large, but worth checking that on a working system in the field.
I've been continuing to work on the new widget palette, and using it as a test case to refine the publish/subscribe stuff, and also working out the issues that inevitably arose wrt to making sure the right messages are being sent and such. It has to always stay in sync with the editor window so nothing can be missing or done wrong.
I've got it correctly tracking the widgets and their selection state (marking the ones that are selected), and enabling/disabling its buttons based on what is selected. Now I need to work it the other way, so that the up/down and delete buttons on the widget palette send the correct msgs to the editor to make it do those things. At that point, plus some more testing, that should be good enough for round one of the widget palette.
I've not been doing anything with the Z-Wave driver since, other looking at bugs such as the above, the only thing left for this first version is getting more device support in place, but I guess I have all of the units that the folks currently playing around with the driver have so far.
Dean can you try to reproduce this with new z-wave Z-stick driver:
If I have the Driver client window and driver window open. Then you pause z-stick. You get a pop up every 3 seconds. Almost impossible to resume the driver.
In client interface screen. If I rename the unit and restart the driver the name goes back to the default. also not sure how the driver picks up this name after rename. I can re-do my templates if we need to stick with the default names (Unit_4). If the renaming will be problematic.