OH2 Z-Wave refactoring and testing... and SECURITY

Tags: #<Tag:0x00007fd30cf8f4a8> #<Tag:0x00007fd30cf8f368>

(Kris K) #3262

Hi All

Every since running the latest zwave binding this new device turns up. I have a Aeon zstick, and one as you can see if offline.

Should both be online? It appears something is wrong as the dimmers are offline also (persumably because the wrong controller is in use?)


(Chris Jackson) #3263

Yes - you should use the correct controller and I guess it will work.

(Kris K) #3264

Why do two come up? Ive only got one.

(Chris Jackson) #3265

A new feature was added to ESH, and then the binding to detect devices on USB. Since you added the controller manually, it is detected again. Just ignore it and use the correct controller - or delete the old controller and use the new one.

(Kris K) #3266

Thankyou Chris.

It seems alot has changed as all my devices have lost their linkages…There used to be a very long number and then the node number, now its just - zwave:device:512:node5

( -) #3267

Chris, do you see any drawback to me using Z-Way server to include all devices instead of Habmin? I will just have to make sure to use the same Network Key.

(Dan) #3268

sorry, not sure what you mean by attaching to the log ticket. The full zwave log is here - the troublesome node is node 29. It’s a wired FGS222 double relay, close to multiple nodes and so it really shouldn’t be offline… but it is!


(Chris Jackson) #3269

This comes from the controller - so it depends on the UID that you gave the controller. In this case, it seems you set it to 512?

(Chris Jackson) #3270

No - this should be fine so long as you transfer the network key correctly. Otherwise secure devices won’t work securely.

(Chris Jackson) #3271

What is node 23?

( -) #3272

Cool - may the force be with me.:sweat_smile:

(Dan) #3273

it’s an Aeon Labs ZW096 Smart Switch 6 - wired, of course. Seems to be behaving…

(Chris Jackson) #3274

Is there an association configured between these devices? The binding is trying to set a route between them…

(Dan) #3275

how weird - that’s the coffee grinder and the entryphone, so would make a pretty peculiar bit of automation.

I’ve used habmin to set the associations to the zwave controller only - I’ll see if that makes a difference



(Dan) #3276

doesn’t seem to help. here’s another log. This time I have offline nodes 17 and 39 (smart switches), 29 (double relay), 4, 30, 31 and 36 (heatit thermostats) and 55 (binary sensor).

I don’t suppose you could post a link to a version of the binding from before you changed the offline logic?

(Leo Siepel) #3277

My log shows some warnings:

2018-07-14 21:33:08.622 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 4: Restore from config: Error. Data invalid, ignoring config.
2018-07-14 21:33:08.639 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 24: Restore from config: Error. Data invalid, ignoring config.
2018-07-14 21:33:08.642 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 35: Restore from config: Error. Data invalid, ignoring config.
2018-07-14 21:33:14.168 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Invalid item type defined (DecimalType). Assuming DecimalType
2018-07-14 21:33:14.368 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Invalid item type defined (DecimalType). Assuming DecimalType
2018-07-14 21:33:14.704 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Invalid item type defined (DecimalType). Assuming DecimalType

For the first three messages it’s unclear for me what config the binding is talking about. Is it node.xml or something else? Maybe good point to add to the message what config it is related to.

About the last three warnings i suppose a DecimalType was expected and a DecimalType is supplied ? So this is wrong? I really don’t know how to read this.

node 33 and 34 are Coolcam PIR motion sensors (with lux sensor) and the channel is bound to a number item. The value does show up right on basicUI.

MySQL specific sensors don't persist their value's
(Scott Rushworth) #3278

What you’re seeing looks to be related to this…

(Chris Jackson) #3279

It means that the initialisation is incomplete. I will remove this as it’s not something the user needs to worry about.

There will be an update tomorrow to fix this.

(Leo Siepel) #3280

Cool, will update and provide feedback if needed.

About the initialisation. The nodes are battery devices and are connected for several days, shouldn’t the initialisation be done allready? Or is this done every time after a openhab restart?

Edit: Another question, if persistence is setup should the channel value be persisted after polling?

( -) #3281

Would there be any benefit for me to also include a Vera Plus as a secondary controller now that I’m re-including my network - or would it only mess things up?