archanglmr / homebridge-occupancy-delay Goto Github PK

HI.
Thank you very much for your hard work. I propose to add the "Characteristic Serial Number". I have the APP "Controller for HomeKit" indicates that this plugin generates duplicate serial number. I think adding this Characteristic will solve the duplicate serial number when you have several accessories with this plugin.

Above image turns the light on when motion is detected.

Above image turns the light off when motion is not detected

See attached image of my shortcut. This works fairly well but sometimes it will still turn off lights when still occupied. I would love to know if your plugin is more reliable with detecting occupancy?

I think you coded this plugin with the assumption that you can turn off the lights on the way out of an area without trigger motion.

And that's indeed the case if you have some sort of motion sensor overlooking the entire room.

However a lot of cases, the motion sensor is monitoring the entry way for entry and exit. Some sensors even are mounted on doors specifically. In those cases, you can't actually turn off the lights and exit the room because it will instantly retrigger it.

Do you have a solution for this scenario? Thanks

Is it possible to set the TimeRemaining characteristics to zero - eg. if you manually turn off the lights the occupancy sensor should be reset to no occupancy.

This plugin pretty does exactly what I'm looking for. But one thing that would be useful is to expose the remaining occupancy time for the occupancy sensor. In the default home app you can't see anything beyond on/off but if you use a third party app (like eve) you can already see additional attributes (like delay setting). In there it would be nice to see remaining time.

Extensively using this plugin in my setup, so thank you for building it.

One thing I have noticed is that switches and occupancy sensors lose their state if homebridge restarts. Is it possible to retain their pre-reboot state?

For the occupancy sensor timer, perhaps it could just continue it — or we can compare the timer against the system clock to add a negative offset to the time homebridge was down for. Thoughts?