Deconz-rest-plugin: Xiaomi Mijia (HonneyWell) smoke detector

The cluster 0x0500 indicated that this sensor is a IAS Zone, I figure therefore it's easy to support it. However question is how should the sensor be represented by the API?

Either ZHAPresence or better ZHAOpenClose or maybe a new type like ZHAAlarm?

ZHAAlarm seems the most appropriate type. There is a Gas sensor as well, and a water leakage sensor. They all could use the ZHAAlarm type I think.

Presence of smoke/gas/water, so ZHAPresence?

However question is how should the sensor be represented by the API?

Tough one. I'm not too thrilled at the prospect of supporting another half a dozen of ZHA sensor types (and corresponding CLIP sensors). On the other hand, I would want a hint through the API what kind of sensor this is. So at least, I'd want different state attributes for presence of people, smoke, gas, water. My suggestion: if there's different ZigBee device types (not that Xiaomi would care for these), use different sensor resource types; if they're all just an IAS Zone device, use a single sensor resource type.

Do you guys know if, once this detector is supported, it would be possible to control the siren from deconz?

Thought it would be really cool to use my 8 smoke detectors as sirens for my alarm... ;) (when not at home of course.. else I would scare the shit out of me in the middle of the night...)

else I would scare the shit out of me in the middle of the night

LOL. We could implement a state.scaringtheshitoutofme attribute for that.

On a more serious note, does it implement cluster _IAS WD_ (0x0502) or provide another means to turn on (and, hopefully, off) the siren over ZigBee?

does it implement cluster IAS WD (0x0502) or provide another means to turn on (and, hopefully, off) the siren over ZigBee?

It might be my lack of knowledge regarding Deconz, but I don't see any endpoints besides 01.

I hope those endpoints will show up when the detector is being supported? Or else; how can I do some more testing / debugging?

Using the MI gateway you are able to enable and reset the alarm. This should mean using Deconz it should be theoretically possible to do this as well.

Those sensors also allow testing / identifying. You can send a command witch makes the smoke detector test itself sounds a short beep, and reports it's status.

Furthermore they report their battery status.

@ebaauw I suddenly realized the Xiaomi Switches and Motion sensors are not reporting their battery levels. I know they report the battery state. How can we solve this?

I hope those endpoints will show up when the detector is being supported? Or else; how can I do some more testing / debugging?

An endpoint is like a logical device. Is has an ID (0x01) a profile (in this example ZHA or _Home Automation_) and a device type (0xffff).
An endpoint might provide multiple clusters. A cluster has a direction indicated by the colour (blue for in or server clusters; grey for out or client clusters), and a type (0x0000 for the _Basic_) cluster.
A server cluster maintains state attributes, which might be read and/or written from clients, or reported to clients, and it accepts commands. (Note: this is not the correct ZigBee terminology, but it helps me in understanding). The _Cluster Info_ panel in the deCONZ GUI shows the standard commands and attributes for known clusters (this is actually configurable in the ZCLDB file, by default /usr/share/deCONZ/zcl/general.xml).

The problem with battery-operated nodes is that they sleep most of the time, causing queries from the gateway to discover their endpoints and clusters to fail. It would seem that this sensor hasn't been fully read by deCONZ, as only the _Basic_ cluster is shown. You might want to try and open the network and press the test button (hoping this will wakeup the smoke sensor). For a motion sensor, you would wave, for a switch, you would press a button, for door sensors, you would move the magnet. If this doesn't result in more clusters being discovered, try deleting the node (select it and press DEL) and repairing it (while pressing the test button to keep it awake throughout the discovery).

Furthermore they report their battery status.

This is typically done thought the _Power Configuration_ cluster 0x0001. Then again, nothing about the Xiaomi sensors is standard.

I suddenly realized the Xiaomi Switches and Motion sensors are not reporting their battery levels.

That's because we haven't found any evidence of the sensors reporting their battery level. We have seen some non-standard messages that we haven't figured out yet (see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/138#issuecomment-325141455).

I know they report the battery state. How can we solve this?

Unless Xiaomi have open-sourced their gateway: Sniff the ZigBee communication between the Mi gateway and the sensors, reverse engineer the Mi gateway behaviour, and implement something similar in deCONZ.

@ebaauw Thanks for your explanation.
I have found some guy who appears to have reverse engineered some Xiaomi sensors.
For example the Xiaomi Motion sensor:

