Lifx no response issues


(Cory S) #1

I just connected my Lifx bulbs, and I got to say it’s hardly serviceable. Sometimes it takes 6-7 tries to get them to change state. The Lifx app however works every single time immediately, even with WiFi on the phone turned off (forcing it to use the cloud) I also don’t have any issues with Google home commands to Lifx.


(F5snopro) #2

I had the same issues here. Liked the bulbs when they worked, but they’re totally unreliable. Gave up and replaced them with Sylvania Lightify. Haven’t looked back.


(Cory S) #3

Here is some stuff from the logs showing it fail.

xxxc5ee-6c8b-4815-axx6-4f8xxx92bca 3:27:05 PM: debug LIFX – Cory’s Lamp – Response [[product:[company:LIFX, name:LIFX A19, capabilities:[max_kelvin:9000, has_multizone:false, has_variable_color_temp:true, min_kelvin:2500, has_chain:false, has_ir:false, has_color:true], identifier:lifx_a19], brightness:1, id:d073d522b634, location:[id:a6665adbf01ecc9254ebe74bdece945c, name:My Home], color:[saturation:0, kelvin:3500, hue:0], connected:true, power:on, label:Cory’s Lamp, uuid:02e5fd79-2173-4a30-abdd-7e7c755d8fdd, last_seen:2018-02-17T21:27:05Z, group:[id:6ac229a6ab529c8939cd521682ba7ae7, name:Bedroom], seconds_since_seen:0]]
5c5bc5ee-6c8b-4815-ac16-4f8ef3592bca 3:27:05 PM: debug LIFX – Cory’s Lamp – Response received from LFIX in the GetReponseHandler.
5c5bc5ee-6c8b-4815-ac16-4f8ef3592bca 3:27:05 PM: info LIFX – Cory’s Lamp – Beginning device update…
5c5bc5ee-6c8b-4815-ac16-4f8ef3592bca 3:26:46 PM: error LIFX – Cory’s Lamp – Error = {*
“error”: “Too many requests. Try again later.”
}
5c5bc5ee-6c8b-4815-ac16-4f8ef3592bca 3:26:46 PM: error LIFX – Cory’s Lamp – LIFX failed to adjust group. LIFX returned 429.
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: debug off()
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace stopAction()
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace stopAction()
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace ambientLightOK = true
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace timeOk = true
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace timeWindowStop = null
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace timeWindowStart = null
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace daysOk = true
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace modeOk = true
ce0d5717-c0ad-44db-860d-a59e84b01da7 3:26:45 PM: trace buttonHandler(button: pushed, [buttonNumber:1])
5c5bc5ee-6c8b-4815-ac16-4f8ef3592bca 3:26:45 PM: info LIFX – Cory’s Lamp – Turning bulb off.
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace ambientLightOK = true
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace timeOk = true
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace timeWindowStop = null
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace timeWindowStart = null
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace daysOk = true
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace modeOk = true
bdfa2d4a-4c3b-4bb2-8ba7-52ca330ee4fe 3:26:45 PM: trace buttonHandler(button: pushed, [buttonNumber:1])
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace ambientLightOK = true
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace timeOk = true
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace timeWindowStop = null
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace timeWindowStart = null
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace daysOk = true
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace modeOk = true
e36f4bce-4f3d-430b-a346-9fffa910c72e 3:26:45 PM: trace buttonHandler(button: pushed, [buttonNumber:1])
38d81195-f75d-4bad-b302-4705ac7b9124 3:26:45 PM: debug Parse returned [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Cory’s Switch button 1 was pushed, isStateChange:true, displayed:true, linkText:Cory’s Switch]
38d81195-f75d-4bad-b302-4705ac7b9124 3:26:45 PM: debug description is catchall: 0104 0006 01 01 0140 00 5EDD 01 00 0000 01 00


(Eric) #4

cool - I never dug deeply into my LIFX failures - thanks. Even the error message looks like an error. Maybe LIFX is choking on volume.

