That's exactly to point though. A stream of events from multiple sources with different intervals and different approaches all contributing to occupancy state. Duplicates aren't a problem.
I am not sure exactly what you are trying to say. Is that an agreement that events from multiple devices are what you are supporting. Then we are on the same page.
Yes, I think I have described it that way multiple times, but if I have done a poor job I apologize.
What I don't support is something linking rooms or spaces to sensors other other things to support occupancy. In my opinion the room or space should be decoupled.
It is probably me 
I've been following this thread tryna distill everything into a Venn diagram or flowchart. Can someone succinctly describe a situation where assigning a Virtual Presence device to a particular Room would be insufficient for representing that Room's "Occupancy"?
(Leaving aside for the moment the OP's desire for this status to be linked per-room/area or to exhibit inheritance, etc.)
2 Likes
Lot's of reasons not to implement a work-around if you can do better. A device driver is a heavy weight workaround for what is a variable|capability and value. Then every year or two later everyone gets confused about what a 'Presence' device really does and are referred back to this thread and the other ones confused about what Presence means for a device driver i.e. device is powered on and working versus person is present.
The options....
Not a criticism... but one of us needs to take control of this request and collate the info so we can present a concise request...
2 Likes
