[Migrated to Custom Capabilities] Rooms Manager: Smarter Rooms: Personalized rules based home automation with rooms Occupancy sensing from devices you already have in your home

Thank you.

I might keep with webcore pistons. But I thought I would just try this out on an easy room first before going to ones with more usage and devices.

So I guess my question would be, if I don’t need the piston, then what triggers the light to come on? I didn’t see anywhere in the rule section anything that specifically stated when motion was detected to turn a switch on, which would then change the state of the room to occupied.

My thoughts were that this setup would set it to occupied and start a 45 sec countdown. So if I walked in and walked out, it would go to checking after 45 secs then turn off after that if no more motion during that whole time. If there was motion, then it would go to engaged and have a longer period of time before the light turned off.

But I guess I am misunderstanding something about it. So it does not automatically change to Engaged if motion is continuous? Just if it cyles through O, C and V in a short time? Ok. So I guess for the time being I just need to see why my device is not registering my continued movement and restarting the 45 sec countdown each time it does.

off course … i would never suggest deleting pistons. as i said just disable that piston while testing this. otherwise the piston and the app will interfere with each other because they both trigger and set the same devices.

the rule is already there but easy mode just gives a simplified view. turn off easy settings … then check the maintain rules settings.

vote above. :slight_smile:

correct on both counts.

if you keep the room open in things in the ST smartapp does the motion indicator show as active for the room or go inactive after the first moton? right below the status line like here:

also what is the motion timeout value for the motion sensor. if its larger than the 45 seconds timeout for occupied state that will also cause this to happen.

It was a larger timeout. Didn’t realize it. Will keep playing.

1 Like

ok. usually recommend:

occupied timeout motion timeout for the motion sensor + 30 seconds

I’m having a new issue. Last night one of my rooms stopped working, and kept saying there was motion when the motion sensors themselves were not indication motion, and the lights weren’t coming on automatically when there was motion in the room. I tried to delete the room, but I keep getting an “an unexpected error occurred”. I then tried removing some devices from the room, but when I go to save, i get an “error saving page” message and the following in the logs:

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: handleAdjRooms <<<<<

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room HVAC Room with adjacent motion sensors: [] | 332 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Living Room with adjacent motion sensors: [Kitchen Aqara Motion Sensor, Garage Motion Sensor, Garage PIR Motion Detector] | 320 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Basement Storage with adjacent motion sensors: [] | 280 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Play Room with adjacent motion sensors: [] | 274 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Guest Bedroom with adjacent motion sensors: [] | 265 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Garage with adjacent motion sensors: [] | 254 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Kitchen with adjacent motion sensors: [Living Room Motion Sensor] | 237 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Bar Room with adjacent motion sensors: [] | 203 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: info rooms manager: rooms manager: updating room Master Closet with adjacent motion sensors: [] | 194 ms

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:04:59 AM: info rooms manager: handleAdjRooms >>>>>

7023c38c-2202-49be-9edf-adb05818261c 9:04:59 AM: info Bar Room updated

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:06 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:05 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:05 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:05 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:04 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:04 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:04 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:04 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:04 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:03 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:03 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:03 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:03 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:02 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:02 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:02 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:01 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:01 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:01 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:01 AM: debug rooms manager: rSH initialized

68de09ea-f305-41b2-b3f0-f7aa044dd569 9:05:00 AM: debug rooms manager: rSH initialized

its virtually impossible for the app to show motion when the motion has not been triggered by the motion sensor. so lets check a few things:

  1. how many zwave devices do you have?
  2. how zigbee devices do you have?
  3. what is the radius over which devices are located?
  4. what is the brand/model of this motion sensor?
  5. is this motion sensor running on mains power or battery?
  6. is the motion sensor in an area that has breeze from a fan or duct or anything else directed towards it?
  7. from ST app if you open this motion sensor in things does it consistently show motion active / inactive when you move around?
  8. using 2 devices like phone or tablet … from ST app if you open this motion sensor on one screen and the room device on another screen under things … then move around does the motion activity for the motion sensor and the room’s motion indicator show active and inactive as they should?

on deletes … i need to look at that. but for deleting a room try this:

  1. from ST IDE go to devices then delete the device for the room
  2. then from ST app go to rooms managers app and delete the room

that should work.

every vote counts … dont tell me later you hate the feature: :wink:

1 Like

tip of the day: want to turn on and off switches on a certain day of the year?

