Xiaomi MiJia Honeywell smoke detector as a alarm Sierene #420

dr-apple · 2018-09-28T12:08:28Z

Hi ich have the Xiaomi MiJia Honeywell smoke detector and it work fine.

Can i controll via Zigbee the Xiaomi MiJia Honeywell smoke detector for put the alarm Sirene /beep turn on / off ?

cu Danny

tb-killa · 2018-09-28T12:21:55Z

Hi actually no..

stale · 2018-11-27T12:42:40Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

JellevdK · 2018-11-29T09:05:07Z

Nice idea, this will also create the 'linking' method, just as which is possible with the Xiaomi GW.

HannesG79 · 2018-11-29T13:58:29Z

Hi, that would be a good Option, if you have a false Alarm. The acknowledge button is small. and you can use it as Alarm as well.

sascha777 · 2019-01-02T08:28:25Z

I would also be interested in an alarm function with the smoke detectors.
Is someone trying to get this going? I don't have a gateway and sniffing knowledge but could help testing on several smoke detectors...

arneeichhorn · 2019-01-16T14:35:56Z

I would also love to see this feature.
Would be super nice to "link" the detectors to each other with this feature and also to use them as sirens in use with motion sensors and/or door contacts.
I read that it should also be possible to set sensitivity for the detection with the original GW? Just like its done for the Gas Detector, that supports selftest and sensitivity settings via zigbee2mqtt

neerdoc · 2019-01-27T20:26:12Z

I had the same idea but I have a Heiman HS1SA smoke detector. I can test the functionality on that but I need some pointers to get started.

When registering my smoke detectors I noticed that they seem to accept the ssIasWd specification which I believe could be used for this purpose. However, I have no idea on how to send such a message to the device. I assume I need to define the message in the toZigbee.js file in the shepherd-converters, but I have no clue on how to trigger it.

Anyone have any suggestions?

Koenkk · 2019-01-28T07:03:48Z

In order to support such feature we need to check what the original gateway sends (https://github.com/Koenkk/zigbee2mqtt/blob/dev/docs/how_tos/how_to_sniff_zigbee_traffic.md). Then it's indeed just a matter of adding a new toZigbee converter.

neerdoc · 2019-01-28T20:16:47Z

Ok, since I am on a Mac, I could not follow those instructions.
I did find these instructions instead that I followed. Don't know if it gives what we need, so please let me know. Pasted it here.

Koenkk · 2019-01-29T10:22:30Z

@neerdoc I don't see the cluster and command being send (that's what we need in order to support this).

neerdoc · 2019-01-29T19:30:42Z

Managed to get the data into WireShark, but there are literary thousands of entries after 60 seconds of data during one join. Exactly which frame to you need?

neerdoc · 2019-01-29T21:45:15Z

Reading the Zigbee standard it seems that this should indeed work:

The IAS WD cluster provides an interface to the functionality of any Warning Device equipment of the IAS system. Using this cluster, a ZigBee enabled CIE device can access a ZigBee enabled IAS WD device and issue alarm warning indications (siren, strobe lighting, etc.) when a system alarm condition is detected (according to [N1])

The following definition is in the standard:

Cluster Identifier = 0x0502
Command Identifier
- Start Warning = 0x00
- Squak = 0x01

After that it gets very detailed on what to send in the payload. It is all defined in chapter 8.4.1 in the specification.

Are there any instructions on how I can trigger a message in the "toZigbee.js" from the command line? (Like pushing a certain button on the keyboard.) If so, maybe I can try to implement this message myself.

Koenkk · 2019-01-30T17:22:25Z

@neerdoc the easiest way to try this is by using an MQTT client (e.g. MQTT.fx).

Add a toZigbee converter with a key (e.g. key: ['alarm'],).
Add this toZigbee converter to your device in devices.js
Send an MQTT command to zigbee2mqtt/[DEVICE_ID]/set with payload {"alert":""}
This will trigger the code of your toZigbee converter.

neerdoc · 2019-01-30T20:12:40Z

Thanks @Koenkk, I got so far that I can trigger the message now! Unfortunately, the message fails to be received it seems. I will continue later, but it is a bit tricky to understand exactly what message is sent through all the layers of npm_modules... It seems very clear what I need to send in the Zigbee standard; it is very unclear how I achieve this.

