2018-03-31 09:58:37.909 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-03-31 09:58:37.934 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-03-31 09:58:37.951 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-03-31 09:58:37.959 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:162781cb352:node29’ to inbox.
2018-03-31 09:59:07.075 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-03-31 09:59:07.083 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:162781cb352:node33’ to inbox.
2018-03-31 09:59:07.097 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-03-31 09:59:07.109 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:162781cb352:node34’ to inbox.
2018-03-31 09:59:07.128 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
Basically, yes. The controller remembers all the devices that it has included into the network - if you include the same device twice without excluding it from the controller, then the controller has no way to know if you added two different devices, or the same device twice.
In HABmin, in the controller configuration, there is an option to hard reset the controller.
Thanks for your fast response - so i understand that i see one point twice.
I have installed
habmin version 2.0
Z-Wave Binding 2.2
Razberry2
When i go to Configuration - Thinks - Zwave controller (is online)
and i want to open tools (there isn’t any options)
When i look at this manual the tool window at excluding is missing?
Also when i look at the controller at Proberties the field for manufacture and type is empty?
I have battery powered FDSG-002 Fibaro Smoke Detector and they are detected as unkown and i think i will wait for a day and look if the are known tomorow
Ok, so from here I think we probably need to see a log. This shows that the device is alive and waking up, but it’s not completed initialisation and we need to find out why.
I suggest the following -:
enable debug logging (log:set debug org.openhab.binding.zwave) in the karaf console
stop openhab (or at least the binding)
delete or rename the openhab log file
restart the binding
wait a minute or so, then wake up the device a few times - let’s say 10 times, pressing the button every 10 second.
If the above doesn’t result in the Type / ID above showing some numbers, then send me the log and I’ll take a look.
The problem is that the device doesn’t appear to be responding to the ping requests that the binding sends to see if it’s alive during the initialisation sequence -:
I’m not sure why it doesn’t respond - it’s a standard requirement for devices to respond to these pings.
I would suggest to exclude it, and re-include it. This will perform a reset on the device which might help if it’s in some strange mode. If that doesn’t help, then we’ll have to look at other options, which probably means you changing to the development binding…
I’m not sure what you mean by this? The device still has the same node number, so it’s not been excluded and re-included.
However, in this log, it has got past the initial request, and it’s now requesting other information from the device - all requests time-out though and there are no responses at all from the device.
Please try again to exclude the device. There is an option in the controller options to set the controller into exclude mode. When you then include it again, it should have a new node id. If the inclusion works, then I’m not sure why the binding wouldn’t get responses to the messages the controller is sending as well.
Hmmm, well I think I’m out of ideas . I would have said it was a hardware problem - either the controller isn’t transmitting well, or the sensor isn’t receiving well, but given that inclusion works, this probably isn’t the case. However, the controller is receiving the wakeup messages, so it is transmitting ok, but there are no acks or responses to any messages the binding is sending - just the timeouts from the controller which mean the controller sent the message, but the device did not respond.
) to get my Raspberry3+Razberry2 in comination with the FGSD-002 V3.3 Smoke sensor up and running.
