New z-wave device needed and existing device to be renamed

[mhilbush (Mark)]

@RichDiedrich

it is showing up as 001D:0702:0261::0.2

What does the Thing show in Paper UI or HABmin? It should be showing up as a VRCS4, which is incorrect. I made the change in the DB so that it will discover as a VRCZ4, but that change is not included in the zwave binding yet.

Can you put the binding into debug mode and then post the debug log from when you push a button?

[RichDiedrich]

It is showing up as an unknown device. The properties are:

zwave_class_basic	STATIC_CONTROLLER
zwave_class_generic	REMOTE_CONTROLLER
zwave_frequent	false
zwave_neighbours	1,2,3,4,5,6,7,12
zwave_version	0.2
zwave_listening	true
zwave_deviceid	609
zwave_nodeid	11
zwave_routing	true
zwave_beaming	false
zwave_class_specific	NOT_USED
zwave_manufacturer	29
zwave_devicetype	1794

I am new to openHAB, can you tell me how to put the binding in debug mode?

[mhilbush (Mark)]

@RichDiedrich

It is showing up as an unknown device.

It may be showing up as Unknown because, even though it’s in the database, it might not have been in the database when the OH release was built. You’re on 2.3, right? That’s pretty dated at this point (May, I think).

Until you’re running a version of the binding that includes this device, you won’t be able to do anything with it.

There’s a way to switch from an OH release version to a snapshot version, but I don’t know how to do that. There’s also a new release process called milestone builds, which are intended to be a good compromise between full releases and snapshots.

openHAB Milestone builds

All, I promised it since a while, but it has cost us quite some efforts to get the whole process working smoothly: We are now in a position to do almost “one-click” releases of openHAB with our Jenkins release pipeline - big thanks to @pfink for setting this up! Just as some background information: To create a distro release, 9 different Github repos need to be built and released individually, with versions being changed in the sources, git tags being created, p2 repos published, etc. Doing t…

Personally, I run all my OH systems (I have three) on snapshot releases.

As for debug mode, in the karaf console, you would type:

log:set DEBUG org.openhab.binding.zwave

To get out of debug mode, you would type:

log:set INFO org.openhab.binding.zwave

You can read about the Karaf console here.

The Console

[RichDiedrich]

I switched to the snapshot version and it is showing up as VRCS4. Can you tell me when the updated database will be available?

Thank you for all your help.

[mhilbush (Mark)]

@RichDiedrich

it is showing up as VRCS4

That’s good news!

@RichDiedrich

Can you tell me when the updated database will be available?

@chris does a binding update every few days. But, I think he’s on holiday right now so it may take a bit longer.

Once you update to the latest binding, you’ll need to delete the VRCS4 thing, then rediscover (i.e. no need to exclude/include the node).

[chris (Chris Jackson)]

I should get this done tonight if internet connections all run ok

[mhilbush (Mark)]

@RichDiedrich There is a new build available that should include this database change.

If you are on a recent snapshot release, you can update just the zwave binding as described in this post.

ZWave binding updates

Now that dev is merged into master, I wanted to revisit how I upgrade to the latest version of the zwave binding without updating the rest of openHAB. Simply using bundle:update org.openhab.binding.zwave from the karaf console is not working for me. The only thing I found to work is to explicitly provide the exact location of the jar in the bundle:update command. Like this. openhab> list -s | grep zwave 227 │ Active │ 80 │ 2.x.0.old-date │ org.openhab.binding.zwave openhab> bundle:upd…

Make sure you delete the VRCS4 thing, then rediscover. It should then show up as a VRCZ4.

[RichDiedrich]

@mhilbush It is being added as a VRCZ4. When I configure the association on the device, it appears to take it, but when I go back in the configuration is gone. When I push a left side of the rocker on the device, it lights up all the LEDs, and the openHAB log shows: DownstairsHallPanelLeft_SceneNumber changed from 0 to 255. Then when I push the right side, it turns all the LEDs off and the log shows: DownstairsHallPanelLeft_SceneNumber changed from 255 to 0.

[mhilbush (Mark)]

@RichDiedrich

It is being added as a VRCZ4.

@RichDiedrich

When I configure the association on the device, it appears to take it, but when I go back in the configuration is gone.

I think this might be just a display issue in HABmin.

@RichDiedrich

When I push a left side of the rocker on the device, it lights up all the LEDs, and the openHAB log shows: DownstairsHallPanelLeft_SceneNumber changed from 0 to 255. Then when I push the right side, it turns all the LEDs off and the log shows: DownstairsHallPanelLeft_SceneNumber changed from 255 to 0

I’m not familiar with this device. Is this the behavior you expect?

[RichDiedrich]

@mhilbush It is a zone controller, so I would expect that once I configured the association groups, it would control those devices in that group. I activate the binding debug and this is what I am seeing in the log:

2018-09-23 09:46:17.027 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update received
2018-09-23 09:46:17.033 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set binding_cmdrepollperiod to 1500 (BigDecimal)
2018-09-23 09:46:17.056 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_4 to null (null)
2018-09-23 09:46:17.059 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 4
2018-09-23 09:46:17.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set action_failed to false (Boolean)
2018-09-23 09:46:17.062 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set action_remove to false (Boolean)
2018-09-23 09:46:17.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_1 to [node_3, node_2] (ArrayList)
2018-09-23 09:46:17.066 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 1
2018-09-23 09:46:17.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set binding_pollperiod to 86400 (BigDecimal)
2018-09-23 09:46:17.081 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Polling intialised at 86400 seconds - start in 39225600 milliseconds.
2018-09-23 09:46:17.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_3 to null (null)
2018-09-23 09:46:17.085 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 3
2018-09-23 09:46:17.087 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_2 to null (null)
2018-09-23 09:46:17.089 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 2
2018-09-23 09:46:17.091 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set action_heal to false (Boolean)
2018-09-23 09:46:17.093 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set nodename_name to null (null)
2018-09-23 09:46:17.095 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Error setting NodeNamingCommandClass name to invalid value null
2018-09-23 09:46:17.097 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set nodename_location to null (null)
2018-09-23 09:46:17.099 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Error setting NodeNamingCommandClass location to invalid value null
2018-09-23 09:46:17.101 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set node_id to 12 (BigDecimal)
2018-09-23 09:46:17.103 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE12: Configuration invalid node_id

I am new to this whole ZWave thing, but it looks like device is not being sent the correct data to do the association.

[mhilbush (Mark)]

Can you post the contents of the node xml file for this device? The file is in the userdata/zwave directory, and will be of the form network_nnnnnnnn__node12.xml, where nnnnnnnn is the network ID

Please use code fences when posting. Code fences also are helpful when posting debug logs, like this:

2018-09-23 09:46:17.027 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update received
2018-09-23 09:46:17.033 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set binding_cmdrepollperiod to 1500 (BigDecimal)
2018-09-23 09:46:17.056 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_4 to null (null)
2018-09-23 09:46:17.059 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 4
2018-09-23 09:46:17.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set action_failed to false (Boolean)
2018-09-23 09:46:17.062 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set action_remove to false (Boolean)
2018-09-23 09:46:17.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_1 to [node_3, node_2] (ArrayList)
2018-09-23 09:46:17.066 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 1
2018-09-23 09:46:17.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set binding_pollperiod to 86400 (BigDecimal)
2018-09-23 09:46:17.081 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Polling intialised at 86400 seconds - start in 39225600 milliseconds.
2018-09-23 09:46:17.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_3 to null (null)
2018-09-23 09:46:17.085 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 3
2018-09-23 09:46:17.087 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Configuration update set group_2 to null (null)
2018-09-23 09:46:17.089 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Unknown association group 2

[RichDiedrich]

@mhilbush I wasn’t seeing that node xml file, but now I am. It is working as expected so far.

Thank you for your help.

[RichDiedrich]

@mhilbush OK, now I am seeing something strange. I added another couple of the VRCZ4 controllers, and the XML files are not appearing. I can see the XML files for the first two, but am not seeing them for the new ones. Is there something that could cause a delay in the creation?

[sihui]

@RichDiedrich

but am not seeing them for the new ones.

Wake the device up, check your manual for how to do that.

[mhilbush (Mark)]

@sihui

Wake the device up

I think these are mains devices.

[mhilbush (Mark)]

@RichDiedrich

Is there something that could cause a delay in the creation?

The XML is created once the device has completed initialization. This can sometimes involve quite a few transactions between the binding and the device. For mains devices, this usually happens within a couple minutes. If there are problems communicating with the device, it could take longer.

[sihui]

@mhilbush

I think these are mains devices.

Upps, you are right