Hello,
since the years I use OpenHAB 2 without problems. With OpenHAB3 I want start a new installation. So I take my PI 3 (from working OH2 Installation) and use new sdcard with fresh OH3 installation. I use openHABian v1.6.2 for install.
I added my HUE with all ligths this work.
After that I added my Z-Wave Controller but this is not working. The controller is still offline. The serial port was found. Port is there in system.
When I switch to sdcard with OH2, all is working fine Z-Wave controller is working.
How can I debug futher in OH3? Has someone a idea?
Platform information:
Release = Raspbian GNU/Linux 10 (buster)
Kernel = Linux 5.4.79-v7+
Platform = Raspberry Pi 3 Model B Plus Rev 1.3
openHAB version: 3.0.0
Z-Wave controller RaZberry
If logs where generated please post these here using code fences:
2020-12-29 14:01:58.051 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing receive thread
2020-12-29 14:01:58.055 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Receive thread dispose
2020-12-29 14:01:58.058 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing serial connection
2020-12-29 14:01:58.062 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Serial connection disposed
2020-12-29 14:01:58.066 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2020-12-29 14:01:58.084 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Deactivate zwave:serial_zstick:0693512b67
2020-12-29 14:01:58.009 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:serial_zstick:0693512b67’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2020-12-29 14:01:58.113 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:serial_zstick:0693512b67’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-12-29 14:02:17.826 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:0693512b67 with scan time of 60
2020-12-29 14:02:17.833 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Active zwave:serial_zstick:0693512b67
2020-12-29 14:02:17.838 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-12-29 14:02:18.016 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2020-12-29 14:02:18.019 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:0693512b67.
2020-12-29 14:02:17.986 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:serial_zstick:0693512b67’ changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2020-12-29 14:02:18.026 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:serial_zstick:0693512b67’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-12-29 14:18:54.149 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:0693512b67
I done this via openhabian-config. I must deactivate serial port and change bluethooth to mini-UART.
Now controller is online. Thanks!
2020-12-29_15:28:22_CET [openHABian] Beginning configuration of serial console for serial port peripherals… OK
2020-12-29_15:28:27_CET [openHABian] Enabling serial port and disabling serial console… OK (reboot required)
2020-12-29_15:28:32_CET [openHABian] Making Bluetooth use mini-UART… OK
I don’t mind. Most of the zigbee coordinator section is talking about different coordinators. Here we only have 1 zwave controller, but the quirk is with the host hardware (I assume).
I’d think anybody to buy specific HW should know how to install it himself.
We cannot add instructions for each and everything.
However, if someone wrote a PR to contribute to docs/openhabian.md I wouldn’t mind accepting it.
I have exactly the same issue but on a Raspi 4. I installed openhabian-pi-raspios32-v1.6.5 (OpenHAB 3.1) and everything was working without problem. However, I can’t get the RaZberry 2 card to work. The two LEDs on the card are on for 2 secs when powering up the Raspi which should indicate the card works correctly.
I have configured the serial port to relocate the Bluetooth module.
On anohter Raspi4 I run successful with RaZberry it will show ttyAMA0 with the r flag on group and well and the group is set to dialout as with ttyS0. Btw, I have tried as well /dev/ttyS0 but same result.
Hi Markus, I tried to change the permissions and the user on /dev/ttyAMA0 before, but after reboot it will be changed back. But I think I have a clue now.
Never add a user to the tty group. A serial device being in tty group suggests that a getty (serial login manager) is running on the port; otherwise it should be in dialout group. Trying to use the port if a getty is also running will just cause other problems.
Disable the login shell on the serial port in the interfacing options of “sudo raspi-config”, and reboot. For B+ that may be all that is required.
For Pi3, and possibly in future, disabling the getty will also put the physical pins back to general-purpose mode. To have them as serial by default, you should add “enable_uart=1” to /boot/config.txt. For best compatibility across Pi models, it may be better to use /dev/serial0, instead of ttyAMA0 or ttyS0.
Now how can I turn this serial login manager off? raspi-config is not available on openHABian. BTW I have not installed anything else, it is a clean openHABian.
Afterwards Z-Wave Controller went online after adding. Puh! Took me the whole evening to get this sorted. Now the question is, why was getty@ttyAMA0.service enabled? systemctl says vendor preset: enabled. Maybe something to look into …
Now I understand … You have to check both items in openHABian-config. I thought the first setting is only applicable to older PI models. But it must be done for all as it disables the console. So for everybody trying to get a Z-Wave RaZberry controller running, both settings need to be enabled: