SmartThing home Monitor status in webcore is wrong

#1

1) Give a description of the problem
Any idea why I see my SmartThings Home Monitor status with wrong info in webcore? It’s shown as Armed Away, but it’s in fact currently deactivated.

2) What is the expected behaviour?
It should match what I see in SmartThings Home Monitor. And my pistons should also trigger the STHM, but they don’t. The piston changes the status of the STHM only in webcore and has no effect in Smarthings.

3) What is happening/not happening?
(PUT YOUR INFO HERE)

4) Post a Green Snapshot of the pistonimage
(UPLOAD YOUR IMAGE HERE)

5) Attach logs after turning logging level to Full
(PASTE YOUR LOGS HERE THEN HIGHLIGHT ALL OF THE LOGS AND CLICK ON THE </> ICON TO FORMAT THEM CORRECTLY)

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

#2

That component no longer works in webcore since they decommissioned the old ST Classic app 2 years ago.

You can set up virtual switches in ST and use automations to sync them with STHM. Then use those virtual switches in webcore.

But just a reminder that it would only be a short term solution. Once ST ends support for groovynon the ST platform… then webcore will most likely cease.

#3

So I cannot trigger the SmartThings Home Monitor anymore in webcore?

#4

I control it via virtual switches and 6 routines in regular ST. They look something like this.

image
719945CD-2967-4E5A-AE2A-EEF7710419B9.jpeg828×1442 293 KB

#5

That works. But I stil can’t add an exit delay… That’s what I’m looking for at the end.

I want to have 30 seconds to open the door and leave before it’s get armed.

The only solution right now for me is to arm the system with the phone when I’m out.

#6

Couldn’t you run your trigger whatever it is, then in webcore tell that switch to wait 2 mins or whatever before switching on? I had mine on presence sensing - when it detected everyone was gone it flipped to armed away, when anyone got back it flipped to disarmed.

Of course this was back in the good days when iOS presence sensing was reliable.

#7

iOS 15.3 was released today… see if that improves presence