fingerprint profileId: "0104", deviceId: "0104", inClusters: "0000, 0003, FFFF, 0019", outClusters: "0000, 0004, 0003, 0006, 0008, 0005, 0019", manufacturer: "LUMI", model: "lumi.sensor_motion", deviceJoinName: "Xiaomi Motion"

This line shows the used (in and out? ) clusters, is this the needed info? His code seems well documented, so proberly some info could be used. I don't know exactly where to add the clusters for this sensor in the XML file though.

https://github.com/a4refillpad/Xiaomi/blob/master/devicetypes/a4refillpad/xiaomi-motion-sensor.src/xiaomi-motion-sensor.groovy

This line shows the used (in and out? ) clusters, is this the needed info? His code seems well documented, so proberly some info could be used.

This would be the needed info, but it doesn't look like any of the Xiaomi devices I've seen. My guess would be he copied these from another sensor. Or he has a very different (hardware/firmware) version.

Looking at the code it looks like he extracts the battery value from the 0x0000 message indeed.

I don't know exactly where to add the clusters for this sensor in the XML file though.

Most are in there already. The XML file is used to build the _Cluster Info_ panel; any clusters missing from the XML file will display in the GUI as unknown. As far as I know, if the clusters don't show in the GUI, the device doesn't have them and there's no way in deCONZ to add them (with the exception of correcting incomplete reads during pairing).

Unless Xiaomi have open-sourced their gateway: Sniff the ZigBee communication between the Mi gateway and the sensors, reverse engineer the Mi gateway behaviour, and implement something similar in deCONZ.

Ok. that's what I did.

I sacrificed one of my Xiaomi push buttons and flashed it into a packet sniffer. I sniffed the transport key so I'm able to sniff and see all packages :)

I've tested my push button:

Pretty nice I think!

Nice, which sniffer is that?

The hardware is a Xiaomi push button ( All Xiaomi devices have onboard ftdi pads)
Inspired by this guy:
http://faire-ca-soi-meme.fr/hack/2017/04/24/hack-xiaomi-mi-smarthome-decouverte-de-clef/

Ubiqua: https://www.ubilogix.com/
1000 Packages per capture free for 21 days.
Allows on the fly decoding and gives a pretty good inside view I think.

Now lets checkout the smoke detector in order to get them supported :)

Looks really good :)

If possible capture as many use cases and setup traffic as possible and safe the log files, maybe Wireshark can open them as well.

Yes, I can export to PCAP? (somethink like that, I believed Wireshark uses that format

Cool! What did you use to flash the button? And where did you get sniffer firmware? I take it the round black board is the late button? And the green board? Is a regular USB to serial converter or something more?

Ok, What I did:

• Started Capturing.
• Joined the smoke detector to gateway
• Set the sensitivity to "Place with no smoke"
• Set the sensitivity to "Place with little smoke"
• Set the sensitivity to "Place with smoke"
• Set the sensitivity to "Place with no smoke"
• Pressed the test button (alarm sounds + Mi home app gives push message)
• Pressed the test button again
• Pulled the battery
• Placed the battery

The image above shows the package capture ID from when I did the tests.
I exported the capute to native ubiqua format, to wireshark and new wireshark.

Xiaomi Mijia Honeywell smoke detector.zip

I tested to import the capture. The downsite of opening those in wireshark is, the data is encrypted. So I guess the best thing would be if I'd shared the capture, and my decription key so you could view them in Ubiqua?

For example the test using the button gives this info:

I think you developers could not wish for more information do you?

Inspired by this guy

Unfortunately the Excel file he captured his sniffing conclusion in doesn't show us anything new. No battery info ;-(

Cool! What did you use to flash the button? And where did you get sniffer firmware? I take it the round black board is the late button? And the green board? Is a regular USB to serial converter or something more?

The black board is the inside of the push button.
I soldered wires onto the FTDI header.
I connected those wires to my serial -> FTDI converter
Pulled down D0 in order to get the Xiaomi Push button into programming mode.
Flashed NXP sniffer sketch (JennickSniffer) included in the NXP sdk.
Started capturing

His Excel sheet is pretty useless indeed.
I will connect one of my motion sensors now and see what info comes around.

It's up to you guys to let me know how the data should be delivered.
Exporting the raw data could be done.
Exporting only relevant frames with some explanation is possible like:
After adding the motion sensor, the sensor sends this announcement:
https://pastebin.com/VSTh1dab
Or just screenshots or something like that.

For your info, I currently have:

• Xiaomi Mijia Smoke detector
• Xiaomi smart socket
• Xiaomi push butten gen. 1
• Xiaomi potion sensor gen. 1
• Xiaomi Mijia door / windows sensor (ordered, will arrive soon)

For those devices I can supply extensive debugging if wanted.

Unfortunately the Excel file he captured his sniffing conclusion in doesn't show us anything new. No battery info ;-(

I think the battery info is in the 0xff01 report send to basic cluster after an hour or so. I see this for the door/window contact sensor.

It's up to you guys to let me know how the data should be delivered.
Exporting the raw data could be done.
Exporting only relevant frames with some explanation is possible like:
After adding the motion sensor, the sensor sends this announcement:
https://pastebin.com/VSTh1dab
Or just screenshots or something like that.

The most interesting frames are the APS layer ones, like ZCL reports and commands which the gateway sends to the devices.

For your info, I currently have:

Xiaomi Mijia Smoke detector
Xiaomi smart socket
Xiaomi push butten gen. 1
Xiaomi potion sensor gen. 1
Xiaomi Mijia door / windows sensor (ordered, will arrive soon)
For those devices I can supply extensive debugging if wanted.

Xiaomi push butten gen. 1 and Xiaomi Mijia door / windows sensor are already supported.

About the round switch.
Yes, it's supported. However I did fount the following. It appears to be reporting double / triple / quad clicks. See this attached picture:

Ok. to get back on topic. I've sampled frames of all events I am aware off.
I've documented them and pasted them on pastebin.
I hope this information will provide enough information to get the smoke sensors supported :-) That's the aim of this issue.