Current error message:
zigbee2mqtt:error 1/30/2019, 9:07:46 PM Zigbee publish to device '0x005043c91f292a8f', ssIasWd - startWarning - {"startwarninginfo":2,"warningduration":2} - {"manufSpec":0,"disDefaultRsp":0} - null failed with error Error: AF data request fails, status code: 240. MAC transaction expired.

Koenkk · 2019-01-31T18:26:28Z

@neerdoc that looks like the correct payload. However the easiest way to solve this is to compare what is send by the original gateway with what is send with zigbee2mqtt.

neerdoc · 2019-01-31T22:14:24Z

Unfortunately, I do not have any gateway except for the CC2531... :)

Debugging some more. After hacking around in the zcl_packet lib, I got it to send this message:
cc-znp:SREQ --> AF:dataRequest, { dstaddr: 10751, destendpoint: 1, srcendpoint: 1, clusterid: 1282, transid: 6, options: 48, radius: 30, len: 8, data: <Buffer 01 07 00 22 02 00 00 00> } +1s

which I believe is very close to what I need. According to the specification, the iasWD definition (cluster id 1285 (or 0x502)) should be: 00 22 02 00 00 00 for a 2 second alert at high level without strobe. Nothing happens, but as you can see, there are an 01 07 in front of the actual message. The 07 also seems to be random (or maybe counting, a bit hard to determine). I do not know where these are generated (and to be totally honest I don't know if they are the problem either).

I actually get a response from the device on this message:
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1282, srcaddr: 10751, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, securityuse: 0, timestamp: 10220817, transseqnumber: 0, len: 5, data: <Buffer 18 06 0b 00 00> } +1ms

Any hints on whether those two bytes are the problem or not is appreciated!

neerdoc · 2019-01-31T22:20:07Z

Unfortunately, I only have the CC2531 as a gateway ;)

Debugging some more. After hacking some in the zcl-packet library, I managed to send the following message:
cc-znp:SREQ --> AF:dataRequest, { dstaddr: 10751, destendpoint: 1, srcendpoint: 1, clusterid: 1282, transid: 5, options: 48, radius: 30, len: 8, data: <Buffer 01 06 00 22 02 00 00 00> } +6s

Now this is very close to the specification. To make the alarm to a high level 2 second siren, I should send the message "00 22 02 00 00 00". As you can see, it is correct except the first two bytes (01 06) which I cannot figure out where they are coming from or how to change. The second byte also seems to change if I repeat the message.

I actually even get a response from the device (though I have not decoded what it means yet...):
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1282, srcaddr: 10751, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, securityuse: 0, timestamp: 10220817, transseqnumber: 0, len: 5, data: <Buffer 18 06 0b 00 00> } +1ms

Any ideas on if those two bytes is the problem?

Koenkk · 2019-02-02T13:17:48Z

@neerdoc how does the rawPayload look like? https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L30

neerdoc · 2019-02-05T17:49:21Z

Been busy for a few days, but now I had the time:
zigbee-shepherd:af <Buffer 01 02 00 22 02 00 00 00> +0ms

So it seems to be the same problem. The first "01 02" should not be there (I think).

Koenkk · 2019-02-06T18:59:58Z

The frame is constructed here: https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L346

Can you add console.log(frameCntl, manufCode, seqNum, cmd, zclData, cId) there?

sascha777 · 2019-02-17T07:04:40Z

@neerdoc it’s really great to see that you are working on the alarm message for the Honeywell Mijia smoke sensor!!
Did you find out how to adress the siren in the payload?

Stefan300381 · 2019-02-25T10:41:33Z

hi all, I joined this game lately and maybe you can help me to help you. If you need the original gateway, I own one :-) Anything I should do?

Stefan300381 · 2019-03-14T10:54:52Z

hi, me again. From reading the information above, is it correct to say that in case of fire, only ONE smoke detector (the one that detects the fire) will give an alarm (loud sirene) and the others will stay calm? This is something that can be achieved with original GW but not via zigbee2mqtt, correct?

neerdoc · 2019-03-14T13:20:40Z

Hi! Sorry for the late reply...

You are correct in the assumption that only the smoke detector that detects the smoke will sound the alarm. The intention is that all sirens should sound, or be able to do it depending on the configuration of course.

I don't know if it is possible with an original gateway, but if it is, it would be very helpful if you can test it and also log the traffic that is sent to the sirene.

The Zigbee protocol specification together with the capability that is reported by the smoke detector seems to support the notion that it should be possible.

stale · 2019-05-13T14:04:16Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

