I have been having a problem for several months now with one of my bulbs and the application getting the on/off status wrong. Sometimes the light is stuck on because the app thinks it is off and sometimes it stays off because the app thinks it is already on. The bulb is a Sengled Element Classic and I am controlling it using an Aqara P1 motion sensor. Tying it all together is a room lighting app. First I will show the app details, then the log details, then the bulb details, and finally the bulb events. Any help would be appreciated.
The bulb is not sending the update when turning off or the turn off command isn't making it. The app isn't part of the equation. If the device itself isn't updated properly, then the app has no way to know otherwise.
I'd reset and rejoin the build. You do not need to delete it from Hubitat. Just reset it (think it's 10x on/off cycles) and then do a ZigBee join. After re-pairing, go to the device page and hit configure. See if your issue clears up
No, issues still exists. Going to try adding "command devices on/off irrespective of reported state (Force)" to the additional options section of the application.
[EDIT 6/14/23] These additional settings did not resolve the issue. Bulb continues to randomly ignore commands for on/off for the application. By the way the bulb in question is only 6-8 feet away from the hub so distance should not be an issue.
[Edit 6/15/23] To be more exact the bulb I am using is a Sengled Extra Bright Daylight (5000K). Could this not be an "element classic"? It seems to not show under the FAQ's for what a classic is (2700K) but have it's own webpage. Maybe I do not have the correct type selected under devices?
If the device doesn't work consistently from the Device Settings page, and the "States" in the upper right corner doesn't match the actual bulb physical state, then the automations definitely won't work correctly. So the first step is to get the bulb to work from the settings page and report their status correctly.
It appears that there are 6 different Sengled drivers, maybe try a different one? Not sure what driver is appropriate for your particular bulb??? Be sure to hit "Configure" if you change drivers.
The device works from the settings page without problems. The issue is the application sends an off command after 4 minutes of no motion and the bulb does not reply with the bulb off event even though it's device event page shows receiving the off command from the app, not always but a few times a day. By the way, this has only been a problem for the last several months. I am thinking of moving this from "room lighting" to "rule machine".
