Oke good!. Have you tried to excluding and re-including the device already? You can also remove your node from the zwcfg_0x???.xml file and restart domoticz.

My patch has been merged. So false fire alerts after a Domoticz restart should be gone.

I don't think so, but since I don't own one I am no expert

Well Domoticz support two different ZWave implementations, Razberry Z-Wave via LAN interface and OpenZWave via USB.
The first one is via Rasberry with a Z-Wave addon board(z-way). The second is via a Z-Wave USB dongle like Aeotec Z-Stick-S2 or Vision ZU1401 USB stick.
So witch one are you using?

Ok, so this one I can explain, as I did earlier: After Domoticz starts up it will retrieve the current settings on the device . This will trigger an alarm. Most times it takes two wakup intervals to retrieve all settings. So If your wakup interval is 6 hours, expect an fire alarm anywhere between 0 ...

I was expecting something like this: 2015-08-07 17:55:25.874 Info, Node044, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Smoke event:254, status=255 2015-08-07 17:55:25.874 Detail, Node044, Initial read of value 2015-08-07 17:55:25.874 Detail, Node044, Initial read of value 2015-08-07 ...

Be sure to enable the debug flag on the controller (setup->hardware->Setup on OpenZWave USB) -> select your controller -> 2. Enable Debug -> set to 1 & apply)

Changing this will restart OZW.

After Domoticz starts up it will retrieve the current settings on the device . This will trigger an alarm. Most times it takes two wakup intervals to retrieve all settings. So If your wakup interval is 6 hours, expect an fire alarm anywhere between 0-12 hours after a domoticz restart. But to be sure ...

My guess is that the smoke sensor send a periodic test alarm, which is not interpreted correctly by Domoticz.
In your OZW_Log.txt you will see a Alarm report with a event code 3, meaning "Smoke Alarm Test"

Event codes have different meaning depending on the type of alarm.

Thanks for testing. I have submitted the change to OpenZwave. Once accepted it will find its way back into Domoticz.

Seems like the OZW config is not quite right. Egregius (or any one that has a ZMNHBA2) could you test the following please? Add the following to Config/qubino/ZMNHBA2.xml <!-- Map endpoints to instances --> <CommandClass id="96" mapping="endpoints" /> Remove the zwcfg_0x???.xml file, start domoticz ...

The configuration has been submitted to OZW (see https://github.com/OpenZWave/open-zwave/pull/640)
(If you have copied an earlier version, please update.)

I am using the dimmer in a 3-wire setup with a 9.5W led bulb. Works like a charm.

Hi Elektrotek, as many others I also have a FGBS001 with 4 DS18B20 sensors and a Aeon Z-Stick USB adapter. As power supply for the FGBS001 I use an old phone charger; 9V If i remember correctly. Others have stressed this already and I will repeat, if you add/remove sensors you must exclude and re ...

Can you report the type and id info for the manufacturer_specific.xml file? And possible other issues? so I can complete the config and submit it to OZW?

mbliek wrote:Could you send me the file? So I can test it when it arrives?

Sure you can find it here https://github.com/xs4/open-zwave/blob/ ... fgd212.xml
Config section is done, just untested, I am missing the type and id info to identify the device in the manufacturer_specific.xml file.

To be clear you are using Razberry aka z-way. Not openzwave?
In that case your out of luck since z-way does not support MultiChannel. Switch to OpenZwave which does support MultiChannel.

Yes it will, I have got the configuration already done, just waiting for the actual device to be delivered so I can test it and submit it to OZW.