Howto add a device to the zwave database

Dim · July 1, 2017, 8:51pm

You should thank @chris for making the Z-Wave binding, maintaining a top class device database, updating code, etc, etc… without all that… we would be all scratching our heads

evilaid · July 1, 2017, 8:52pm

That dude is also awesome!

yobobby · July 8, 2017, 12:22am

Hi all, thanks @chris for the binding… really looking forward to getting devices up and running but mine’s one that isn’t in the database. I’ve asked for permission on the database guide page but I’m not sure if that’s the most appropriate place to ask. Any advice fellow OpenHAB’ers?

chris · July 8, 2017, 7:57am

What is your username on the database? No problem to give you access…

TheLexus · September 3, 2017, 10:22am

@chris Hi Chris, is there any way to add a device “privately” with my own device.xml or is it necessary to add it the official way?

Background: I have a Z-Uno and I think it isn’t useful for other to have my private project at the device database. I have no problems with that of course, but if I change something I need to readd it again and it messes up the official db a little bit…

chris · September 3, 2017, 10:41am

The XML files are compiled in to the binding - so you can create your own binding if you like, but that’s the only way.

There has been some discussion about creating a superset of channels to handle the Z-Uno to get around this current limitation.

sjcliffe · September 28, 2017, 12:54am

@chris is the XML format for your database the same as that used by Open-ZWave? I’ve got a couple of Aeotec Wallmote (ZW129) switches that aren’t in your database but are in Open-ZWave so was wondering if I can just upload the XML file from it.

chris · September 28, 2017, 9:52am

No - it’s not related to OZW at all. The XML files that you upload are automatically generated by OH - this will generate all the basic information (and this information is not contained in the OZW files anyway) and the parameters need to be manually entered.

wrotebyreuben · October 2, 2017, 10:22am

@chris I’m struggling to generate a node.XML files from the “/var/lib/openhab2/zwave” folder. I have the same ZW129 as @sjcliffe above. My log from /var/log/openhab2/openhab.log is below. I saw that you sometimes need to wake up the device several times to register, but doesn’t seem to make a new node.XML. Is there some other step to do, I’ve tried using paper UI and habmin but seem to get the same result. Once I get the xml generated I can upload to your website.

2017-09-29 10:45:23.605 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:4802214c:node3' to inbox.
2017-09-29 10:45:23.607 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 10:45:23.608 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:4802214c:node4' to inbox.
2017-09-29 10:45:38.078 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 10:45:38.081 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:07:46.500 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:07:46.501 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:4802214c:node3' to inbox.
2017-09-29 11:07:46.503 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:07:46.503 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:4802214c:node4' to inbox.
2017-09-29 11:08:01.270 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:08:01.272 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:09:45.823 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-09-29 11:09:45.825 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-10-02 10:13:32.149 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 0086:0202:0081::1.8
2017-10-02 10:13:33.161 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 4: unknown ZWavePlus device type: 7170
2017-10-02 10:13:33.596 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 4: unknown ZWavePlus device type: 7169
2017-10-02 10:13:33.787 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 4: unknown ZWavePlus device type: 7169
2017-10-02 10:13:39.243 [WARN ] [l.serialmessage.SendDataMessageClass] - Node 255 not found!

sjcliffe · October 2, 2017, 10:27pm

Yes, I too tried adding my ZW129 on the weekend and ran into the same problem. I’ll turn on debug logging tonight and post my results. I’m running the 2.2 snapshot version of the binding with an Aeotec Z-stick controller.

sjcliffe · October 3, 2017, 7:58am

Here’s my debug log:

