Rooms Manager: Smarter Rooms: Personalized home automation with Occupancy


#709

Here is one example where my lock has sent zigbee messages according to the zigbee logs, but both Hubitat and Rooms Manager say it is inactive:

DEVICES THAT HAVE NOT CONNECTED WITHIN LAST 24 HOURS:

Back door lock

From <http://10.0.0.67/installedapp/configure/1/mainPage>

Name Value Unit Description Text Source Type Date
battery 97 % Back door lock battery is 97% DEVICE 2019-01-06 08:11:14.453 PM GMT
lock locked Back door lock was locked DEVICE 2019-01-05 09:39:03.232 PM GMT

From <http://10.0.0.67/device/events/34>

Last Activity At 2019-01-06 8:11:14 PM GMT

From <http://10.0.0.67/device/edit/34>

Back door lock2019-01-08 00:50:40.537 profileId:0x104, clusterId:0x101, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-88

Back door lock2019-01-08 00:50:30.954 profileId:0x104, clusterId:0x101, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-88

From <http://10.0.0.67/hub/zigbeeLogs>

Also the reason I asked about whether you used the events page data, is that I also have seen cases where Hubitat reported the "Last Activity At" for a device at a later time than any of the events on the events page. But again I also see messages in the ZIgbee logs for even later times than either. Below are the logs of such an example:

Name Value Unit Description Text Source Type Date
temperature 11.48 ┬░C Front door contact sensor temperature is 11.48┬░C DEVICE 2019-01-06 02:22:30.683 PM GMT

From <http://10.0.0.67/device/events/326>

Last Activity At 2019-01-06 9:08:54 PM GMT

From <http://10.0.0.67/device/edit/326>

Front door contact sensor2019-01-06 21:12:18.465 profileId:0x0, clusterId:0x6, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-64

Front door contact sensor2019-01-06 21:08:54.531 profileId:0x104, clusterId:0x1, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-64

Front door contact sensor2019-01-06 21:08:52.715 profileId:0x104, clusterId:0x1, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-64

Front door contact sensor2019-01-06 21:02:10.902 profileId:0x0, clusterId:0x6, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-64

From <http://10.0.0.67/hub/zigbeeLogs>


Where did "status" go in Hub Update 2.0.6 just released
#710

Can someone explain how to enable connectivity check? Do I need to set up a room first or something? I have the app and child app installed, but when I go to the connectivity check page most of the options are grayed out :frowning: Thanks in advance.


#711

Never mind. I figured it out. You have to set up your SMS device on a separate page first...


#712

Hi, Can I use Room Manager to control a heater in my Room?

When I click on "Room Device" I can not see my Outlet.


#713

I just started playing with the announcement features of the app after setting up the Echo Speaks app. Is there any way to set up Rooms Manager so that it plays the announcement through whatever Echo is in a room thatÔÇÖs currently occupied or engaged? That way I know it will play in whatever room IÔÇÖm in.


#714

please share a screenshot of the heater device details.


#715

this is a great idea ÔÇŽ will look at adding.

but for now if you add all echo devices to rooms manager do they all play the message?


#716

updated to github with the following changes:

Version: 0.99.4

DONE:   1/05/2018

1) added support for multiple power meters
2) added command optimization at the app level
3) added setting room occupancy device on / off so it can be used in the rules
4) other small fixes

#3 above is useful for keeping lights on in a vacant room when adjacent rooms are occupied / engaged.


#717

I am going to apply the update in a few minutes. In process of building room rules and have a question. The 'Time trigger?' under rules, is this really a trigger or a condition or a triggered condition? It is listed under the RULE TRIGGERS AND CONDITIONS. So I want to limit rule to to a specific time, say 5:20am - Sunrise +20 minutes. Is this where I apply those conditions to be triggered on a occupied state?


#718

yes. its a trigger and a condition.


#719

I just updated to 0.99.4, but my app in the apps list is still named ÔÇťrooms manager - v0.99.3ÔÇŁ. Do I need to do anything else to update the already setup rooms?


#720

yes please go to rooms manager and save the settings for rooms manager only once.


#721

Has anyone managed to get the device connectivity check working? I have several devices now that have failed to check in for a few days and yet I have not received an sms.

Here's my setup:

I installed rooms manager as well as the rooms child app. In the rooms manager app itself I did not install a room. I simply clicked next.

In the sms settings I set the hours from 1 to 24. I set my SMS number to my number (preceeded by +1 like all the other Hubitat SMS configs).

On the device connectivity page I ensured the slider was set to enable device connectivity check. I set 37 past the hour / 24 hours and then selected all the devices I care about under "devices to check". I also set the "critical devices" slider and set all the same devices there.

Is there anything more to it? What am I missing?


#722

I wonder if not setting up a room somehow prevents the device check from happening. will check and update.


#723

Hi I want to use this MonoPrice 27481 to turn On/Off my heater, I have temperature sensor on my room.


#724

Seems like in Rule #7 the Under Cabinet Lighting set level is being ignored and turning on the color strip lights at 100% instead of 5%. I pasted everything here in the event it is something that I am missing. Is this a rule order issue? Thanks

EDIT: Also tried removing color temp but same results.

ROOM OCCUPANCY DEVICE:
Room child device ´Żą ´Żą ´Żą ´Żą ´Żą Child device OK

