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

Hicco · May 22, 2018, 5:10pm

It’s the same model.
Would you be able to add a new entry to the database?

Thanks!

chris · May 22, 2018, 5:12pm

Yep - No problem, I’ll update the database… If I get a chance I’ll update the binding tonight as well - I’m just trying to finalise the database updates for the next release.

DubZ · May 23, 2018, 12:40pm

so the manufacture answered me for 3 products (siren, power plug and mutlisensor). until now, smoke detector is missing (but I also asked for it again). In the evening I try to fill out the form on your website for the power plug which I can also test here.

edit:
mhh. so it seems that I cant test and do the entry in moment. for smoke detector the documentation is still missing from manufacture. and from the power plug I do have the predecssor of the new one where I got the documentation from. additionally the power plug got recognized as AN158 switch meter plugin

one question: I understand from your website, that everytime after including a new devices an xml file should be created. but for smoke detector no node file appears in /userdata/zwave directory. did I understand it wrong?

chris · May 23, 2018, 4:28pm

An XML should be created once the device finishes initialisation. If it’s not generated, then either there is something wrong, or (most commonly) for battery devices, the device has not been woken up to allow the initialisation to complete.

First try waking the device up a few times, if that doesn’t work, then we’d need to get a debug log to find out why it’s not working.

DubZ · May 23, 2018, 5:05pm

I tried to wake it up during inclusion mode by pressing sometimes the binding button… every second. dunno how to wake it up no documentation… but seems not to help. no xml file generated.

attached the debug log file (rename to .txt or sth similar). its about node 28
zwave.xml (129.0 KB)

chris · May 24, 2018, 7:07am

There are no wakeup messages, or in fact any messages, from node 28 in the log. I think that the wakeup is not working and until the binding receives the wakeup, it won’t proceed with the initialisation.

DubZ · May 24, 2018, 7:47am

what is a message for a complete inclusion? because in the log I see some entries regarding inclusion and adding command classes etc.

update: did another try with inclusion. now regarding node 29. pretty similar like before with one more property entry Application update request: “2018-05-24 09:55:19.410 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 29: Application update request. Node information received. Transaction null”

is this a wake up? but still: no xml file generated

attached new log file
zwave.xml (193.8 KB)

chris · May 24, 2018, 8:13am

The device is included - no problem there. But there is still more to do. After inclusion, the binding needs to read all the information about the device - for this it actually needs to communicate with the device, and for this, the device needs to be awake. When the device wakes up, it sends a WAKEUP_NOTIFICATION and this I don’t see in the log.

gauch · May 26, 2018, 3:53am

Hi,

Chris, would it be possible to add Leviton VRC0P-1LW Plug-in Serial Interface Module to the binding database? Right now it’s showing as unknown, and messes up with locks. I mean it binds without security.

Here link to openzwave :http://www.openzwave.com/device-database/001d:030b:0b02

Thanks,
gauch

Dim · May 26, 2018, 4:10am

I believe that you can help here by providing the device xml
The listing exists here: http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/702

but I think that it is not working since it is missing info (and as a result, it is not approved).

chris · May 26, 2018, 9:29am

In addition to the information provided by @Dim, I can also say that adding the device to the database won’t change how it is included. If it’s included unsecurely for some reason, then this will not change by making any changes to the database so you’ll need to work out why it’s not securely included.

Or, is this a controller? (It’s a bit hard to tell really). If it is, then adding it to the database is not relevant as the database is not used for controllers.

mueslee · May 27, 2018, 5:33pm

I have a Devolo MT02792, a switchable meter plug, running openHAB 2.3.0~RC2-1 (Milestone Build)
I linked 2 channels DevoloMT02792ZWaveNode2_ElectricMeterKWh and DevoloMT02792ZWaveNode2_ElectricMeterWatts
In HABmin/PaperUI i can see the value of both channels, so far so good
In Basic UI i can’t see the value of ElectricMeterWatts, so i looked up the differences in REST and noticed that the watts channel is missing the stateDescription

How or better where can I add the stateDescription to the watts channel?

{
  "link": "http://openhab:8080/rest/items/DevoloMT02792ZWaveNode2_ElectricMeterKWh",
  "state": "16.88",
  "stateDescription": {
    "pattern": "%.1f",
    "readOnly": true,
    "options": []
  },
  "editable": true,
  "type": "Number:Dimensionless",
  "name": "DevoloMT02792ZWaveNode2_ElectricMeterKWh",
  "label": "Beamer - Electric meter (kWh)",
  "category": "Energy",
  "tags": [],
  "groupNames": [
    "gDevoloMT02792_Mediaroom",
    "gLogall"
  ]
}

