[OBSOLETE] Honeywell / Ademco Vista 20P Integration

[ruinertt]

@orangebucket

Apparently they have reworked Automations and Scenes to use the Rules API so that could be a factor.

Using the Virtual Switch handler might not help because it sends the events with ‘isStateChange’ true which forces events to propagate even if the state hasn’t changed. By contrast the Simulated Switch handler sticks to the default and only propagates changes. However I’m not sure how that legacy setting interacts with ‘new’ settings where I seem to remember seeing the option on the subscribe side.

@nathancu

With all of the weirdness that’s been going on the last 6 days and given that it was working before last week and suddenly wasn’t AND I’ve seen multiple reports of people having issues with the V-Switches handling STHM triggering as many as 48 times when they’re thrown… I’m inclined to think it’s related to that.

I changed the type from Virtual Switch to Simulated Switch and it worked perfectly across the board with all pistons and automations.

I changed the type back to Virtual Switch and the problem came back.

The reason why @steinauf might not have seen this issue is because he had them defined as ‘contact sensors’ I do believe. I’ll keep monitoring. Strange for sure, but it appears that Virtual Switch is the culprit and any recent changes on the ST platform might have affected it.