setup a room … then add a rule with the following settings:

  • name of the rule
  • from date and to date (make sure hide advanced settings is false on the main settings page)
  • switches to turn on and off

when the rules date condition is met, switches specified in the rule will be turned on and off respectively.

i use a seasons room setup like this to turn on and off season switches spring, summer, fall and winter. you can then do a bunch of stuff that is season dependent.

So this was a really strange one… The room showed motion, but if I went to the individual motion sensors in the room, they were not showing motion. If I walked past the motion sensors (I have two in the room), they would indicate motion as expected, then return to no motion as expected when no movement, but the room consistently showed motion. I discovered that one of the plug in z-wave dimmers in the room had stopped working around the same time this problem cropped up, so I deleted it from SmartThings but still could not delete the room. I had to go into the IDE under locations and delete it from there. I then was able to recreate the room and now all is good.

As for the z-wave dimmer, it was showing offline, so I pulled it out of the wall and plugged back in and I could see it and turn it off and on from the app, but the actual light wouldn’t turn on. After much troubleshooting, I had to junk it.

1 Like

glad to hear its all working now.

these motion sensors were they also zwave?

The 2 motion sensors in that room are the zigbee Xaiomi sensors. One is an Aqara and the other is the older non-Aqara Xiaomi. Then there’s the z-wave lamp dimmer that went out and was replaced with the same brand/type, and three Lifx bulbs.

ok. i have used xiaomi sensors for a while now. they have a tendency to drop off unless there is a good zigbee signal repeater around.

personally i use xbee devices to act as repeaters … makes the xiaomi sensors much more stable.

I shall have to look into that. Perhaps I could replace one of the Lifx bulbs in that room with a Cree zigbee bulb, assuming it acts as a repeater. Thanks!

also see this thread:

a user had this ask:

Currently it is only possible to temperature control a room with one physical thermostat.

My current scenario, I have one or more vents in each room along with a temp sensor.
I want to be able to allow controlling each room using the central thermostat.

When a room needs HVAC but the central thermostat is not running,
reduce/increase current setpoint on the physical thermostat to service the demand.

i am waiting for the user to respond so i can tag this with their id. didnt realize connected vents were popular. :slight_smile:

i have an idea on how to make vents work better when using a central cooling/heating systems. here is what i am thinking:

allow specifying another option to manage temperature lets call it "manage vents only".
with this option the app will require a temperature sensor, both heat and cool temperature and vents.
then open and close vents proportionately based on the current room temperature and specified heating and cooling temperature.

the other part of the setup is ... in one room set it up with the thermostat and temperature sensor from all of the rooms that are heated and cooled.
then set the heat and cool temperature to the highest and lowest value respectively throughout the house.

this way the room with the thermostat will average all the rooms temperature to set the cooling and heating mode.
then each room will open and close vents according to their own temperature rule.

was i able to explain that?

thoughts on the feature?

thank you.

updated to github with the following changes:

*  Version: 0.65.0
*
*   DONE:   8/13/2018
*	1) fixed temperature colors on DTH for ST
*	2) added option to select which room motion sensors trigger occupancy from VACABT state.
*	3) added option to trigger busy check with repeated motion to the existing checks for state change trigger.
*	4) added option to override OCCUPIED state trigger devices when in ENGAGED state.
*	5) on HE added support for deleting rules.
*	6) added option to override OCCUPIED and ENGAGED state trigger devices when in ASLEEP state.
*	7) added option to override OCCUPIED, ENGAGED and ASLEEP state trigger devices when in LOCKED state.
*	8) fixed a bug on power time type selection when limiting power trigger during certain hours.
*	9) on HE started work on save and restore settings. currently only allows viewing settings to save.
*	10) fixed bug for only on state change where mode and lux change would still trigger rules evaluation.
*	11) added github update notification via sms.
2 Likes

anyone want to use multiple buttons (either with same or different button devices) to trigger rooms occupancy state changes? :slight_smile:

as an example you could use 2 button devices one each on either side of bed and 1 wall mounted main room button device … this would allow setting up 1 button from each device to trigger asleep state.

That would be excellent @bangali - currently I need to use pistons to implement a workaround for exactly that scenario.

this would be a breaking change … so anywhere you have a button configured in settings you would need to set those up again.

how do you feel about that? :slight_smile:

I need some help with this Room. I haven’t been able to get it to work right. When we are in the room, the lights still go out even though there is motion detected. I can’t figure out what I am doing wrong with the settings. Can you have a look and see what you think.? I have tried different settings and timings but things still don’t work right.