Jenkins build problems

[mbuchberger1967 (markus buchberger)]

Hi CHris,

e.g. this here during idle operations

2017-04-16 16:02:34.277 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (INITIALIZING:PROTOINFO)
2017-04-16 16:02:34.278 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.NullPointerException
	at org.openhab.binding.zwave.internal.protocol.ZWaveNode.setNodeState(ZWaveNode.java:235)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:46)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[196:org.openhab.binding.zwave:2.1.0.201704151452]

Or this one if I try to switch power on/off (node 10 is a power plug)

2017-04-16 16:28:49.976 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: ProtocolInfo
2017-04-16 16:28:49.977 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Listening = true
2017-04-16 16:28:49.979 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Routing = true
2017-04-16 16:28:49.980 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Beaming = true
2017-04-16 16:28:49.982 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Version = 4
2017-04-16 16:28:49.984 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: FLIRS = false
2017-04-16 16:28:49.985 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Security = false
2017-04-16 16:28:49.987 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Max Baud = 40000
2017-04-16 16:28:49.988 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Basic = Routing Slave
2017-04-16 16:28:49.989 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Generic = Binary Switch
2017-04-16 16:28:49.990 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 10: Specific = Binary Power Switch
2017-04-16 16:28:49.992 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Creating new instance of command class NO_OPERATION
2017-04-16 16:28:49.993 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Command class NO_OPERATION, endpoint null created
2017-04-16 16:28:49.995 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Version = 1, version set. Enabling extra functionality.
2017-04-16 16:28:49.997 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.NullPointerException
	at org.openhab.binding.zwave.internal.protocol.ZWaveNode.addCommandClass(ZWaveNode.java:520)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.serialmessage.IdentifyNodeMessageClass.handleResponse(IdentifyNodeMessageClass.java:129)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingResponseMessage(ZWaveController.java:291)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:217)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[196:org.openhab.binding.zwave:2.1.0.201704151452]
2017-04-16 16:28:54.910 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=IdentifyNode[0x41], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
2017-04-16 16:29:59.154 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:a62f5073:node10:switch_binary --> ON
2017-04-16 16:29:59.156 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling handler: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:220)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:189)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:358)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
	at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:46)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:192)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:181)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
Caused by: java.lang.NullPointerException
	at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBinarySwitchCommandClass.setValueMessage(ZWaveBinarySwitchCommandClass.java:144)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.internal.converter.ZWaveBinarySwitchConverter.receiveCommand(ZWaveBinarySwitchConverter.java:90)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleCommand(ZWaveThingHandler.java:911)[196:org.openhab.binding.zwave:2.1.0.201704151452]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:361)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:1)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:218)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
	... 12 more

[Kai (Kai Kreuzer)]

@Kai

One last thing I need to do is to also populate the online repo from the build.

Done! The online repo is now also filled with the latest snapshot builds, so all should be fine again!

@mbuchberger1967 Any issues that you might find from now should be considered as bugs, so please open a dedicated topic or issue for them.

[mbuchberger1967 (markus buchberger)]

Thanks.

I just did an apt-get update / upgrade but no changes arrived ( I use apt-get on snapshot repository)
I’d have expected to get update on bindings… can u explain me why there are no changes in apt-get?

DO I need to use manual installation to get the latest snapshots on bindings?

Sorry, maybe a stupid question but I’m confused a little bit now.

Thanks
Markus

[rtvb (Robert)]

@mbuchberger1967

I just did an apt-get update / upgrade but no changes arrived ( I use apt-get on snapshot repository)I’d have expected to get update on bindings… can u explain me why there are no changes in apt-get?

If your are on unstable builds, you should have build #884. I have.

[mbuchberger1967 (markus buchberger)]

@Kai

@mbuchberger1967 Any issues that you might find from now should be considered as bugs, so please open a dedicated topic or issue for them.

where shall I create an issue? here in the forum or is there another system in place for bug tracking?

[sihui]

@mbuchberger1967

where shall I create an issue?

I guess because @rtvb got the newest build you are just doing something wrong …

Double check if you did all required steps and if you are really on snapshot builds:

http://docs.openhab.org/installation/linux.html#upgrade

Edit: ahhh, you just forgot to report you’ve solved it:

[Solved] NPEs in zwave binding with latest sanpshot build 2.1.0.201704151452

Hi @chris, I updated to the latest snapshot build and restarted everything. I have exceptions during startup, in idle mode and when try to switch one device since I upgraded to the latest snapshot today. I attached a complete log for one server startup with one action on node10. Here an extract of the two NPEs: IDLE MODE: 2017-04-16 21:24:23.915 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF 2017-04-16 21:24:23.935 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Me…

[swamiller (Steve)]

I’m having a similar issue with the zwave binding (both 2.1.0 and the in work security version) after updating to the latest snapshot (2.1.0-SNAPSHOT Build 884). The error message below consistently occurs at start up and goes away after uninstalling the zwave binding.

2017-04-16 18:37:22.697 [ERROR] [org.openhab.binding.zwave           ] - FrameworkEvent ERROR - org.openhab.binding.zwave
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [230]
  Unresolved requirement: Import-Package: gnu.io

	at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]

For post update troubleshooting, I also ran sudo apt-get install openhab2-addons with no change in results.

All else seems to work okay after the update.

[sihui]

@swamiller

The error message below consistently occurs at start up

OH2 Z-Wave refactoring and testing... and SECURITY

On a completely clean installation of OH2 Snapshot (#771), you will get the following error when you try to start the new Z-Wave binding: openhab> bundle:start org.openhab.binding.zwave Error executing command: Error executing command on bundles: Error starting bundle 208: Could not resolve module: org.openhab.binding.zwave [208] Unresolved requirement: Import-Package: gnu.io To fix this: feature:install openhab-transport-serial and then Z-Wave will start

[swamiller (Steve)]

Thank you, this seems to have corrected the error.

I thought this was odd, however, because I haven’t been doing anything with my zwave binding (I was using the available version from the Paper UI) and this was new behavior since Kai was able to make the latest snap shot available again. I did a typical snapshot update via apt-get which is what triggered the error.

[Michal_Szymanski]

Question little off topic but where can I find road map of OpenHab?
I’m almost happy user of OpenHabian and I wonder when I see e.g 2.1. I waiting for this version because as I know it fix this bug Strange behaviour of Fibaro Flood Sensor with Razberry and OpenHabian .

I know I can use snapshot but I’m affraid using snapshot because later migration problems…but maybe I’m wrong?

Michał Szymański