https://pastebin.com/59rUTJKv

About the round switch.

Cool. I only have the Aqara switch (round button, square-ish outside), which doesn't send Press, only Release. I'll double-check on the 0x8000 attribute. Is it also on cluster 0x0006 (see APS header)? And a Report Attributes command (see ZCL header)? And is the Manufacturer Specific flag set? If so which Manufacturer Code is used?

Ok cool, found the battery reporting as well. Will open a new issue regarding this push button.

Added the attribute AD's and endpoints of the smoke detector to my Excel sheet.

https://tenklooster-my.sharepoint.com/personal/richard_tenklooster_net/_layouts/15/guestaccess.aspx?docid=0745e883aa555494cb8885a2d8eb48f3e&authkey=AQ08dGXdAz2r02LBPoyxdMw

I just got this smoke detector today. Does it work with deCONZ in any way right now?
Also, what do I need to press on the detector to pair it? :)

To pair you should open the network and push the button three times.

And no, the smoke detectors are not supported yet. The smart plugs and round buttons multiple press events and battery data haven’t been added yet.

Thanks rtenklooster that worked!
So right now we cannot get anything out of the the smoke detector?
I use the other Xiaomi buttons, pir and magnets to Node-Red and then to Home Assistant.

You’re welcome.
Yes it’s true.. you can’t use it until the captured addresses have been added to the xml file.

Have sniffed all packets and posted the result in an excel spreadsheet above. Feel free to give it a try, it should contain all needed info. Currently I’m way to short on time to do it myself.

The (Dresden) developers are currently focusing on other things I guess. Maybe they will find time in the near future to add my captured data in order to get the sensors fully supported. Including battery states etc. I have sacrificed one of my push buttons in order to provide them all data needed. Documented it and published the result so I’ve put my fingers crossed and hope they will find the time :-)

Documented it and published the result so I’ve put my fingers crossed and hope they will find the time :-)

Absolutely, it's not forgotten I can't provide an ETA but the sniffer logs will be used to proceed on the integration of the detector :)

Thanks rteenklooster, really nice work!! And thanks manup for hopefully integrating this detector in the not to distant future :)

@ebaauw is it possible to get the Xiaomi Smoke detector working with Homekit (Homebridge-hue Plugin)

Probably. I need to see what the sensor resource(s) look(s) like in the REST API. Homebridge-hue should issue a warning message with all the info when it encounters an unknown sensor.

I totally missed PR #310. Could some-one please post what the sensor resources for the Heiman sensors look like, so I can add support for them to homebridge-hue? Thanks.

I've got a Schwaiger smoke sensor which seems be a Heiman sensor. I posted some information about it in issue #352 , maybe this helps. Unfortunately I don't have a zigbee sniffer ...

@rtenklooster, @AntiHeld889, I've got the Xiaomi Aqara flood sensor working with deCONZ (and with homebridge-hue). It too reports alarms through the _IAS Zone_ cluster, but doesn't advertise the cluster. I think the smoke sensor could be supported in the same way. Can you test my latest PR?

I think the smoke sensor could be supported in the same way. Can you test my latest PR?

I'm still quite new to this, but I tried connecting one of my Xiaomis with 2.05.04 (which include your latest PR?), no luck. I even tried activating the alarm with a couple of blown matches, while the network was still open, to push it to transmit something, but no zhafire in the REST api.

No, the PR for the Xiaomi smoke sensor has been merged into deCONZ, but it is not included in v2.05.04. You need to wait for the next release, or compile the REST API plugin yourself (see README).

Could you please double-check on the _Node Info_ panel that the _Manufacturer Code_ is 0x1037 and that the MAC address starts with 0x00158d?

You need to open the network from the web app (or the Phoscon app). deCONZ won't create any API resources when you open the network from the GUI. When pairing the other Xiaomi devices, it's best to press/release the rest button (hole) regularly after opening the network, and then try and read the attributes of the _Basic_ cluster. Typically, they support _Manufacturer Name_, _Date Code_ and _SW Build ID_, but it takes a few attempts to read these.

Opening the network from the webapp did the trick.
When pushing the test button:

It's listed as fire instead of smoke.



So it looks great 🥇
Is it possible to set the fire state to on in order to make the sensor beep?
Like a PUT request to /sensor/id/state
fire: true?

Gave it a try but get error 400. Can imagine it's not designed to work like that. However it would be very nice to be able to sound the siren from home asistant. To extent my home assistant alarm with my 8 fire alarm's... can imagine the whole street would wake up when someone tries to break into my house in the middle of the night... 🗡

The rest api reports this:
{ "config": { "on": true, "reachable": true }, "ep": 1, "etag": "748cfe1cfdba9ee12a9db46213a286e5", "manufacturername": "LUMI", "modelid": "lumi.sensor_smoke", "name": "Fire 29", "state": { "fire": false, "lastupdated": "2018-02-19T22:26:06" }, "swversion": "20161018", "type": "ZHAFire", "uniqueid": "00:15:8d:00:01:4d:31:5c-01-0500" }

It's listed as fire instead of smoke.

That’s the name of IAS Zone Type.

Did you manage to activate the siren remotely or does it sound only when the sensor itself has an alarm?

It havent managed to activate it remotely. Haven’t tested it either.

Maybe I can give it a try tomorrow. I believe I have seen a YouTube video suggesting when connected to the same mi gateway the alarm of all smoke detectors are linked. That would suggest the functionality is there..

Time to give it a try tomorrow. Let’s make some fire and see what happens with the other sensors.

Outlook voor iOShttps://aka.ms/o0ukef downloaden

From: Erik Baauw notifications@github.com
Sent: Monday, February 19, 2018 11:48:13 PM
To: dresden-elektronik/deconz-rest-plugin
Cc: Richard; Mention
Subject: Re: [dresden-elektronik/deconz-rest-plugin] Xiaomi Mijia (HonneyWell) smoke detector (#152)

It's listed as fire instead of smoke.

That’s the name of IAS Zone Type.

Did you manage to activate the siren remotely or does it sound only when the sensor itself has an alarm?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/152#issuecomment-366820741, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGNMwi919ZT6dtPIKGRA-JnBGSDZKT0tks5tWfotgaJpZM4PH0WK.

No, the PR for the Xiaomi smoke sensor has been merged into deCONZ, but it is not included in v2.05.04. You need to wait for the next release, or compile the REST API plugin yourself (see README).

Ok. Got it working today with 2.05.05! :)

No luck activating the siren remotely for me neither. When paired to the xiaomi hub and app, it's possible to send a test signal to the siren from the app, but afaik not trigger the siren. The xiaomi hub can be configured as a repeater siren though, maybe that is what you have seen in the youtube video @rtenklooster ?

Got the same smokedetectors connected today.
Working like charm, except on turning on the sirene remotely.

That would be awesome to create your own home alarm/security system 👍

I started off by ordering one of these smoke detectors just to verify that i could get them working, and the first one i got connected right away, very nice - not sure what pattern i pressed but i remember the pairing as super easy...

3 weeks fast forward, another 10 of these devices arrives by mail, the first one i pick up i'm having some trouble pairing to deconz, after googling around for a few seconds, reading other users pairing advice in this issue, i found out it seems to pair if the button it has was pressed 3 times in a row...

All was good however :)

I seem to have hit some kind of limit for these smoke detectors in the way it is absolutely impossible for me to pair a third smoke detector, I've tried not only one but 3 different directly from the original packaging and i cannot get them to pair with deconz - the Phoscon app just says failed to add device ( and i can confirm, the rest-api did indeed not have a sensor added to it...)

Currently using 2.05.12, some not too old raspbian on the Pi 3 with a raspbee - is there anything i can do to debug this?

I've got 5 of them paired to deconz.
Took me some time but it looks like you gave to open the network en then press the button 3 times on the smoke sensor

My guess is you have reached the device limit per router. Experienced the same a while ago. There is a limited nummer of child devices per router. So adding a extra router, like a Ikea bulb or Xiaomi outlet could solve youre issues.
Outlook voor iOShttps://aka.ms/o0ukef downloaden

From: QempZor notifications@github.com
Sent: Wednesday, April 4, 2018 8:00:01 AM
To: dresden-elektronik/deconz-rest-plugin
Cc: Richard; Mention
Subject: Re: [dresden-elektronik/deconz-rest-plugin] Xiaomi Mijia (HonneyWell) smoke detector (#152)

I've got 5 of them paired to deconz.
Took me some time but it looks like you gave to open the network en then press the button 3 times on the smoke sensor

Op 3 apr. 2018 23:29 schreef Kristian Mide notifications@github.com:

I started off by ordering one of these smoke detectors just to verify that i could get them working, and the first one i got connected right away, very nice - not sure what pattern i pressed but i remember the pairing as super easy...

3 weeks fast forward, another 10 of these devices arrives by mail, the first one i pick up i'm having some trouble pairing to deconz, after googling around for a few seconds, reading other users pairing advice in this issue, i found out it seems to pair if the button it has was pressed 3 times in a row...

All was good however :)

I seem to have hit some kind of limit for these smoke detectors in the way it is absolutely impossible for me to pair a third smoke detector, I've tried not only one but 3 different directly from the original packaging and i cannot get them to pair with deconz - the Phoscon app just says failed to add device ( and i can confirm, the rest-api did indeed not have a sensor added to it...)

Currently using 2.05.12, some not too old raspbian on the Pi 3 with a raspbee - is there anything i can do to debug this?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/152#issuecomment-378405607, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiHjwmGjm1Jj6VZgwR1d9LHK2GCS7fsoks5tk-nOgaJpZM4PH0WK.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/152#issuecomment-378489383, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGNMwvTZi2849z76CSO1YewiR3l6Z_0Yks5tlGFhgaJpZM4PH0WK.

I have 5 smoke detectors connected so just keep trying. Some devices can really be a pain in the butt, my first water sensor took about 100 tries to get connected but I haven't been succesfull with the second one, must have done over 300 tries with it so far :P

@QempZor @rtenklooster @martikainen87 Thanks for your suggestions :)

Today i finally managed to add another one, it went something like this:
I tried some sensors that i was 100% sure about how should be paired - these suddenly could not pair either which made me think it must have been deCONZ that somehow didn't really open the network when it should.
An upgrade to the latest version didn't help
But, a good old hard reboot with the power token off did the trick, now im able to pair both the smoke detectors and other sensors i have laying around...

To those wondering: The xiaomi mijia smoke detectors should pair when the only button they have is pressed 3 times somewhat quickly in a row

Hello! Great work with these sensors! I added two today successfully. They are listed ny the /sensors resource and show up in HASS - however they do not show up in Phoscon app. Should they? How can I change their names/ids?

They aren't shown in Phoscon App yet but will be soon. Names can therefore currently only be changed via REST-API.

Anyone who's been able to control the siren in the smoke detectors?

@rtenklooster, do you have an Xioami gateway? If so, if you:

1. pair two smoke detectors to it
2. configure them to chime as a group
3. trigger one with smoke
4. capture the zigbee traffic

Maybe you see the messages that turns on the siren?

Btw. I'm considering buying some of these, are they present in Phoscon yet @manup, no rush, just curious?

@sveip
Haven’t tried it yet on the latest firmware for my gateway. Will give it a try ASAP. Just moved to my new home so have to find out where all my sniffers and other hardware are laying around.

@rtenklooster, fantastic, no hurry :) Would be great to be able to make all sirens chime even if only one detects smoke. I'm thinking of making a button in hass to silence all but the one(s) that have detected smoke, to easier locate the fire/smoke source.

1. configure them to chime as a group..
   As far as I know there is no grouping option. I connected two of them to the Mi gateway on the latest version, no way to make them both alarm. The only linking they offer is linking the gateway alarm itself.
   I would love this feature as well. When asleep I can't hear the smoke detector in the garage for example.

I think it's stupid they haven't implemented such functionality. Have googled on the topic, bat haven't seen any reports of such linked alarms.

Thanks for trying @rtenklooster. It's a shame it isn't supported. Maybe the only way to ever finding out if grouping is supported is to ask Xiaomi?

Reading the manual, it says "Press and hold the «Sound stop / Self-check» button for 3 seconds, after which
the red indicator will begin to flash and beeps will turn on, the alarm goes into the
simulation mode of the alarm sound;"

Do you know if there is any indication on the hub/app about this event? Maybe there is some Zigbee traffic related to it. Long shot, but maybe worth checking?

No, there is not.

Outlook voor iOShttps://aka.ms/o0ukef downloaden

Van: sveip notifications@github.com
Verzonden: dinsdag, augustus 21, 2018 2:05 PM
Aan: dresden-elektronik/deconz-rest-plugin
CC: Richard; Mention
Onderwerp: Re: [dresden-elektronik/deconz-rest-plugin] Xiaomi Mijia (HonneyWell) smoke detector (#152)

Reading the manual, it says "Press and hold the «Sound stop / Self-check» button for 3 seconds, after which
the red indicator will begin to flash and beeps will turn on, the alarm goes into the
simulation mode of the alarm sound;"

Do you know if there is any indication on the hub/app about this event? Maybe there is some Zigbee traffic related to it. Long shot, but maybe worth checking?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/152#issuecomment-414650768, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGNMwjj6RGCMVbSMuLlBz-Uu1fLncJjcks5uS_d1gaJpZM4PH0WK.

Anything new regarding the support of (XIAOMI) Honeywell LUMI smoke sensors in deconz?
I can add the sensor, but the first is not visible in Phoscon.
When I add the device in FHEM, then i only can see the battery and reachable reading. How can I check for Fire events to trigger some needful stuff in my house? I think this is not provided properly by the REST API

Hi,

I have smoke sensor. Devices is added It is not visible is Phoscon app.
Rest API reports to domoticz data like this:

when adding device:
2019-01-22 17:26:49.536 (Deconz zigbee) ###### WebSocket Data : {'id': '54', 'sensor': {'config': {'temperature': 2500, 'battery': 100, 'reachable': True, 'on': True}, 'id': '54', 'name': 'lumi.sensor_smoke', 'state': {'lowbattery': False, 'fire': False, 'lastupdated': '2019-01-22T16:26:18', 'tampered': False}, 'ep': 1, 'etag': 'b73470512b6a6b3496808bbec411e7be', 'manufacturername': 'LUMI', 'type': 'ZHAFire', 'modelid': 'lumi.sensor_smoke', 'uniqueid': '00:15:8d:00:01:db:93:f9-01-0500'}, 'uniqueid': '00:15:8d:00:01:db:93:f9-01-0500', 'e': 'added', 'r': 'sensors', 't': 'event'}

raise alarm:
2019-01-22 19:51:23.131 (Deconz zigbee) ### Update device (Deconz zigbee - lumi.sensor_smoke) : {'BatteryLevel': 100, 'sValue': '', 'nValue': 0}
2019-01-22 19:51:23.131 (Deconz zigbee - lumi.sensor_smoke) Updating device from 0:'' to have values 0:''.
clear alarm:
2019-01-22 19:51:33.846 (Deconz zigbee) ### Update device (Deconz zigbee - lumi.sensor_smoke) : {'BatteryLevel': 100, 'sValue': '', 'nValue': 0}
2019-01-22 19:51:33.846 (Deconz zigbee - lumi.sensor_smoke) Updating device from 0:'' to have values 0:''.

I can send more diagnostic data if required.

Adam

I’ve about 6 of them. They work fine and trigger events. No, you can’t see them in the app, but they are there.

Also showing properly in home assistants.

Hi,

I will check at home again.
No change. Is HA using also REST API to get data from deconz or different protocol is used?
Because for me it seems that through Rest API updates of status are not correctly send to Smanar/Domoticz-deCONZ plugin.

Adam

Oh yes, you are right. I am using FHEM, and here I had to make some adaptions to 31_HUEDevice.pm Module.
Now I get all the values as reading. I informed the maintainer of this module to get it permanently in.

Here is what I had to do: Edit Module file FHEM/31_HUEDevice.pm
After this line: $readings{state} = $state->{presence}?'motion':'nomotion' if( defined($state->{presence}) );
Insert:
$readings{state} = $state->{fire}?'fire':'nofire' if( defined($state->{fire}) );

After this line: $readings{consumption} = $state->{consumption} if( defined($state->{consumption}) );
Insert:
$readings{fire} = $state->{fire} if( defined($state->{fire}) );
$readings{tampered} = $state->{tampered} if( defined($state->{tampered}) );
$readings{lowbattery} = $state->{lowbattery}?'low':'OK' if( defined($state->{lowbattery}) );

Then you will receive events once Alarm is triggered, or test button is pressed.

So REST Plugin is working fine. It is not maintainable using Phoscon APP. So I think it is also not possible to create a chiming/alarming group when fire is detected. But it is good to see, that I can now create automations on emergency.

Waiting for group functionality from xiaomi :)

Smanar fixed issue in his plugin!

@rtenklooster, would it be possible for you to use your Xiaomi Smoke detector and gateway to sniff the zigbee traffic for the following scenarios?

1) Test alarm from the MI home app.
2) Trigger alarm with real smoke and silence the active alarm with the MI home app.

I don't think those cases were covered in your earlier captures and those would be useful features to expose via deCONZ.

I have previously used my Honeywell Smoke Sensors (Xiaomi) using the Xiaomi GW but I have now moved them to my ConBee on Hass.io using the arthoc deCONZ addon. The devices works fine (I can't see them in Phoscon but in HASS) but I can't seem to find any option for configuration? When using the Xiaomi GW I could set the sensitivity of the smoke sensors. Is this not possible using deCONZ?

The earlier trace mentioned includes a test [but not silence] ( https://pastebin.com/59rUTJKv )

The earlier trace mentioned includes a test [but not silence] ( https://pastebin.com/59rUTJKv )

Hi, you found my paste ;) This dump contais all actions possible. Including the sensitivity settings @aronsjoberg and @barnish . Currently there is no way to adjust those settings from deconz.
It would be great however to be able to adjust the sensitivity. But that's something @manup could possible fix (if he had the time ;))

Is it possible to trigger via deconz an alarm?

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.

Any chances Xiaomi / Honeywell smoke detector will be added as recognized device?

Any chances Xiaomi / Honeywell smoke detector will be added as recognized device?

The device is recognized, but it wan`t show in Phoscon.
I have it working so far good in Home Assistant.

I can’t recall the steps you have to do to get it fully functional because
it uses IAS doesn’t it?

Op vr 13 dec. 2019 om 11:52 schreef L3H0 notifications@github.com

Any chances Xiaomi / Honeywell smoke detector will be added as recognized
device?

The device is recognized, but it wan`t show in Phoscon.
I have it working so far good in Home Assistant.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/152?email_source=notifications&email_token=ABNGEKEUF3AAFCA4ASQJD4TQYNSPBA5CNFSM4DY7IWFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGZUIWY#issuecomment-565396571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNGEKCIC6H4ZHBIEATMGFDQYNSPBANCNFSM4DY7IWFA
.

You don't need to to a lot. Just press button 3 times while pairing.

Is it working correctly now with deconz?

It is working with homeassistant but not in phoscon as a sensor.

Good morning!
Any chance to integrate the smoke detectors in homebridge via the homebridge-hue plugin?
I have two of them, visible in deconz and not in the phoscon app.

Regards!
Mike

If the REST API supports them, homebridge-hue probably already exposes them to HomeKit. If not, please open an issue with homebridge-hue, attaching the full debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file).

Thansk for the very fast answer... i try to restart my homebridge and after that i can see the smoke detectors! Perfect! :)

Is it possible to trigger via deconz an alarm?

Of course not. You can't set almost anything that you can do via mi app.

Pity. Thanks

Any chances Xiaomi / Honeywell smoke detector will be added as recognized device?

Would love to get it in the app too 🙏

Is it possible to set the sensitivity using the deconz REST API?

Serious??? This is a request of aug 2017 and still not done?
I'm using now Zigbee2MQTT for this, this is really ashamed that a open source product can read the voltage, sensitivity, how much smoke and can see if the siren is going off but a product like deCONZ still CANT.

Fix ASAP

+1'ing this issue won't change anything as DE seems to fully don't care about any Xiaomi stuff.

But this sensor is supported in REST API. you can use it in domoticz or HA.

I was under the wrong impression that the webgui was part of the deconz-rest-plugin but phoscon is a separate product so my +1 is now removed.

But you can't set anything on it, just read the current state...

so what options would you like to 'set'? @andriej
isn't a smoke detector a sensor that only provides sensor data?

@RezzZ yes, but I think setting the sensitivity of a smoke detector is a essential thing - especially since both the original gateway and zigbee2mqtt support this setting.
There would also be a the self-test that can be triggered - but this may not be as important as the sensitivity.