Time	Node	Entry
18:24:38.131		
TX REQ AddNodeToNetwork ADD_NODE_ANY HIGH POWER
18:24:38.140		
RX REQ AddNodeToNetwork ADD_NODE_STATUS_LEARN_READY
18:24:44.777		
RX REQ AddNodeToNetwork ADD_NODE_STATUS_NODE_FOUND
18:24:44.924	13	
RX REQ AddNodeToNetwork ADD_NODE_STATUS_ADDING_SLAVE NODE 13
18:24:44.960		
TX REQ AddNodeToNetwork ADD_NODE_STOP
18:24:45.015	13	
RX REQ AddNodeToNetwork ADD_NODE_STATUS_DONE NODE 13
18:24:45.035	13	
Stage advanced to IDENTIFY_NODE
18:24:45.040	13	
TX REQ IdentifyNode
18:24:45.045	13	
RX RES IdentifyNode ROUTING_SLAVE SWITCH_REMOTE2_MULTILEVEL LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
18:24:45.050	13	
Stage advanced to MANUFACTURER
18:24:49.681	13	
RX REQ ApplicationCommandHandler WAKE_UP_NOTIFICATION
18:24:49.710	13	
Node is AWAKE
18:24:49.721	13	
TX REQ SendData 131 MANUFACTURER_SPECIFIC_GET  ACK AUTO_ROUTE EXPLORE
18:24:49.728	13	
RX RES SendData 131 ACCEPTED BY CONTROLLER
18:24:49.748	13	
RX REQ SendData 131 ACK RECEIVED from device in 27ms
18:24:49.763	13	
RX REQ ApplicationCommandHandler MANUFACTURER_SPECIFIC_REPORT 0086:0202:0081
18:24:49.806	13	
Stage advanced to SECURITY_REPORT
18:24:49.810	13	
Stage advanced to APP_VERSION
18:24:49.820	13	
TX REQ SendData 132 MANUFACTURER_SPECIFIC_GET  ACK AUTO_ROUTE EXPLORE
18:24:49.828	13	
RX RES SendData 132 ACCEPTED BY CONTROLLER
18:24:49.847	13	
RX REQ SendData 132 ACK RECEIVED from device in 27ms
18:24:49.856	13	
RX REQ ApplicationCommandHandler MANUFACTURER_SPECIFIC_REPORT 0086:0202:0081
18:24:49.886	13	
TX REQ SendData 133 VERSION_GET  ACK AUTO_ROUTE EXPLORE
18:24:49.893	13	
RX RES SendData 133 ACCEPTED BY CONTROLLER
18:24:49.909	13	
RX REQ SendData 133 ACK RECEIVED from device in 23ms
18:24:49.923	13	
RX REQ ApplicationCommandHandler VERSION_REPORT APPLICATION_VERSION VERSION 1.8
18:24:49.951	13	
Stage advanced to DISCOVERY_COMPLETE
18:24:50.098	13	
Stage advanced to VERSION
18:24:50.120	13	
TX REQ SendData 134 VERSION_COMMAND_CLASS_GET BASIC  ACK AUTO_ROUTE EXPLORE
18:24:50.126	13	
RX RES SendData 134 ACCEPTED BY CONTROLLER
18:24:50.143	13	
RX REQ SendData 134 ACK RECEIVED from device in 23ms
18:24:50.154	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT BASIC VERSION 2
18:24:50.164	13	
TX REQ SendData 135 VERSION_COMMAND_CLASS_GET VERSION  ACK AUTO_ROUTE EXPLORE
18:24:50.170	13	
RX RES SendData 135 ACCEPTED BY CONTROLLER
18:24:50.187	13	
RX REQ SendData 135 ACK RECEIVED from device in 23ms
18:24:50.198	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT VERSION VERSION 2
18:24:50.210	13	
TX REQ SendData 136 VERSION_COMMAND_CLASS_GET WAKE_UP  ACK AUTO_ROUTE EXPLORE
18:24:50.216	13	
RX RES SendData 136 ACCEPTED BY CONTROLLER
18:24:50.232	13	
RX REQ SendData 136 ACK RECEIVED from device in 22ms
18:24:50.244	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT WAKE_UP VERSION 2
18:24:50.254	13	
TX REQ SendData 137 VERSION_COMMAND_CLASS_GET MULTI_INSTANCE_ASSOCIATION  ACK AUTO_ROUTE EXPLORE
18:24:50.260	13	
RX RES SendData 137 ACCEPTED BY CONTROLLER
18:24:50.277	13	
RX REQ SendData 137 ACK RECEIVED from device in 23ms
18:24:50.288	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT MULTI_INSTANCE_ASSOCIATION VERSION 3
18:24:50.305	13	
TX REQ SendData 138 VERSION_COMMAND_CLASS_GET ALARM  ACK AUTO_ROUTE EXPLORE
18:24:50.311	13	
RX RES SendData 138 ACCEPTED BY CONTROLLER
18:24:50.327	13	
RX REQ SendData 138 ACK RECEIVED from device in 22ms
18:24:50.338	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT ALARM VERSION 4
18:24:50.347	13	
TX REQ SendData 139 VERSION_COMMAND_CLASS_GET COMMAND_CLASS_ASSOCIATION  ACK AUTO_ROUTE EXPLORE
18:24:50.353	13	
RX RES SendData 139 ACCEPTED BY CONTROLLER
18:24:50.370	13	
RX REQ SendData 139 ACK RECEIVED from device in 23ms
18:24:50.382	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT COMMAND_CLASS_ASSOCIATION VERSION 2
18:24:50.400	13	
TX REQ SendData 140 VERSION_COMMAND_CLASS_GET CONFIGURATION  ACK AUTO_ROUTE EXPLORE
18:24:50.406	13	
RX RES SendData 140 ACCEPTED BY CONTROLLER
18:24:50.425	13	
RX REQ SendData 140 ACK RECEIVED from device in 25ms
18:24:50.433	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT CONFIGURATION VERSION 1
18:24:50.462	13	
TX REQ SendData 141 VERSION_COMMAND_CLASS_GET FIRMWARE_UPDATE_MD  ACK AUTO_ROUTE EXPLORE
18:24:50.468	13	
RX RES SendData 141 ACCEPTED BY CONTROLLER
18:24:50.486	13	
RX REQ SendData 141 ACK RECEIVED from device in 24ms
18:24:50.496	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT FIRMWARE_UPDATE_MD VERSION 2
18:24:50.504	13	
TX REQ SendData 142 VERSION_COMMAND_CLASS_GET MANUFACTURER_SPECIFIC  ACK AUTO_ROUTE EXPLORE
18:24:50.511	13	
RX RES SendData 142 ACCEPTED BY CONTROLLER
18:24:50.526	13	
RX REQ SendData 142 ACK RECEIVED from device in 22ms
18:24:50.538	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT MANUFACTURER_SPECIFIC VERSION 2
18:24:50.547	13	
TX REQ SendData 143 VERSION_COMMAND_CLASS_GET CENTRAL_SCENE  ACK AUTO_ROUTE EXPLORE
18:24:50.553	13	
RX RES SendData 143 ACCEPTED BY CONTROLLER
18:24:50.570	13	
RX REQ SendData 143 ACK RECEIVED from device in 23ms
18:24:50.582	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT CENTRAL_SCENE VERSION 2
18:24:50.595	13	
TX REQ SendData 144 VERSION_COMMAND_CLASS_GET ASSOCIATION_GROUP_INFO  ACK AUTO_ROUTE EXPLORE
18:24:50.607	13	
RX RES SendData 144 ACCEPTED BY CONTROLLER
18:24:50.619	13	
RX REQ SendData 144 ACK RECEIVED from device in 24ms
18:24:50.631	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT ASSOCIATION_GROUP_INFO VERSION 1
18:24:50.653	13	
TX REQ SendData 145 VERSION_COMMAND_CLASS_GET ZWAVE_PLUS_INFO  ACK AUTO_ROUTE EXPLORE
18:24:50.660	13	
RX RES SendData 145 ACCEPTED BY CONTROLLER
18:24:50.675	13	
RX REQ SendData 145 ACK RECEIVED from device in 22ms
18:24:50.687	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT ZWAVE_PLUS_INFO VERSION 2
18:24:50.705	13	
TX REQ SendData 146 VERSION_COMMAND_CLASS_GET MULTI_INSTANCE  ACK AUTO_ROUTE EXPLORE
18:24:50.711	13	
RX RES SendData 146 ACCEPTED BY CONTROLLER
18:24:50.727	13	
RX REQ SendData 146 ACK RECEIVED from device in 22ms
18:24:50.739	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT MULTI_INSTANCE VERSION 4
18:24:50.754	13	
TX REQ SendData 147 VERSION_COMMAND_CLASS_GET DEVICE_RESET_LOCALLY  ACK AUTO_ROUTE EXPLORE
18:24:50.760	13	
RX RES SendData 147 ACCEPTED BY CONTROLLER
18:24:50.776	13	
RX REQ SendData 147 ACK RECEIVED from device in 22ms
18:24:50.788	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT DEVICE_RESET_LOCALLY VERSION 1
18:24:50.801	13	
TX REQ SendData 148 VERSION_COMMAND_CLASS_GET POWERLEVEL  ACK AUTO_ROUTE EXPLORE
18:24:50.807	13	
RX RES SendData 148 ACCEPTED BY CONTROLLER
18:24:50.823	13	
RX REQ SendData 148 ACK RECEIVED from device in 22ms
18:24:50.835	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT POWERLEVEL VERSION 1
18:24:50.855	13	
TX REQ SendData 149 VERSION_COMMAND_CLASS_GET BATTERY  ACK AUTO_ROUTE EXPLORE
18:24:50.862	13	
RX RES SendData 149 ACCEPTED BY CONTROLLER
18:24:50.879	13	
RX REQ SendData 149 ACK RECEIVED from device in 24ms
18:24:50.889	13	
RX REQ ApplicationCommandHandler VERSION_COMMAND_CLASS_REPORT BATTERY VERSION 1
18:24:50.901	13	
Stage advanced to ENDPOINTS
18:24:50.903	13	
TX REQ SendData 150 MULTI_INSTANCE MULTI_CHANNEL_END_POINT_GET  ACK AUTO_ROUTE EXPLORE
18:24:50.909	13	
RX RES SendData 150 ACCEPTED BY CONTROLLER
18:24:50.925	13	
RX REQ SendData 150 ACK RECEIVED from device in 22ms
18:24:50.937	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_END_POINT_REPORT 2 ENDPOINTS DYNAMIC
18:24:50.967	13	
TX REQ SendData 151 MULTI_INSTANCE MULTI_CHANNEL_CAPABILITY_GET  ACK AUTO_ROUTE EXPLORE
18:24:50.973	13	
RX RES SendData 151 ACCEPTED BY CONTROLLER
18:24:50.989	13	
RX REQ SendData 151 ACK RECEIVED from device in 22ms
18:24:51.004	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CAPABILITY_REPORT ENDPOINT-1 ROUTING_SLAVE SWITCH_REMOTE2_MULTILEVEL
18:24:51.023	13	
TX REQ SendData 152 MULTI_INSTANCE MULTI_CHANNEL_CAPABILITY_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.029	13	
RX RES SendData 152 ACCEPTED BY CONTROLLER
18:24:51.045	13	
RX REQ SendData 152 ACK RECEIVED from device in 22ms
18:24:51.061	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CAPABILITY_REPORT ENDPOINT-2 ROUTING_SLAVE SWITCH_REMOTE2_MULTILEVEL
18:24:51.077	13	
Stage advanced to UPDATE_DATABASE
18:24:51.080	13	
Stage advanced to STATIC_VALUES
18:24:51.095	13	
TX REQ SendData 153 WAKE_UP_INTERVAL_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.102	13	
RX RES SendData 153 ACCEPTED BY CONTROLLER
18:24:51.117	13	
RX REQ SendData 153 ACK RECEIVED from device in 22ms
18:24:51.130	13	
RX REQ ApplicationCommandHandler WAKE_UP_INTERVAL_REPORT Period=0 Reporting to BROADCAST
18:24:51.138	13	
TX REQ SendData 154 WAKE_UP_INTERVAL_CAPABILITIES_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.145	13	
RX RES SendData 154 ACCEPTED BY CONTROLLER
18:24:51.160	13	
RX REQ SendData 154 ACK RECEIVED from device in 22ms
18:24:51.176	13	
RX REQ ApplicationCommandHandler WAKE_UP_INTERVAL_CAPABILITIES_REPORT Min=0 Max=864000 Default=0 Step=240
18:24:51.185	13	
TX REQ SendData 155 MULTI_INSTANCE_ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.191	13	
RX RES SendData 155 ACCEPTED BY CONTROLLER
18:24:51.207	13	
RX REQ SendData 155 ACK RECEIVED from device in 22ms
18:24:51.218	13	
RX REQ ApplicationCommandHandler MULTI_INSTANCE_ASSOCIATION_GROUPINGS_REPORT Supports 5 groups
18:24:51.226	13	
TX REQ SendData 156 ALARM_SUPPORTED_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.232	13	
RX RES SendData 156 ACCEPTED BY CONTROLLER
18:24:51.248	13	
RX REQ SendData 156 ACK RECEIVED from device in 22ms
18:24:51.260	13	
RX REQ ApplicationCommandHandler ALARM_SUPPORTED_REPORT
18:24:51.268	13	
TX REQ SendData 157 ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.274	13	
RX RES SendData 157 ACCEPTED BY CONTROLLER
18:24:51.290	13	
RX REQ SendData 157 ACK RECEIVED from device in 22ms
18:24:51.302	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUPINGS_REPORT Supports 5 groups
18:24:51.309	13	
TX REQ SendData 158 CENTRAL_SCENE_SUPPORTED_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.315	13	
RX RES SendData 158 ACCEPTED BY CONTROLLER
18:24:51.332	13	
RX REQ SendData 158 ACK RECEIVED from device in 23ms
18:24:51.344	13	
RX REQ ApplicationCommandHandler CENTRAL_SCENE_SUPPORTED_REPORT
18:24:51.351	13	
TX REQ SendData 159 ZWAVE_PLUS_INFO_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.357	13	
RX RES SendData 159 ACCEPTED BY CONTROLLER
18:24:51.376	13	
RX REQ SendData 159 ACK RECEIVED from device in 25ms
18:24:51.388	13	
RX REQ ApplicationCommandHandler ZWAVE_PLUS_INFO_REPORT
18:24:51.413	13	
TX REQ SendData 160 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 CENTRAL_SCENE_SUPPORTED_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.421	13	
RX RES SendData 160 ACCEPTED BY CONTROLLER
18:24:51.437	13	
RX REQ SendData 160 ACK RECEIVED from device in 24ms
18:24:51.452	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 CENTRAL_SCENE_SUPPORTED_REPORT
18:24:51.483	13	
TX REQ SendData 161 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 MULTI_INSTANCE_ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.489	13	
RX RES SendData 161 ACCEPTED BY CONTROLLER
18:24:51.506	13	
RX REQ SendData 161 ACK RECEIVED from device in 23ms
18:24:51.519	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 MULTI_INSTANCE_ASSOCIATION_GROUPINGS_REPORT Supports 3 groups
18:24:51.528	13	
TX REQ SendData 162 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.534	13	
RX RES SendData 162 ACCEPTED BY CONTROLLER
18:24:51.551	13	
RX REQ SendData 162 ACK RECEIVED from device in 23ms
18:24:51.563	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUPINGS_REPORT Supports 3 groups
18:24:51.573	13	
TX REQ SendData 163 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ZWAVE_PLUS_INFO_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.579	13	
RX RES SendData 163 ACCEPTED BY CONTROLLER
18:24:51.596	13	
RX REQ SendData 163 ACK RECEIVED from device in 23ms
18:24:51.612	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ZWAVE_PLUS_INFO_REPORT
18:24:51.622	13	
TX REQ SendData 164 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-2 CENTRAL_SCENE_SUPPORTED_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.629	13	
RX RES SendData 164 ACCEPTED BY CONTROLLER
18:24:51.645	13	
RX REQ SendData 164 ACK RECEIVED from device in 23ms
18:24:51.658	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-2 -> EP-1 CENTRAL_SCENE_SUPPORTED_REPORT
18:24:51.667	13	
TX REQ SendData 165 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-2 MULTI_INSTANCE_ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.673	13	
RX RES SendData 165 ACCEPTED BY CONTROLLER
18:24:51.691	13	
RX REQ SendData 165 ACK RECEIVED from device in 24ms
18:24:51.703	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-2 -> EP-1 MULTI_INSTANCE_ASSOCIATION_GROUPINGS_REPORT Supports 3 groups
18:24:51.712	13	
TX REQ SendData 166 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-2 ASSOCIATION_GROUPINGS_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.719	13	
RX RES SendData 166 ACCEPTED BY CONTROLLER
18:24:51.736	13	
RX REQ SendData 166 ACK RECEIVED from device in 24ms
18:24:51.749	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-2 -> EP-1 ASSOCIATION_GROUPINGS_REPORT Supports 3 groups
18:24:51.758	13	
TX REQ SendData 167 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-2 ZWAVE_PLUS_INFO_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.764	13	
RX RES SendData 167 ACCEPTED BY CONTROLLER
18:24:51.780	13	
RX REQ SendData 167 ACK RECEIVED from device in 22ms
18:24:51.796	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-2 -> EP-1 ZWAVE_PLUS_INFO_REPORT
18:24:51.836	13	
TX REQ SendData 168 ALARM_EVENTSUPPORTED_GET  ACK AUTO_ROUTE EXPLORE
18:24:51.842	13	
RX RES SendData 168 ACCEPTED BY CONTROLLER
18:24:51.858	13	
RX REQ SendData 168 ACK RECEIVED from device in 22ms
18:24:51.871	13	
RX REQ ApplicationCommandHandler ALARM_EVENTSUPPORTED_REPORT
18:24:51.879	13	
TX REQ SendData 169 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:51.885	13	
RX RES SendData 169 ACCEPTED BY CONTROLLER
18:24:51.901	13	
RX REQ SendData 169 ACK RECEIVED from device in 22ms
18:24:51.916	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_1 Lifeline
18:24:51.924	13	
TX REQ SendData 170 ASSOCIATION_GROUP_INFO_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:51.930	13	
RX RES SendData 170 ACCEPTED BY CONTROLLER
18:24:51.947	13	
RX REQ SendData 170 ACK RECEIVED from device in 23ms
18:24:51.960	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:51.969	13	
TX REQ SendData 171 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:51.975	13	
RX RES SendData 171 ACCEPTED BY CONTROLLER
18:24:51.991	13	
RX REQ SendData 171 ACK RECEIVED from device in 22ms
18:24:52.007	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_1
18:24:52.017	13	
TX REQ SendData 172 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.023	13	
RX RES SendData 172 ACCEPTED BY CONTROLLER
18:24:52.039	13	
RX REQ SendData 172 ACK RECEIVED from device in 22ms
18:24:52.056	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_2 On/Off (Key 1)
18:24:52.066	13	
TX REQ SendData 173 ASSOCIATION_GROUP_INFO_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.072	13	
RX RES SendData 173 ACCEPTED BY CONTROLLER
18:24:52.089	13	
RX REQ SendData 173 ACK RECEIVED from device in 23ms
18:24:52.103	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.122	13	
TX REQ SendData 174 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.129	13	
RX RES SendData 174 ACCEPTED BY CONTROLLER
18:24:52.146	13	
RX REQ SendData 174 ACK RECEIVED from device in 24ms
18:24:52.158	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_2
18:24:52.188	13	
TX REQ SendData 175 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:52.195	13	
RX RES SendData 175 ACCEPTED BY CONTROLLER
18:24:52.212	13	
RX REQ SendData 175 ACK RECEIVED from device in 24ms
18:24:52.281	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_3 Dimmer (Key 1)
18:24:52.289	13	
TX REQ SendData 176 ASSOCIATION_GROUP_INFO_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:52.295	13	
RX RES SendData 176 ACCEPTED BY CONTROLLER
18:24:52.311	13	
RX REQ SendData 176 ACK RECEIVED from device in 22ms
18:24:52.326	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.340	13	
TX REQ SendData 177 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:52.347	13	
RX RES SendData 177 ACCEPTED BY CONTROLLER
18:24:52.366	13	
RX REQ SendData 177 ACK RECEIVED from device in 26ms
18:24:52.376	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_3
18:24:52.396	13	
TX REQ SendData 178 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:52.410	13	
RX RES SendData 178 ACCEPTED BY CONTROLLER
18:24:52.419	13	
RX REQ SendData 178 ACK RECEIVED from device in 23ms
18:24:52.436	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_4 On/Off (Key 2)
18:24:52.447	13	
TX REQ SendData 179 ASSOCIATION_GROUP_INFO_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:52.454	13	
RX RES SendData 179 ACCEPTED BY CONTROLLER
18:24:52.470	13	
RX REQ SendData 179 ACK RECEIVED from device in 23ms
18:24:52.484	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.495	13	
TX REQ SendData 180 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:52.500	13	
RX RES SendData 180 ACCEPTED BY CONTROLLER
18:24:52.517	13	
RX REQ SendData 180 ACK RECEIVED from device in 22ms
18:24:52.530	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_4
18:24:52.539	13	
TX REQ SendData 181 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_5  ACK AUTO_ROUTE EXPLORE
18:24:52.545	13	
RX RES SendData 181 ACCEPTED BY CONTROLLER
18:24:52.561	13	
RX REQ SendData 181 ACK RECEIVED from device in 22ms
18:24:52.577	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_5 Dimmer (Key 2)
18:24:52.586	13	
TX REQ SendData 182 ASSOCIATION_GROUP_INFO_GET GROUP_5  ACK AUTO_ROUTE EXPLORE
18:24:52.591	13	
RX RES SendData 182 ACCEPTED BY CONTROLLER
18:24:52.608	13	
RX REQ SendData 182 ACK RECEIVED from device in 22ms
18:24:52.622	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.631	13	
TX REQ SendData 183 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_5  ACK AUTO_ROUTE EXPLORE
18:24:52.638	13	
RX RES SendData 183 ACCEPTED BY CONTROLLER
18:24:52.655	13	
RX REQ SendData 183 ACK RECEIVED from device in 24ms
18:24:52.666	13	
RX REQ ApplicationCommandHandler ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_5
18:24:52.674	13	
TX REQ SendData 184 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:52.681	13	
RX RES SendData 184 ACCEPTED BY CONTROLLER
18:24:52.698	13	
RX REQ SendData 184 ACK RECEIVED from device in 24ms
18:24:52.718	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_1 Key 1 via Lifeline
18:24:52.728	13	
TX REQ SendData 185 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:52.734	13	
RX RES SendData 185 ACCEPTED BY CONTROLLER
18:24:52.752	13	
RX REQ SendData 185 ACK RECEIVED from device in 24ms
18:24:52.768	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.777	13	
TX REQ SendData 186 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_1  ACK AUTO_ROUTE EXPLORE
18:24:52.783	13	
RX RES SendData 186 ACCEPTED BY CONTROLLER
18:24:52.801	13	
RX REQ SendData 186 ACK RECEIVED from device in 24ms
18:24:52.814	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_1
18:24:52.823	13	
TX REQ SendData 187 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.830	13	
RX RES SendData 187 ACCEPTED BY CONTROLLER
18:24:52.847	13	
RX REQ SendData 187 ACK RECEIVED from device in 24ms
18:24:52.864	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_2 On/Off (Key 1)
18:24:52.874	13	
TX REQ SendData 188 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.881	13	
RX RES SendData 188 ACCEPTED BY CONTROLLER
18:24:52.899	13	
RX REQ SendData 188 ACK RECEIVED from device in 25ms
18:24:52.913	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:52.924	13	
TX REQ SendData 189 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_2  ACK AUTO_ROUTE EXPLORE
18:24:52.930	13	
RX RES SendData 189 ACCEPTED BY CONTROLLER
18:24:52.948	13	
RX REQ SendData 189 ACK RECEIVED from device in 24ms
18:24:52.961	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_2
18:24:52.996	13	
TX REQ SendData 190 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:53.005	13	
RX RES SendData 190 ACCEPTED BY CONTROLLER
18:24:53.021	13	
RX REQ SendData 190 ACK RECEIVED from device in 25ms
18:24:53.040	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_3 Dimmer (Key 1)
18:24:53.055	13	
TX REQ SendData 191 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:53.063	13	
RX RES SendData 191 ACCEPTED BY CONTROLLER
18:24:53.080	13	
RX REQ SendData 191 ACK RECEIVED from device in 25ms
18:24:53.096	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:53.111	13	
TX REQ SendData 192 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_3  ACK AUTO_ROUTE EXPLORE
18:24:53.119	13	
RX RES SendData 192 ACCEPTED BY CONTROLLER
18:24:53.136	13	
RX REQ SendData 192 ACK RECEIVED from device in 25ms
18:24:53.150	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_REPORT GROUP_3
18:24:53.164	13	
TX REQ SendData 193 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:53.170	13	
RX RES SendData 193 ACCEPTED BY CONTROLLER
18:24:53.188	13	
RX REQ SendData 193 ACK RECEIVED from device in 24ms
18:24:53.208	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_NAME_REPORT GROUP_4 On/Off (Key 2)
18:24:53.224	13	
TX REQ SendData 194 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:53.231	13	
RX RES SendData 194 ACCEPTED BY CONTROLLER
18:24:53.249	13	
RX REQ SendData 194 ACK RECEIVED from device in 25ms
18:24:53.265	13	
RX REQ ApplicationCommandHandler MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_REPORT GROUP_1
18:24:53.279	13	
TX REQ SendData 195 MULTI_CHANNEL_CMD_ENCAP EP-1 -> EP-1 ASSOCIATION_GROUP_INFO_COMMAND_GET GROUP_4  ACK AUTO_ROUTE EXPLORE
18:24:53.286	13	
RX RES SendData 195 ACCEPTED BY CONTROLLER
18:24:53.304	13	
RX REQ SendData 195 ACK RECEIVED from device in 25ms
18:24:58.294	13	
Message retry (2 attempts remaining)
18:25:05.846		
TX REQ AddNodeToNetwork ADD_NODE_STOP
18:25:05.902	13	
RX REQ AddNodeToNetwork ADD_NODE_STATUS_DONE NODE 13

