I’ve had a ticket open with support ever since migrating from v1 hub to v2 a few weeks back. Initial problem I reported was that my power allowance smart lighting smartapps were triggering in Home mode even though they are configured to only trigger in Away or Night mode (and of course my smartapps that were configured to only run in Home mode, were not triggering at all when I expected them to).
Over the course of communication with support I have determined that the problem is not with smartapps, but rather with routines often not changing mode. I see this lack of mode change within the Location event history, but within the mobile app the mode does appear to be updated.
Anyway, here’s the evidence from Location event history:
Last night, I executed Goodnight routine with minimote, all is well:
2016-05-16 12:27:52.795 AM PDT
18 hours ago LOCATION /LOCATION_MODE_CHANGE LOCATION_MODE_CHANGE mode Night 2Home is now in Night mode
2016-05-16 12:27:52.750 AM PDT
18 hours ago LOCATION /API routineExecuted 4e1ee37e-b1bd-460a-83c7-7d991… Goodnight2 was executed
This morning Good Morning routine executes when things start happening but no corresponding mode change is logged, and even though my location appears to be in Home mode, my smart lighting smartapps think the location is still in night mode (Interestingly, non local smartapps like Lighting Director run as if in Home mode)
2016-05-16 6:47:04.026 AM PDT
12 hours ago LOCATION /API routineExecuted 385e7bbb-2eca-4547-8d39-5e8c3… Good Morning WD! was executed
This afternoon I test and let Goodnight routine execute when things quiet down: Mode changes to night. Smart Home monitor does not alert me to anything when I open and close doors, but smartapps configured to notify me when doors open in Night or Away mode do send me notifications when I open doors.
2016-05-16 3:59:29.218 PM PDT
3 hours ago LOCATION /LOCATION_MODE_CHANGE LOCATION_MODE_CHANGE mode Night 2Home is now in Night mode
2016-05-16 3:59:29.173 PM PDT
3 hours ago LOCATION /API routineExecuted 4e1ee37e-b1bd-460a-83c7-7d991… Goodnight2 was executed
Then I manually execute I’m Back routine, but there is no corresponding log of a mode change from Night to Home (I’m Back is configured to change mode to Home regardless).
2016-05-16 4:41:53.438 PM PDT
2 hours ago LOCATION /API routineExecuted 4e23fbcc-6129-447e-b0fe-b3174… I’m Back! was executed
In this state after the above, Mobile app location shows as Home mode, but once again my Away/Night only configured Power Allowance smartapps keep turning off the lights.
Then I manually change mode from Home to Away and back to Home again in SmartTiles dashboard, and suddenly all is well, all my locally running smartapps run with correct mode recognized and my lights stay on.
2016-05-16 6:00:34.204 PM PDT
30 minutes ago LOCATION /LOCATION_MODE_CHANGE LOCATION_MODE_CHANGE mode Home 2Home is now in Home mode
2016-05-16 6:00:31.890 PM PDT
30 minutes ago LOCATION /LOCATION_MODE_CHANGE LOCATION_MODE_CHANGE mode Away 2Home is now in Away mode
So the question is, what am I doing wrong? How do I fix this? I should mention that all of these routines are configured to change mode as you would expect. Goodnight routine to Night Mode, GoodMorning routine to Home, I’m Back to Home, Goodbye to Away etc. And I’ve tried removing and reinstalling them multiple times over the past few weeks with no luck. Support suggests recent platform changes may have resolved the problems but they have not…
Ideas?