PINE64

Hi, 

I'm using the pine64_openhab_20160915_8GB.img image with the zwave module and adapter for the PI2 GPIO header but it seems as if the zwave module is not detected. The module should turn up as /dev/ttyS2 but from syslog all I get is:

Sep 24 07:57:58 openhab kernel: [    8.285353] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI

And then in openhab.log:



Any ideas on what could be wrong?

/Eric

(10-01-2016, 08:28 AM)eric Wrote: [ -> ]Hi, 

I'm using the pine64_openhab_20160915_8GB.img image with the zwave module and adapter for the PI2 GPIO header but it seems as if the zwave module is not detected. The module should turn up as /dev/ttyS2 but from syslog all I get is:

Sep 24 07:57:58 openhab kernel: [    8.285353] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI

And then in openhab.log:

2016-10-01 14:25:21.389 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyS2'
2016-10-01 14:25:21.485 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2016-10-01 14:25:21.504 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2016-10-01 14:25:21.532 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2016-10-01 14:25:21.534 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2016-10-01 14:25:21.990 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2016-10-01 14:25:21.998 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key zwaveerial_zstick:board in ManagedThingProvider, because it does not exists.
2016-10-01 14:25:22.001 [WARN ] [.core.thing.binding.BaseThingHandler] - Error while applying configuration changes: 'IllegalStateException: Could not update thing zwaveerial_zstick:board. Most likely because it is read-only.' - reverting configuration changes on thing 'zwaveerial_zstick:board'.

Any ideas on what could be wrong?

/Eric

Try running as sudo  (root)

Thanks, but I already tried that and it's not a permission problem. Compiled openzwave and the issue persists so I may have a faulty zwave module. Time to pull out the old scope.

(10-04-2016, 11:52 AM)eric Wrote: [ -> ]Thanks, but I already tried that and it's not a permission problem. Compiled openzwave and the issue persists so I may have a faulty zwave module. Time to pull out the old scope.

Did you find anything out? I believe I might have a faulty module as well. It worked for a while, but halfway through pairing my devices it just quit.

What was the verdict here? All I know about mine is that it's listed as "offline" when I pull it up in the recent OpenHab image. Trying to create my own thing hasn't helped.