Yes, that worked. Here are the logs (that go right back to the earlier). Still "null" but the lights turned on with the sunset/sunrise restriction in the rule.
There are no sunset/sunrise subscriptions in the "i" for the Room.
cool.
just means there is no time specified in the rule itself.
somehow the subscriptions are not being setup which is the root cause of the problem. dont know if that has anything to do with you being down under. 
also the missing method exception for check switches is still being thrown when you save the room - yes?
Is it solvable?
Yes - just tested. Is that an issue with my devices or Rooms Manager?
Love your work !
1 Like
HE folks would have to take a look at why. for the app … since its working for you … its solved already.
i will update the code with the same fix and the push it to github.
issue in my code when multiple check on/off devices … will fix and push that too.
thank you
EDIT: the check on/off issue wasnt actually a code issue. its not working because subscription function that works on ST does not work exactly the same on HE. have a fix … will push later today.
OK. I have a similar issue with a different Rule. This time before midnight, so might be a related issue, but the changes to the coding (already implemented by commenting out those three lines) did not fix this issue.
I only just got home and the lights didnt turn on. I then removed the sunset to sunrise clause in the rule, and the lights immediately turned on.
can you please add the sunrise/sunset back to the rule and share the log for the debug line we had uncommented?
New situation I'm looking into...
I have a room set up for Basement Stairs, with adjacent rooms Kitchen and TV Room. The Basement Stairs room consists of lights that are in both Kitchen and TV Room (Basement Stairs A & B are up at the top of the steps, and light part of the kitchen, Basement Stairs Bottom lights part of the TV Room).
I'd like to have Basement Stairs set up to activate the adjacent rooms Kitchen and TV room, so that the lights at the other end will turn on before I get there (I think that's how the adjacent rooms setting works, right? Set the surrounding rooms to Occupied?). That all should be standard functionality I think.
The piece I'm missing is, since these lights are in multiple rooms, I've noticed that the Basement Stairs rules turn these room lights off once the Basement Stairs room times out.
For example, I'll come up the stairs, the stairs lights will come on, I'll get to the kitchen, and the kitchen lights will come on (which include the Basement Stairs A & B lights at the top). I'll be working in the kitchen, and after a minute or two, the Basement Stairs A & B lights will turn off because the Basement Stairs room has now gone vacant.
I'd like to have a way to use adjacent room occupancy in my execution rule for the Basement Stairs so that I can make a rule to only turn the top lights off if Kitchen is vacant, and bottom light off if TV Room is vacant.
I'm not sure if this all makes sense like I've described, but please let me know if I can explain it further.
for the basement stairs room try turning off the Turn off all switches on no rule match? settings so the lights only get turned off by the kitchen and tv room but do get turned on by the basement stairs room.
1 Like
Well that is a nice simple solution! I just made the change and will test it out. I was probably overthinking what I wanted to happen and didn't realize it was already there!
1 Like
Just wondering about the adjacent rooms property... I have the TV Room set up as an adjacent room on the Basement Stairs room, and if motion in room to turn on switches in adjacent rooms, but it doesnt seem to be activating the TV Room when the Basement Stairs room goes occupied. Is that how its supposed to work or am i missing something else?
no you are not.
something seems to have changed on HE where if you provide a list of devices to the subscribe command it silently fails. i have a fix. will push to github this weekend.
sorry about that.
1 Like
Cool, that's awesome! Thanks!
Your weather (lux etc) program is a winner with this app.
I've just removed all references to sunrise and sunset, and set every room so that it turns on with a lux below 1000. Great integration Bangali ! It's simplified a whole set of rules.
Thanks
1 Like
cool. exactly what I do and why I put together that apixu driver. 
even if the cloud api call fails the apixu driver should continue to publish the calculated lux every 5 mins … I think? if not I will make it so this weekend.
@bangali I can confirm that your lux calculation reports continue even if API calls fail. It's been very reliable for months.
1 Like
sweet! prescient!
@csteele to be honest I hadnt thought of that. However, something is not working with my sunset/sunrise automations (even when paused, they stop all automations for that room). As soon as I disable the sunrise/sunset component, the automation works as expected.
Yes, my location is set correctly. I've been in contact with @bobbyD and @bangali about it, but no fix yet.