DoctorOctagonapus · 2019-05-14T10:16:48Z

I don't know if it is possible with an original gateway, but if it is, it would be very helpful if you can test it and also log the traffic that is sent to the sirene.

According to the documentation it is possible, though they call it Tandem Mode. It's only supported with the official gateway though, presumably there's some kind of payload or signal the gateway can send to the alarm to make it sound.

Koenkk · 2019-05-18T08:17:20Z

What firmware are you running?

AS137430 · 2019-05-18T09:51:12Z

The hex file from CC2531_20190425.zip taken from here

peterforeman · 2019-05-18T13:18:54Z

I'm interested in running this code so added it to my zigbee2mqtt 1.4.0 container. The smoke sensor is working/connected and I can receive messages. But same here as @AS137430: "No network route" (code 205).

Also firmware version 20190425.

Koenkk · 2019-05-19T17:31:11Z

@AS137430 at the moment that setting sensitivity fails, does the self test work?

AS137430 · 2019-05-20T01:44:14Z

@Koenkk : Self test doesn't work, sending the MQTT message doesn't sound the alarm siren anymore. And the log shows the following

5/20/2019, 9:39:06 AM - info: Zigbee publish to device '0x00158d00028785ae', ssIasZone - write - [{"attrId":65521,"dataType":35,"attrData":50397184}] - {"manufSpec":1,"disDefaultRsp":1,"manufCode":4447} - null
5/20/2019, 9:39:07 AM - error: Zigbee publish to device '0x00158d00028785ae', ssIasZone - write - [{"attrId":65521,"dataType":35,"attrData":50397184}] - {"manufSpec":1,"disDefaultRsp":1,"manufCode":4447} - null failed with error Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.
5/20/2019, 9:39:07 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.","meta":{"entity":{"ID":"0x00158d00028785ae","type":"device","friendlyName":"0x00158d00028785ae"},"message":"{\"self_test\":\"\"}"}}'

Koenkk · 2019-05-20T15:53:06Z

@AS137430 I'm not sure what is causing this, why did it work before? Do you perhaps need to wake the device by pressing a button on it?

AS137430 · 2019-05-21T04:11:15Z

The cc2531 was on an earlier version of firmware when it worked. I will flash to the earlier version to test if it works and report back the results

AS137430 · 2019-05-22T09:36:36Z

The AF code 205 error is still present with firmware: CC2531_MAX_STABILITY_20190315.zip.

VictorvandenHoven · 2019-05-29T14:01:31Z

Try with the following in toZigbee.js

JTYJ_GD_01LM_BW_self_test: {
    key: ['self_test'],
    convert: (key, value, message, type, postfix) => {
        if (type === 'set') {
            return [{
                cid: 'ssIasZone',
                cmd: 'write',
                cmdType: 'foundation',
                zclData: [{
                    attrId: 0xFFF1,
                    dataType: 0x23,
                    attrData: 0x03010000,
                }],
                cfg: cfg.xiaomi,
            }];
        }
    },
},

add to https://github.com/Koenkk/zigbee-shepherd-converters/blob/master/devices.js#L399 tz.JTYJ_GD_01LM_BW_self_test and publish to zigbee2mqtt/[DEVICE_ID]/set payload {"self_test": ""}

After doing what you suggest, zigbee2mqtt/Rookmelder3/set json payload: {"self_test": ""}
I get the following logging:

May 29 14:50:30 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:50:30 PM Received MQTT message on 'zigbee2mqtt/Rookmelder3/set' with data '{"self_test": ""}'
May 29 14:50:30 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:50:30 PM Zigbee publish to device '0x00158d00025d94f5', undefined - undefined - undefined - {"manufSpec":0,"disDefaultRsp":0} - null
May 29 14:50:30 ZIGBEE npm[14419]: **zigbee2mqtt:error 5/29/2019, 2:50:30 PM Unknown zigbee publish cmdType undefined

Any idea what to change to get it working?

When pushing the "test"-button, I get the following:

May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:32 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":{"1":3125,"3":28,"4":5032,"5":8,"6":[0,0],"8":4100,"10":38681,"100":0,"150":0}}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:32 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":39,"battery":100,"voltage":3125}'
May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:32 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"modelId":"lumi.sensor_smoke"}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:33 PM Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":0}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:33 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":39,"battery":100,"voltage":3125}'
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:33 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":{"1":3125,"3":27,"4":5032,"5":8,"6":[0,1],"8":4100,"10":38681,"100":0,"150":0}}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:33 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":36,"battery":100,"voltage":3125}'