{
  "link": "http://openhab:8080/rest/items/DevoloMT02792ZWaveNode2_ElectricMeterWatts",
  "state": "225.7",
  "editable": true,
  "type": "Number:Dimensionless",
  "name": "DevoloMT02792ZWaveNode2_ElectricMeterWatts",
  "label": "Beamer - Electric meter (watts)",
  "category": "Energy",
  "tags": [],
  "groupNames": [
    "gDevoloMT02792_Mediaroom"
  ]
}

Thank You!

chris · May 27, 2018, 5:56pm

Just to note that RC2 will not contain the security features discussed in this thread.

The binding provides this normally, so I’m not sure why it’s not here in this case.

DubZ · May 27, 2018, 5:57pm

does this mean that in the coming 2.3 stable release this zwave security build is not included and still needs to be installed manually?

chris · May 27, 2018, 5:59pm

Yes, that’s correct. I will look to merge this soon.

DubZ · May 28, 2018, 6:33pm

today I upgraded to 2.3 stable release. now I want to troubleshoot my errors which I thought that it was because I was running oh2.2 with the zwave 2.3 security snapshot binding. but it seems not.

first (new) error after upgading to 2.3 (not sure if its regarding zwave): to all my nodes I get an info loggin

2018-05-28 20:13:08.830 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2018-05-28 20:13:08.831 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 2: Node found
2018-05-28 20:13:08.831 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 3: Node found
2018-05-28 20:13:08.831 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 4: Node found
2018-05-28 20:13:08.831 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 5: Node found
2018-05-28 20:13:08.832 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 6: Node found
2018-05-28 20:13:08.832 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 7: Node found
2018-05-28 20:13:08.832 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 8: Node found
2018-05-28 20:13:08.832 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 9: Node found
2018-05-28 20:13:08.833 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 10: Node found
2018-05-28 20:13:08.833 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 11: Node found
2018-05-28 20:13:08.833 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 12: Node found
2018-05-28 20:13:08.833 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 13: Node found
2018-05-28 20:13:08.834 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 14: Node found
2018-05-28 20:13:08.834 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 16: Node found
2018-05-28 20:13:08.834 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 17: Node found
2018-05-28 20:13:08.834 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 19: Node found
2018-05-28 20:13:08.834 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 20: Node found
2018-05-28 20:13:08.835 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 21: Node found
2018-05-28 20:13:08.835 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 22: Node found
2018-05-28 20:13:08.835 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 23: Node found
2018-05-28 20:13:08.836 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 24: Node found
2018-05-28 20:13:08.836 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 25: Node found
2018-05-28 20:13:08.837 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 29: Node found

but all nodes are working, also showing as online.

coming now to the error logging:

2018-05-28 20:13:19.381 [ERROR] [age.AssignSucReturnRouteMessageClass] - NODE 8: AssignSucReturnRoute command failed.
2018-05-28 20:13:19.385 [ERROR] [age.AssignSucReturnRouteMessageClass] - NODE 6: AssignSucReturnRoute command failed.

on some nodes this message appear. on oh2.2 the error message looked like this

2018-05-28 19:57:12.182 [ERROR] [age.AssignSucReturnRouteMessageClass] - NODE 19: Assign SUC return routes failed.

I think that could be a reason why I’m running into some problems with my fibaro switchs (and association groups), that the current state of the switch sometimes doesnt get reported back correct. sometimes I need to reconfigure on my switch the association group (although it was already defined correct). Also in habmin the lifeline group was on 90% of switch empty after saving the openhab controller into it and refreshing habmin (never understood this).

any idea?

chris · May 28, 2018, 6:49pm

This is not an error. It’s just saying that the node is found.

Yes - that’s what the log says - they are found ok.

I will reduce these messages to debug so that they are removed from normal logging.

Why do you think it’s related? Personally, I doubt it, but maybe I’m wrong. This “error” is the failure to set the SUC return route, but it is VERY unlikely to cause any problem unless you have multiple controllers in your network?

MrWendal · May 28, 2018, 10:08pm

Do you mean Fibaro Single/Double Switch 2 (ie FGS-213/FGS-223) or Fibaro Relay Switch (ie FGS-212/FGS-222)? And were they first included using the development binding?

Thanks,
Steve.

DubZ · May 29, 2018, 7:04am

oh man… thats embarrassing :S I dont know why… I read “Node not found” in the log file… maybe it was regarding my evening beer I’m sorry …

regarding suc return route log:
I dont have any rational explaination why I thought that. I dont even now what suc and sis is. It’s just, because I had a problem with zwave states and there are error messages with terms like suc (which seems to be sth controller relevant) and return route. But after your statement I dont believe anymore.

I’m using and talking about Fibaro Doubleswitch. That is a good question with what zwave binding I included them! I dont really remember

sihui · May 29, 2018, 7:12am

Explanation: