That sure looks like some bug in the Hub. There's only a couple relevant lines in the log:
- Code: Select all
LIFX Bridge Debug LightSetPower command is for device: under walkway, payload = [('Power', 65535), ('Duration', 1000)]
'LightSetPower' is the command to turn an LIFX device on/off. 65535 is on, 0 is off.
- Code: Select all
LIFX Bridge Debug LightSetColor command is for device: under walkway, payload = [('Color', (18432, 33343, 49920, 47969)), ('Duration', 256011)]
'LightSetColor' is the command to set the hue/saturation/brightness of a light. The third number is the brightness, which is what I use to map to dimmer values for Indigo. In this case, it's 49920, which is 49920/65535 * 100 = 76% on the dimmer:
- Code: Select all
Sent INSTEON "under walkway" on to 76
Later on, I get a command to set it to 0 brightness:
- Code: Select all
LIFX Bridge Debug LightSetColor command is for device: under walkway, payload = [('Color', (18432, 33343, 0, 47872)), ('Duration', 256011)]
.
.
Sent INSTEON "under walkway" on to 0
So as far as I can tell, the plugin is doing exactly what the Hub is asking for.
What I don't see anywhere is the Hub doing a "LightGetColor", which I would expect if it was trying to find out what the current brightness of the light is. It's possible I'm doing something in one of the response messages that's confusing the hub. I have an LIFX bulb I bought just to develop this plugin. I guess I could install it somewhere (again) and see if I can spot something in the traffic to it.