Develco Smoke Alarm SMSZB-120 how to trigger Siren using a command topic?

Setup, Configuration and Use Beginners
,
1

*Pi,Debian,zigbee2mqtt
Hi…
Total Newbie…
I have a Develco Smoke Alarm SMSZB-120 that’s on the list of supported devices of zigbee2mqtt…
I have had no trouble getting it integrated…
But I’m more or less clueless on how to trigger the siren…
zigbee2mqtt support site states this…

Triggering alarm
This smoke alarm can be triggered manually by sending these commands to it:
To start (Change duration to what you need):

  • {"warning": {"mode": "burglar", "level": "high", "strobe": false, "duration": 300}}
    To stop:
  • {"warning": {"mode": "stop", "level": "low", "strobe": false, "duration": 300}}

But I have no clue on how to send all theese commands at once ?
I guess I would put it in my rule below some where…

rule “Movement”
when

Item IRSensor1 changed to ON or
Item IRSensor2 changed to ON or
Item HueMotionSensorGang_Motion_Presence changed to ON or
Item Door_Sensor_Gang changed to OPEN or
Item Door_Sensor_Livingroom changed to OPEN

then
if(SystemStarting.state == OFF) {

	if (AlarmSikring.state == ON) {
		logInfo("MySteet","Alarm - Movement!")
		sendNotification("Myemail@gmail.com","ALARM - Movement")
				
	}
}

end

Thanks!!

2

Don’t look at it as “all these commands”. It’s just one string.

A simple way is to link a String Item to an MQTT channel with the commandTopic you need, and send the whole string to your Item as a command.

3

Still no luck, but i think there might be a general issue with zigbee2mqtt and this device
Look here…

I’ve tried alot since… The even more strange thing is that the interview goes fine and the device report no errors in the log untill i turn the “permit join” value from true to false and restart the zigbeetomqtt…

Jun 08 15:29:26 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:26: Device ‘0x0015bc00310022aa’ joined
Jun 08 15:29:26 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:26: Starting interview of ‘0x0015bc00310022aa’
Jun 08 15:29:26 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:26: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“device_connected”,“message”:{“friendly_name”:“0x0015bc00310022aa”}}’
Jun 08 15:29:26 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:26: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“pairing”,“message”:“interview_started”,“meta”:{“friendly_name”:“0x0015bc00310022aa”}}’
Jun 08 15:29:27 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:27: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“device_announced”,“message”:“announce”,“meta”:{“friendly_name”:“0x0015bc00310022aa”}}’
Jun 08 15:29:52 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:52: MQTT publish: topic ‘zigbee2mqtt/0x0015bc00310022aa’, payload ‘{“voltage”:3000,“battery_low”:false,“linkquality”:49,“enrolled”:false,“smoke”:false,“tamper”:false,“supervision_reports”:true,“restore_reports”:true,“trouble”:false,“ac_status”:false}’
Jun 08 15:29:53 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:53: Successfully interviewed ‘0x0015bc00310022aa’, device has successfully been paired
Jun 08 15:29:53 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:53: Device ‘0x0015bc00310022aa’ is supported, identified as: Develco Smoke detector with siren (SMSZB-120)
Jun 08 15:29:53 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:29:53: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{“type”:“pairing”,“message”:“interview_successful”,“meta”:{“friendly_name”:“0x0015bc00310022aa”,“model”:“SMSZB-120”,“vendor”:“Develco”,“description”:“Smoke detector with siren”,“supported”:true}}’
Jun 08 15:34:48 JIPI npm[6815]: zigbee2mqtt:info 2020-06-08 15:34:48: MQTT publish: topic ‘zigbee2mqtt/0x0015bc00310022aa’, payload ‘{“voltage”:3000,“battery_low”:false,“linkquality”:42,“enrolled”:false,“smoke”:false,“tamper”:false,“supervision_reports”:true,“restore_reports”:true,“trouble”:false,“ac_status”:false}’

And after I set the Join option to false:
Jun 08 23:05:00 JIPI npm[23926]: zigbee2mqtt:error 2020-06-08 23:05:00: Failed to configure ‘0x0015bc00310022aa’, attempt 3 (Error: ConfigureReporting 0x0015bc00310022aa/35 genPowerCfg([{“attribute”:“batteryPercentageRemaining”,“minimumReportInterval”:3600,“maximumReportInterval”:62000,“reportableChange”:0}], {“timeout”:10000,“manufacturerCode”:null,“disableDefaultResponse”:true}) failed (Error: Status ‘UNSUPPORTED_ATTRIBUTE’)

Also tried to send the message as written while the join was enabled but still no alarm.
pi@JIPI:~ $ mosquitto_pub -t “zigbee2mqtt/0x0015bc00310022aa/35” -m “{“warning”:{“mode”:“burglar”,“level”:“high”,“strobe”:false,“duration”:300}}” -d
Client mosqpub|8650-JIPI sending CONNECT
Client mosqpub|8650-JIPI received CONNACK (0)
Client mosqpub|8650-JIPI sending PUBLISH (d0, q0, r0, m1, ‘zigbee2mqtt/0x0015bc00310022aa/35’, … (61 bytes))
Client mosqpub|8650-JIPI sending DISCONNECT

No success…
Any other suggestions on where to go from here ?

4

Hey
Just wanted to let you know that i got i to work. For now just as an on/off thing, but I will integrate it in my survailance rules…

The on of switch channel is configured like this.

image
image1074×527 46.5 KB

1 Like
5

wanted to let you know : just received the same Develco Smoke Alarm :slight_smile:
for Zigbee, I’m using an Ember EM35x Coordinator (bitronvideo)

Pairing the smoke alarm went without any problems : these channel are visible : Switch,Warning Device,Tamper,Battery Alarm,Low Battery,Battery Voltage,Fire Alarm,Binary Input,Temperature

I managed to trigger the alarm within a rule (just an experiment, triggering at a certain hour) :

rule “alarm on”
when
Time cron “0 23 15 ? * * *”
then
SmokeAlarm_WarningDevice.sendCommand(“type=warning useStrobe=true warningMode=BURGLAR sirenLevel=HIGH duration=PT30S”)
end

as described in the openhab manual : https://www.openhab.org/addons/bindings/zigbee/#warning-devices

1 Like
6

I have a question for the ones that own this device:
where did you get it from?
I only found a sample ordering form where they charge enormous amounts of money for shipping and handling…

7

I got from a Danish store “El-Giganten” where it was re-branded as a Wattle device😎

1 Like
8

Sorry for late reply, was not monitoring this thread : i got mine at : https://en.cozify.fi/
very fast delivery (± 2days)

1 Like