If you could make it secondary, or if it works for you to have smartthings as a secondary to the lynx, they don’t “send a signal” of the kind that you’re envisioning, that contains content information like “I just changed to arm status.”
They just send information about The shared Z wave devices, and then only if the secondary has the ability to check for updates, which many do not.
Z wave communicates in a set of very structured command transmissions. Even the primary controller.
And unfortunately smartthings is not really designed to “play nice” with other Z wave controllers, so it doesn’t do the listen for updates thing.
If lynx could be added as a secondary Z wave controller, you could have it turn on a Z wave switch when it arms and then have smartthings respond to that switch coming on.
I’m not 100% sure, but if smartthings is added as a secondary, I don’t think it will be aware of the switch status when the lynx turns it on (because it doesn’t do that listen for updates thing), but it’s possible that you could just poll that switch every five minutes or so and then respond to that. Note that adding polling traffic to your network may slow down the rest of the network, though.
What most people do when trying to combine smartthings with a non-Z wave alarm system is the add an additional bridge device that actually checks the current on one of the other system sensors. You can use the quick browse list in the community – created wiki, look in the project reports section, and look under security to see what some other people have done.
http://thingsthataresmart.wiki/index.php?title=How_to_Quick_Browse_the_Community-Created_SmartApps_Forum_Section
Alternatively, if your alarm system can send an email or a text, you could have that go to IFTTT as the “if” in an applet and have smartthings turn on a virtual switch as the “that.” Then have SmartThings respond to that switch coming on. this can work quite well, it is easy to set up, and doesn’t require any additional devices, but it may introduce some lag because of the time it takes IFTTT to respond to and process the trigger event.
There are some other more Rube Goldberg approaches, but I think these are the most straightforward.
One) put the two zwave controllers on the same network, have one turn on the switch and have the other respond to the switch turning on. Whether this will not work or not depends on the exact features of each controller.
Two) use a bridge device to monitor electrical activity on one system and report it to the other
(updated to add as @geko notes above, this could be as simple as wiring an open/close sensor on the SmartThings network to a device on the lynx network)
- if both controllers have an IFTTT channel/service, use it. If only one does ( and SmartThings does), see if the one that doesn’t could send email or text to IFTTT instead.