If I remember correctly you can't turn off that warning with the current code as it doesn't come from the drivers directly, but rather from sendHubCommand.
It's almost like the local ping doesn't update the status (if changed) when controlled by an API. This happens quite often with Z strips, but I've had one bulb that's exhibited the same behavior. I have to manually turn it off and back on for it to properly recognize state. On a side note, since moving from ST to Hubitat (a couple months ago), I've also noticed that, occasionally, Hubitat (and correspondingly, Alexa, Webcore, and anything else) will think a light is off when it absolutely isn't. Maybe, instead of a 1 minute ping, could you aggregate a failure count and ping every 40 seconds, and only show an error once the threshold has been reached? That could lead into notifying users when a bulb goes offline as well instead of scratching your head about an automation that doesn't trigger for days. I've assigned all my devices (13 of them, I believe) to static IPs with long TTLs. All devices show up on my router (Amplifi mesh, which is the same subnet my Hubitat is connected to), can be turned on and off via the Lifx app, and work fine when being controlled by Webcore or directly from a Hubitat dashboard. I have the same issues with log error messages. File Size: 11.49 MB Date Released: Add info Works on: Android 4.04.0.2 Ice Cream Sandwich (API level 14) / Android 4.0.34.0.4 Ice Cream Sandwich (API.
0 kommentar(er)
