thank you. thats the only reason i keep working on this. 
funnily that is how this project started. i built a occupancy driver and released it. this was about a year ago on ST. users started using the driver with webcore and other native tools to set state and run various rules. through their subsequent requests what i found was that while they were finding it easy to do this:
when this state set these switches / lights
but driving the decision for when state should change or other complex conditions was not working for them as it should. it would typically be either too complex all in all or it took so many rules to try to replicate all the conditions that it became a maintenance nightmare. this was all on ST off course.
thats when the app came out to solve those issue. the rules are almost a small part of the app and in some way the easiest part of the app. in fact i would be happy to delegate the rules to any native app. see this request for example:
however the configuration settings does a lot more that may not be immediately apparent. for example how to decide between occupied, engaged and vacant states? the rules dont handle that. the app uses the configuration setting and drives those decisions transparently.
i have already moved out vacation to its own app. unfortunately it wont make the child app, which does majority of the processing, any smaller since it was handled by rooms manager.
next step is to move holiday lights out of the child app and in to its own app like vacation which will reduce a couple hundred lines from the child app and that should help with the size. i am still considering other alternatives for how the child app size could be reduced.
ok with that context … the occupancy device driver has always been built to run both independently and integrated with the rest of rooms.
you can use the occupancy driver to create a virtual driver outside of rooms manager and it is smart enough to know it was not installed by rooms manager and will handle calls to the other components accordingly as in not make those calls any more. so when state changes to occupied it will stay occupied and not process any switches and so on.
please give it a try. love to hear feedback on the independent driver only usage.
