yeah seems very likely. all of last night lights all over the house went on randomly multiple times including lights not controlled by the rooms app.
thanks. for the first screenshot could you please share the recently tab for one of the lights that is going off then on when dim timer is set? immediately afters it happens will let me see the commands that were issued just preceding this issue…
Hi,
First of all - thank you for a great app. Does exactly what I wanted to achieve with Smartthings. Having a couple of small teething problems, but that will be solved with a bit more trial and error.
Couple of questions though:
-
Is there any way to switch the tiles to the more simple view seen in the screenshots from December? I’m not using all the features of the app so having a more simple view might be beneficial for the other members of my house.
-
I’ve seen information on a ‘Reserved’ state perilously (can’t find it now though!). This is an interesting idea for guest rooms - is it something that exists in the app still/yet? Not seen it anywhere.
1 Like
thanks. looks like the app is sending the off command but it did not send the on command. if you check in the smart apps tab for that light is there any other smart app listed other than the loft child app?
you are welcome.
- unfortunately ST does not currently support dynamic device tiles so it would require editing the DTH to display the simpler version.
- there are a couple of “hidden” states like reserved, donotdisturb … all of them behave the same as locked … that is they disable all automation for the room from this app. may be use locked? does that work for you?
You should see that at 2:11pm, Loft is sending a set level (100%) command prior to the off. I believe that set level is what is turning on the light (possibly some latency going on). Again, all I have to do is remove the dim value in checking for this to go away. You cant reproduce this?
right can’t reproduce in my install. it resets the level back to the pre dim level then turns off the light and it stays off.
yes quite likely this is caused by latency. I have put in a 250ms pause after the undimming and before the turn off. hopefully that fixes this issue.
going to put the code out after the ongoing ST issues from the last hub firmware update settles.
1 Like
Question about contact sensors:
How does Rooms handle inside contact sensors on doors? Is the rule of thumb door open no occupancy? Just curious.
when contact sensors are opened or closed the room moves to checking state. if during checking state motion is detected and sensor is open room is moved to occupied and if sensor is closed room is moved to engaged.
this logic is reversed if the contact sensor is marked as an outside door contact sensor in engaged settings.
are you still experiencing these issues?
thanks.
Yes… I still cannot update rooms.
ok lets see if we can get to bottom of the update first. please do the following after clearing logs. at any point if you see the error in the log please post the logs for the room including which step generated the error.
- create a new room, give it a name and save it.
- open the room and turn on easy settings.
- put in all settings in the easy settings page and save it.
- open the room and turn off easy settings.
- go to rules and add another rule for room and save everything.
thanks.
Failed - Error creating room, Step 1
Error: Error Saving Page
Log Xxx created - empty
Log rooms child app created - as follows:
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug isAnyASwitchOn
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug isAnyOccupiedSwitchOn
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug isAnyESwitchOn
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug isAnySwitchOn
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:56 PM: debug updateIndicators
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:54 PM: error java.lang.NullPointerException: Cannot execute null+null
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:51 PM: debug childCreated
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:51 PM: debug spawnChildDevice
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:51 PM: debug childCreated
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:51 PM: debug updated
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug whichSwitchesAreOn:
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug whichSwitchesAreOn
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug switches2Off
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug Xxx unschedule calling class: handle switches
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug Xxx room state - old: null new: vacant
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug dateInputValid
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:52 PM: debug updateChildTimer
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:43 PM: debug childCreated
0690d17f-abf1-49ea-8357-dda8238c18d6 8:24:43 PM: debug childCreated
1 Like
I went and updated all the code from latest and retried. Same error - updated previous post with latest logs.
1 Like
are you able to pick piston to execute now?
thanks.
Oh yeah… I can (I just can’t save it…)
details 
(still trying to repro here)
I have the same problem I think - java.lang.NullPointerException: Cannot execute null+null
The culprit is this line in updated():
if (!parent || !parent.handleAdjRooms())
I’m not up to speed with groovy/ST execution path. AFAICS parent is defined as the rooms manager app. How can it be null?
2 Likes
exactly. 
i made the unfortunate choice some time back of signing up for the beta firmware release. with the current beta i am not able to control most of my devices. so unable to debug stuff right now.
sorry for the delay. thought i was getting a beta not alpha :-/