Outage Affecting STHM and some automations (19 Jan 2021)

New week, new cloud problem. :disappointed_relieved:

Discussion in the following thread, plus a note from support posted by one member:

3 Likes

Son of a biscuit, literally just tried my automations that sync STHM to other things and now it works. Hallelujah! Now to get rid of some infinite loops I apparently created in the automations… ha!

I am syncing a Nexx Alarm device which acts as a keypad to my security system w/STHM arm stay/away/disarm.

I want to sync alarm status --> SHTM and SHTM --> Alarm, so I had to create automations both directions. I’m afraid in some cases this could cause some infinite loops and already saw some weird behavior. Any ideas how to keep it from going “oh alarm armed, better arm STHM! oh SHTM armed, better arm alarm!” over and over?

Yeah - this is insane. I just got my WiFi hub on Monday and cannot get it connected. At least the rep on the phone admitted there was still a huge issue, but there is ZERO excuse for this outage to last this long. Samsung needs to step up and get this fixed. :angry:

More than likely, that’s what’s going on. They are working on the system as a whole and breaking things in the process. I’m practicing patience. :pensive:

1 Like

Yep, this is ridiculous! This last issue is making me consider migrating to another hub. Please share you thoughts. Considering Hubitat.

1 Like

Status page said this was sorted but it surely isn’t and the support doesn’t seem to reply to emails?
I can’t use the STHM feature as any change in mode triggers an infinite loop och Goodbye and I’m back until I disable the automations in the app.

1 Like

Same here. I am disappointed the Status page has no issues the last two days since the STHM problem is on-going and I have a couple of lights not turning off on schedule in Automations and in the Smart Lighting App and I have seen a few post here stating same.

2 Likes

I agree - I just received a notification that supposedly the issues are resolved, but I am still getting the 36-302 error when trying to activate my new wifi/hub. I looked at Hubify too - I chatted with the manufacturer about functionality and it looks like it will work, though it is a fairly complex setup. It also functions as a locally stored config with a cloud interface. A feature that has good and bad implications. Either way, my return window for this Samsung device is up in a few days, so I guess it either works this weekend or back it goes!

Has anyone got any replies from the support regarding this?
I can’t use the STHM automations anymore and have to do each step manually?

I have virtual switches that are supposed to Arm and Disarm the STHM and they are still not functioning. I have recreated them as well as removed and reinstalled STHM. The only way to change the status of STHM is to manually click the status on the STHM. @vlad can you look into this, the STHM is useless if you can’t automate changing it based on presence (which also has been flaky lately). I am seriously about to throw in the towel on this platform.

3 Likes

Change them to a Simulated Switch. That worked for me.

I just found one thing that might be a solution to the looping… Unfortunately I run my phone in Swedish so the screenshots are not English but I think you’ll get the point.
The mode has been changed from a “first” parameter to just a parameter in the if statement on all automations using them. I changed all mine back to be the first parameter as they’ve always been using the little switch at the bottom. Then it seems to stop the looping… Not celebrating yet but it would explain the irratic behavior of all my other automations.

1 Like

Not sure what the difference between the 2 are as they mean the same thing. However, I changed them to Simulated Switches as there was an option to do so. The behavior stayed the same, the status does not change on STHM. Webcore is not able to modify the STHM status directly even though you can code to do so. To work around that, I set up the virtual switches to make the change which was working fine until a few days ago. There seems to be no current way to programmatically change the status in STHM.

I see what you mean. The ‘precondition’ setting for the location mode had been turned off in all my Automations.

2 Likes

Although the words mean the same thing, technically the two DTHs do have some significant differences. One of them checks the state, the other does not. One of them runs locally, the other runs in the cloud. So it happens that some people have found that the looping problem was apparently caused by the state issue, and switching to the other DTH fixed it for them.

Exactly…! All of a sudden I could run the Goodnight automation without the house looping into I’m back och Goodbye routines…

I’m still having issues with SHM and virtual switches which change alarm states

Been over a week.

2 Likes

Same here. STHM either shows no sensors, or when it is there it loops many times from armed to disarmed and it you never know how many times. Please help.

1 Like

I had the same issue with the infinite loop and the app showing no sensors. If you are using Virtual switches to Arm and Disarm STHM, log into the IDE and change them to Simulated switches. Immediately corrected my issue.

3 Likes

I am trying this as well and hopefully better