Domoticz

Hi,

I'm trying to get a Popp CO Detector working... It works in the Zwave.Me software from the Razberry manufactor, but not yet in Domoticz.
There are hardly any Carbon Monoxide sensors on the market, so this is my only chance!

First try

No additional xml file, Z-wave working.
Domoticz devices screen shows a POPP CO switch
Question 1: I would expect a meter or sensor, not only switches, because Zwave shows a sensor displaying a value in mol/m3. Why is this?

Question 2: Off course, I can overrule it to be a readonly sensor, but not change it into a value measuring mol/m3 CO. Is there a way to do this?

Question 3: I would expect an on/off value, not a %. Why is this a %?

Strangly, the underlying OZWP software shows what I'd expect: Question 3: Why does the underlying software shows the correct values/configuration, and Domoticz not?

Second try

Now I'm using the XML file given by the manufactor (see attachement), removed zwcfg_xxxx.xml, excluded and included the device.
Rasperry Pi3, Domoticz 3.5837, Aeon Multisensor 6, Popp CO Detector 7704.

Still the same problems... what's going on

Hopefully anyone can help...!
Thanks in advance!
[Domoticz 3.5837, Razberry, Raspian, Aeontec Multisensor 6, Popp CO detector 4407]

Hi,

Did you have any progress on this topic? I also want to buy this CO sensor.

me3

anyone got it working?

A new updated config file has been added 2 days ago in the beta.
Can you verify if above problems are still there?

Greetz YcKe

I see: https://github.com/domoticz/domoticz/co ... a7dd097c0e

I'm going to take the risk now and buy one, will report back...

//edit
Upgraded Domoticz to the latest beta just now and ordered the sensor, should arrive monday

Hmmmmm I am unable to even include it in my Z-Wave network... nothing happens at the Domoticz end. When I press the button on the sensor it flashes green a couple of times, thats it.

I did include a Fibaro smoke sensor today so that part is working...

With the september 2017 release v3.8153, Domotics is doing a bit better. It is usable right now, still not perfect.

• The test button now generates a signal on the main sensor (test button did not give any signal before). You could now define notifications or rules based on them.

• The burglar alarm does work.

• Still missing is the current CO value. Although this may not be precise, it is handy to define advanced rules with a e.g. a very prelimanary warning.

I'm planning to test this with a few candles and a in a box, to do the real thing and trying to use another XML file.
Keep you updated!

Also the real test with candles and the Popp CO Detector in a closed box generates a real Domoticz alarm! That makes this sensors usable, although still not perfect.

The first alarm fase (only a red flashing light) generates NO sensor message/alarm.
The second alarm phase (red flashing light + loud beep) does generate a SENSOR signal. A notifaction was indeed sent.

Popp support confirms that reading the CO value (mol/m3) is just an indication. This value is not readable in Domoticz, but that is no big deal apparantly. (Other systems, like OpenHab for instance, can indeed see the value.) The only thing you can count on is the alarm, which works just as I describe in my post above. This is a pitty, as you can not use this sensor to act in an early way, for example to switch off the heating before anything gets dangerous. Popp says they do not plan any Z-wave firmware update to fix that. I thing they miss an opportunity here, as this is one of the few in Euope available Z-wave CO sensors.

Next time we should buy this one then: https://www.fibaro.com/en/products/co-sensor/

Why can OpenHAB see the value but Domoticz does not? This implies that something is wrong at the Domoticz side not?