Zwave Database Update for EcoLink Firefighter

Add-ons Other
1

I am having problems installing this device. It installs and is recognized with the proper name but it doesn’t actually work and I get discovery errors in the logfile:

2024-07-23 14:48:36.831 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:Z-Wave_Serial_Controller:node63' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {config_1_1=The value -91 does not match allowed parameter options. Allowed options are: [ParameterOption [value="165", label="Smoke alarm detection only"], ParameterOption [value="255", label="Smoke and carbon monoxide alarm detection"]]}


2024-07-23 14:53:03.892 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 30: Device discovery could not resolve to a thingType! Manufacturer data not known.


2024-07-23 14:53:04.396 [INFO ] [openhab.event.ChannelTriggeredEvent ] - logreader:reader:LogReader:newWarningEvent triggered 2024-07-23 14:53:03.892 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 30: Device discovery could not resolve to a thingType! Manufacturer data not known.

This device is in the opensmarthouse database but the parameters tab is essentially empty. I am attaching the xml file here.
network_fad4ef5c__node_63.xml (11.8 KB)

2

One problem is the allowable 165 and 255 are returned by the device as signed (-91 and -1) and the rigorous OH checker is throwing an error. Not sure about the Thing type as it looks okay to me in the ZW DB. It may need a DB update, but try inputting 165 or 255 first.

3

Yeah I wanted to do that but the parameters don’t even show:

image
image504×522 23.2 KB

4

Hmmm. Try the Code Tab. Edit: will also have to wake device to transmit.

The more complicated option is to overwrite your current binding XML with this file. The location is eco/firefighter5_0_0.xml
firefighter5_0_0.xml (9.8 KB)

Using this method or something similar. Update ZWave binding with new/updated device xml - Tutorials & Examples - openHAB Community.

I’ve changed the ZW DB, but don’t know when the binding will be updated. Also the binding will be a OH4.3 snapshot, so I think you will have to be on OH4.2 release for it to work. The jar update will work with any OH3+ version