ziocan Posted December 28, 2021 Share Posted December 28, 2021 Hi guys, can someone please explain me why a driver (in this case the Philips HUE Single Lamp White Warmth) wouldn't keep a property across controller restarts? One of the properties for the driver is defined as follows: <property> <name>Turn On Values</name> <type>LIST</type> <items> <item>Startup Values</item> <item>Last Used Values</item> </items> <default>Last Used Values</default> </property> I want to set this property to "Last Used Values" (which by the way should be default) and although I can set it that way, save it and have the driver obey this setting, it is reverted to "Startup Values" if director is restarted, eg. after a controller reboot. Can someone please shed some light about where the properties are persisted and/or how is it possible for a driver to have such a behaviour? I'm really stumped. Thanks in advance, Rick Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 What version of white warmth driver are you using? Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 The one which is available in the online database: Source Online Database Device Type Light (v2) Manufacturer Philips Model Single Lamp White Warmth Name Single Lamp White Warmth - FREE File light_ExtraVeg_Philips_Hue_CT_V3.c4i Creator Control4 Control Method(s) other Certified No Creation Date 5/2/2013 10:30:00 AM Modification Date 11/6/2019 12:20:00 PM Version 832 Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 What bulb are you using it with? Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 White ambience Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Hmm, confirmed here. I didn't notice with my personal system because all of mine have startup values. Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Looks like it was reported in May. I'll put in a comment to see if it gets prioritized. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 where are you seeing this? is this a bug? dunno if this driver is maintained although I see it's distributed by C4 Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 I work for Snap One. It's in a nonpublic bug reporting system. Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Two solutions exist at the moment even though both may not be ideal. 1) Don't reboot the controller. 2)Don't use the 'last used values' config. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 3. patch the driver code What puzzles me is that the "Startup Value" that is shown in the properties does not come from the XML in the driver definition, nor is it set in driver code... I really have no idea where it comes from -- can only think it was originally persisted when I first installed and configured the driver and for some reason it is read back at driver init... Anyway I now patched the driver to override what comes from the persisted property. Thank you for your time, and for checking into this! Rick Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 3) is what needs prioritized. Since the bug has been open since May, my options of 1 and 2 are more likely the permanent solution. Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Be aware that a driver update will likely override the modification. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 2 minutes ago, Dunamivora said: 3) is what needs prioritized. Since the bug has been open since May, my options of 1 and 2 are more likely the permanent solution. Well, I need the bulbs to start with whatever CT they had when turned off, because I am tracking that on a per-room basis, where a keypad button allows the user to select between a number of preset temperatures. I only send a "temperature set" command when the user chooses a new one, not at each switch-on because I have many bulbs and sending that to each of them (in addition to the turn on command) would overload the poor hub. Not to mention the unpleasant visual effect it would have. Thanks Rick -defunct- 1 Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 That is why I use the group drivers. I have 17 color bulbs and stopped using independent bulb drivers because it was way too easy to overload the hub. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 Group drivers are not efficient and do not work well when you have 10+ bulbs in a room. They send way too many commands to the hub. For me what works best is to use one bulb as lead (which receives the brightness and temp commands) and have all the other bulbs track it. Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 The group drivers should send one command. It's why I use them instead of popcorning 17 single bulb drivers. But you can do what works for you. Just thought I'd give a tip as an active user and the person who tested the drivers for a few years. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 IIRC the problem was with the dimmer function, it has terrible performances with 10+ bulbs, whereas tracking the lead bulb performs way better. Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Hmm, has not been my experience. All of my bulbs change together with the one drag of the slider. Quote Link to comment Share on other sites More sharing options...
ziocan Posted December 28, 2021 Author Share Posted December 28, 2021 I use keypads here , so the ramp function, that was a no-go with group driver Quote Link to comment Share on other sites More sharing options...
-defunct- Posted December 28, 2021 Share Posted December 28, 2021 Hmm, that would explain it. I use the apps and touchscreens with the lighting menu and custom buttons. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.