Webcore suddenly not recognizing Smartthings "location mode"

#1

1) Give a description of the problem
I use Smartthings location mode as an input for one of my pistons. When the location mode changes to “stay”, I want another action to run to keep my keypad in sync. The piston I’ve been using for quite a while for this suddenly stopped working over the last couple of days.

2) What is the expected behaviour?
Location mode changes to “stay” and keypad is set to its “stay” mode.

3) What is happening/not happening?
In tracing the piston, it appears as if Webcore never sees that the location mode changes. All built-in Smartthings Automations using location modes are working fine.

**4) Post a Green Snapshot of the piston![image|45x37]

image
image.png1178×481 22 KB

5) Attach logs after turning logging level to Full
8/26/2021, 6:20:17 AM +144ms
+0ms ╔Starting piston… (v0.3.113.20210203)
+400ms ║╔Subscribing to devices…
+406ms ║║Subscribing to Home.mode…
+455ms ║║Subscribing to Keypad…
+456ms ║╚Finished subscribing (67ms)
+483ms ║Comparison (string) :afd954100a49a551fe6758c3b9c6098e: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = false (1ms)
+491ms ╚Piston successfully started (491ms)
8/26/2021, 6:13:05 AM +561ms
+1ms ╔Starting piston… (v0.3.113.20210203)
+380ms ║╔Subscribing to devices…
+408ms ║║Subscribing to Home.mode…
+469ms ║║Subscribing to Keypad…
+469ms ║╚Finished subscribing (99ms)
+493ms ║Comparison (string) :afd954100a49a551fe6758c3b9c6098e: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = false (1ms)
+504ms ╚Piston successfully started (504ms)
8/25/2021, 10:27:50 PM +416ms
+1ms ╔Starting piston… (v0.3.113.20210203)
+371ms ║╔Subscribing to devices…
+401ms ║║Subscribing to Home.mode…
+468ms ║║Subscribing to Keypad…
+469ms ║╚Finished subscribing (110ms)
+496ms ║Comparison (string) :f4d313ed72df2304f8e113294f8ec02c: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = false (0ms)
+497ms ║Cancelling condition #2’s schedules…
+499ms ║Cancelling condition #1’s schedules…
+513ms ╚Piston successfully started (513ms)
8/25/2021, 10:25:33 PM +734ms
+1ms ╔Starting piston… (v0.3.113.20210203)
+364ms ║╔Subscribing to devices…
+428ms ║║Subscribing to Home.mode…
+515ms ║║Subscribing to Keypad…
+517ms ║╚Finished subscribing (162ms)
+541ms ║Comparison (string) :f4d313ed72df2304f8e113294f8ec02c: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = true (1ms)
+543ms ║Cancelling condition #2’s schedules…
+544ms ║Cancelling condition #1’s schedules…
+561ms ╚Piston successfully started (559ms)
8/25/2021, 10:24:30 PM +875ms
+1ms ╔Received event [Home].test = 1629944670875 with a delay of 0ms
+56ms ║RunTime Analysis CS > 15ms > PS > 6ms > PE > 35ms > CE
+60ms ║Runtime (36732 bytes) successfully initialized in 6ms (v0.3.113.20210203) (57ms)
+62ms ║╔Execution stage started
+69ms ║║Comparison (string) :afd954100a49a551fe6758c3b9c6098e: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = false (1ms)
+72ms ║║Condition #2 evaluated false (6ms)
+73ms ║║Condition group #1 evaluated false (state did not change) (7ms)
+77ms ║╚Execution stage complete. (16ms)
+79ms ╚Event processed successfully (78ms)
8/25/2021, 10:20:20 PM +716ms
+2ms ╔Starting piston… (v0.3.113.20210203)
+398ms ║╔Subscribing to devices…
+463ms ║║Subscribing to Home.mode…
+583ms ║║Subscribing to Keypad…
+585ms ║╚Finished subscribing (192ms)
+612ms ║Comparison (string) :afd954100a49a551fe6758c3b9c6098e: changes_to (string) :f4d313ed72df2304f8e113294f8ec02c: = false (1ms)
+634ms ╚Piston successfully started (633ms)
8/25/2021, 10:20:18 PM +620ms
+62ms ╔Stopping piston…
+148ms ╚Piston successfully stopped (87ms)

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.

Smartthings Location mode changes not executing
#3

Sorry. I created those modes to keep my keypad and STHM in sync. Some use virtual switches, I use the modes. It has worked perfectly up until today. The mode is definitely changing in Smartthings but not registering as a change in Webcore and therefore the piston is not executing.

#4

I am having the exact same problem. Just started a few days ago (Sept 28, maybe?). I’ve made no changes to my pistons or any of my Smartthings configurations. Completely baffled. I’ve spent hours troubleshooting and cannot figure out what would prevent a piston from triggering off a location change.

If I use a scene to change the location mode, and then hit the “test” button on my piston, it will then see the location change and take the appropriate action. So my location modes work, and the piston works. It’s like the piston isn’t subscribing to location mode events, even though I’ve set each of the conditions to “always subscribe”.

Hopefully someone can help.

#5

It seems that location change events have recently stopped propagating to legacy apps. I’d be surprised if it were intentional. I’ve not seen an acknowledgement of the problem from ST yet.

#6

Yep same here. Location mode changes not triggering pistons :disappointed: