Hi,
I have also Xiaomi Mijia (HonneyWell) gas detector. It connects without any issue to Xiaomi Gateway so it work correctly. It does not connect at all to Deconz zigbee. It is not visible in Deconz graphical interface (In oposite to Xiaomi smoke sensor, which is visible in Deconz app).
How I can help to diagnoze issue?
Adam
The device is currently not supported.
Please provide the details as described here:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support
I've hit the same road block, I also have a gas detector I'd like to use.
I'd be more than happy to supply the needed details, but I have no idea where to find "Cluster Info Panel" and the rest mentioned in the link. I guess it's not via Phoscon?
For starters. Tomorrow I will buy lighter to start alarm and capture what is send by the device when alarm is raised and cleared:




This one plugs into the mains power? It looks a lot like the Heiman sensor I had on loan, also Jennic based. While detecting gas, it issues an alarm from the _IAS Zone_ cluster while making a lot of noise. Same for pressing the test button. Unfortunately, the siren cannot be activated externally.
It鈥檚 probably enough to whitelist the sensor (twice: in the sensor whitelist and in the _IAS Zone_ logic, to create the right sensor type). Could you press _Read_ on the cluster into panel so the attribute values get populated?
It's powered by 12V and comes with a mains adapter. It also have a NO set of contacts, for hard wired alarm.
To charge the battery? Or is the battery only meant as a backup when mains power is down? It鈥檚 a Zigbee router, meaning its radio is always on. I wonder how long the battery lasts.
There's no battery.
Ah, OK. Then it's "just" an external power adapter.
Basic

Ias

power

Rest is empty.
There are two push options
Is it possible to sniff traffic between xiaomi gateway and gas sensor?
PS The same options are available for smoke sensor.
Adam
OK, if you write the mac address of the RaspBee or ConBee to the _IAS_CIE_Address_ attribute (0x0010 in the _IAS Zone_ cluster), _Zone State_ should change to _Enrolled_ and you should see alarms in _Zone Status_ when pressing the test button. Be sure to protect your ears ;-)
It doesn't look like the sensitivity is exposed over Zigbee.
Hi,
should it be visible in Rest API?

It is recognized as co sensor after putting MAC as you recommended. Not enrolled
Adam
Is there any additional information required before it can be added? If so, I'd be happy to help.
I have one with the same issue, when updating the address of the Deconz Gateway in to the IAS_CIE_Address i am also unenrolled, when trying to read the reporting configuration i get the following error

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.
Hi,
Are you going to support this device? Or is it already compatible with RaspBee?
I got my new Xiaomi Mijia (HonneyWell) gas detector, it is not connecting to RaspBee. Any plan?
Any hope to get this available?
Is there any additional information required before it can be added? If so, I'd be happy to help.
+1
I have this device and Conbee II. What information needs to be provided to add support?
I also have 2 of these and Conbee 2 and also can help with info.
So any news?
hi, i also try to connect to the Gas Sensors,
when its poosibel to Help ? please contact me
Thanks
Any hope to get this available?
+1
This was working on zigbee2mqtt, maybe it's possible to get some inspiration from that code? :)
I've given up on deconz, zigbee2mqtt is being maintained much better.
Maybe, in my case it did not handle the size of my network well (+80 nodes).
On topic: If we can help in anyway to get this supported, please let us know.
I second the request and offer to help. Not a coder, but let me know if any more data is needed or so.
push Also available for any Help
@SirJMD is there also a way to set up direct bindings with zigbee2mqtt?
Hello,
Can you tell that you plan to add support for this device?
any update?
I gave up and setup zigbee2mqtt :-(
I gave up and setup zigbee2mqtt :-(
z2m on Conbee2 or C2538?
is this device supported now? i currently looking for a gas detector to buy and i would like to buy the xiaomi one
@And3rsL nope, till today this device is not supported.
It can be seen in integrations using API (like HomeAssistant) not in Phoscon.
Nor you will be able to set sensitivity as in app.
But I still recommend the sensor, I had tested it. I just hope dresden will finally wake up some day and keep up to the market...
No it is not. You are mixing gas sensor with smoke sensor which is really working like you explain.
Sorry! You're right.
I'll add it soon, should be a quick one
Very much appreciated! @SwoopX
Very nice 馃憤馃徎
At last 馃憤
I still need someone to collect me 1h of log data so I can inspect the special attribute reporting for this device.
sudo systemctl stop deconz-gui
/usr/bin/deCONZ --dbg-info=2 > xiaomi_debug
@SwoopX
I hope you find the file helpful this time. It is worth mentioning that the Gas detector is not connected to the RaspBee, because it is not supported yet.
Please let me know if there is anything else I can do.
That's perfect, thanks!! Lots of stuff in there I always wanted to get a look at.
What I actually do not see it the gas sensor as far as I can tell. You got one right?
@SwoopX I got the Gas Sensor, but it is not connected with RaspBee. When I try to connect via Phoscon App (web), it does not connect.
@alahdal I see. Will come with the next release. Do you use HA or docker? If not, you could compile a dev version of the plugin and become my lab rat ;)
It is installed on a Raspbian.
So, you might want to try the following. Would really appreciate if you could generate another debug file when you want to play with it (then use /usr/bin/deCONZ --dbg-info=2 > xiaomi_debug2 for step 5 mentioned below):
git clone https://github.com/SwoopX/deconz-rest-plugin.gitcd deconz-rest-pluginsudo systemctl stop deconz-guisudo mv /usr/share/deCONZ/zcl/general.xml /usr/share/deCONZ/zcl/bak_general.xmlsudo cp general.xml /usr/share/deCONZ/zcl/sudo systemctl start deconz-guiFor the smoke sensors, you should see 2 additional attributes in cluster 0x0500 IAS Zone. For attribute Selftest/Density, double click on it and read the value (not read config!). Please share a screenshot from that.
Now, if all wen well, you should be able to initiate selftest by writing value 03010000 to that attribite. Sensitivity should be setable with values as follows:
040100000402000004030000@SwoopX These are the screenshot for the attributes in 0x0500.


My bad, used the wrong manufacturer code. Can you try once again? Start with deleting the downloaded repository locally sudo rm -rf ./deconz-rest-plugin.
Reading Failed.
Sensitivity is read only
PS. Just to clarify, we are at the Gas detector topic not the Smoke Detector

Yes, but if I understand this correctly, it should work for both, smoke and gas. I'm not in front of my desktop to double check, but at least both attributes are offered. Did sesnitivity succeed in reading? If yes, can you share the screenshot?
From what I've read, those devices are deep sleepers, waking up only every 30 secs. So you might try a bit for reading. The node should blink blue/green when ready...
I tried to read from another sensor that is close to the RaspBee system (I thought maybe with better connection I may get different results), I got different error:


Moreover, I tried reading other basic attributes all gives the same error (reading failed), maybe something wrong with my setup?
Here is a log
xiaomi_debug2.txt
I restarted deCONZ with sudo, however, it showed all nodes without names and does not show all clusters. I will leave it for sometime and check again, I noticed the clusters are shown gradually.
Why I run as sudo? I noticed that I can read the cluster info when it is run as sudo.
If you think I am doing something wrong, please interrupt.
I have stopped deCONZ and restarted without sudo, when I tried to read attribute in basic cluster info, it worked without problem. However, for the new two new attributes, I am still getting the error shared in the last screenshot either for read or write.
Hm, maybe the 2 attributes are not required to be manufacturer specific. The additions to general.xml were the following
<attribute-set id="0xf000" description="Xiaomi specific" mfcode="0x1037">
<attribute id="0xfff0" name="Sensitivity" type="u32" access="r" required="o" mfcode="0x1037"></attribute>
<attribute id="0xfff1" name="Selftest/Density" type="u32" access="rw" required="o" mfcode="0x1037"></attribute>
</attribute-set>
You could try removing this part for the data above mfcode="0x1037" (before copying the file over) to see if that changes anything.
Btw, if you pull my repo now, support for the gas sensor is included.
@SwoopX after removing (mfcode="0x1037") from above data, I get "unsupported attribute" error.

I believe the Gas Sensor is connected now, and I could read some of its attributes. However, the item does not appear in the REST API nor discovered by Phoscon.

@alahdal Please leave the Sensitivityattribute for further tests. Have you tried to write any of the low/medium/high values yet to Selftest/density yet? If not, please do so (with and without the mfcode in general.xml). You can also test the selftest value if you're brave.
For the gas sensor to work, you need to compile my repo. Instructions are in the readme.
@SwoopX when I remove the mfcode, both attributes are not supported, hence, I cannot read or write. With the mfcode, I get the error shared earlier here where I read/write.
Hi! I'm wondering about the status of this development 馃. @SwoopX can you share what is going on?
I can't wait to try this capability in Home Assistant (for the smoke detectors!).
Thanks!
Hi! I'm wondering about the status of this development . @SwoopX can you share what is going on?
I can't wait to try this capability in Home Assistant (for the smoke detectors!).
Thanks!
Smoke sensor is working with rest api even though it is not visible in phoscon
Yes, and I'm aware of that 馃憤 . But this extra development is about having a trigger for the alarm test functionality and support for more sensors (actually the related issue is about that, but they are a combined effort with the gas detector if I understand it correct).
@DaveRuijter Is this something you want in Phoscon?
@Mimiix Slow down ;)
It either doesn't work or hasn't been tested correctly. z2m has a 30 sec delay with that. Anyway, should be able to be easily tested as mentioned above.
@SwoopX I made a clean install and I am going to try again :) and compile your repo
For the gas sensor to work, you need to compile my repo. Instructions are in the readme.
I compiled your plugin and now the Gas Sensor appears in the Rest API, very cool.
Tell me what do you want next for both the Gas and the Smoke.
On the latest beta, sensor visible in VNC.
In Home Assistant too.

Yes with @SwoopX plugin, I have the gas sensor visible in OpenHAB and tested working fine.
Closing this one as support has been provided with version .79.
Any news on support for this device?
What else would you expect?
a nice addition would be to add a toggle exposed also in HA in order to manually trigger the siren. currently in HA only a sensor is exposed
Most helpful comment
I'll add it soon, should be a quick one