Closed cronutan closed 3 years ago
Let me know if you think there's still something to be done in the input logic of the zones. I don't really have any control over the timeouts on the input sensors. Unless I separate the on and off actions and treat them differently. That is, add a class of sensors that are only used for "on" sensing or "off" sensing. Hmmm.
The only thing I would change is how the cancel timer function works. I think it would be nice if you could invoke it even before the timer starts which would then simply change to unoccupied as soon as all the motions are off.
That way I could cancel timer without immediately without changing occupied state not worrying about how long an individual motion sensor is set to.
P.S. Not going out anymore.
I don't understand. How can you cancel a timer that hasn't started yet? If you want the zone to go unoccupied as soon as all the sensors are off, then don't put in a delay at all. In any case, I think the specific issue here is fixed. If you want to add some other functionality, then open a new issue. If you do that, give a step by step description of what should happen when, including sensor changes and user actions.
When I cancel timer for zone (off) I get the state of the occupatum device off as exppected, however when one of my motion sensors turns off subsequently the occupatum device becomes on again and then after timeout becomes off again.
Log of the sequence: