2nd Fibaro Dimmer 2 (FGD212) not recognized in Domoticz

[andrehj]

Last year I bought a Qubino and a Fibaro z-wave dimmer to see which one was best. Fibaro won, so last week I bought some more.
However, Domoticz (with a Aeotec Gen5 USB stick) does not recognize this new dimmer (NodeID 008). It says unknown, although the old dimmer (NodeID 006) was recognized without issues.

Strangely both nodes (006 and 008) have the same Type, whatever that means.
Does anybody know how I can solve this issue so I can start using this dimmer?

[coenvdz]

The device has a new ID that is not yet specified in the manufacturer_specific.xml

I fixed it by manual adding this device by adding a new line in the fibaro chapter with
<Product config="fibaro/fgd212.xml" id="1001" name="FGD212 Dimmer 2" type="0102"/>

assuming the device works similar to the old o==device with id=1000.

[dami10]

The device has a new ID that is not yet specified in the manufacturer_specific.xml

I fixed it by manual adding this device by adding a new line in the fibaro chapter with
<Product config="fibaro/fgd212.xml" id="1001" name="FGD212 Dimmer 2" type="0102"/>

assuming the device works similar to the old o==device with id=1000.

many thanks!

[hugoleij]

Hi,

I'm running domticz in docker, where can edit it? i dont have a manufacturer_specific in my config.

Config folder:

Code: Select all

ozwcache_0xda245848 dot xml
ozwcache_0xf18450ff dot xml
ozwcache_0xf20d7de6 dot xml
ozwcp dot poll dot XXXXXX dot xml
OZW_Log dot txt
plugins
scripts
zwscene dot xml

[waltervl]

I do not use Docker. It should be in the container in domoticz/config

[xmanpower]

I have made the file change. But no configuration by 'Unknown'

[xmanpower]

solved, after unlinking and unsecured linking, you will see the correct configuration.

[andrehj]

The device has a new ID that is not yet specified in the manufacturer_specific.xml

I fixed it by manual adding this device by adding a new line in the fibaro chapter with
<Product config="fibaro/fgd212.xml" id="1001" name="FGD212 Dimmer 2" type="0102"/>

assuming the device works similar to the old o==device with id=1000.

Just found out that I completely forgot to thank you for your excellent help suggestion last year. Your solution solved my problem!