ROOM SENSOR SETTINGS:
Motion sensors ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Kitchen Main Entryway Motion Sensor, Kitchen Window Motion Sensor, Kitchen Under Cabinet Work Area Motion Sensor, Kitchen Under Cabinet Prep Area Motion Sensor]
Trigger motion ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [1460]
Which no motion ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą Last Motion Inactive
Lux sensor ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Family Room Entry Motion Sensor]
Humidity sensor ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Kitchen Temp and Humidity Sensor]
Music player ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą Kitchen Sonos Play 1

OCCUPIED SETTINGS:
Motion timeout ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 180 seconds

ENGAGED SETTINGS:
Busy check ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą Heavy traffic
Require motion ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 360 seconds
Engaged overrides ´Żą ´Żą ´Żą ´Żą ´Żą true

CHECKED SETTINGS:
Dim timer ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 5 seconds

VACANT SETTINGS:

ASLEEP SETTINGS:
Asleep from time ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 02:00
Asleep to time ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 07:00
Switches ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Kitchen Asleep]
Asleep timeout ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 300

LOCKED SETTINGS:
Switches ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Kitchen Override]
When switch turns on ´Żą ´Żą ´Żą ´Żą true
Turn off switches ´Żą ´Żą ´Żą ´Żą ´Żą true
Locked timeout ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą 2 hours
Locked overrides ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą true

AUTO LEVEL SETTINGS:

TEMPERATURE SETTINGS:
Temperature sensor ´Żą ´Żą ´Żą ´Żą ´Żą [Kitchen Temp and Humidity Sensor]
Use thermostat ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą true
Room thermostat ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą Downstairs Thermostat
Temperature delta ´Żą ´Żą ´Żą ´Żą ´Żą 2
Thermostat override ´Żą ´Żą ´Żą ´Żą ´Żą 30
Outdoor Temperature ´Żą ´Żą ´Żą ´Żą ´Żą Deck Outdoor Netatmo Station
Adjust with outdoor ´Żą ´Żą ´Żą ´Żą ´Żą true

HOLIDAY LIGHT SETTINGS:

RULE SETTINGS:
Rules:
1: Mode´╝Ł[Home - Day] State´╝Ł[engaged, occupied] From´╝Ł05:00 To´╝ŁSunrise +10 Type´╝ŁExecution ON´╝Ł[Kitchen Lights] Level´╝Ł30 OFF´╝Ł[Kitchen Under Cabinet Work Area Light, Kitchen Under Cabinet Lights] Engaged Timer´╝Ł240
2: Mode´╝Ł[Home - Day, Home - Evening] State´╝Ł[engaged, occupied] Lux´╝Ł50 From´╝ŁSunrise +10 To´╝Ł16:00 Type´╝ŁExecution ON´╝Ł[Kitchen Lights] Level´╝Ł90 OFF´╝Ł[Kitchen Under Cabinet Work Area Light, Kitchen Under Cabinet Lights] Engaged Timer´╝Ł240
3: Mode´╝Ł[Home - Day, Home - Evening] State´╝Ł[engaged, occupied] Lux´╝Ł50 From´╝Ł16:00 To´╝Ł19:00 Type´╝ŁExecution ON´╝Ł[Kitchen Lights] Level´╝Ł60 OFF´╝Ł[Kitchen Under Cabinet Work Area Light, Kitchen Under Cabinet Lights] Occupied Timer´╝Ł240 Checking Timer´╝Ł480
4: Mode´╝Ł[Home - Evening] State´╝Ł[engaged, occupied] From´╝Ł19:00 To´╝Ł23:59 Type´╝ŁExecution ON´╝Ł[Kitchen Lights] Level´╝Ł40 OFF´╝Ł[Kitchen Under Cabinet Lights, Kitchen Under Cabinet Work Area Light] Occupied Timer´╝Ł90 Engaged Timer´╝Ł210
5: Mode´╝Ł[Home - Sleep] State´╝Ł[asleep] Check ON´╝Ł[Lavender Hill Asleep Override, Lavender Hill Guest Present] Type´╝ŁExecution ON´╝Ł[Kitchen Lights] Level´╝Ł15
6: Mode´╝Ł[Away, Home - Day, Home - Evening, Home - Override, Home - Sleep] State´╝Ł[vacant] Type´╝ŁExecution OFF´╝Ł[Kitchen Pantry Lights, Kitchen Sink Light, Kitchen Lights, Kitchen Under Cabinet Work Area Light, Kitchen Under Cabinet Lights]
7: Mode´╝Ł[Home - Day, Home - Evening] State´╝Ł[vacant] Lux´╝Ł5 Type´╝ŁExecution ON´╝Ł[Kitchen Under Cabinet Work Area Light, Kitchen Under Cabinet Lights] Level´╝Ł5 Color´╝Łwhite Kelvin´╝Ł3322

ADJACENT SETTINGS:
Adjacent rooms ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [1779]
Motion check ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą true

ANNOUNCEMENT SETTINGS:

GENERAL SETTINGS:
Away modes ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Away]
Pause modes ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą [Home - Override]
Execute on state ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą true
Which room state ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą occupied
Icon URL ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą ´Żą https://cdn.rawgit.com/adey/bangali/master/resources/icons/roomOccupancySettings.png


#725

shouldnÔÇÖt set the wrong level. there are no overlapping rules are there?


#726

in temperature settings specify the temperature sensor and the heater switch then create a rule to maintain the temperature you want.


#727

The "# rooms vacation" app is throwing a lot of errors in the Hubitat logs (see attached screenshot). Do you have any idea why this is? I have no intention of ever using this feature of the app, so would be fine with removing it altogether if possible.


#728

if you go in to the app and save the settings once does this still continue?

edit: if you update the code just for rooms vacation the error should go away.