New Plugin - Occupatum - Occupancy/Presence detection

Occupatum is Latin for Occupied.

Got some basic functionality working, and looking for feedback on the approach. No releases tagged yet, you'll need to update manually for now.

• Install Plugin.
• Create an Occupancy Zone device for each room or area you're monitoring.
• Set the sensor list for the sensors for that zone. The plugin only allows indigo.sensor devices that support "onState". If yours doesn't, use the Masquerade plugin to make one that does.
• On the second section of the device config panel (pop up at top), select the logic to be used to turn on the occupancy device.

I'm working on how to implement delayed changes now. I need to go through all the comments in the various recent threads for more features.

https://github.com/FlyingDiver/Indigo-Occupatum

First official test release: https://github.com/FlyingDiver/Indigo-O ... /tag/0.0.1

Install plugin as usual. Create an "Occupancy Zone" device and specify the sensors for that zone. Below you can specific some logic options for determining the occupancy state. You can also configure the delay before the occupancy state changes. If the input sensor states change during the delay period, the timer will be cancelled and restarted.

Installed and giving this a go. I'm liking the simplicity and looking forward to incorporating it into my "home" and "away" logic plus build on it for more indoor occupancy I've never had.

Thanks!

Hey Joe... I was actually pondering something similar to this a month or so back -- kind of a vendor-agnostic approach to the occupancy sensor and determination. What would be kind of cool would be if there was a defined "API" via the publish/subscribe that would allow non-sensor type devices to let you know a change in status.

Might be more work than you are wanting to do and envisioning, but something along the lines of subscribing to the plugins for the selected devices and expecting some defined data object format that you have specified (even as simple as the device ID and new present/not-present status). Was thinking it might work for the geofencing/Unifi/whatever plugins that are more complex and not a simple sensor.

I've lots of ideas and little time, though. Feel like Durosity throwing things out there like that!

Can this work with iPhone presence detection, for simply who's home and away, and "all phones home", "all phones away" ? No need for which room.

You can set up one "room" which is the whole house. This is a logical aggregator for other sensors.

I just got around to installing it and works great. Thank you. There is one more thing that I use that would be great addition to the plugin. For things like doors in the area, I like to trigger occupancy, but in most cases I don't care if the door is opened or not, I just want it to trigger the area as occupied. It would be great to be able to add devices that trigger the occupancy regardless of state on/off.

That is, if a door in an area is opened or closed that would mean that someone made this happen so the area is occupied. I don't wait for the door to close or open again, I just re-start the timer.

This is especially important, as most of the time, the motion sensors trigger one to several seconds after I come in (depending on location) which then makes it seem as its not working. In two of my bathrooms the sensor is behind the door as you walk in, and only triggers motion after the door is shut. So the light comes on one or two seconds after you close the door and its total darkness till then. So in this case what I do is as soon as the door is opened, I trigger bathroom occupancy and start a timeout (lights on right away), then the motion gets triggered and takes it from there. When the motion no longer registers, then the timeout is restarted and lights go off regardless of door state. I don't want the light to stay on just because the bathroom door is opened.

I'm not sure if I'm describing my situation clearly.

I think I understand, you want a trigger based on any change in the sensor, not just on or off.

Is that right?

Yes. Motion sensors would still wok as they do right now, but I would add doors to a separate list that triggers on any. That would simplify my occupancy setup tremendously.

Ok, issue created: https://github.com/FlyingDiver/Indigo-O ... m/issues/3

Thanks a lot.

One more thing. Another issue that I have, is that if somebody leaves the room and turns off the light manually while the timeout is in progress and then re-enters before the timeout expires the lights don't come on. So in my old logic, when the light is turned off, I would reset all the motion timer and set all the motion variables to false.

Possibly a way to reset of the occupatum device that would make it off (and reset of timers) until any of the motions becomes on again. I know there is still a build in timeout on each motion sensor, but I keep them at the lowest level (10s ) and the DSC motion sensors are basically instantaneous.

https://github.com/FlyingDiver/Indigo-O ... m/issues/4

I was wondering if you have an idea when you might have time to add the last two items to the plugin. If you aren't planning to work on it any time soon, I might try to take a stab at it and send you my changes for review. I would prefer to have you do it, but I'm willing to help to get those two items added.

Kinda buried with updates to plugins that are officially released, so it might be a couple more weeks. If you want to fork it on GitHub and try to add it, go ahead. Then you do a pull request for me to see your changes.