Hi @Zakuska ! @Barkis is correct, I unfortunately do not have any Vivint panels in my lab, nor have I had my paws in their ecosystem. I just lurk from afar. LOL
In general security system panels are deliberately limited or locked down, typically to maintain their UL compliances. I would not be surprised if the panel is completely not customizable. As such, building a separate automation environment (like a second z-wave network) is usually needed. Iām not sure if you are implying that you want to write your own code (?) for this z-wave network, but it is likely easier to leverage a standard z-wave hub (say home assistant with a Zooz dongle, or a Zooz Z-Box, as just examples) since they have all the inclusion, exclusion and automation logic already built in. From there interfacing to, receiving triggers from, and sending triggers to the Vivint becomes the challenge.
Iāve found the following high level approaches when dealing with such panels:
Leverage existing interfaces/integrations
If you can find an api or interface (even if unofficial or intended for a different purpose) you may be on to something. For the IQ panels, as an example, they offer Control4 integration and that interface has been reverse engineered to be used to integrate to several other platforms (some homegrown). This can be used to push/pull the various triggers and sensor data between the two systems. This has grown into actual plugins for Home Assistant, Hubitat, and a home developed solution with Node-Red called IQ Mate. Iād look to see if Vivint has Control4 integration. If so, you may be able to re-use some of this code!!. It is all on Github.
āDirect wire methodā using Dry Contact Sensors
This sometimes is easiest to implement, but results in some wiring and electronics logic, but requires no āhackingā so to speak.
Hereās an example: setup a ZEN58 or ZEN57 on the Vivint panel, and tell the Vivent to close that relay upon doorbell press. (Likely Vivint would see that as a light switch).
Then wire that ZEN58 relay into the switch input on another z-wave device joined to your z-wave hub (letās say itās a z-box, with a ZEN16 for example).
So when the doorbell is pressed, the contact closes in the ZEN58 which triggers the switch input on the ZEN16. From there you can configure your light to blink as needed (the light would need to be added to your z-box, and youād need to program the automation to blink the light. )
Secondary Z-Wave Controller Method
There is also the long desired leveraging of secondary z-wave controllers. That is where a given z-wave environment can have more than one controller. This was intended for the use of wireless remotes, but can be used to allow, say, a second controller to join an existing network. I believe the requirement for secondary controller support was removed from the z-wave certification requirements a few years back, which means support for this is likely absent from your Vivint panel! (since it is a newer device).
PLEASE BE AWARE THIS can be a dangerous option, as trying this in the lab has caused corruption and the need to factory default the panel and/or secondary z-wave dongle/controller!
That said, if it works it would allow the secondary controller to perform some logic against devices on the primary controller. The issues youāll have include lifeline - where the secondary controller likely will not be able to see switch states, and coordination of the conversation with the SUC/SIS. Also the adding/removing of devices is a whole other adventure which Iām envisioning would freak out the Vivint. I would not recommend the approach because of the high risk and high likelihood of failure.
However I will say I had it working between a Z-Box and an IQ 4 panel for about 2 hours⦠and it worked, until it massively corrupted both devices. Again, Iād not recommend playing here with a live system.. (I replicated the corruption failure multiple times. Specifically the IQ 4 had secondary controller support removed when it wasnāt required by the Z-Wave Alliance for certification any longer)
[Last note: Home Assistant (specifically Zwave JS and ZWave JS UI) do not yet have full secondary controller support. The Z-Box does seem to support it, however Iām not sure if that is an āofficialā stance.]
Anyway - just a quick core dump on my thoughts and adventures here⦠
Out of curiosity - which Vivint panel do you have ? Is it the Vivint Smart Hub?
Certainly keep us updated on your progress. Always curious to see how others tackle the beast of locked down systems.