You think “Beginning device update…” means its firmware? I noticed that my some of my bulb updates did not clearly indicate success.

Looks like Sylvania Lightify is cheaper too.


(Cory S) #5

I am not interested in Lightify bulbs, they aren’t bright enough for my application and their color accuracy isn’t as good. Not to mention, I have Lifx bulbs, and as a rule I no longer buy anything that is completely dependant on a ST hub.

The error indicates ST is hitting the API limit of 120 requests per minute from Lifx. My theory is ST is flooding Lifx with requests through some programming error. My other Lifx integrations continue to work fine.


(Michael) #6

I have 22 Lifx bulbs currently and i dont have an issue. I’ve been using this DH for them and it works flawlessly.


(Cory S) #7

I am actually using that same DH on one of the bulbs as a test, and getting the same “429 too many requests” as soon as the first command I try to send.


(Michael) #8

Interesting. I checked my logs as well and have it pop up randomly. Only on certain bulbs though.

@whoismoses
Think you could possibly help us out here?


(Cory S) #9

Well, with as many bulbs as you have you may be occasionally legititmately hitting the API limit. I only have two bulbs and get the error totally randomly…including when I haven’t attempted to use it for hours. Of course, ST is doing its own polling which is using up API requests…but as far as I can see in the logs that isn’t anywhere close to the limit. If ST supported local LAN control for Lifx…this wouldn’t be an issue.


(Cory S) #10

I have a hilariously over engineered work around for this…I setup a simulated switch, which my physical smart button flips. The Simulated switch toggles Lifx on or off through IFTTT. So It’s Physical Zigbee Button>Simulated ST Switch>IFTTT>Lifx API. The Simulated switch is needed because IFTTT can’t see my physical smart buttons.

This works, but has a delay that isn’t ideal. It is also prone to failure with so many services involved. I had almost forgot how much…fun SmartThings was.


(Cory S) #11

So, I am not sure what has changed, but currently the Lifx integration is working as intended in SmartThings. I can spam refresh status the bulbs and only get the 429 error when I actually hit the 120 request per minute limit. I’ll continue monitoring, it may just be a fluke.

Edit: Scratch that, back to 50% success rate…

Ironically, as that started working, the two zigbee buttons I purchased to control the lights now take minutes to register a button press.


(Michael) #12

Hahaha.
I’m laughing with you. Not at you.

I used ifttt before I got so deep into ST. It’s never been consistent or quick for me. If you have them setup through ST then ifttt should be able to see them… I only use it now if I absolutely have to. What buttons are you using if you don’t mind me asking. Been thinking of getting a couple to play around with.


(Cory S) #13

Haha I’m entering that phase now too. Im using the lightifiy zigbee switches. ST sees them as two button, buttons.

They worked great the first few days, instantly registering presses. But now they don’t register at all most the time for minutes if ever.

Lifx seems to be “acceptable” working 9/10 times. Now if only the switches worked…
Which was the whole point of controlling the bulbs through ST in the first place.


(Michael) #14

Should have mentioned this earlier. Not sure what kind of router you’re using. But Lifx bulbs are VERY picky when it comes to routers. At least in my experience.


(Cory S) #15

Yeah, I’ve seen reports of that. This isn’t a local network issue though. The bulbs work great with the lifx app, and the error is from outside the network anyway.

Zigbee switches seem to be working better after a few hub reboots, but now the bulbs are back to 429 error every third toggle :laughing:


(Michael) #17

Has everything seemed to smooth out? Or are you still getting errors?


(Cory S) #18

Looks like Lifx thinks it’s an issue with the entire SmartThings integration. They are seeing abnormal traffic in general. They are reaching how to ST to troubleshoot.


(Cory S) #19

SmartThings fixed the issue on the backend. All is good now. Luckily Lifx support was quick to identify the problem and contact ST. I wasn’t able to get past the “turn it off and on again” stage with my own efforts in working with them.


(Michael) #20

Good to hear! Lifx has epic customer service.