VictorvandenHoven · 2019-05-29T19:23:58Z

Try with the following in toZigbee.js
JTYJ_GD_01LM_BW_self_test: {
    key: ['self_test'],
    convert: (key, value, message, type, postfix) => {
        if (type === 'set') {
            return [{
                cid: 'ssIasZone',
                cmd: 'write',
                cmdType: 'foundation',
                zclData: [{
                    attrId: 0xFFF1,
                    dataType: 0x23,
                    attrData: 0x03010000,
                }],
                cfg: cfg.xiaomi,
            }];
        }
    },
},
add to https://github.com/Koenkk/zigbee-shepherd-converters/blob/master/devices.js#L399 tz.JTYJ_GD_01LM_BW_self_test and publish to zigbee2mqtt/[DEVICE_ID]/set payload {"self_test": ""}
After doing what you suggest, zigbee2mqtt/Rookmelder3/set json payload: {"self_test": ""}
I get the following logging:

May 29 14:50:30 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:50:30 PM Received MQTT message on 'zigbee2mqtt/Rookmelder3/set' with data '{"self_test": ""}'
May 29 14:50:30 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:50:30 PM Zigbee publish to device '0x00158d00025d94f5', undefined - undefined - undefined - {"manufSpec":0,"disDefaultRsp":0} - null
May 29 14:50:30 ZIGBEE npm[14419]: **zigbee2mqtt:error 5/29/2019, 2:50:30 PM Unknown zigbee publish cmdType undefined

Any idea what to change to get it working?

When pushing the "test"-button, I get the following:

May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:32 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":{"1":3125,"3":28,"4":5032,"5":8,"6":[0,0],"8":4100,"10":38681,"100":0,"150":0}}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:32 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":39,"battery":100,"voltage":3125}'
May 29 14:57:32 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:32 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"modelId":"lumi.sensor_smoke"}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:33 PM Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":0}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:33 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":39,"battery":100,"voltage":3125}'
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:debug 5/29/2019, 2:57:33 PM Received zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":{"1":3125,"3":27,"4":5032,"5":8,"6":[0,1],"8":4100,"10":38681,"100":0,"150":0}}}' of device 'lumi.sensor_smoke' (0x00158d00025d94f5) of endpoint 1
May 29 14:57:33 ZIGBEE npm[14419]: zigbee2mqtt:info 5/29/2019, 2:57:33 PM MQTT publish: topic 'zigbee2mqtt/Rookmelder3', payload '{"smoke":false,"linkquality":36,"battery":100,"voltage":3125}'

After updating zigbee2mqtt to 1.4.0 I now get the following:

May 29 18:26:20 ZIGBEE npm[15706]: zigbee2mqtt:debug 5/29/2019, 6:26:20 PM Received MQTT message on 'zigbee2mqtt/0x00158d00025d94f5/set' with data '{"self_test": ""}'
May 29 18:26:20 ZIGBEE npm[15706]: zigbee2mqtt:info 5/29/2019, 6:26:20 PM Zigbee publish to device '0x00158d00025d94f5', ssIasZone - write - [{"attrId":65521,"dataType":35,"attrData":50397184}] - {"manufSpec":1,"disDefaultRsp":1,"manufCode":4447} - null
May 29 18:26:26 ZIGBEE npm[15706]: zigbee2mqtt:error 5/29/2019, 6:26:26 PM Zigbee publish to device '0x00158d00025d94f5', ssIasZone - write - [{"attrId":65521,"dataType":35,"attrData":50397184}] - {"manufSpec":1,"disDefaultRsp":1,"manufCode":4447} - null failed with error Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.
May 29 18:26:26 ZIGBEE npm[15706]: zigbee2mqtt:info 5/29/2019, 6:26:26 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.","meta":{"entity":{"ID":"0x00158d00025d94f5","type":"device","friendlyName":"Rookmelder3"},"message":"{"self_test": ""}"}}'

When pushing the test-button by hand, I do receive messages. So I suspect the message "Please confirm that the device has (re)joined the network" is not valid..........

So I suppose I have the same issue now as @AS137430.
What else to try to get self_test working?

VictorvandenHoven · 2019-05-29T19:33:59Z

After a couple of hours the alarm beep went off after setting the "self_test" message on the queue.
Did not change anything, but it seems to work now!

Next thing to try is the sensitivity.

lovethat777 · 2019-06-12T21:50:13Z

Any progress ?

klitscheIO · 2019-07-11T12:18:23Z

I could also trigger the test via MQTT. But the single beep the detector fires cannot be used as siren. It is short and not very loud. We have to find the message the original gateway sends to a second smoke detector in "tandem mode" to trigger the alarm.

I don't know if it is possible with an original gateway, but if it is, it would be very helpful if you can test it and also log the traffic that is sent to the sirene.

According to the documentation it is possible, though they call it Tandem Mode. It's only supported with the official gateway though, presumably there's some kind of payload or signal the gateway can send to the alarm to make it sound.

stale · 2019-09-09T12:41:32Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

dwainscheeren · 2019-09-24T12:19:01Z

When I try to publish the self_test I get a warning PM No converter available for 'self_test' ()

kovaga · 2019-10-31T13:19:23Z

I could also trigger the test via MQTT. But the single beep the detector fires cannot be used as siren. It is short and not very loud. We have to find the message the original gateway sends to a second smoke detector in "tandem mode" to trigger the alarm.

I don't know if it is possible with an original gateway, but if it is, it would be very helpful if you can test it and also log the traffic that is sent to the sirene.

According to the documentation it is possible, though they call it Tandem Mode. It's only supported with the official gateway though, presumably there's some kind of payload or signal the gateway can send to the alarm to make it sound.

I dont think it is possible to remotely trigger the second detector to sound the alarm. I have two connected smoke detectors, but no option in the original Xiaomi map to start the 2nd alarm when the 1st detects smoke. The "Linkage hub alarm" option allows only the Hub to sound the alarm.

And thats triggered by the ZoneStatus: 0x0001, Alarm 1

ZigBee Cluster Library Frame
Frame Control Field: Cluster-specific (0x19)
Sequence Number: 0
Command: Zone Status Change Notification (0x00)
ZoneStatus: 0x0002, Alarm 2
.... .... .... ...0 = Alarm 1: Closed or not alarmed
.... .... .... ..1. = Alarm 2: Opened or alarmed
.... .... .... .0.. = Tamper: Not tampered
.... .... .... 0... = Battery: Battery OK
.... .... ...0 .... = Supervision Reports: Does not report
.... .... ..0. .... = Restore Reports: Does not report restore
.... .... .0.. .... = Trouble: OK
.... .... 0... .... = AC (mains): AC/Mains OK
Extended Status: 0x00
Zone ID: 0xff
Delay (in quarterseconds): 0

danielo515 · 2021-10-28T10:37:52Z

How this ended? Is it possible to stop the siren? Foor me it is very hard to reach and I would love to be able to stop it using mqtt

kovaga · 2021-10-29T05:50:00Z

How this ended? Is it possible to stop the siren? Foor me it is very hard to reach and I would love to be able to stop it using mqtt

yes, it is possible to turn it off. just send "off" to it :)

