SMH With New ST Client

#1

I have been using WebCORE for a wile, and have some pistons which work very nicely for Leaving Home, Driving In, Walking In, etc…

All of these have an integration with SHM to either arm or disarm the Monitor. And these have been working very nicely with the LEGACY client and SHM.

However, I am in the process of migrating to the new client version, and after adding the SHM app on that client, I see that the pistons continue to arm/disarm the SHM on the old client, but not on the new one.

I have not been able to decipher why the SHM is treated differently between the clients, nor how I can get the pistons to speak to the other client.

Any suggestions?

Thanks in advance!

  • Nate
#2

SHM (classic app) and STHM (new app) are completely separate programs. You cannot control STHM from any 3rd party program. To control STHM you will have to use virtual switches. Control the state of the virtual switches in webCore and then use the virtual switches to change/monitor state of STHM using Automations in the new app.

Also, when discontinuing the use of the SHM in classic, make sure you remove all of your SHM rules.

#3

Excellent!

I am using vSwitches to kick off CORE pistons… Now I need CORE pistons to kick off vSwitches! LOLOL

I appreciate the feedback! I will get about the changes.

Thanks!