Yes, and by newer binding I assume you mean the 2.5 M1? Yes, that’s the one I’m using.
Delete was done by admin interface - waste basket icon. Add was done in Admin.
Yes, normally, so I tried doing them through Admin, but still resulted in the same errors:
2019-06-21 12:34:26.951 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update received
2019-06-21 12:34:26.964 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update set group_4 to [node_23] (ArrayList)
2019-06-21 12:34:26.966 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Unknown association group 4
2019-06-21 12:34:26.969 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update set group_1 to controller (String)
2019-06-21 12:34:26.972 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Unknown association group 1
2019-06-21 12:34:26.974 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update set group_3 to [node_32] (ArrayList)
2019-06-21 12:34:26.977 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Unknown association group 3
2019-06-21 12:34:26.979 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update set group_2 to [node_15] (ArrayList)
2019-06-21 12:34:26.984 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Unknown association group 2
2019-06-21 12:34:48.814 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:VERSION)
2019-06-21 12:34:48.818 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2019-06-21 12:34:48.821 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2019-06-21 12:34:48.824 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
2019-06-21 12:34:48.828 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 43: Sensor Type = Luminance(3), Scale = 1
2019-06-21 12:34:48.832 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 43: Sensor Value = 275
2019-06-21 12:34:48.836 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2019-06-21 12:34:48.840 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 275
2019-06-21 12:34:48.845 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating channel state zwave:device:25c838a3:node43:sensor_luminance to 275 % [QuantityType]
2019-06-21 12:34:48.851 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2019-06-21 12:34:48.860 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1474d34.
Tried to set the other association groups too, but as you can see, same problem there.
however, changing wakeup seem to work
2019-06-21 12:39:42.460 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update received
2019-06-21 12:39:42.466 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Configuration update set wakeup_interval to 1500 (BigDecimal)
2019-06-21 12:39:42.469 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Set wakeup interval to '1500'
2019-06-21 12:39:42.484 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Wakeup node not specified, using 1
2019-06-21 12:39:42.487 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 43: Creating new message for command WAKE_UP_INTERVAL_SET to 1500s, node 1
2019-06-21 12:39:42.490 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2019-06-21 12:39:42.494 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-06-21 12:39:42.496 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Bump transaction 213 priority from Config to Immediate
2019-06-21 12:39:42.499 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Adding to device queue
2019-06-21 12:39:42.502 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Added 213 to queue - size 11
UPDATE1: @sihui Problem solved! Will try to describe what I did/had to do tomorrow. Big thank you for pointing me in the right direction! Part of it seem to be Admin/Paper UI.
UPDATE2:
I think there were at least two different problems involved here.
- I hadn’t included my device using admin ui (I had seen posts about not using paper ui for zwave but I also remember seeing posts that it was supposed to work fine)
- There seem to be something weird in the things/items db (internal one, not CJs)
so, I as I said before, I had a working system with a Neo Zwave PIR device. For some reason I decided to fiddle about and change the item connected to the motion channel, to a different category. From Door to Motion. For some reason this made the device not register (or at least not in the eyes of OH) Luminance however worked. The thing had an original ID of 40.
So after much fiddling about I came to the conclusion that the easiest would be to exclude/re-include. At this point I used the paper ui to include. The new ID was 42.
It still didn’t register motion but luminance was working.
This is when I reached out to the community and @sihui helped me.
So I excluded/re-include the device again, using the admin ui. The thing now got a ID of 43. No motion, still luminance.
And now it gets weirder. I deleted the device and rediscovered it, but now OH found the previous Thing, as undiscovered but with the ID 42, meaning the previous ID, not the current. (To me this indicates that the internal db for some reason was in a bad/incorrect state)
At this point I was ready to through the device in the trash and buy a new one - but alas - I gave it one more shot.
This time I excluded the device, cleared the OH cache and restarted the RPI.
- I reincluded the device using the admin ui (I noticed in the logs that the channels this time were detected which I think was a first) The Thing had the correct ID of 43
- I kept waking the device up until it had FULLY initialized (many times…) and then
- added the item for the motion channel, in the admin ui.
Now it worked!!
The conclusion I draw is this, always use the admin ui for zwave. If something seem really weird, clear cache and restart.