my (second) Aeon ZW100 Multisensor now also shows I saw that device had a recent edit in the Db… mhh
10:49:01.690 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Size error 2<>1 from config_42_2
10:49:02.024 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@121bb36
10:49:02.039 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:15348538564:node9' has been updated.
10:49:02.723 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:15348538564:node9' has been updated.
10:49:02.737 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@848a24
10:49:02.880 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Size error 2<>1 from config_44_2
my Fibaro RGBW sometimes causes:
20:34:23.433 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:15348538564:node12' has been updated.
java.lang.ArrayIndexOutOfBoundsException: 1120:34:23.549 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2.
at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:337)
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMeterCommandClass.handleApplicationCommandRequest(ZWaveMeterCommandClass.java:136)
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:118)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:240)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:201)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1072)
20:34:28.439 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 12: Timeout while sending message. Requeueing - 2 attempts left!
20:34:28.440 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 12: Got an error while sending data. Resending message.
java.lang.ArrayIndexOutOfBoundsException: 11
20:34:28.560 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2.
at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:337)
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMeterCommandClass.handleApplicationCommandRequest(ZWaveMeterCommandClass.java:136)
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:118)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:240)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:201)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1072)
20:34:33.450 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 12: Timeout while sending message. Requeueing - 1 attempts left!
20:34:33.451 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 12: Got an error while sending data. Resending message.
java.lang.ArrayIndexOutOfBoundsException: 11
20:34:33.568 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2.
at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:337)
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMeterCommandClass.handleApplicationCommandRequest(ZWaveMeterCommandClass.java:136)
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:118)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:240)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:207)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:201)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1072)
Well I guess it’s no surprise that it’s doing the same thing as the other… I guess this should be changed, but it would be really great if you can capture a debug log of this message so I can actually see the data…
This likely means that the device is sending corrupted data, which does happen occasionally. Again, a debug log of this would be very useful, although I am adding an exception into the code to better handle exactly this issue…
Sorry - should have been more specific… I meant during the initialisation (which is where the ESH discovery happens) - not the inclusion… There’s two parts I want to see - firstly that it’s got the manufacturer data, and secondly what happens when it tries to run through the discovery inbox addition…
maybe its time for me to learn the best way to do this…
I always try to trigger the needed and catch the log directly on karaf shell …
Is it better to just let it run until it happens and find the appropriate part in habmin log viewer for that node?
For “initializaton” of an unknown node… there is no option to “reinitialize” in habmin… so should I just leave logging on debug and wait?
In my opinion, yes. That way you capture everything that’s happening. If you’re only logging information when you’re looking for a known problem, then you’ll never find the unknown ones (ie the ones you weren’t expecting).
No - this is a good point. I’ll add this (it was possible in HABmin1 and it is useful).
The easiest way at the moment is to delete the XML for this node (if it exists) and restart the binding. The problem of course is that his will generate a lot of traffic, so you’ll need to filter. However, given this is a battery device, you can choose when to wake it up, so just wait until after all the other startup traffic has completed.
So - it seems this is already included and I’d forgotten I’d added it… It’s in the tools menu - select the device, select advanced mode, then you should see it…
No - it’s a bit after this that I need - feel free to email me a larger log if you like (although I might not look at it for a while as I’ve got some other stiff to look at).
I’m trying to get habmin configuration to work, I don’t know if you remember, but I have had issues with it earlier. Anyway, I can change a name of a thing, as well as polling period. But if I e.g. want to change a node setting, e.g. association group or a configuration parameter, after I press the green save, I get: