I have several motion & lighting automations. They all work fine but one of them is acting weird.
It is a basic rule , there is a motion sensor named “stairs sensor 3” and a lamp named “stairs lamp 3” , the automation should normally turn on and off according to the motion state.
It turns on normally. But does not turn off when motion is inactive. It says (as below) there is an additional motion sensor which is active but that is the main triggering motion sensor. (stairs sensor 3)
app:1742026-06-23 15:49:40.836infoNot turning off: additional motion still active: Stairs Sensor 3
app:1742026-06-23 15:49:40.829infoMotion inactive: Stairs Sensor 3
app:1742026-06-23 15:49:21.905infoStairs Lamp 3 set to 55
app:1742026-06-23 15:49:21.638infoStairs Lamp 3 was turned on
app:1742026-06-23 15:49:20.918infoSetting dimmers [Stairs Lamp 3] to 55
app:1742026-06-23 15:49:20.894infoMotion active: Stairs Sensor 3
It looks like the issue is not the rule. The issue is your sensor 3 is reporting active, which is what should reset the rule as it does. It is literally doing exactly what it should based on the feedback from the sensor.
Sounds like there is an issue with the sensor itself if there was indeed no additional motion action. You could try resetting it and readding (if it is zigbee, it should jump right back into the same spot). Or see if there are any sensitivity settings on the device itself. If that doesn't work, you need to do some troubleshooting on the sensor itself
I am sure if you added the rest of the information requested in the pinned post for get help (hub type: C7, C8, etc; firmware version, model of the sensor, and driver used at a minimum), others might be able to chime in and provide some more specific troubleshooting information.
Also, logs not limited to the offending app would be more useful. Many times, as I suspect in this case, other device logs might be pertinent (in this case, sensor 3 probably shows some insight that shows it is reporting active)
1- The app itself isn't the issue. It reports that the motion was still triggered as active.
2- Copy/Pasting excerpts of the logs for a single device and app that have been shifted around isn't as helpful as posting the full logs so that they are shown sequentially
3- I didn't say I disbelieved you, I said if you posted more of the information, others might be more able to help, (they might see something you didn't since they aren't working on your presumptions - not a dig - this is the reason you have someone else proofread)
4- Firmware is always relevant as they sometimes update apps when they do firmware updates
5- Hardware is always relevant as some devices have their own peculiarities (You still didn't state the model of the sensor - that may matter)
Not trying to ping you at all. Just trying to get the information to be helpful.
I believe there is a problem on the DB about this device or the app (automation) instance.
is there a way to force a db repair without resetting and restoring from backup ?
ps: I am not hiding logs or information. It’s just that I believe the problem won’t be resolved by looking at logs. This seems to be a problem on DB and by looking at logs we won’t see anything. The app says there is an additional motion sensor and it is the same as the original triggering sensor. Obviously a DB problem.
