dinki
June 8, 2016, 2:52pm
3
@sihui Thanks for the suggestions. I’ve copied the old xml file and removed it. The line read:
<name>Plug-In Dimmer��</name>
Also that particular device’s name looks different in habmin:
Finally, how do I reinitialize? I selected the node and pressed the ‘Reinitialise Node’ button in habmin:
But nothing seems to happen. I’m using Chrome. Should that recreate the xml file? Am I doing this totally wrong?
Still getting errors even after deleting the xml and restarting:
2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 1: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 4: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 5: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 6: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 7: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 8: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - NODE 9: Node found 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller using Controller API 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------ 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - # Nodes = 7 2016-06-08 09:44:34.537 [INFO ] [rialApiGetInitDataMessageClass] - ---------------------------------------------------------------------------- 2016-06-08 09:44:34.912 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class POWERLEVEL 2016-06-08 09:44:34.943 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class POWERLEVEL 2016-06-08 09:44:35.177 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 8: Node name: Plug-In Dimmer 2016-06-08 09:44:35.208 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:44:40.195 [ERROR] [WaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left! 2016-06-08 09:44:40.195 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message. 2016-06-08 09:44:40.210 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:44:45.201 [ERROR] [WaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 1 attempts left! 2016-06-08 09:44:45.201 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message. 2016-06-08 09:44:45.216 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:44:50.205 [ERROR] [WaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 0 attempts left! 2016-06-08 09:44:50.205 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message. 2016-06-08 09:44:50.220 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:44:55.220 [WARN ] [WaveController$ZWaveSendThread] - NODE 8: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 08 02 77 05 2016-06-08 09:44:55.252 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 8: Node name: Plug-In Dimmer 2016-06-08 09:44:55.283 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 8: Node name: Plug-In Dimmer 2016-06-08 09:44:55.298 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:45:00.294 [ERROR] [WaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left! 2016-06-08 09:45:00.294 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message. 2016-06-08 09:45:00.309 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na] 2016-06-08 09:45:05.304 [ERROR] [WaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 1 attempts left! 2016-06-08 09:45:05.304 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message. 2016-06-08 09:45:05.320 [ERROR] [b.z.i.protocol.ZWaveController] - Exception during Z-Wave thread: Input.
sihui
June 8, 2016, 3:53pm
4
Yes, it should. Maybe it is too far away from the controller???
dinki
June 8, 2016, 3:55pm
5
Very odd. It is no more than 15’-20’ (4.5m-6m) away from the controller. I can see it from the controller.
Perhaps I should exclude it and then include it again?
sihui
June 8, 2016, 4:03pm
6
Is it a battery operated device? Then you may need to wake it up with a button to get initialized, sometimes even several times …
< gesendet von Samsung Smartphone >
dinki
June 8, 2016, 4:05pm
7
No, it’s a plug in lamp dimmer. I forced the light on just now to see if it would then reinitialize but it didn’t do anything. Does habmin log anything when you try to heal/reinitialize (if yes, where)? It just doesn’t seem like it responds when I do either of those.
sihui
June 8, 2016, 4:56pm
8
Yes, but you won’t see a lot if you are not in debug mode.
If your other devices are running fine I would exclude, reset the device and include it again as a last resort.
dinki
June 8, 2016, 5:28pm
9
I tried in debug mode and it looks like it’s querying node 8 like crazy. I let it run for about 10 minutes and my log file kept saying the same stuff over and over again. Log file was over 60 megs when I decided to stop it. I didn’t see any errors in the debug log thought I could have overlooked them. The xml file was never written again though. How do I get this to happen?
dinki
June 8, 2016, 5:50pm
10
I don’t have a zwave.log file. How do I get OH to generate this?
sihui
June 8, 2016, 6:07pm
11
If you make a setup like suggested in the wiki you will have a zwave.log:
otherwise the debug messages go to openhab.log
dinki
June 8, 2016, 6:52pm
12
I read that page a million times and never noticed the logging part. I got it working, but I’m still seeing that error in my openhab.log but getting other stuff in the zwave.log. It really seems like it is not liking the naming of the device:
2016-06-08 13:41:50.835 [DEBUG] [ApplicationCommandMessageClass:38 ]- NODE 8: Application Command Request (ALIVE:STATIC_VALUES) 2016-06-08 13:41:50.835 [DEBUG] [ApplicationCommandMessageClass:56 ]- NODE 8: Incoming command class NODE_NAMING 2016-06-08 13:41:50.835 [DEBUG] [.c.ZWaveNodeNamingCommandClass:116 ]- NODE 8: Received NodeNaming Command Class Request 2016-06-08 13:41:50.837 [ERROR] [b.z.i.protocol.ZWaveController:1173]- Exception during Z-Wave thread: Input. java.lang.ArrayIndexOutOfBoundsException: 5 at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:313) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:169) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:242) ~[na:na] at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na] at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:80) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:196) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:191) ~[na:na] at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1166) ~[na:na]
This comes as no surprise as you can see by the screenshot above and in the strange characters after the name. Why does this device not look like the others? Why isn’t it called Node 8 like the others? It functions just fine, but keeps throwing these errors.
sihui
June 8, 2016, 7:09pm
13
To be honest: I don’t know (and have never used openHAB on Windows).
Maybe you should look at this thread, it could be related to your problem:
Hello,
I’ve been using 1.7 for a while now and things have been running pretty smoothly. Then something went wacky with Windows 10 and I had go restore an old image of it. I figured it would be a good time to jump to 1.8, but it has not been pleasant.
When I try to run OpenHAB now, I am getting all sorts of errors. I went back to 1.7 but I am also getting errors with that. I did also need to reinstall the JRE. So with all the changes, I don’t even know where to start.
I would greatly apprecia…
dinki
June 8, 2016, 7:33pm
14
Hmm… the link you posted was resolved by changing the port. This doesn’t seem to be related to my problem.
Do you, or anyone, know who maintains the zwave binding? Perhaps he/she could be of help on this seemingly odd behavior.
sihui
June 8, 2016, 7:41pm
15
For that you need to shout at @chris
< gesendet von Samsung Smartphone >
rlkoshak
June 8, 2016, 8:09pm
16
If it is truly the name it is having a problem with, you should be able to manually change the name by editing the XML file. This is probably considered a bad idea but when all else fails…
Just remove the weird stuff after “Dimmer” and save the XML file. The � is an escaped character in XML/HTML and it should be a four digit HEX number so the x0 is clearly not valid.
A more important question is where did those rogue characters come from. Perhaps there is an error in the Zwave DB?
Reinitializing the node won’t help if the problem is that the zwave database is adding these rogue invalid characters to the name. It does indeed look like the binding is having a problem creating the xml file which might account for the weird invalid characters.
Hopefully chris will chime in. He will almost certainly ask for your logs.
In the mean time, assuming the rest of the XML file is valid manually editing it like this should get you past this immediate problem.
chris
June 8, 2016, 9:16pm
17
The problem is not with the database - it’s a problem with the node name.
I’ve not followed this through totally, but I see at the top of the thread that you are using 1.8.3 - please make sure that you are using 1.9. I’m not completely sure this bug is fixed in 1.9, but we should at least start from a recent version of code
If the problem persists in 1.9, then I will sort it out as it is definitely fixed in 2.0.
TheKorn
June 8, 2016, 10:05pm
18
Another occurrence of #4046 maybe?
TheKorn
June 8, 2016, 10:08pm
20
D’oh, ninja edited it to 4046.
(And now I take it back, I think it really is 4058 !)
dinki
June 9, 2016, 12:29am
21
@chris Thanks for the reply. I didn’t realize there was a version 1.9 . I tracked down org.openhab.binding.zwave-1.9.0.b3.jar and installed but am still seeing an error. I’m attaching the zwave.log file if you could take a moment to look at it would be great. Thanks again.
Hmm… maybe I can’t upload a zip file? Here’s a copy/paste:
2016-06-08 19:24:19.572 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38 ]- NODE 8: Sent Data successfully placed on stack.
2016-06-08 19:24:19.582 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 05 00 13 22 00 CB
2016-06-08 19:24:19.592 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-06-08 19:24:19.592 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 07 00 13 22 00 00 00 C9
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 07 00 13 22 00 00 00 C9
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = SendData (0x13), type = Request (0x00), payload = 22 00
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.p.s.SendDataMessageClass:73 ]- NODE 8: SendData Request. CallBack ID = 34, Status = Transmission complete and ACK received(0)
2016-06-08 19:24:19.592 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 08 02 77 05
2016-06-08 19:24:19.592 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 22 00
2016-06-08 19:24:19.592 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=SendData, expected=ApplicationCommandHandler, cancelled=false
2016-06-08 19:24:19.592 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 08 00 04 00 08 02 77 06 88
2016-06-08 19:24:19.592 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-06-08 19:24:19.592 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 08 00 04 00 08 02 77 06 88
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 08 00 04 00 08 02 77 06 88
2016-06-08 19:24:19.592 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 08 02 77 06
2016-06-08 19:24:19.592 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 8: Application Command Request (ALIVE:DYNAMIC_VALUES)
2016-06-08 19:24:19.592 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 8: Incoming command class NODE_NAMING
2016-06-08 19:24:19.592 [DEBUG] [.c.ZWaveNodeNamingCommandClass:114 ]- NODE 8: Received NodeNaming Command Class Request
2016-06-08 19:24:19.592 [ERROR] [b.z.i.protocol.ZWaveController:1202]- Exception during Z-Wave thread: Input.
java.lang.ArrayIndexOutOfBoundsException: 5
at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessagePayloadByte(SerialMessage.java:329) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.getString(ZWaveNodeNamingCommandClass.java:168) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processLocationReport(ZWaveNodeNamingCommandClass.java:246) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:147) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:84) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:225) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:198) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:193) ~[na:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1197) ~[na:na]
2016-06-08 19:24:21.639 [DEBUG] [z.internal.ZWaveNetworkMonitor:323 ]- Network Monitor: Queue length is 11 - deferring network monitor functions.
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1126]- NODE 8: Stage DYNAMIC_VALUES. Initialisation retry timer triggered. Increased to 20000
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:267 ]- NODE 8: Node advancer - DYNAMIC_VALUES: queue length(0), free to send(false)
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1158]- NODE 8: Initialisation retry timer started 20000
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:332 ]- NODE 8: Node advancer: loop - DYNAMIC_VALUES try 2: stageAdvanced(false)
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:803 ]- NODE 8: Node advancer: DYNAMIC_VALUES - checking SWITCH_MULTILEVEL
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:806 ]- NODE 8: Node advancer: DYNAMIC_VALUES - found SWITCH_MULTILEVEL
2016-06-08 19:24:24.569 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:810 ]- NODE 8: Found 1 instances of SWITCH_MULTILEVEL
chris
June 9, 2016, 4:46pm
22
Ok - thanks. I’ll take a look - it’s probably the same/similar issue we’ve seen before so I’ll copy over the OH2 implementation which I believe solves this.
.