Tested with open-zwave-control-panel and everything work well.
Trying to revert back to 2.1.0 stable release and still nothing, “communication error”.
I don’t understand why the bundle can’t communicate with the dongle.
New openhabian on raspberry pi, zwave OFFLINE - COMMUNICATION_ERROR zwave.thingstate.serial_notfound
If you’ve reinstalled, maybe you’ve lost some settings such as the EXTRA_OPTIONS which tells java about the serial ports?
EXTRA_OPTIONS are used and the mysensors gateway connected on /dev/ttyS1 works well.
Is there a way to trace the connection to the serial port ?
No - I don’t think so.
What is the actual error you are getting?
This is the last “restart org.openhab.binding.zwave”
11:06:17.023 [DEBUG] [org.openhab.binding.zwave ] - BundleEvent STARTING - org.openhab.binding.zwave
11:06:17.025 [DEBUG] [inding.zwave.internal.ZWaveActivator] - Z-Wave binding started. Version 2.2.0.201707190537
11:06:17.428 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigOptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={component.name=org.openhab.binding.zwave.ConfigDescription, component.id=222, service.id=1013, service.bundleid=208, service.scope=bundle} - org.openhab.binding.zwave
11:06:17.486 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zwave.internal.ZWaveHandlerFactory, component.id=225, service.id=1014, service.bundleid=208, service.scope=bundle} - org.openhab.binding.zwave
11:06:17.502 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.events.EventFactory}={component.name=org.openhab.binding.zwave.event.BindingEventFactory, component.id=226, service.id=1015, service.bundleid=208, service.scope=bundle} - org.openhab.binding.zwave
11:06:17.555 [DEBUG] [org.openhab.binding.zwave ] - BundleEvent STARTED - org.openhab.binding.zwave
11:06:27.484 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node5' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.498 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node6' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.507 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node7' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.520 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node8' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.536 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node9' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.549 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node10' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.559 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node2' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.572 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node3' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.583 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:gateway:node4' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
11:06:27.777 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
11:06:27.779 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller.
11:06:27.786 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:gateway' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
11:06:27.805 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:gateway' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
11:06:27.829 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=1018, service.bundleid=208, service.scope=singleton} - org.openhab.binding.zwave
11:06:27.834 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=1019, service.bundleid=208, service.scope=singleton} - org.openhab.binding.zwave
11:06:27.848 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
11:06:27.855 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=1020, service.bundleid=208, service.scope=singleton} - org.openhab.binding.zwave
11:06:27.859 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=1022, service.bundleid=208, service.scope=singleton} - org.openhab.binding.zwave
11:06:27.863 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=1021, service.bundleid=208, service.scope=singleton} - org.openhab.binding.zwave
11:06:27.909 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:gateway' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE (COMMUNICATION_ERROR): zwave.thingstate.serial_notfound
After wiping the org.eclipse.smarthome.core.thing.Thing.json, I was able to add the zwave controller (delete and reinstall in paperui was not working).
When I open the new json and the old, the only difference is the format of the variables : integer in the new and float in the old. I dig in to find if this is the cause.
Found it !!! When I remove all the mysensors things, the zwave is working. I try to tell it to the person who wrote the binding. Maybe you can take a look Chris ?
I don’t think there’s anything I can look at. It’s probably a problem with the way the serial ports/driver work, but I don’t want to get into developing that…
Ok, thank you Chris. For my part, the Zwave side is solved.
All, I have not been able to resolve the aeotec zwave dongle off line message, after multiple reloads of openhabian I thought that it might be a old hardware issue and upgraded to a Raspberry pi 3 model b and a aeotec gen 5 zwave usb dongle but I continue to be plauged by the same issue. Below are the steps that I took when installing openhabian 3.1
openHABian Configuration Tool [master]v1.3-300(e8b0428) openHABian Configuration
Upgrade System Upgrade all installed software packages - No errors
Apply improvements:
Packages Install needed and recommended system packages - No errors
Bash&Vim Settings Update customized openHABian settings - No errors
System Tweaks Add /srv mounts and update settings - No errors
Fix Permissions Update file permissions of common - No errors
FireMotD Upgrade the program behind the system - No errors
System Settings:
Set System Timezone Change the your timezone, execute - No errors
Change passwords - no errors
Serial Port Prepare serial ports for peripherals - [*] 1 (RPi) Disable serial console (Razberry, SCC, Enocean)
(RPi3) Disable Bluetooth module (Razberry) │
Add common serial ports to openHAB JVM (Razberry,
All done. After a reboot the serial console will be available via │
│ /dev/ttyAMA0 or /dev/ttyS0 (depends on your device).
Sudo reboot
http://192.168.1.137:8080/start/index
Standard - paper UI
Addins:
Zwave - binding-zwave - 2.1.0
Zwave configuration port - /dev/ttyAMA0
Status: OFFLINE - BRIDGE_OFFLINE Controller is offline
Zwave configuration port - /dev/ttyS0
Status: OFFLINE - BRIDGE_OFFLINE Controller is offline
ls -la /dev/ttyAMA0
crw-rw---- 1 root dialout 204, 64 Jul 30 13:45 /dev/ttyAMA0
ls -la /dev/ttyS0
crw-rw---- 1 root dialout 4, 64 Jul 30 13:20 /dev/ttyS0
lsmod
Module Size Used by
cdc_acm 19350 0
brcmfmac 222874 0
brcmutil 9092 1 brcmfmac
cfg80211 543027 1 brcmfmac
rfkill 20851 2 cfg80211
snd_bcm2835 24427 0
snd_pcm 98501 1 snd_bcm2835
snd_timer 23968 1 snd_pcm
snd 70032 3 snd_timer,snd_bcm2835,snd_pcm
bcm2835_gpiomem 3940 0
uio_pdrv_genirq 3923 0
uio 10204 1 uio_pdrv_genirq
fixed 3285 0
ipv6 408971 58
Any help to get this resolved will be greatly appreciated
Thank you
I have a pi2, and my serial port is /dev/ttyACM0…
I am experiencing the exactly same problems using a Raspberry pi 3 and a Aeotec gen 5 zwave usb dongle.
I tried 2 different RPs and 2 different dongles with the same results as gtigen. I tried using a new OH image to no avail.
I then installed OH on a PC and the dongles worked. My preference however is to have OH on an RP.
Vic_Roy
I was never able to get the dongle to work on the raspberry so I finally moved on to another open source platform that works flawlessly with the RPI and the Aeotec dongle.
I have openhabianpi installed. (openHABian hassle-free openHAB Setup)
I noticed that when the dtoverlay=pi3-miniuart is in the /boot/config.txt will stop z-wave from working.
My config.txt is as follows:
.
. lines before
.
# Disable the PI3 bluetooth and wifi and remove the miniuart
dtoverlay=pi3-disable-bt
dtoverlay=pi3-disable-wifi
#dtoverlay=pi3-miniuart-bt
Thank you Rob but no joy
I started again from scratch and used a fresh image on a RP3 to no avail. Below are the log files.
Below are the last few lines of config.txt
# Disable the PI3 bluetooth and wifi and remove the miniuart
dtoverlay=pi3-disable-bt
dtoverlay=pi3-disable-wifi
#dtoverlay=pi3-miniuart-bt
enable_uart=1
OPENHAB.LOG file
2017-09-04 23:12:28.729 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing ‘zwave:serial_zstick:4c945542’ takes more than 5000ms.
2017-09-04 23:12:28.748 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyAMA0’
2017-09-04 23:12:28.778 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2017-09-04 23:12:28.780 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2017-09-04 23:12:28.782 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2017-09-04 23:12:28.784 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
EVENTS.LOG file
2017-09-04 23:12:23.535 [ItemChannelLinkAddedEvent ] - Link ‘zwave_serial_zstick_4c945542_serial_sof-zwave:serial_zstick:4c945542:serial_sof’ has been added.
2017-09-04 23:12:23.539 [ItemChannelLinkAddedEvent ] - Link ‘zwave_serial_zstick_4c945542_serial_ack-zwave:serial_zstick:4c945542:serial_ack’ has been added.
2017-09-04 23:12:23.543 [ItemChannelLinkAddedEvent ] - Link ‘zwave_serial_zstick_4c945542_serial_nak-zwave:serial_zstick:4c945542:serial_nak’ has been added.
2017-09-04 23:12:23.549 [ItemChannelLinkAddedEvent ] - Link ‘zwave_serial_zstick_4c945542_serial_can-zwave:serial_zstick:4c945542:serial_can’ has been added.
2017-09-04 23:12:23.553 [ItemChannelLinkAddedEvent ] - Link ‘zwave_serial_zstick_4c945542_serial_oof-zwave:serial_zstick:4c945542:serial_oof’ has been added.
2017-09-04 23:12:23.582 [ThingAddedEvent ] - Thing ‘zwave:serial_zstick:4c945542’ has been added.
2017-09-04 23:12:23.722 [hingStatusInfoChangedEvent] - ‘zwave:serial_zstick:4c945542’ changed from UNINITIALIZED to INITIALIZING
2017-09-04 23:12:28.772 [ThingUpdatedEvent ] - Thing ‘zwave:serial_zstick:4c945542’ has been updated.
2017-09-04 23:12:28.782 [hingStatusInfoChangedEvent] - ‘zwave:serial_zstick:4c945542’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
Using the following port in the binding config
/dev/ttyAMA0
If you have openhabianpi, please do not forget to add access to the /dev/tty* ports using the openhabian-config script.
When the script has started execute 30, 35 and select all options. Then and you should then all the way out and reboot.
Still no joy
Hi Vic, Had the issue on a fresh install and did exactly as above, rebooted, deleted the controller, re-added with the correct ports (till now I only had /dev/ttyAMA0, after reboot now I had the correct /dev/ttyACM0 as well) and instantly the controller came alive. Hope it works for you.
A fresh install unfortunately did not work. In fact, I tried many combinations of the following to no avail and just keep seeing the ‘offline’ message.
- A fresh image on a 16Gig card
- A fresh image on another card (8Gig).
- 3 different RP3s
- RP Zero wireless
- 2 different Aeotec gen 5 zwave usb dongles
- All the config changes found on this site
If I install OH2 and Aeotec gen 5 zwave usb dongle on a Windows 10 machine, it all works first go.
I really would prefer to run a RP3. Can someone help by logging via remote desktop? I would be happy to pay.
Regards
Vic
I ran into the same problem and did the same you did to resolve it. Well, my ZWave stick works again, but not with MySensors. I am new to MySensors with openHAB so I am going to try something different to get that working. Maybe an Ethernet gateway for MySensors.