So I’ve taken the plunge and setup a Mosquito MQTT broker on an old Raspberry pi.
Currently in pack of an edge driver, using TAustin’s MQTT device creator seems to get all the old functionality back (nearly*), including child devices for each of the sensors. The Alarm device created can be synced to ST’s Home monitor (STHM) by setting simple automations, so you get a nice well integrated interface within the app, and additional automation options.
In order to make this work, first get yourself a permanently installed mosquito broker (I actually tested the whole thing using a Broker App on my phone), then install @TAustin’s great MQTT device creator from this thread, get ST to create the device by running “add device”, and use it to create an Alarm panel and a device for each of your sensors.
For each of these devices you need to setup a topic to listen to
Panel (listen): alarm/panel
Panel (set): alarm/set
Zones: alarm/zone1, alarm/zone2 etc…
And, configure the topic values for each state of the device.
For example, here’s the interface of the panel:
And here’s the relevant settings:
Here’s a movement sensor:
And it’s settings:
The only thing that unfortunately doesn’t work out of the box is actually setting the alarm from the created panel. The device has the ability to both listen to a topic to change its state, and update a different topic to publish a state, but the values published for listen/publish are expected to be the same, and the wemo device is configured to publish “siren”, “strobe”, “off”, but listen to “AlarmArm”,“Disarm” etc.
@cjcharles I see in the past you were able to make some adaptations to the topic values… Any chance you still have this set up and could make the change so topics values match?
Any other suggestion?