I saw some unexpected behaviour during first start but after a restart and letting the network settle a bit everything is working fine (as always).
20-Jan-2018 20:02:10.853 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! 0002:0005:0003::2.51
20-Jan-2018 20:02:10.857 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 0154:0100:0201::2.1
20-Jan-2018 20:02:10.857 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 26: Device discovery could not resolve to a thingType! 0060:000D:0001::1.5
20-Jan-2018 20:02:10.860 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 40: Device discovery could not resolve to a thingType! 010F:0501:1002::2.1
20-Jan-2018 20:02:10.862 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:10.865 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! 010F:0202:1002::2.2
20-Jan-2018 20:02:10.872 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 010F:0600:1000::25.25
20-Jan-2018 20:02:10.877 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 41: Device discovery could not resolve to a thingType! 010F:0600:1000::25.25
20-Jan-2018 20:02:10.882 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 31: Device discovery could not resolve to a thingType! 010F:0203:1000::3.2
20-Jan-2018 20:02:10.886 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:10.900 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 010F:0501:1002::2.1
20-Jan-2018 20:02:10.934 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:10.939 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 010F:0800:1001::2.6
20-Jan-2018 20:02:10.944 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:10.942 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:10.935 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
20-Jan-2018 20:02:11.133 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 36: Device discovery could not resolve to a thingType! 010F:0202:1002::2.2
20-Jan-2018 20:02:11.133 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 39: Device discovery could not resolve to a thingType! 0108:0002:000D::1.18
20-Jan-2018 20:02:11.155 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 37: Device discovery could not resolve to a thingType! 010F:0102:1000::3.3
20-Jan-2018 20:02:11.155 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 30: Device discovery could not resolve to a thingType! 010F:0203:1000::3.2
i think i have the same problem??
Its a Fibaro Plug
Device discovery could not resolve to a thingType! 010F:0600:1000::25.25
I deleted it and readded … but now its in Habmin a unknown device too.
I deleted it again … and the xml file and readded it again. I upload the new created xml file to chris database
i use the zwave Binding from 20.01.18 and the release version 2.2 from Dez 17
configuring the things via paperui is not an option, i need the manual thing configuration (remote access).
i also tried the latest org.openhab.binding.zwave-2.3.0-SNAPSHOT.jar version from the first post - but same error message.
any ideas?
Thomas
Quick question about upgrading… I am running OH2 2.2.0 with the zwave jar from this thread back in november: 2.2.0.201711192127. Things are working well.
I tried upgrading to the current Jan 18 jar at the top of this thread (2.3.0.201801212218), but when I restarted and applied the new binding I got a ton of errors on startup.
Are there extra steps needed to upgrade from 2.2.0.201711192127 to 2.3.0.201801212218?
Did you delete the old jar and drop in the new one? If so, odds are the old one was cached. The new jar’s name is different than the old one, so it didn’t replace it like a regular update would do (same names). Do a bundle:list|grep -i zwave. and you will probably see two versions of the binding installed. Restarting OH may help, or do a bundle:uninstall X, where X is the old bundle ID. Hope this helps!
which appears correct. Restarted but still getting lots of errors; looks like issues parsing the thing files:
[WARN ] [ig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/thing/fibaro_fgs222_0_0.xml' in module 'org.openhab.binding.zwave' could not be parsed: The document is invalid, it contains further unsupported data <SNIP>
class : org.eclipse.smarthome.core.thing.xml.internal.ThingTypeXmlResult
required-type : org.eclipse.smarthome.core.thing.xml.internal.ThingTypeXmlResult
converter-type : org.eclipse.smarthome.core.thing.xml.internal.ThingTypeConverter
path : /thing-descriptions/thing-type
line number : 272
class[1] : java.util.ArrayList
converter-type[1] : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[2] : org.eclipse.smarthome.core.thing.xml.internal.ThingDescriptionList
converter-type[2] : org.eclipse.smarthome.core.thing.xml.internal.ThingDescriptionConverter
version : 1.4.7
See lots of these for different thing files. Full log is on pastebin
Any way to increase the number of nodes that are initialising? HABmin shows a max of 3 devices in “Node initialising: REQUEST_NIF”. I have 27 IX32 based motion sensors and since they are battery powered they only talk to the controller when there is active motion. Since only 3 devices can be in that initialising state, motion from other sensors is ignored, it requires the motion of the sensors in that state to initialise. If all battery powered devices could be in REQUEST_NIF that network could come up much faster then randomly hoping there is motion in the 3 devices in that state. @chris, is this possible or does it cause other problems?
The root of the issue may be that my IX32 devices don’t wake up unless there is motion rather than waking up every 30 min or something.
I don’t see any issues with the file so I’m not sure why you get these errors. I also checked the file using another XML checker, and it also shows the format is ok so I’m not really sure what’s up…
I have installed the new binding and am trying to add my Kwikset Smartcode 916 lock to openhab. I can find the lock and add it but not with security enabled. I have tried “forgetting” and refinding it both by excluding it and re-including it from the zwave net and by delting it and refinding it with open had (paper ui). Nothing has worked. I have attacned my debug code below. Any suggestions would be appreciated.
Thanks
12:14:54.362 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from ONLINE to REMOVING
12:14:54.372 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from REMOVING to REMOVED
12:14:54.423 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from REMOVED to UNINITIALIZED
12:14:54.589 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from REMOVED to UNINITIALIZED (HANDLER_MISSING_ERROR)
12:16:48.378 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'zwave:device:654457c4:node2' has been added.
12:16:48.376 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:654457c4:node2' to inbox.
12:16:48.393 [ERROR] [ding.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
12:16:54.909 [INFO ] [smarthome.event.InboxRemovedEvent ] - Discovery Result with UID 'zwave:device:654457c4:node2' has been removed.
12:16:54.925 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from UNINITIALIZED to INITIALIZING
12:16:55.010 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
12:16:55.027 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
12:16:55.050 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
12:16:55.115 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
12:16:55.119 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
12:16:55.125 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:654457c4:node2' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
12:16:55.150 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:654457c4:node2' has been updated.
12:16:55.175 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:654457c4:node2' has been updated.
12:16:55.194 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:654457c4:node2' has been updated.
12:16:55.207 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:654457c4:node2' has been updated.