ZWave binding updates

[menzy (Adam Menzel)]

@chris

At a guess, the device may not have excluded from the network. When the binding starts, it asks the controller for the list of nodes on the network, and then tries to contact them. If the device didn’t exclude, then the controller will still think it’s on the network - if you reset it, then it won’t be, but the binding will continue to try to talk to it as the controller still thinks it’s there.

To confirm this, we’d need to see the log during startup when this information is exchanged.

To get out of it, you will need to remove the failed node - there is an option in the thing parameters to do this - you would need to add the thing back again of course (and it doesn’t always work unfortunately).

Hi Chris

I have atatched the log at start up

zwave.txt (352.8 KB)

[chris (Chris Jackson)]

@menzy

I have atatched the log at start up

This confirms the above theory - assuming node 2 is the old node, the controller still thinks it is included in the network, so the binding will continue to try and communicate with it.

[menzy (Adam Menzel)]

No matter what I try I cannot get the device to remove from the controller. I have tried paper ui, habmin & zensys tools but the device wont mark as failed or remove.

[menzy (Adam Menzel)]

I managed to use the Zensys tools to replace the device with the same device, re added to openhab and so far everything is working again.

@chris thanks as always for the fast response & putting me in the right direction!

[HAB123 (Tz)]

Thanks Scott,

I checked the tutorial script but It is not clear for me if It should be done or not for zwave! I ran the script, I was ready to Install it but decided to be patient ahahahha… I think I can wait until the binding is updated!. @chris would it be to much to announce here whenever the updated binding is uploaded?, so I dont apt-get update / upgrade everyday?

Cheers,
T

[5iver (Scott Rushworth)]

@HAB123

I checked the tutorial script but It is not clear for me if It should be done or not for zwave!

Yes, it works for zwave… just don’t select Development (use Snapshot). If you’d rather not use a manual install, there is another option here, just replace the 2.4s with 2.5s. The change for your device is not yet in the binding.

[Dory_Fakhry]

Hi guys,
I have successfully added a new zwave device to the database MH-C221 and it was approved recently, but what is the next step? how to update my zwave binding on OPNEHAB2 in order to read the new device?
Thank you

[5iver (Scott Rushworth)]

Have you read the post just before yours? There’s also another option a little further up. The build system has had some changes recently, so it may take longer than normal for a new build to be available, so here is a third option.

[sihui]

@Dory_Fakhry

and it was approved recently

After a device has been approved in the database it needs to be merged into the binding, so please watch the MCO Home folder:

https://github.com/openhab/org.openhab.binding.zwave/tree/master/ESH-INF/thing/mcohome

After you see the merged device there it will take another couple of hours until the new zwave snapshot binding is available:

https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.binding$org.openhab.binding.zwave/

[Mickroz (¯\_(ツ)_/¯)]

Hi @chris , just updated from 2.4.0 M7 to 2.4.0 and been trying to get the binding to work, until i finally saw that the https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/787 doesn’t have a switch parameter anymore zwave:device:controller:node5:switch_dimmer, is this intentionally or?

[chris (Chris Jackson)]

Yes, this would be intentional. Since this is a dimmer, it doesn’t require a separate switch channel.

[Mickroz (¯\_(ツ)_/¯)]

ah ok, i used that to turn on the light, have to change my rules for that then.

[chris (Chris Jackson)]

@Mickroz

i used that to turn on the light

You can still do this exactly the same - just use the dimmer channel.

[Mickroz (¯\_(ツ)_/¯)]

Hmm, when i turn off the light with the switch, it doesn’t report back that its off, turning it on/off with openhab does.

[chris (Chris Jackson)]

@Mickroz

when i turn off the light with the switch

That’s not related to the above channels - that is an association issue.

[Mickroz (¯\_(ツ)_/¯)]

well, it did with that zwave:device:controller:node5:switch_dimmer channel

[chris (Chris Jackson)]

@Mickroz

it did with that zwave:device:controller:node5:switch_dimmer channel

What do you mean? So you change the wall switch, and it updates the level, but not when you turn it off?

[Mickroz (¯\_(ツ)_/¯)]

i used to use this:

Switch	LV_dimmer1		"Hal" 		{ channel="zwave:device:controller:node5:switch_dimmer" }
Dimmer	LV_dimmer1_dim	"Hal [%d %%]"	[ "Lighting" ]	{ channel="zwave:device:controller:node5:switch_dimmer1" }
Number	LV_dimmer1_power	"Hal - huidig verbruik [%.2f W]"	(gEnergy)		{ channel="zwave:device:controller:node5:sensor_power" }
Number	LV_dimmer1_energy	"Hal - totaal verbruik [%.2f KWh]"	(gEnergy)		{ channel="zwave:device:controller:node5:meter_kwh" }

if i used my wall pulse switch to turn on the light, the LV_dimmer1 switch would turn to on, and LV_dimmer1_dim would show the dim level, same when i turn it off.

now with:

Switch	LV_dimmer1		"Hal" 		{ channel="zwave:device:controller:node5:switch_dimmer1" }
Dimmer	LV_dimmer1_dim	"Hal [%d %%]"	[ "Lighting" ]	{ channel="zwave:device:controller:node5:switch_dimmer1" }
Number	LV_dimmer1_power	"Hal - huidig verbruik [%.2f W]"	(gEnergy)		{ channel="zwave:device:controller:node5:sensor_power" }
Number	LV_dimmer1_energy	"Hal - totaal verbruik [%.2f KWh]"	(gEnergy)		{ channel="zwave:device:controller:node5:meter_kwh" }

this doesn’t work anymore, it’s not showing if its on or off, and not showing the dim level.

[sihui]

You need to use the switch_dimmer1 channel for your switch item.
Edit: okay, you already did, sorry. Works fine for me with switch_dimmer1

[chris (Chris Jackson)]

@Mickroz

it’s not showing if its on or off, and not showing the dim level.

Ok, so your statement that it works with the dimmer is wrong?

In that case, the issue is with the association configuration as I said above. Please check this, or preferably change to a more recent version of the binding as this will help.