You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be improved. The lag is technically only needed if you are using the built-in distance sensor. Because the distance sensor can be noisy, and transient events like a person walking below it can trigger a false positive, it uses multiple reads separated by 'read interval' between every two sensor readings, to filter out noise. The switch sensor reading is handled in the same function as distance sensor, as a result, it also incurs this long lag, which I agree is not necessary. This can certainly be modified in the firmware, by decoupling the reading of switch sensor from reading of distance sensor. In the meantime, you can reduce the 'read interval' value, which is in Advanced tab of options, and that should reduce the lag.
That would be fantastic if the setting could be decoupled!
I will try adjust the read interval to reduce the lag.
I'm sorry I'm not much help on the coding side.
Also, out of interest, I wired my Aqara sensor up to the board as the open/close sensor. When disconnected from the board it updates via zigbee on state change, when hooked up to the board it remains on closed. Could this be due to the voltage the board outputs through the sensor affecting the state change?
Hi, I've set up my OpenGarage using a contact sensor to detect open/close
My old setup involved an Aqara door/window sensor to detect the door status and a spare garage remote hooked up to an ESP board.
The status changes on my old setup were pretty much instant, as soon as it closed or opened the status would change.
Using opengarage the state change definitely has ~ a 10s lag before updating.
Is there a way to make the device poll quicker? I would understand a delay with the distance sensor but not a wired open/close.
The text was updated successfully, but these errors were encountered: