This feature has been sitting there for a while (since 2024-01-16), although I just discovered its great power and thought it may help someone else. For a long time I was wondering why can’t I trigger my siren via Satel integration. It’s a standard fire/burglary output function, so I thought there is either something wrong with my configuration or integration. Finally, I got back to it and want to share the outcome with you:
Not being able to trigger the siren is in fact protocol limitation by Satel. But I also found a neat workaround! Since there are not that many informations around the internet and Satel helpdesk is not that helpful (same as their docs), let me sum it up:
1. Satel protocol
Satel protocol is able to switch only MONO/BI switches but not Siren (fire/burglary function). Some leads are mentioned here and here:
It depends on the outputfunction of the output.
If your using outputfunction 1:burglary , these are not allowed to control directly thru homey.
But if you e.g. using outputfunction 25:make/break these can control thru homey.
24. MONO switch, 25. BI switch, 105. Roller shutter up, 106. Roller shutter down and 64~79 Remote switch outputs!
2. IP zones to the rescue!
IP zone is a new feature that allows ETHM-1 to spin up a server that listens for a phrase on a specific port and by calling this endpoint you can actually violate a zone. It is originally meant for IP cameras that support Alarm Server with HTTP Alarm transmission. This is all you need:
- integra fw >
1.23, ethm-1 plus fw >2.12. (tested with 1.23, 2.12) DISCLAIMER: Upgrade on your own risk! - new zone with wiring other than
0: no detectorand8: follow output(note down zone number!) - assign zone to some object/partition (depending on your case)
- create IP zone in ETHM-1 - pick a suitable port, use zone number and generate a phrase
3. HomeAssistant integration
ETHM endpoint accepts any request (I tested json/xml/text, also different methods get/post/put…), but generated phrase suggests it should be a part of url http://[ethm_ip]:[ip_zone_port]/phrase. All these still result in a socket hang up error, however the zone gets violated. There are more ways, but I used rest_command integration with url and post method.
due to the response error, don’t forget to add continue_on_error: true to your action call.
Arm your partition, bind the rest_command to any IoT device state change and when it changes the state, Siren is triggered 
4. ![:bulb:]( ":bulb:")
Security TIP
Security TIPSince ETHM protocol requires a user code only for switchable outputs, the best you can do is to create a separate user (via DLOADX) with authority only for BI & Mono outputs rather than sharing your code that you use to arm your system.
1 post - 1 participant