Binding has generated XML at the end, but it does not work. No channels are recognized at all: network_d8a23a12__node_163.xml (1.8 KB)
There is one faliure message in trace log:
This is the log of the original inclusion: node163.log (25.5 KB)
All in all I think it needs to be added into the zwave database. I can prepare manually an xml for that from network_d8a23a12__node_104.xml (10.4 KB)
as it is same manufacturer’s motion sensor what works very well for years now for me. Pls advise what to do that I can start using this sensor. Thanks in advance!
Using information from the manual and from other source one could hack an XML file together, but I strongly recommend trying to get a valid XML file from your device. I may be wrong, but I would assume that if OH cannot get 0x60/1/4 from your device, it cannot match your device to an entry in the Z-Wave database (even if the entry exists).
It would be good to see a full log of the inclusion - without any filtering (I’m not sure if this log is filtered, but it doesn’t seem complete).
The only commands received are security commands which makes me think that this device might need to be included differently to avoid S2, or possibly it was included previously and needs to be reset. Again though, a complete log of the inclusion, without any filtering would be good - include the device, then wake it up every 5 seconds for a minute or so, then send over the logs.
Yes it is filtered as I have nearly 100 devices. Ok. I’ll make a new inclusion and I reset the device and clear Zwave stick as well before the inclusion. May be it was included before I was not resetting after all inclusion and I don’t remember witch one it is.
The problem is that you remove too much, and it’s impossible to see what is happening - the log shows absolutely no commands being sent by the binding, which doesn’t look right. It’s very difficult to filter the logs in this way and still keep enough information to make it useful and it’s best just to feed it into the log viewer and do the filtering there.
If you provide a log that is only a minute or two long, it won’t be too big, and the log viewer will easily be able to filter this in a nice manageable way.
In this log, the device doesn’t respond to the security requests. This is likely indicative that the device was already included since the device will only respond to the security requests within the first 15 seconds after inclusion.
Maybe there’s another explanation - I’m not familiar with the device. The device does acknowledge that it received the commands, but doesn’t send back the required response.
I also don’t see any wakeup messages in the log. After failing the key exchange, the binding moves on to try without security but this doesn’t proceed since there are no wakeups. Did you wake up the device every few seconds as suggested above?
If you did this I don’t see it in the logs which is a bit strange.
Do you need to use security on this device? If not, why not disable security and try to include it? You can set the setting in the controller thing to only include security devices - or simply not to use security at all.
Here it is. I have turned off secured inclusion and I was pushing button during inclusion.
But I’m not sure how to wake it up as it has not written in the manual. Just inclusion, exclusion and device reset.
So secure inclusion was still active, but at least it completed ok this time.
Well, I guess this is your homework .
Somehow there needs to be a way to wake up the device, otherwise it can’t communicate. You could leave it for “some time” (I’ve no idea how long) and it might wake up - but this is not guaranteed - it’s not guaranteed that wakeup is enabled by default, and if it is, it normally uses a broadcast message which will not route in the mesh network, so the device will need to be kept close to the controller.
manufacturer not set. What should I do to complete the inclusion? I was succesull with SP816 same manufacturer, but I think it was also hard. However it does not have this DMC code exchange possibility. I have set Do not use Security in the Zwave controller. I thought this is the way to stop secured inclusion.
So I hate to poke in here because you have the master looking at your problem. However, after he gets you up and running your inclusion logs are great data for PRs I’m promoting, so I’m going to try to help this along and try not to get in the way.
First there are more than a few devices that use 3 pushes to include/exclude, but one push (a solid one, but not too long) for wake-up. I do not see that in the documentation, but it might be worth a try. Space the tries out about 10 seconds apart. From the logs I glanced over the include sequence is not producing the correct message “wake up Notification”. You could wait as @chris suggests(it looks like the default is 4 hours), but usually that is set in the part of the initialization that you haven’t got to yet. Hard to say.
The other issue is the device is in the OH zwave database, but in a modified state. Whoever, did the initial set-up did not press “Request review” AND it looks like this is the original edit, so it is NOT in the Zwave binding you are using. Modified devices are excluded from the biweekly builds.
Again - you need to wake up the device or wait for it to wake up by itself - as mentioned above.
There should be a way to wake it up manually as this is nearly always needed, and I don’t think I’ve come across a battery device that doesn’t support this.
This is being done by @kovacsi2899 but until there is an XML file created for the device, we can’t create the database. He created this manually which is not a good idea. Also, having a database entry will not in any way help here - what is needed is the discovery to complete - the database is not involved in this at all.
Thanks for the clarification on that. I thought maybe it was set up some time ago and just not reviewed. again, trying to help, but not get in the way.
@kovacsi2899 Ok besides the one press idea, the device document talks about holding the tamper button for 10 seconds and then releasing. That could be the wake-up notification. Put the binding in Debug to see if either idea works.
Exclude the device from your Z-Wave controller in order to not create a ghost device.
Press the learn key 3 times within 1.5 seconds to put the unit into exclusion mode.
Within 1 second of step 1, press the learn key again and hold for 5 seconds.
Node ID is excluded. The device reverts to factory default state.
LED indication: 2-second on, 2-second off For 2 minutes
Then remove the battery, wait for 5 seconds, set the Z-Wave binding to Include Mode (“Scan”) and refit the battery. This should activate Auto Inclusion and should give the Z-Wave binding 30 seconds for interviewing the device.
This time binding recognized the device manufacturer and data. No channel created unfortunatelly. Now as device is recognized I have a hope that correct XML will be created by the binding. System is always recreating the XMLs. I do not know what’s behind. All of my devices has right XML except this one. So I keep trying and as soon as I have result I post.
.