Z-Wave Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

[qualar (Paul Smith)]

Hi All,

I’m having trouble getting the z-wave add-on to recognise all my devices, I got so frustrated with it that yesterday I wiped everything and re-installed. I still get:-

2017-03-26 09:50:35.943 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:36.286 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:36.629 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:36.966 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:37.298 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:37.666 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:38.334 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:38.638 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:38.944 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:39.278 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 16: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:50:39.548 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

I recently purchased a AEON zwave-plus stick (replacing a non-plus stick) as node 2+3 needed is, hence my nodes are not in purchase chronological order.

I think node 13 was node 8 which I performed a hardware reset on to see if that would send the manufactor details, node 4 to 11 are Fibaro Eye’s, 15 & 16 might be Fibaro smoke detectors (FGSS-001 v2.5 EU), node 7 & 14 worked on Friday and are both Fibaro Eye FGMS-001 EU v3.2, node 11 is an old Fibaro Eye (v2.6) and is detected.

It’s strange how everything that fails is battery operated…?

Any pointers to how I can debug this?

I’d like to attach the full zwave log but as a new user it’s stopping me, so here a grep on node 14:-

2017-03-26 09:27:17.857 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 14: Node found
2017-03-26 09:27:18.233 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 14: Init node thread start
2017-03-26 09:27:18.990 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 14: Serializing from file /opt/openhab2/userdata/zwave/node14.xml
2017-03-26 09:27:18.993 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 14: Error serializing from file: file does not exist.
2017-03-26 09:27:19.139 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Starting initialisation from EMPTYNODE
2017-03-26 09:27:19.148 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer - EMPTYNODE: queue length(0), free to send(true)
2017-03-26 09:27:19.167 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer: loop - EMPTYNODE try 1: stageAdvanced(false)
2017-03-26 09:27:19.168 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer: Initialisation starting
2017-03-26 09:27:19.170 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer - advancing to PROTOINFO
2017-03-26 09:27:19.172 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer: loop - PROTOINFO try 0: stageAdvanced(true)
2017-03-26 09:27:19.178 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer: PROTOINFO - send IdentifyNode
2017-03-26 09:27:19.219 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Node advancer - queued packet. Queue length is 1
2017-03-26 09:27:19.242 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 14: Init node thread finished
2017-03-26 09:27:19.553 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: ProtocolInfo
2017-03-26 09:27:19.556 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Listening = false
2017-03-26 09:27:19.558 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Routing = true
2017-03-26 09:27:19.560 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Beaming = true
2017-03-26 09:27:19.563 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Version = 4
2017-03-26 09:27:19.565 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: FLIRS = false
2017-03-26 09:27:19.567 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Security = false
2017-03-26 09:27:19.569 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Max Baud = 40000
2017-03-26 09:27:19.572 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Basic = Routing Slave
2017-03-26 09:27:19.574 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Generic = Sensor Notification
2017-03-26 09:27:19.576 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Specific = Notification Sensor
2017-03-26 09:27:19.578 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class NO_OPERATION
2017-03-26 09:27:19.580 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Command class NO_OPERATION, endpoint null created
2017-03-26 09:27:19.583 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Version = 1, version set. Enabling extra functionality.
…
…
…
2017-03-26 09:28:00.715 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Is sleeping
2017-03-26 09:28:00.716 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
2017-03-26 09:28:00.727 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: ProtocolInfo
2017-03-26 09:28:00.727 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Listening = false
2017-03-26 09:28:00.727 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Routing = true
2017-03-26 09:28:00.727 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Beaming = true
2017-03-26 09:28:00.728 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Version = 4
2017-03-26 09:28:00.728 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: FLIRS = false
2017-03-26 09:28:00.728 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Security = false
2017-03-26 09:28:00.728 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Max Baud = 40000
2017-03-26 09:28:00.728 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Basic = Routing Slave
2017-03-26 09:28:00.729 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Generic = Sensor Notification
2017-03-26 09:28:00.729 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 14: Specific = Notification Sensor
2017-03-26 09:28:00.729 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class NO_OPERATION
2017-03-26 09:28:00.729 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Command class NO_OPERATION, endpoint null created
…
…
…
2017-03-26 09:39:41.503 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER)
2017-03-26 09:39:41.505 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class ALARM
2017-03-26 09:39:41.506 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Received ALARM command V0
2017-03-26 09:39:41.507 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Process NOTIFICATION_REPORT V0
2017-03-26 09:39:41.508 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: NOTIFICATION report - 0 = 0, event=0, status=255
2017-03-26 09:39:41.509 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm Type = BURGLAR (0)
2017-03-26 09:39:41.547 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER)
2017-03-26 09:39:41.548 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class ALARM
2017-03-26 09:39:41.548 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Received ALARM command V0
2017-03-26 09:39:41.549 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Process NOTIFICATION_REPORT V0
2017-03-26 09:39:41.550 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: NOTIFICATION report - 0 = 0, event=0, status=255
2017-03-26 09:39:41.550 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm Type = BURGLAR (0)
…
2017-03-26 09:48:08.226 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class SENSOR_BINARY
2017-03-26 09:48:08.227 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 14: Received SENSOR_BINARY command V0
2017-03-26 09:48:08.228 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 14: Sensor Binary report, type=Unknown, value=0
2017-03-26 09:48:08.300 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER)
2017-03-26 09:48:08.302 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class SENSOR_BINARY
2017-03-26 09:48:08.303 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 14: Received SENSOR_BINARY command V0
2017-03-26 09:48:08.304 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 14: Sensor Binary report, type=Unknown, value=0
2017-03-26 09:48:08.467 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER)
2017-03-26 09:48:08.468 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class BASIC
2017-03-26 09:48:08.470 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Received Basic Request
2017-03-26 09:48:08.471 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Basic Set sent to the controller will be processed as Basic Report
2017-03-26 09:48:08.473 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Basic report, value = 0x00
2017-03-26 09:48:08.544 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER)
2017-03-26 09:48:08.546 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class BASIC
2017-03-26 09:48:08.547 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Received Basic Request
2017-03-26 09:48:08.549 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Basic Set sent to the controller will be processed as Basic Report
2017-03-26 09:48:08.550 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Basic report, value = 0x00
2017-03-26 09:50:38.335 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery completed
2017-03-26 09:50:38.335 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:qubino_zmnhaa_00_000
2017-03-26 09:50:38.336 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:cbcc_swzcs1_00_000
2017-03-26 09:50:38.336 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:everspring_sf812_00_000
2017-03-26 09:50:38.337 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:philio_psm02_00_000
2017-03-26 09:50:38.337 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:benext_benextalarmsound_00_000
2017-03-26 09:50:38.338 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:vision_zm1601_00_000
2017-03-26 09:50:38.338 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:vision_zm1601_00_000
2017-03-26 09:50:38.338 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:aeon_dsb28_00_000
2017-03-26 09:50:38.339 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:dragontech_wd100_00_000
2017-03-26 09:50:38.339 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:dragontech_wd100_00_000
2017-03-26 09:50:38.340 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:cooper_rfwc5_00_000
2017-03-26 09:50:38.340 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:benext_builtindimmer_00_000
2017-03-26 09:50:38.341 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:ufairy_ufairy2gangwallswitch_00_000
2017-03-26 09:50:38.341 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:tkb_tsm02_00_000
…
…
…
2017-03-26 09:50:38.634 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:mcohome_mhs312_00_000
2017-03-26 09:50:38.634 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:ge_zw3101_00_000
2017-03-26 09:50:38.635 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Checking zwave:aeon_dsc18_00_000
2017-03-26 09:50:38.638 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-26 09:51:50.867 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: MANUFACTURER not set
2017-03-26 09:51:50.868 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Controller status changed to ONLINE.
2017-03-26 09:51:50.868 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Controller is ONLINE. Starting device initialisation.
2017-03-26 09:51:50.870 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating node properties.
2017-03-26 09:51:50.871 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating node properties. MAN=2147483647
2017-03-26 09:51:50.874 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Properties synchronised
2017-03-26 09:51:50.880 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration synchronised
2017-03-26 09:51:50.928 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising Thing Node…
2017-03-26 09:51:50.931 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-03-26 10:02:10.413 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 14: Serialise aborted as static stages not complete
2017-03-26 10:02:10.424 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: MANUFACTURER not set
2017-03-26 10:02:10.425 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Controller status changed to ONLINE.
2017-03-26 10:02:10.426 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Controller is ONLINE. Starting device initialisation.
2017-03-26 10:02:10.428 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating node properties.
2017-03-26 10:02:10.429 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating node properties. MAN=2147483647
2017-03-26 10:02:10.430 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration synchronised
2017-03-26 10:02:10.460 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising Thing Node…
2017-03-26 10:02:10.461 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Polling intialised at 1800 seconds - start in 1800000 milliseconds.

Kind regards,

Paul

[chris (Chris Jackson)]

This indicates that the devices haven’t completed (or possibly started) their interrogation so the binding doesn’t know what they are. If the are battery devices, then they need to be woken up while in range of the controller so that the controller can interrogate them an initialise them. If they are mains devices, then this is normally a bit easier.

[qualar (Paul Smith)]

Thanks Chris,

I managed to get node 7 & 14 working by repeatedly deleting the inbox entry and repeating the discovery, each device appeared in different iterations.

I’ve left the 2 smoke detectors (FGSS-001 v2.5 EU) on there for over a day, how long do they take to initialise? Although these devices were purchased a couple of years ago, I’ve only just included them into the zwave network.

Paul

[chris (Chris Jackson)]

@qualar

I’ve left the 2 smoke detectors (FGSS-001 v2.5 EU) on there for over a day, how long do they take to initialise?

They probably won’t ever initialise - unless you wake them up manually.

Until the device is woken up (possibly a few times), the binding can’t configure it. Once the configuration is done, then the device will wake up automatically every hour or so (depending on your configuration) and the binding will be able to control it, but first time, it needs to be done manually.

[qualar (Paul Smith)]

That fixed 2 of the Eyes (so far), I had to triple click the B-Button then wait a bit for the zwave log to stop, and repeat that 2-3 times.

Hoping this will fix everything, thanks

Kind regards,

Paul

[tino21 (Tino)]

@chris
I have trouble to get my Devolo Home Control Metering Plug working. (same with the Devolo smoke alarm sensor). I have about 25 z wave items working (Fibaro, Devolo thermostate,…) but I can not get those working. I checked data base and as far as I understand both are in the data base. Openhab log file says:
017-12-12 19:04:15.247 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 31: Device discovery could not resolve to a thingType! 0175:0001:0012::1.14 (same for the smoke sensor) and
NODE 31: Invalid meter scale 7

Because at least the metering plug is not a battery device it should not have the wake up issue. Any idea what I can do ? Never had that problem with the other devices.

Thx

[tino21 (Tino)]

updating to the latest snapshot solved it --> Thx to @chris