i.e.
case OFF: {
// Send turn off signal if the switch was turned off
mqtt_string = '{"warning": {"mode": "off"}}'

danielo515 · 2021-10-30T16:06:05Z

Thanks or the answer. But will that disable the siren or just stop the one that is already running?

kovaga · 2021-10-31T08:30:42Z

Thanks or the answer. But will that disable the siren or just stop the one that is already running?

Not quite sure what you mean here, but basically the siren is always connected to the network.
When you set a duration and a signal to start producing a noise, there are two ways how it will stop this noise, either wait for the duration to expire or send an "off" signal. This will stop the running noise until a new command will arrivve to initiate a new one.

danielo515 · 2021-11-03T06:08:32Z

Maybe if I explain the scenario I have in mind it is easier to understand. I have the Honeywell smoke detector in my kitchen, on the ceiling. When the siren starts I'm the only one on the family tall enough to hit the button that stops it. For that reason, I want to create an automation to send the stop command to the smoke detector. But of course, if there is smoke again I want it to work, I don't want to disable it permanently. Hope my explanation makes sense now. Regards

…

On Sun, Oct 31, 2021 at 9:30 AM Konstantin Gavrilenko < ***@***.***> wrote: Thanks or the answer. But will that disable the siren or just stop the one that is already running? Not quite sure what you mean here, but basically the siren is always connected to the network. When you set a duration and a signal to start producing a noise, there are two ways how it will stop this noise, either wait for the duration to expire or send an "off" signal. This will stop the running noise until a new command will arrivve to initiate a new one. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARKJWKCD4JCLCMQLOBNZ2DUJT5DZANCNFSM4FXZROKQ> .

-- --- https://danielorodriguez.com

alanieska · 2023-03-25T11:34:07Z

hello, has anyone solved this? it happened to me that it triggered a false alarm (I looked through the camera that nothing was on fire) but unfortunately it beeped the whole time until I got home from work. Is there a way to turn this off in m2qtt? (sorry for the english, google translate)

stale bot added the stale Stale issues label Nov 27, 2018

stale bot removed the stale Stale issues label Nov 29, 2018

stale bot added the stale Stale issues label May 13, 2019

stale bot removed the stale Stale issues label May 14, 2019

b2un0 mentioned this issue May 22, 2019

Support for Develco smoke sensor dresden-elektronik/deconz-rest-plugin#1534

Closed

lovethat777 mentioned this issue Jun 17, 2019

Smoke detectors composite #1533

Closed

stale bot added the stale Stale issues label Sep 9, 2019

stale bot closed this as completed Sep 16, 2019

gonzasmts mentioned this issue Oct 10, 2019

Xiaomi MiJia Honeywell smoke detector add support for features #2113

Closed

kovaga mentioned this issue Nov 7, 2019

Xiaomi MiJia Honeywell smoke detector Selftest works every 2nd attempt #2287

Closed

redeyejoe mentioned this issue Aug 19, 2020

Using Xiaomi Smoke Alarm as a Siren for alarm system w Home Assistant #4133

Closed

manup mentioned this issue Nov 22, 2020

Xiaomi Mijia (HonneyWell) smoke detector self test and sensitivity dresden-elektronik/deconz-rest-plugin#2954

Open

Xiaomi MiJia Honeywell smoke detector as a alarm Sierene #420

Xiaomi MiJia Honeywell smoke detector as a alarm Sierene #420

Comments

dr-apple commented Sep 28, 2018

tb-killa commented Sep 28, 2018

stale bot commented Nov 27, 2018

JellevdK commented Nov 29, 2018

HannesG79 commented Nov 29, 2018

sascha777 commented Jan 2, 2019

arneeichhorn commented Jan 16, 2019

neerdoc commented Jan 27, 2019

Koenkk commented Jan 28, 2019

neerdoc commented Jan 28, 2019

Koenkk commented Jan 29, 2019

neerdoc commented Jan 29, 2019

neerdoc commented Jan 29, 2019

Koenkk commented Jan 30, 2019 • edited Loading

neerdoc commented Jan 30, 2019

Koenkk commented Jan 31, 2019

neerdoc commented Jan 31, 2019

neerdoc commented Jan 31, 2019

Koenkk commented Feb 2, 2019

neerdoc commented Feb 5, 2019

Koenkk commented Feb 6, 2019

sascha777 commented Feb 17, 2019 • edited Loading

Stefan300381 commented Feb 25, 2019

Stefan300381 commented Mar 14, 2019

neerdoc commented Mar 14, 2019

stale bot commented May 13, 2019

DoctorOctagonapus commented May 14, 2019

Koenkk commented May 18, 2019

AS137430 commented May 18, 2019

peterforeman commented May 18, 2019

Koenkk commented May 19, 2019

AS137430 commented May 20, 2019

Koenkk commented May 20, 2019

AS137430 commented May 21, 2019

AS137430 commented May 22, 2019

VictorvandenHoven commented May 29, 2019

VictorvandenHoven commented May 29, 2019 • edited Loading

VictorvandenHoven commented May 29, 2019

lovethat777 commented Jun 12, 2019

klitscheIO commented Jul 11, 2019

stale bot commented Sep 9, 2019

dwainscheeren commented Sep 24, 2019

kovaga commented Oct 31, 2019 • edited Loading

danielo515 commented Oct 28, 2021

kovaga commented Oct 29, 2021

danielo515 commented Oct 30, 2021

kovaga commented Oct 31, 2021

danielo515 commented Nov 3, 2021 via email

alanieska commented Mar 25, 2023

Koenkk commented Jan 30, 2019 •

edited

Loading

sascha777 commented Feb 17, 2019 •

edited

Loading

VictorvandenHoven commented May 29, 2019 •

edited

Loading

kovaga commented Oct 31, 2019 •

edited

Loading