Lifx light has big delay with motion sensor

#1

1) Give a description of the problem
From motion detected to light on is very slow

2) What is the expected behavior?
Turn on quick

3) What is happening/not happening?
So more just wanting to see what other peoples times are with Lifx lights? I have zigbee motion sensors and with Seglend light it will complete basic motion active turn light on piston in 234ms however with these new lifx lights and same piston design it is taking upwards of 2865ms .

This just way they are? or is something else going on here?

#2

Someone please correct me if I am wrong, but I believe Lifx bulbs communicate thru WiFi.
(not Zigbee or Zwave)

With WiFi devices, there are lots of reasons you may have delays…

  • Distance from modem
  • Modem may be using a ‘noisy’ channel
  • Refrigerator or other appliance may be blocking the signal
  • Extensive downloading from another device (bittorrent, video streaming etc)
  • Poorly coded pistons (this one applies to ALL devices)

Possible solutions:

  • Re-position things to get a better signal from modem to bulb
  • In your modem, change the WiFi channel to a ‘quieter’ one.
  • Some modems also let you prioritize traffic for certain IPs/MAC addresses.
  • Tweak pistons related to the motion sensor and the bulb

Personal note:
I tend to avoid buying WiFi bulbs so my modem does not get cluttered with the number of connected devices.

#3

Yeah the are Wifi, just odd how other brand wifi lights are a lot faster and as far as I can tell it is getting hung up on Hubitat somewhere

   9/8/2018, 10:48:31 AM +819ms
    +1ms ╔Received event [Master Bedroom Closet Motion Sensor].motion = active with a delay of 1366ms
    +105ms ║RunTime Analysis CS > 60ms > PS > 28ms > PE > 16ms > CE
    +118ms ║Runtime (45900 bytes) successfully initialized in 28ms (v0.3.107.20180806) (115ms)
    +120ms ║╔Execution stage started
    +125ms ║║Comparison (enum) active changes_to (string) active = true (1ms)
    +126ms ║║Cancelling condition #2's schedules...
    +127ms ║║Condition #2 evaluated true (5ms)
    +128ms ║║Cancelling condition #1's schedules...
    +130ms ║║Condition group #1 evaluated true (state changed) (7ms)
    +131ms ║║Cancelling statement #3's schedules...
    +2486ms ║║Executed physical command [Bathroom Light].on() (2350ms)
    +2487ms ║║Executed [Bathroom Light].on (2351ms)
    +5361ms ║║Executed physical command [Bedroom Lights].on() (2868ms)
    +5363ms ║║Executed [Bedroom Lights].on (2871ms)
    +5366ms ║╚Execution stage complete. (5247ms)
    +5415ms ╚Event processed successfully (5415ms)
#4

It’s even longer on some other lights (right next to these ones)

 9/8/2018, 9:02:47 PM +536ms
+0ms ╔Received event [Master Bathroom Motion Sensor].motion = inactive with a delay of 181ms
+105ms ║RunTime Analysis CS > 57ms > PS > 29ms > PE > 20ms > CE
+124ms ║Runtime (48181 bytes) successfully initialized in 29ms (v0.3.107.20180806) (122ms)
+127ms ║╔Execution stage started
+136ms ║║Comparison (enum) inactive changes_to (string) active = false (1ms)
+141ms ║║Cancelling condition #2's schedules...
+144ms ║║Condition #2 evaluated false (10ms)
+147ms ║║Condition group #1 evaluated false (state did not change) (13ms)
+208ms ║║Comparison (time) 75767687 is_between (time) 1536401040000 .. (time) 79140000 = true (7ms)
+211ms ║║Time restriction check passed
+214ms ║║Condition #9 evaluated true (64ms)
+218ms ║║Condition group #8 evaluated true (state did not change) (67ms)
+222ms ║║Cancelling statement #10's schedules...
+6712ms ║║Executed physical command [Bathroom Light].setColor([[hex: #F3F6F7, hue:52, saturation:19, level:96]]) (6476ms)
+6715ms ║║Executed [Bathroom Light].setColor (6480ms)
+10594ms ║║Executed physical command [Bathroom Light].setLevel([100]) (3851ms)
+10597ms ║║Executed [Bathroom Light].setLevel (3854ms)
+10616ms ║║Skipped execution of physical command [Bathroom Light].on([]) because it would make no change to the device. (7ms)
+10621ms ║║Executed [Bathroom Light].on (14ms)
+10626ms ║║Comparison (enum) inactive is (string) inactive = true (1ms)
+10628ms ║║Cancelling condition #15's schedules...
+10630ms ║║Condition #15 evaluated true (5ms)
+10631ms ║║Cancelling condition #14's schedules...
+10633ms ║║Condition group #14 evaluated true (state changed) (9ms)
+10635ms ║║Cancelling statement #16's schedules...
+12803ms ║║Executed physical command [Bathroom Light].off() (2162ms)
+12806ms ║║Executed [Bathroom Light].off (2166ms)
+12812ms ║╚Execution stage complete. (12684ms)
+12831ms ╚Event processed successfully (12830ms)