![]() There we go, that is definitely a bug…a strange one (arguably not a result of sloppy coding). ![]() I’m seeing this in my log and the category/sub-category are not set.Ġ1 06/16/18 13:30:10.169 LuaInterface::CallFunction_Startup-1 device 39 function startupMajimusLifx failed :1090: attempt to concatenate local ‘cat’ (a nil value) There are some strange going on’s with the UI lately (after last update), but I have not changed anything…will have to sit down and have a good look. Currently adding them adds the root device (controller) with the same settings as the bulbs… funny the controller getting a dim slider next to it when it doesn’t use it. However registering as a “-1” then it has to be parsed out and “guessed” that it is a bulb or not a bulb as other plugins use the “-1” as well.Įxample the two Hue plugins (mios and AltHue) both register as category 2 as dimmable which makes them immediately usable by external interfaces (dashboards…)Ĭool. A LIFX bulb supports all the standard functions of a dimmable light (category 2) so if it’s registered as a category 2 it’s “auto” controllable. When interfacing with Vera through the web api it reduces the amount of parsing necessary for device control. Can you set the Category for the LIFX bulbs as Category 2 which is the Mios standard for Dimmable.Ĭan you please expand a bit as to the reason for this request? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |