@joel_dj reset of what? Hubitat or the light?
Hubitat
I did find something while playing - any time you update the settings the version you have will fire off another runEvery1Minute() call (in fact the same applies whenever the device is initialised). However it wasn't clearing the existing runEvery1Minute() call, so playing with settings a lot could eventually cause a huge slowdown.
1 Like
That ive been doing. So a reset clears that if you've finished playing with settings ?
Yes, although the next version will do the right thing and unschedules the runEvery1Minute() calls for polling. I may also add a setting to control the polling frequency, which may be more important for those with very large numbers of bulbs. I was also wondering about and option to disable polling for those who don't every use the LIFX app to modify the settings, however, in the case of a power cut or someone turning a bulb off that may not be a good idea
1 Like
Hi Rob and all,
Here is my Monday morning log with no LIFX coding installed on HE:
Up to now I have been having those red ERROR flags, but without using the coding, I have a normal log (no warnings, no errors)
I am using my LIFX bulbs by integrating LIFX and HE into IFTTT.
So, using cloud access and experiencing cloud latency. But at least I am not soft resetting HE every Monday morning.
The red box highlights the log in the time frame of 2 AM Monday morning when the error flags would start.
Weird - I'm sure you've mentioned it before, but how many LIFX devices do you have?
19 total, 17 color bulbs (12 minis and 5 BR30s non-infra-red) plus two z-strips.
Just realized I highlighted midnight instead of 2 am, but you can still see no red error flags in log.
I picked up a Hubitat a few days ago and it's been great! Much better than ST. I had this Lifx integration working perfectly and hooked up to my Lutron Pico remotes which is a big reason I bought Hubitat to begin with.
Unfortunately now I am getting the same problem as darrall with illegal argument exception null line xx errors for every poll or command sent to a lifx device. I don't know exactly what time it started but I can't seem to fix it without rolling back to an earlier backup.
Can you change the poll method of e.g. the LIFX Color driver to
def poll() {
logDebug "Parent is $parent, device is $device"
parent.lifxQuery(device, 'LIGHT.GET_STATE') { List buffer -> sendPacket buffer }
}
And see what shows up in the log - I suspect that it's device that's null which I really can't explain, but it would be good to be sure
Hello, The only errors that I have received are just 2 days ago.
dev:62019-10-03 04:33:29.136 pm warnError occured with UDP message: SocketTimeoutException: Receive timed out
dev:62019-10-03 04:29:29.122 pm warnError occured with UDP message: SocketTimeoutException: Receive timed out
dev:62019-10-03 02:18:29.131 pm warnError occured with UDP message: SocketTimeoutException: Receive timed out
Hi QuantumHome,
Thanks for sharing your log here. Glad to have a shared experience that hopefully we’ll help contribute a solution to.
I noticed that your log shows heavy errors on 9/23, which is a Monday. I wonder if your problem starts Monday mornings at 2 am as well?
Rob’s suggestion to make a change in the app heartens me to try reloading his LIFX app for further investigation. Thanks again!
That means that no response was received from that device - I think it occurs about 30 seconds or so after polling. Not sure what could cause it, especially on a single device as in this case. If you were seeing that every minute then it would mean that the device wasn't powered, but that's clearly not the case.
Hi Rob,
Saw this and was curious if you know where in the firewall his problem was (in general) so I can look at mine?
Wondering if you worked offline with Danny or if he figure it out himself.
Thanks!
Darrall
I didn't work with Danny on this - for some reason I don't seem to be getting notifications from my github account
Hi - I recently upgraded Hubitat to 2.16 and once again tried creating a group for my 7 overhead Lifx bulbs to be controlled by a pico. The new group is so much faster - not sure if it was the upgrade, new group changes or what. But it used to be that it might be 30 seconds while each light went on, or changed. I noticed it seems like button controller isn't active anymore, so I moved one of my picos for these bulbs to a rule machine rule. For button 2/4 I have raise and lower for the lifx bulbs - but I'm getting an error. Perhaps my rule is wrong, I just have raise and the Lifx group selected. Anyone have suggestions on raise/lower for a Pico and Lifx?
Here is what I'm getting:
Also here is the rule:
Have you upgraded to the latest version of my LIFX drivers (as of yesterday/today)?
They're the first version to support startLevelChange/stopLevelChange. If you have already upgraded then can you try with a single device rather than a group and see how that goes.
Just discovered the update. Just tried setting with all of the bulbs together not in a group, no error messages but it doesn't seem to raise or lower. The on, off, and color changes are definitely so much faster than a few months ago!!
app:4182019-11-03 07:02:05.066 am infoAction: Start raising: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:02:05.000 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 2
dev:22019-11-03 07:02:04.846 am infoKitchen Pico Side Entry button 2 was pushed
dev:12019-11-03 07:02:04.790 am inforcvd: DEVICE,2,5,4
dev:12019-11-03 07:02:04.577 am inforcvd: DEVICE,2,5,3
app:4182019-11-03 07:02:02.796 am infoAction: Start raising: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:02:02.746 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 2
dev:22019-11-03 07:02:02.594 am infoKitchen Pico Side Entry button 2 was pushed
dev:12019-11-03 07:02:02.549 am inforcvd: DEVICE,2,5,4
dev:12019-11-03 07:02:02.249 am inforcvd: DEVICE,2,5,3
dev:9932019-11-03 07:02:01.918 am infoKitchenOverhead level was set to 50%
dev:9932019-11-03 07:02:01.911 am infoKitchenOverhead switch was turned on
dev:9932019-11-03 07:02:00.654 am infoKitchenOverhead colorName is Incandescent
dev:9932019-11-03 07:02:00.651 am infoKitchenOverhead colorTemperature was set to 2500
dev:9932019-11-03 07:02:00.619 am infoKitchenOverhead switch was turned on
app:4172019-11-03 07:02:00.571 am errorjava.lang.NumberFormatException: For input string: "0.0" on line 150 (indicatorHandler)
dev:9232019-11-03 07:01:59.143 am warnError occured with UDP message: SocketTimeoutException: Receive timed out
app:4182019-11-03 07:01:59.066 am infoAction: Color Temperature: KitchenOverhead: 2500: 50
app:4182019-11-03 07:01:59.027 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 1
dev:22019-11-03 07:01:58.881 am infoKitchen Pico Side Entry button 1 was pushed
dev:12019-11-03 07:01:58.827 am inforcvd: DEVICE,2,2,4
dev:12019-11-03 07:01:58.585 am inforcvd: DEVICE,2,2,3
dev:9742019-11-03 07:01:56.148 am warnError occured with UDP message: SocketTimeoutException: Receive timed out
dev:9932019-11-03 07:01:55.219 am infoKitchenOverhead level was set to 0%
dev:9932019-11-03 07:01:55.211 am infoKitchenOverhead switch was off
app:4182019-11-03 07:01:53.638 am infoAction: Dim: KitchenOverhead: 0
app:4182019-11-03 07:01:53.596 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 5
dev:22019-11-03 07:01:53.443 am infoKitchen Pico Side Entry button 5 was pushed
dev:12019-11-03 07:01:53.389 am inforcvd: DEVICE,2,4,4
dev:12019-11-03 07:01:53.162 am inforcvd: DEVICE,2,4,3
dev:9752019-11-03 07:01:41.262 am warnError occured with UDP message: SocketTimeoutException: Receive timed out
app:2272019-11-03 07:01:40.746 am debugSending DEVICE Event (Pantry Door | CONTACT: closed) to Homebridge at (172.16.16.14:8005)
dev:1672019-11-03 07:01:40.655 am infoPantry Door was closed
dev:9732019-11-03 07:01:38.166 am warnError occured with UDP message: SocketTimeoutException: Receive timed out
app:4182019-11-03 07:01:33.074 am infoAction: Start lowering: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:01:33.021 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 4
dev:22019-11-03 07:01:32.875 am infoKitchen Pico Side Entry button 4 was pushed
dev:12019-11-03 07:01:32.805 am inforcvd: DEVICE,2,6,4
dev:12019-11-03 07:01:32.233 am inforcvd: DEVICE,2,6,3
dev:9702019-11-03 07:01:32.157 am warnError occured with UDP message: SocketTimeoutException: Receive timed out
app:4182019-11-03 07:01:31.634 am infoAction: Start lowering: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:01:31.578 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 4
dev:22019-11-03 07:01:31.392 am infoKitchen Pico Side Entry button 4 was pushed
dev:12019-11-03 07:01:31.338 am inforcvd: DEVICE,2,6,4
dev:12019-11-03 07:01:30.966 am inforcvd: DEVICE,2,6,3
app:4182019-11-03 07:01:30.027 am infoAction: Start lowering: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:01:29.969 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 4
dev:22019-11-03 07:01:29.778 am infoKitchen Pico Side Entry button 4 was pushed
dev:12019-11-03 07:01:29.722 am inforcvd: DEVICE,2,6,4
dev:12019-11-03 07:01:29.317 am inforcvd: DEVICE,2,6,3
app:4182019-11-03 07:01:28.254 am infoAction: Start lowering: Lifx Kitchen Bulb Sink, Lifx Kitchen Bulb Den, Lifx Kitchen Bulb Wine, Lifx Kitchen Bulb Fridge, Lifx Kitchen Bulb Pantry, Lifx Kitchen Bulb Banquette, Lifx Kitchen Bulb Basement
app:4182019-11-03 07:01:28.200 am infoPico Side Entry Rule: Kitchen Pico Side Entry pushed 4
dev:22019-11-03 07:01:28.031 am infoKitchen Pico Side Entry button 4 was pushed
dev:12019-11-03 07:01:27.888 am inforcvd: DEVICE,2,6,4
dev:12019-11-03 07:01:27.624 am inforcvd: DEVICE,2,6,3
Updated Rule:
Okay, that's weird - can you go to the device page for one of the bulbs and try the Start Level Change command there, see if that works at least
I've just tried a simple RM4 rule to raise and lower multiple bulbs (LIFX Color) and that works for me. Most of my bulbs are LIFX Color, are you using one of the other types? Perhaps there's a bug there if so?
And I can confirm that a group bulb dimmer does not have startLevelChange() and stopLevelChange() methods, which is a bit of a shame.
