[ZWAVE] HeatIt Z-Din 616

  • Platform information:
    • Hardware: Raspberry Pi3B+
    • OS: latest openHABian
    • openHAB version: latest snapshot
  • Issue of the topic: I’ve added this device to the database, but it was my first attempt and maybe I made some mistake. I can switch the outputs (relays) on and off via PaperUI or rules. But HABmin shows that the device is stuck in Node Initialising: REQUEST_NIF and the Attributes show: Manufacturer: 0234 “Unknown Manufacturer”.
    The other issue (probably related to the previous): I can not set any configuration parameter of this device.
    The device is Node 2. But when I try to update it, the changes are PENDING.

2019-02-14 02:15:52.544 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-14 02:17:04.316 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-14 02:17:04.325 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-14 02:28:59.866 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-14 02:28:59.899 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_5_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-14 02:30:03.080 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-14 02:30:03.084 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-14 02:30:40.459 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-14 02:30:40.480 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_12_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

Binding Uninstalled/Re-Installed, Item removed and added again and still in this half working state.

Thank you very much for any help.

It might be best to provide a zwave debug log. The log should include the binding startup, so that we can see the initialization steps.

Then probably it is not communicating with the controller. Either it is not included properly, or it is out of range.

If it is not communicating, then the binding won’t be able to update it. The binding will therefore queue the updates and set them to pending state.

As Mark said, a log would help.

I will add the log soon. I’m away from my PC now. The device is in the same room as the RPi server with RaZberry. It is definitely not out of range as I can switch the relays on and off via PaperUI or rules. I will prepare the log and hopefully we could figure out why it is not included properly. As I already wrote, it’s my first device added to the database, maybe I made some mistake there.

There is the requested zwave.log:
http://skrew.sweb.cz/zwave.zip
Please ignore the Node4.
The HeatIt Z-Din device is Node2.

From what I can see in the log, node 2 is communicating just fine. It looks like it has been fully initialized, which you can confirm by verifying that a node.xml file exists for node 2 in the userdata/zwave directory.

I did see one thing that I didn’t quite understand.

It looks like the Group 1 Association is being removed, then is being reported as node 182. Maybe @chris understands and can explain what’s going on here.

One other question. Are you using Paper UI or HABmin to manage the device? Im guessing Paper UI because of all the config updates I see in the log. I would suggest you use HABmin instead of Paper UI. Paper UI sends the entire config to the device, even though there’s only a single change to the config. OTOH, HABmin sends only what has changed. This also may explain the above issue with the association.

Even the HABmin does not update the config parameters successfuly.

2019-02-14 23:08:31.340 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-14 23:08:31.343 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_18_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

And the initialisation of the device is also not OK :frowning:

It looks to me like node 2 is initialized. Did you check for the existence of network_ece17ae4__node_2.xml

2019-02-14 21:16:10.691 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 3: Serializing from file /var/lib/openhab2/zwave/network_ece17ae4__node_3.xml
2019-02-14 21:16:10.691 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 1: Serializing from file /var/lib/openhab2/zwave/network_ece17ae4__node_1.xml
2019-02-14 21:16:10.691 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 4: Serializing from file /var/lib/openhab2/zwave/network_ece17ae4__node_4.xml
2019-02-14 21:16:10.691 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 2: Serializing from file /var/lib/openhab2/zwave/network_ece17ae4__node_2.xml

I wouldn’t worry about the Unknown Manufacturer. One of my devices (August Smart Lock) shows the same thing, and it works just fine.

The xml file for Node2 does exist. It existed since first start of the device. I’ve used it as the base when I was adding the device to the database.

Ok, so the device is initialized. :+1:

And the Unknown Manufacturer is likely not an issue. I suspect that is a matter of HABmin not having an updated table of manufacturers here.

So, then the issue is that config updates are not being applied… With the binding still in DEBUG mode, use HABmin to change the config parameter for which you’re having an issue, then post the debug log. That will show exactly what the binding is doing with the config update.

http://skrew.sweb.cz/zwave2.zip

Changing the state works, config updates still pending.

2019-02-15 01:11:17.363 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_1_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-15 01:12:42.721 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-15 01:12:42.725 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2019-02-15 01:15:30.296 [ome.event.ItemCommandEvent] - Item ‘V2e’ received command ON

2019-02-15 01:15:30.341 [nt.ItemStatePredictedEvent] - V2e predicted to become ON

2019-02-15 01:15:30.357 [vent.ItemStateChangedEvent] - V2e changed from OFF to ON

2019-02-15 01:15:32.896 [ome.event.ItemCommandEvent] - Item ‘V2e’ received command OFF

2019-02-15 01:15:32.907 [nt.ItemStatePredictedEvent] - V2e predicted to become OFF

2019-02-15 01:15:32.921 [vent.ItemStateChangedEvent] - V2e changed from ON to OFF

2019-02-15 01:15:49.873 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:492a2fb2:node2’ has been updated.

2019-02-15 01:15:49.881 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_1_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

Here’s the config SET, GET, and REPORT for parameters 1 and 3. These look perfectly normal.