(this way the bindings and other dependencies, are al freshly downloaded I believe)
The addons dir only has the now 30 minute old org.openhab.ui.habmin_2.0.0.SNAPSHOT-0.1.0.jar, and influxdb persistence (1.8.1) and wol binding (1.8.1).
At first startup I see some ‘Unresolved requirement’ messages, but this settles down later.
I’ve been able to test the z-wave binding. First, congrats for it. Great job.
All my devices were found right awway and added, I got a problem with my remote control NODON and found in the logs the following: 15:02:28.600 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:unknown:1532328a11f:node8' to inbox. 15:02:28.602 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'zwave:unknown:1532328a11f:node8' has been added.
Is this device already in the database? I attached the file just in case it might help. node8.xml (4.3 KB)
Thanks in advance,
The number 1800 of the default polling period gets set (initially) as a String apparently, (aeotec color led bulb again)
saw this exception:
Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.math.BigDecimal
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:108)[152:org.openhab.binding.zwave:2.0.0.201602270203]
This goes away when I set the polling period manually.
A small thing I guess, when I understand this whole thing better, you get some PR’s from me
I think I can find out why some converters are not found as well… will take some time
2016-02-27 16:47:41.519 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No converter set for zwave:greenwave_gwpn6_00_000:1530ad9faba:node10:meter_watts1
2016-02-27 16:46:10.765 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:meter_watts
2016-02-27 16:44:44.870 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:alarm_general
2016-02-27 16:42:10.362 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter set for zwave:aeon_zw098_00_000:1530ad9faba:node8:switch_dimmer
2016-02-27 16:40:05.560 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:sensor_power
It’s defined an integer - there was a long discussion on this a week or so back on GH. The problem is elsewhere - the issue is that if the value isn’t set when the thing is first created, then OH2 assume it’s a String. I suspect that this is a hangover from a previous save where the period wasn’t set…
Currently this isn’t in the database - well, it’s in the online database, but not exported into the binding… The issue is I need to have a think about how to handle remote controls - I’ll look at this over the next week…
I restarted from scractch today, with the maven 157 build, (online). Great to have zwave, but have I understood correctly that I need to install Habmin2 manually? (download jars and put in addons folder)
I see no reference for it in Paper.
Yes - at the moment you just need to download it and drop it into the addons folder. I hope that in the coming week or so we should get that sorted but I want to tidy up a few things first…
I also have the same problem with my BNext Plugin dimmer
2016-02-27 16:22:07.544 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
2016-02-27 16:22:08.104 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device could not be resolved to a thingType! 008A:0018:0100::0.63
2016-02-27 16:22:08.200 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:unknown:1532328a11f:node6’ to inbox.
2016-02-27 16:22:08.206 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID ‘zwave:unknown:1532328a11f:node6’ has been added.
2016-02-27 16:22:38.074 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device could not be resolved to a thingType! 008A:0018:0100::0.63
Whats triggering items to show up as unknown? I understand that when they aren’t in the database they are ofc unknown. But i have som items that does not show up at all even though i know they are in the network and i can see their messages in the log.
This often happens with battery items. They, depending on the device, have to go through one to many cycles of wake-up before all the information is transacted between the device and the binding. The device will only show up in the binding once this process is done and the xml file is generated. If you desire to speed this up, often the devices have a wake button or z-wave button on the device that can be pressed. You may have to go through a few presses with the button as well.
I think there’s a bug somewhere where the database isn’t being read some of the time. Some people have this issue, but most don’t - and some people might have it sometimes (so it seems here)…
Do you have a full debug log - ie not just the zwave parts, but also the other parts of OH2? If so, I’d really like to see what happens during startup and discovery.
Hey @chris, here is my full startup log on debug level, you’ll see the multiple occurrences of converters not found. At the end I’ve set the dimmer of the aeotec leb bulb up. openhab.part1.log.xml (735.5 KB)openhab.part2.log.xml (658.5 KB) Hope this helps, I’ll try to get a development environment running later.
Yep - hopefully (??) it will pick up all the same thing names again. I just need to make sure that it’s reading the new configuration changes I made on Friday…
