Howto add a device to the zwave database

Yes…

And this message keeps repeating in the log too…

2016-10-31 15:56:56.025 [TRACE] [.z.internal.protocol.ZWaveNode:504 ]- NODE 8: App version requested but version is unknown
2016-10-31 15:56:56.028 [DEBUG] [.z.i.config.ZWaveConfiguration:288 ]- NODE 8: No database entry: GE [ID:3133,Type:4953]
2016-10-31 15:57:01.052 [TRACE] [.z.internal.protocol.ZWaveNode:504 ]- NODE 8: App version requested but version is unknown
2016-10-31 15:57:01.053 [DEBUG] [.z.i.config.ZWaveConfiguration:288 ]- NODE 8: No database entry: GE [ID:3133,Type:4953]

Still no other node xml’s in the folder either.

12:23:56.623 8
RX REQ Add Node ADD_NODE_STATUS_ADDING_SLAVE NODE 8AddNodeToNetwork
12:23:56.907
RX REQ Add Node ADD_NODE_STATUS_PROTOCOL_DONEAddNodeToNetwork
12:23:59.116 8
RX REQ BATTERY_REPORT 100%ApplicationCommandHandler
12:24:17.330
TX REQ Add Node ADD_NODE_STOPAddNodeToNetwork
12:24:17.483 8
RX REQ Add Node ADD_NODE_STATUS_DONE NODE 8AddNodeToNetwork
12:24:17.548 8
Stage advanced to PROTOINFO
12:24:17.552 8
TX REQ IdentifyNode
12:24:17.555 8
RX RES IdentifyNode: ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMINGIdentifyNode
12:24:17.584 8
Stage advanced to NEIGHBORS
12:24:17.593 8
TX REQ GetRoutingInfo
12:24:17.600 8
RX RES RoutingInfo: Found 1 neighboursGetRoutingInfo
12:24:17.621 8
Stage advanced to FAILED_CHECK
12:24:17.629 8
TX REQ Check if node 8 is failedIsFailedNodeID
12:24:17.631 8
RX RES Node is marked as HEALTHY by controllerIsFailedNodeID
12:24:17.652 8
Stage advanced to WAIT
12:26:07.878 8
Stage advanced to PROTOINFO
12:26:07.881 8
TX REQ IdentifyNode
12:26:07.887 8
RX RES IdentifyNode: ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMINGIdentifyNode
12:26:07.916 8
Stage advanced to NEIGHBORS
12:26:07.927 8
TX REQ GetRoutingInfo
12:26:07.934 8
RX RES RoutingInfo: Found 1 neighboursGetRoutingInfo
12:26:07.959 8
Stage advanced to FAILED_CHECK
12:26:07.966 8
TX REQ Check if node 8 is failedIsFailedNodeID
12:26:07.968 8
RX RES Node is marked as HEALTHY by controllerIsFailedNodeID
12:26:07.989 8
Stage advanced to WAIT
13:33:37.294 8
RX REQ ApplicationUpdate UPDATE_STATE_NODE_INFO_RECEIVEDApplicationUpdate
13:33:37.350 8
Node is AWAKE
13:33:37.353 8
Heal stage advanced to STARTING
13:33:37.353 8
Heal stage advanced to PING
13:33:37.360 8
TX REQ SendData 2 Sent NO_OPERATIONSendData ACK AUTO_ROUTE EXPLORE
13:33:37.369 8
Stage advanced to PING
13:33:37.376 8
RX RES SendData 2 ACCEPTED BY CONTROLLERSendData
13:33:37.389 8
RX REQ SendData 2 ACK RECEIVED from device in 29msSendData
13:33:37.403 8
Heal stage advanced to SETSUCROUTE
13:33:37.404 8
Heal stage advanced to UPDATENEIGHBORS
13:33:37.411 8
Stage advanced to DETAILS
13:33:37.413 8
Stage advanced to MANUFACTURER
13:33:37.421 8
TX REQ SendData 4 Sent MANUFACTURER_SPECIFIC_GETSendData ACK AUTO_ROUTE EXPLORE
13:33:37.431 8
RX RES SendData 4 ACCEPTED BY CONTROLLERSendData
13:33:37.447 8
RX REQ SendData 4 ACK RECEIVED from device in 26msSendData
13:33:37.459 8
RX REQ MANUFACTURER_SPECIFIC_REPORT 0063:4953:3133 Device UNKNOWNApplicationCommandHandler
13:33:37.482 8
Stage advanced to VERSION
13:33:39.062 8
TX REQ SendData 5 Sent VERSION_COMMAND_CLASS_GET WAKE_UPSendData ACK AUTO_ROUTE EXPLORE
13:33:39.072 8
RX RES SendData 5 ACCEPTED BY CONTROLLERSendData
13:33:39.088 8
RX REQ SendData 5 ACK RECEIVED from device in 26msSendData
13:33:39.103 8
RX REQ VERSION_COMMAND_CLASS_REPORT WAKE_UP VERSION 2ApplicationCommandHandler
13:33:39.133 8
TX REQ SendData 6 Sent VERSION_COMMAND_CLASS_GET SENSOR_BINARYSendData ACK AUTO_ROUTE EXPLORE
13:33:39.143 8
RX RES SendData 6 ACCEPTED BY CONTROLLERSendData
13:33:39.158 8
RX REQ SendData 6 ACK RECEIVED from device in 25msSendData
13:33:39.173 8
RX REQ VERSION_COMMAND_CLASS_REPORT SENSOR_BINARY VERSION 2ApplicationCommandHandler
13:33:40.704 8
Stage advanced to APP_VERSION
13:33:40.712 8
RX REQ DEVICE_RESET_LOCALLY 01ApplicationCommandHandler
13:33:40.726 8
TX REQ SendData 7 Sent VERSION_GETSendData ACK AUTO_ROUTE EXPLORE
13:33:40.734 8
RX RES SendData 7 ACCEPTED BY CONTROLLERSendData
13:33:45.004 8
RX REQ SendData 7 NO ACK after 4278msSendData
13:33:45.027 8
TX REQ RequestNodeNeighborUpdate
13:33:45.064 8
RX REQ Neighbor update STARTEDRequestNodeNeighborUpdate
13:33:52.729 8
RX REQ Neighbor update FAILEDRequestNodeNeighborUpdate

