Multiple Lights turn on sometimes fails

[bigjezza]

Hi,
I have an event that triggers from a motion sensor - it sets 2 bulbs white, then powers them on.

Also I have another sensor and another 2 lights in a different room.

Sometimes, I'm talking maybe 1 in 7 times, it will not turn on the second bulb. This doesn't happen with the Lifx app if I play with them there (by tapping the group to turn them on). It happens with both sets of lights though in Homeseer. If I re run the event the light pops on like it should.

It seems the event for yet another light/sensor combo works reliably - this combo has only one light connected.

Strangely it doesn't happen when turning them off.

Does anyone have any ideas?

[Ultrajones]

Hello bigjezza,

I am sorry to hear you are having trouble with my plug-in. My plug-in has a built in retry mechanism if the power command isn't acknowledged by the LIFX LED bulb. Please enable debug, then attempt to duplicate the failure. When you're done testing, disable debug, then inspect the debug log that was put into HomeSeer's root directory. The debug file will contain the command sent to the LFIX LED bulb and the time it took to get a response back. If the command time-out, you'll also see the time-out and the retry. Please let me know what you find in the debug logs.

Regards,
Ultrajones

[bigjezza]

Thanks for getting back to me. I've checked the debug log it is getting replies to command 117 when the light fails to light up.

My router lets me trace with wireshark. As is typical I cant reproduce the problem while trying haha! I'll keep playing...

[bigjezza]

Ultrajones,

For testing I physically killed the power to one bulb - it was completely off at the wall. It cant respond. I ran the event. As expected only one light came on. The debug log lists two commands (102,117) sent to each bulb, and responses received from each bulb for the commands! How can this be with one of the bulbs off!

24/09/2016 8:49:21 PM...Debug~~!~~Waiting for LIFX to respond with '15491' for up to 1 seconds...
24/09/2016 8:49:21 PM...Debug~~!~~Waited 31 milliseconds for the command response 0.
24/09/2016 8:49:21 PM...Debug~~!~~Response received from LIFX command 102 ...
24/09/2016 8:49:21 PM...Debug~~!~~Waiting for LIFX to respond with '26317' for up to 1 seconds...
24/09/2016 8:49:21 PM...Debug~~!~~Waited 31 milliseconds for the command response 0.
24/09/2016 8:49:21 PM...Debug~~!~~Response received from LIFX command 102 ...
24/09/2016 8:49:21 PM...Debug~~!~~Waiting for LIFX to respond with '21498' for up to 1 seconds...
24/09/2016 8:49:21 PM...Debug~~!~~Waited 31 milliseconds for the command response 0.
24/09/2016 8:49:21 PM...Debug~~!~~Response received from LIFX command 117 ...
24/09/2016 8:49:21 PM...Debug~~!~~Waiting for LIFX to respond with '3227' for up to 1 seconds...
24/09/2016 8:49:21 PM...Debug~~!~~Waited 31 milliseconds for the command response 0.
24/09/2016 8:49:21 PM...Debug~~!~~Response received from LIFX command 117 ...

[Ultrajones]

The debug code was wrong. I had the debug statement in the wrong spot. Please update the plug-in and try again.

Regards,
Ultrajones

[bigjezza]

Hmm still getting the response when the bulb is off.

24/09/2016 10:50:06 PM...Debug~~!~~Waiting for LIFX target 186968580649936 to respond to command 102 with '235' for up to 1 seconds ...
24/09/2016 10:50:06 PM...Debug~~!~~The LIFX target 186968580649936 responded to command 102 with '235' in 31 milliseconds.
24/09/2016 10:50:06 PM...Debug~~!~~Waiting for LIFX target 57209028703184 to respond to command 102 with '7286' for up to 1 seconds ...
24/09/2016 10:50:06 PM...Debug~~!~~The LIFX target 57209028703184 responded to command 102 with '7286' in 31 milliseconds.
24/09/2016 10:50:06 PM...Debug~~!~~Waiting for LIFX target 57209028703184 to respond to command 117 with '14948' for up to 1 seconds ...
24/09/2016 10:50:06 PM...Debug~~!~~The LIFX target 57209028703184 responded to command 117 with '14948' in 31 milliseconds.
24/09/2016 10:50:06 PM...Debug~~!~~Waiting for LIFX target 186968580649936 to respond to command 117 with '21121' for up to 1 seconds ...
24/09/2016 10:50:06 PM...Debug~~!~~The LIFX target 186968580649936 responded to command 117 with '21121' in 31 milliseconds.
24/09/2016 10:52:25 PM...Debug~~!~~Waiting for LIFX target 186968580649936 to respond to command 102 with '29048' for up to 1 seconds ...
24/09/2016 10:52:25 PM...Debug~~!~~The LIFX target 186968580649936 responded to command 102 with '29048' in 31 milliseconds.
24/09/2016 10:52:25 PM...Debug~~!~~Waiting for LIFX target 57209028703184 to respond to command 102 with '23863' for up to 1 seconds ...
24/09/2016 10:52:25 PM...Debug~~!~~The LIFX target 57209028703184 responded to command 102 with '23863' in 31 milliseconds.
24/09/2016 10:52:25 PM...Debug~~!~~Waiting for LIFX target 57209028703184 to respond to command 117 with '17197' for up to 1 seconds ...
24/09/2016 10:52:25 PM...Debug~~!~~The LIFX target 57209028703184 responded to command 117 with '17197' in 31 milliseconds.
24/09/2016 10:52:25 PM...Debug~~!~~Waiting for LIFX target 186968580649936 to respond to command 117 with '31784' for up to 1 seconds ...
24/09/2016 10:52:25 PM...Debug~~!~~The LIFX target 186968580649936 responded to command 117 with '31784' in 31 milliseconds.

10:50PM it was off. 10:52 is when I put power back on.

Its not just the event either. Here is me pressing the button on device page with it powered off

24/09/2016 10:56:38 PM...Debug~~!~~Entered SetIOMulti Subroutine
24/09/2016 10:56:38 PM...Debug~~!~~SetIOMulti set value: 0, type Button, ref:385
24/09/2016 10:56:38 PM...Debug~~!~~Waiting for LIFX target 57209028703184 to respond to command 21 with '9466' for up to 1 seconds ...
24/09/2016 10:56:38 PM...Debug~~!~~The LIFX target 57209028703184 responded to command 21 with '9466' in 31 milliseconds.

[Ultrajones]

I see the issue. The plug-in is not ignoring it's own broadcast packet. I need to redesign the plug-in so each bulb gets its own communication socket. If all goes well, I hope to be done within a week or two.

Regards,
Ultrajones

[bigjezza]

You the man!