@rezzZ this smokesensor allows to set how sensitive they are when used with xiaomi gateway/app. Fx in the kitchen you can trigger different than livingroom 🙏

Also they should be in the GUI

@RezzZ if you would kindly take a look at the issue posts above... there's everything, dump of sniffed options, options themselves - this sensor has more than just dumb 'on/off' state and you can't manage it after joining to zigbee deconz network.

Appear in Jeedom not into Phoscon App.

Suggestion for developers: Could you add the Honeywell smoke detector as a light for example? Like the Ikea USB extender. For the moment, I'm not able to delete the smoke detector thought the App.

You can use it via API, i.e. in HA.

I don't want to sound rude, but how come issue has just been closed without any comment?

I made a mistake here. Miss clicked on alt tabbing. Sorry!

Please add an option to set sensitivity and controll the siren like zigbee2mqtt did. Thanks!

@baneb5 I could give it a look, but can't promise anything. Please raise a seperate issue for that so we can flag appropriately and track. We're mixing a bit too much here. Thanks!

@baneb5 Is this something you want in phoscon? Then please open a issue in that repository: https://github.com/dresden-elektronik/phoscon-app-beta

@Mimiix That probably needs to be taken care of from here. Lemme check it first.

@baneb5 please raise a seperate issue for your request as per @Mimiix 's suggestions.
@andriej please do the same. We can move it to phoscon beta repo if required.

Guys, please note that we require infomation from your end as this isn't working out otherwise!

I really want to know what the issues are.

I dont have one, but the missing features are setting the sensitivity of the detector, and also starting the siren (I think this is some sort of test mode)

Here is some info on how it behaves in z1mqtt:
https://github.com/foz333/Xiaomi/blob/master/devicetypes/bspranger/xiaomi-mijia-honeywell-fire-detector.src/xiaomi-mijia-honeywell-fire-detector.groovy
https://github.com/Koenkk/zigbee2mqtt.io/blob/develop/docs/devices/JTYJ-GD-01LM_BW.md#sensitivity

@sveip Is this a request for Phoscon or Deconz? Either way , open a feature request for this in its appropriate place.

I want to close this issue as nobody really knows in what is up with this nomore 😂

I dont want to be rude, but this is clarely a deconz request, and the issue
has been described at least a few times in this thread. Iom it would make
much more sense renaming the issue instead of making a new one and refer to
this, since this is where all the info isif you read back a bit.

man. 15. jun. 2020 kl. 18:21 skrev Dennis D notifications@github.com:

@sveip https://github.com/sveip Is this a request for Phoscon or
Deconz? Either way , open a feature request for this in its appropriate
place.

I want to close this issue as nobody really knows in what is up with this
nomore 😂

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/152#issuecomment-644234217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLR4L565ORC5KWFE5LQXUDRWZDARANCNFSM4DY7IWFA
.

Your not rude :) Don't worry i'll be fine.

A issue since 2017 with over 108 comments is really hard to track for me whats needed 😄

@SwoopX Can you provide a list of screens what we need?

The one like at the beginning. Should show more clusters now.

I apologize if I did something wrong, but I've red whole thread, and whole thread is about the issue that I have, which is that we can not controll xiaomi smoke detector the way zigbee2mqtt can (not to mention original xiaomi gateway). It seemed logical to me to bump this thread instead of making new one, because all tecnical info is already here..

@baneb5 all good and valid. Just go ahead and raise a seperate issue for that so we have that one clear for us. No big deal.

Btw, the ability to test the sensor is already given via REST API it I read the links correctly. However, exactly the required technical details are missing since the very first screenshot depicts an incomplete join.

It is interesting to find this topic active this much again.

@SwoopX , How can I test the sensor via REST API? I could not find a way.

If I understood the request right, we also need to trigger the siren via REST API. For example, if the sensor in ROOM A is triggered, I want to trigger other sensors as well. Any ways, please let us have the link of the new thread to track the progress.

Thank you for the support.

@rtenklooster, do you still have that gear to sniff the packets? Would it be possible for you to connect one of the smoke detectors to the official Xiaomi Home Gateway, and issue a "set sensitivity" from it? And maybe also a "test siren" (terms taken out of my head, so might not match their UI.) If there are any other commands available from the Hub/app, please also those.

Guys, please. Can you just do what I've asked for? It's just 2 things: a seperate issue for each request, 1-2 screenshots and some debug output. No real need to sniff the traffic although that would be brilliant.

Once I have that info, it's just a matter of 5 mins as far as I can tell. Closing this one now.

As per request of @SwoopX I'll close this issue.