Ignore it. This is caused by HABmin polling for information - it’s nothing to do with the actual ZWave protocols etc.

I think you’re using OH1, so the database is not required for you to be able to use a device - only to configure it.

Yep, OH1.

It is actually showing a red dot now.

The data that comes up for the sensor is not displaying the correct information.

for instance…Generic device class comes up as garage_door

specific generic device comes up as simple_garage_door. I had the manufacturer name… now it comes up unknown.

If you restart OH, then the initialisation will start again from the beginning if it hasn’t got to certain points where it saves a consistent snapshot of the device, that’s probably why you used to have the manufacturer name etc.

Really though, without looking at logs, we can speculate forever and it’s all guesswork. If you want me to take a look at the log then I’m happy to do so, but really without the logs I can only guess - sorry.

I really appreciate the time that you have spent helping folks on this site. I am really trying to figure this out without bothering you even more.

I will try a restart of OH and see where that goes.

After that, if you REALLY do have time to look at the logs… How do I go about getting the logs to you?

Thanks for all that you do for us here!

Rob

I appreciate it :slight_smile: , but if you’re stuck I’m happy to take a look…

Either put them on dropbox or a similar file sharing system, or you can mail them to me - chris -at- cd-jackson.com

I restarted OH… Some changes… Two other “phantom” nodes showed up???

Still a red dot.

I sent my log file to you moments ago.

Thanks again!

Rob

I’ve got the logs - will take a quick look shortly.

Clearly the device has been working - we see this earlier in the day -:

However, more recently we only get the following -:

This tells us that the controller (ie the USB stick) thinks that the device is dead - this is always bad news. Is the device a long distance from the controller?

I think I would be tempted to reset the device and re-include it. Keep it close to the controller while you do all this (it doesn’t have to be inches away - but in the same room). Keep the logging set to DEBUG or TRACE and let’s see what that shows.

The sensor is about 3 inches away from the USB stick. I did try moving the sensor into another area of the room as well as into another nearby room, in case there was a problem in the “cone of confusion”. That didn’t make any difference either.

Resetting this device calls for pressing the button 10 times within 6 seconds… which I have tried. Honestly, I’m pretty sure that is not actually resetting and I don’t think that I have successfully excluded the device from OH.

Should I try a different technique?

Thanks!

Rob

I have successfully added the device!

WHEW! That was frustrating!

Ok, I now have a node xml for this device to add to the database.

I’ll email it to you shortly.

Thanks again!!!

Rob

EDIT Email sent!

Somehow, the create user account showed up this time when I went to your z wave database site.

I created a user account, got the email back activating my account. But I am unable to login… something about not having access to private data…

My user account is treborjm87.

I think that this is where I can go to upload that xml?

Thanks Chris!

Rob

Can you tell me where you get this error - ie what page is giving it? I recently updated the CMS and some security changed - I’ve just tried this with a new user and it seems to work ok…

This is the error that I get.

Warning
You can’t access the private section of this site.

I’ll try to create another user.

Thanks, but what page did you try and access to get the error? Is it on all pages, or something specific?

That’s just logging in after creating an account, activating, then trying to log in.

BTW… what do I do about the “secret key”?

Ignore it. If I can get rid of it I will - I added extra authentication on the admin page recently, so it’s only valid for that - I’ve just not worked out how to remove the box on the frontend login :confused:

Ok - I see the error here - I’ll take a look.

So, I created a second user, with the same results.

I have two users, both activated via email, that get the same error about no access to private section.

Warning
You can’t access the private section of this site.

Also tried using an incorrect password to see if the results would be different…

Got the usual wrong username or password.