correct. there was a typo in the subscription to the adjacent rooms motion sensors which should have been fixed when you updated the rooms manager app a few minutes ago.
to be clear i mean updated from github not in the ST app.
Rooms Manager: Smarter Rooms: Personalized home automation with Occupancy
should be there now.
bangali
#196
nah, you and the rest of the users are the best. without you guys being willing to give it a try - i am nothing.
bangali
#197
thought was going to do speaker next. thats still on the cards but auto level settings coming before that. starting off with simple level calculations but once this is working easy to do more fancy circadian rhythm based stuff. also allows setting color temperature.
rainbowValue for kelvin units for tunable white bulbs?
bangali
#199
didnt want to hang on to this code while working on the next features. so pushed this to github.
UPDATE: updated version 0.08.1 to github with the following changes:
* Version: 0.08.1
*
* DONE: 12/10/2017
* 1) added support for auto level which automatically calculates light level and optionally color temperature to
* to be set based on local sunrise and sunset times. this does not yet use circadian rhytym based calculation.
pcgirl65
#202
Yes, I did do the update and it does seem to be working now with the setting as occupancy. Thanks!
pcgirl65
#204
I have a problem with one of my motion sensors stuck in “motion”. But even though it is stuck and registering motion, my lights are going off. My Basement Room is saying that it is vacant but if one of the motion sensors that it is subscribed to is reading motion, shouldn’t it stay on?
bangali
#205
when using devices it does not check state rather events. since your motion sensor is not generating motion events the lights are probably turning off. i think … not run in to stuck motion sensor before. 
pcgirl65
#206
It is strange because I am right in front of the motion sensor and it stays in motion which should be correct because I am working in front of it. However, I noticed that the Basement Room would change from “Occupied” to “Vacant”. There wasn’t an “Engaged” stage. Then the lights would just turn off when the Room went to “Vacant”. When I left the room, the motion sensor did detect no motion and the Basement Room went into “Engaged” and then “Vacant” and then the lights turned off.
anthonymorris
#208
I had mixed results. So I went ahead and setup the sensor on the door. playing with the settings a bit. It seems to work best when I do not have the set immediately to vacant, and no motion timer on for engaged for some reason.
This may have to do with the motion sensor I am using it seems to have a 15 second reset after detecting motion to go back to inactive and depending on where it is in the active/not active state and when the door re-opens and when you walk out and close the door behind you it sometimes goes back to engaged and sometimes accurately goes to vacant as needed.
Not sure if there is some logic on your checking timer that could be tweaked to help with the multitude of sensors in the market. I have a mix, of aeon gen 5 multis, eco link motion, and monoprice multis zplus sensors. The gen5s with the dth I am using have a 15 second response the ecolinks are in test mode and have about 10 secs the monoprice are 20 seconds. So with zwave latency and sensor trip resets the checking portion of the room app might be benefited by either being configurable if possible by the user or I just need to finish setting up sensors and configure the adjacent rooms and setup the engaged status for all rooms not just select ones.
so that when they change they force the previous room to checking but in high traffic areas or shared rooms I could see this also causing problems because if you leave someone sitting at a table and walk out and into another and close the door it will force the other room to reset to vacant if they don’t move within the current short checking interval. unless I am not understanding the logic.
bangali
#209
this is often though not always the result of test settings. almost all motion sensors have a blind window for motion. some longer than others. when testing it folks tend to set to it 10, 20, 30 seconds for timeout settings and that ends up conflicting with the motion blind window. if set to some reasonable real life settings things usually work well because that avoids this sort of conflict. learnt that from personal experience. 
the dim timer is used for the checking state. so if you set timeout to say couple of mins and dim timer to 30 seconds (double the blind time of the motion sensor) usually it works consistently 99% of the time in real world usage.
this helps with your next question as well where the dim timer can be setting for the room can be set to double the blind time of that motion sensor. doesnt need to be always double but always a bit higher.
yes you are right. but unless that motion requirement is there, in a situation where there is no one in the room it ends up keeping the lights on which folks dont like as well. but there is always the option of using a switch or a presence sensor to keep the room on. these are also in the engaged settings.
bangali
#210
a quick note on occupied and engaged states. think of occupied as a transient state and engaged as a persistent state.
occupied is you go to a room are in there for a few minutes then leave the room. lights come on when you enter the room and turn off after a couple of minutes of your leaving the room.
engaged is when you stay in a room for an extended period of time and may be motionless for some or all of the time. since we cant depend on the motion event for engaged state there are different options to set the room to engaged for extended occupancy. these are all under engaged settings and there is more coming. but these help make sure the switches you set to on stay on even if there is no motion in the room.
when in engaged state you have a different and longer timeout state than the occupied state. so there is still a motion requirement but a much higher time threshold than transient occupied state.
happy to answer any questions.
anthonymorris
#211
The Dim timer is likely my missing piece. Since I was using webcore for the light rules I never configured the dim timer. I was not aware that is it’s purpose. Might want to add a blurb about that unless I missed it in all the posts. Will setup and see if it fixes my false positives and let you know.