Siren Output

[rodime]

Monitor

[rodime]

Hi Chiu,
I created a dummy zone on Partition 1 and also did a full system write rather than selective and now both the Set/Unset Status Output and Siren Output on Partition 0 are working.
The use case is twofold - 1. controlling the siren from Samsung Smartthings and also from Amazon Alexa via a Smartthings skill.  And vice versa - so that Comfort siren trigger also triggers Smartthings managed alerts - push notifications, sirens etc.  2. controlling Arm/Disarm from Smartthings to Comfort and vice versa.
I\'ve now achieved both using two Shelly 1 relays (£17 each) which are dry contact, remote (zigbee, zwave, wifi, MQTT etc) and also externally switched 12v relays.  The dry contact relay is attached to an input zone for each relay, one for Siren/Strobe, one for Arm.  
On remote triggering of each relay, the corresponding input zone is triggered with a response to trigger on or off the siren and arm or disarm Comfort, separately.  I\'m using four simple responses, two for each relay, and a flag for the Siren status to also reflect in a simple \'Siren\' toggle switch in the Comfort ios app.  The difficulty I was having was reflecting the Siren and Arm status from Comfort to Smartthings triggered via an Output zone to the external input switch on each relay.  Hence the desired use of the Status Output and Siren Output events.  That is all now working perfectly.
I realise there are multiple other ways to do this, but this appears to be the simplest and most straightforward and lowest cost, as a catch all for all siren and arm events.  From a Smartthings perspective we are only interested in triggering Away mode remotely on Smartthings security set and of course being able to then set security off via the Comfort keypad and hence then also disarm security in Smartthings.
This basically allows for a hybrid but somewhat synchronised system of older comfort controlled security and newer Smartthings compatible components and control.  With a much louder and more resilient Comfort controlled siren than the feeble Arlo doorcam alarm in play .  It\'s not perfect, can\'t (currently) tell specific zone triggers in Smartthings, but incredibly useful nonetheless.  You could of course go further with relays on each zone though.   Indeed this method of hybrid control will work with any Smarthub as the Shelly Switches are pretty much universally standards based.  
Thanks again for your helpMike

[slychiu]

Thanks for the info on this interesting use of shelly relays. 
I suspect that the status outputs are working because of the full write, not adding a dummy zone in partition 1. Partition 1 zones should only allow partition 0 siren output to work.

anyway this is a good example of the user of the Status Outputs in Comfigurator which can be very useful

[rodime]

For testing, I was using responses triggered in Comfigurator. What I observed was that Comfigurator sometimes does not react with realtime status to the event, including setting of outputs.

For example, executing the response to arm from inside Comfigurator would trigger the response and arm but on occasion, whilst I could hear the countdown beeps on the speaker, the arm delay countdown was not displaying in the status bar in Comfigurator. When that occurred, the corresponding set/unset output was also not being triggered in the output status monitor which remained off. If I then ‘refreshed’ Comfigurator through a system information call to comfort, and tried again, the arm delay would now display a countdown in Comfigurator status bar and the output status monitor would also trigger. This anomaly seemed random, but each time a system information call would seem to resolve it. Curiously, with this behaviour, it wasn’t just a failure to display the output status in Comfigurator, the actual output also did not trigger.

Away from Comfigurator, testing the responses with keypad arm events, and siren triggering events, I’ve so far not experienced any issues with the outputs being set correctly, so it does seem that the issue was related to Comfigurator somehow.

I’m using Comfogurator 3.14.14.0

[slychiu]

Comfigurator may be slow to update the changes maybe because of tooo many rs485 mesages being reporte