chris · October 3, 2017, 9:10am

Please provide the actual log - I’veno idea what this format is, but it’s not usable for me - sorry.

sjcliffe · October 3, 2017, 10:06am

Sorry - it was a cut/paste from the log viewer. The raw logs exceed the body size limit here and txt files aren’t allowed as attachments so the logs are here - http://www.sjcnet.id.au/ZW129-logs.txt

sjcliffe · October 15, 2017, 7:03am

@chris just wondering if you’ve had a chance to look at these logs and can offer any suggestions? Thanks.

wrotebyreuben · November 6, 2017, 3:08am

Hi @sjcliffe did you manage your ZW129 this working? I’m about to try homeseer or something else, as they are just sitting in a draw at present.

sjcliffe · November 6, 2017, 4:53am

No, I never heard anything back from Chris and I haven’t had much time to dig into the issue myself.

sjcliffe · December 4, 2017, 3:29am

It looks like this device has been added to the Zwave database @wrotebyreuben, so I’m going to update to the latest snapshot version of the binding and see how it goes.

dbadia · December 9, 2017, 10:27am

@chris Hey Chris
Been reading through this thread to get up to speed on how to add a device to the database since they have moved out of the zwave project. I bought (yet another) Jasco power plug (always looking for the cheapest!) that seems slightly different and is not in the database yet.

The question is, should I create a new database entry for it?
The unknown device looks similar to this
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/719

Mine has the same manufacturer id, but a different manufacturerRef of 4450:3031, here is a screenshot from habmin:

PS I couldn’t remember the name of the database site so I googled “zwave chris” and the first hit was cd-jackson.com

chris · December 9, 2017, 11:44am

Hi Dave,
If it’s the same device name (ie model number), and has the same/similar command classes, then just add the ids to the existing device… Otherwise, create a new one.

Cheers
Chris

dbadia · December 9, 2017, 7:14pm

@chris ok it looks I will create a new one, as the model number is different. What is the proper procedure, should I submit somthing through your website or can I copy and update an existing xml from the zwave github project?

Thanks!
Dafe