When I set the home mode to Away in AltUI on openLuup, there is a counter visible. This suggests that there is a delay on executing the actual mode change. But this doesn’t seem to work. I have a workflow that, amongst others, turns the lights off when I set the house mode to Away. But the lights turn off immediately when I set the mode and not when the counter has finished counting.
Is this a known issue, a feature or a bug?
The workflow is triggered on the HouseMode variable of openLuup.
It’s just an unimplemented feature that I haven’t got around to doing, because nobody has asked. AFAIK, it should be 30 seconds to any mode other than home?
The side-effect will be to add a further delay to bridged Vera mode changes if they are slaved to openLuup (and vice versa.)
There seems to be a strange issue after the last development update. My workflow triggers on the house mode of openLuup when it shouldn’t. It worked before.
My WF triggers on a triple click. It then sets house mode to ‘Night’. But immediately after that it returns back to mode ‘Home’, through the “Manual home” condition. This shouldn’t happen. See attached screenshots.
I can’t find out why and by what the openLuup variable is set to ‘1’. When I set the house modes manually through the gui, it works fine. And when I delete the “Manual Home” condition it obviously works too.
[ul][li]a workflow calls the openLuup SetHouseMode action with parameter ‘3’[/li]
[li]this gets translated into the actual HomeAutomationGateway action[/li]
[li]unmarked in the log, this nevertheless starts a 30-second timer (as you asked for previously!)[/li]
[li]3mS later, a workflow calls the openLuup SetHouseMode action with parameter ‘1’[/li]
[li]this gets translated into the actual HomeAutomationGateway action[/li]
[li]unmarked in the log, this effectively cancels the 30-second timer, and…[/li]
[li]… immediately set the Mode to ‘1’, as requested[/li][/ul]
This is exactly the behaviour that I would expect under these conditions.
Yes, I think you are right. Then it seems to be a AltUI issue, because the transition to ‘Manual Home’ should not be triggered. I don’t think there is a change of the variable to ‘1’, that happens later on when the the WF arrives at the ‘Home’ state.