Hi @nayelyz , I noticed it last week end, it was Saturday i think so maybe it happens from 16th September.
Mu hub FW version is 000.049.00009
Iām unsure if it matters, but I run a mixed environment. My iOS app is 1.7.06 (updated this morning) and Android 1.8.06.03 (updated Aug 31}. My hub is V3.
To add to @Fred79 my location mode preconditions work in the morning but sometime in the late afternoon, they stop working. Flipping between the modes in the app does not get the auto routines with location mode preconditions to start working again.
No issues here, either. Android app 1.8.06.23, V2/2015 hub running 49.9
I have a couple of Routines that used location modes as a precondition and they have been working normally.
Edit to add:
My routines with location modes as preconditions have multiple modes and trigger after sunset or during the night.
To compare, iām on Android environnement (Andoird 13) and my hub is also V3.
I just have the bug again (it was working fine all the morning), and flipping the location mode solve again the bug. Really strange ā¦
My hub is V3 and my phone is Android.
I have a ticket with Smartthings support, and they suggested I delete and re-created the problem routines. My see motionāturn on light routine did not work after being re-created like normal with the Home precondition. But, just like before, if you remove the mode precondition, it works.
Another one I have, I added a notification to it to let me know for sure if it runs, and that one did start working with no other modifications.
I have tried this, deleting and rebuilding the affected routines several times. Back to the point @Fred79 made earlier, something happens as the day progresses. Today, my location mode-based routines failed at 2:20p ET.
I noticed something this morning that I thought might be related and a clue. I donāt exactly remember when, within the last week or so, but my home has not been going into night mode consistently.
This is not all that unusual as any motion sensor thatās acting up (often happens when battery gets low) will prevent it, but Iāve been unable to find a culprit. Usually happens once every few months yet at least 3 times in last week. This morning I traced it down to what I think is a motion sensor that has a current status in the app showing no motion . . . but the history shows last recorded motion event was motion as it never received the no motion event. It records changing temperature after what was actually the last motion, but never captured the no motion event. This would prevent my night routine from triggering.
It could all just be a flaky motion sensor specific to me, but this might explain why people are seeing a transient nature of the issue. Maybe sometimes events are captured in the right place and sometimes they are not, so to the app it looks like everything is fine, but via whatever system actually triggers the routine, it isnāt seeing certain events.
1 Like
My routines seem to be acting normal now. Iām not sure why or what happened, but I noticed the location modes trigger lights on Saturday.
Anyone experiencing the same?
Hi @nayelyz,
Yes I do believe I started noticing this issue somewhere right around that day. Hub version is showing as 000.049.00009.
I noticed a hub disconnection notification at 1:03am on Friday 9/22, possibly related?
@nayelyz and othersā¦
Being on vacation, often off the grid in the wilds, this has been extremely frustrating! I use lighting automations for security reasons.
My failure cases all use Location Mode = Away as a precondition and involve lights/switches. One case is a light that always turns on at sunset (no Home/Away precondition) and turns off at a set time when (precondition) Location Mode = Away. This light always turns on and is not turning offāI have to catch it when I have an Internet connection or it stays on indefinitely! Another light is to come on and turn off at set times with precondition Location Mode = Away. This automation always failsā¦
Guess all I can do is hang in there and wait! 
1 Like
Hi, everyone.
I asked about this issue to the engineering team and they are investigating. In case more information is needed, weāll let you know.
3 Likes
I spoke too soon, my location mode routines are still intermittent. My goodnight routine when at home still is not working. Iāll check which ones are working and which are not tomorrow.
Adding additional observations.
None of my location mode preconditions are working. I replaced some of these preconditions with security mode to test which seemed to work temporarily. As of today the security mode preconditions are no longer working. Iāve removed them and the routines work as expected. The only precondition that is currently working is time and timeframe.
Is there any update from the engineers?
1 Like
Iāve tried to reproduce this issue but no luck so far with hub beta firmware 0.50. Iāll switch to 0.49 and try again.
Thanks, Jerry.
To help, here is a screenshot of one of my simpler routines that does not work with location mode āhomeā as a precondition.
Many of my routines have two preconditions, time and location mode. E.g. If Iām āawayā and itās āsunsetā run the āevening awayā routine.
This example will not run with both preconditions, if I remove the location mode, the routine runs at sunset.
1 Like
Interesting.
Iām surprised using a specific time like āsunsetā works as a precondition. It seems you would need there to be motion exactly at that time for the Routine to trigger
when I added sunset, the toggle button for āpreconditionā wasnāt available. sunset was just a normal condition in the āifā expression. the only āpreconditionā in your example appears to be location mode with a gray background.
what happens if both are normal āconditionsā?
1 Like
Hello,
I tried to change the location mode from āPreconditionā to ānormalā condition in one of my routine but no improvement.
It happen again yesterday afternoon (French time), and if i flip to night mode and come back to Home mode, the routine is working again.
It there any correlation between failing routines and their execution location? Bear in mind that adding and removing conditions can affect that.
hub is back on firmware 0.49 and I think I reproduced the error. next step is to find out why it happens.
4 Likes