Hey
how can I change both items?
In the config itselfe I´m not able to set th “*”
so I use sudo nano /boot/config.txt
and add:
dtoverlay=miniuart-bt
enable_uart=1
now I have the “*” at 2 (RPi3/4) move Bluetooth to mini UART
but how do I get the 2nd “*” for 1 (RPi) Disable serial console
because the console is still enabled
THX
ok my fault, had a typing error.
I have the “*” for both lines now, but bridge is still offline
I took a look at: dmesg -T grep tty
and there the console for ttyAMA0 is still enabled:
openhabian@rv84:~ $ dmesg -T | grep tty
[Wed Feb 2 14:08:52 2022] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:9E:D2:53 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyAMA0,115200 console=tty1 root=PARTUUID=4d915286-02 rootfstype=ext4 fsck.repair=yes rootwait
[Wed Feb 2 14:08:52 2022] printk: console [tty1] enabled
[Wed Feb 2 14:08:53 2022] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
[Wed Feb 2 14:08:54 2022] printk: console [ttyAMA0] enabled
[Wed Feb 2 14:08:54 2022] fe215040.serial: ttyS0 at MMIO 0xfe215040 (irq = 37, base_baud = 62500000) is a 16550
[Wed Feb 2 14:08:56 2022] systemd[1]: Created slice system-getty.slice.
[Wed Feb 2 14:08:56 2022] systemd[1]: Created slice system-serial\x2dgetty.slice.
what to do now?
I had a different experience with a Pi 4, manual openhabian 3 install, and a ZooZ ZST10 700 series S2 stick. The tips here were very helpful, but didn’t quite match what I was seeing.
After setting the two configuration options, above, getty stopped “stealing” ttyAMA0, but the controller still wouldn’t work. The Z-wave binding debug logs showed all transactions timing out.
After digging around a little into USB devices, I found they create dmesg entries when they are plugged in. I unplugged it, rebooted, then plugged it in again, resulting in this:
[ 213.215071] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
[ 213.352161] usb 1-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 213.352184] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.352203] usb 1-1.3: Product: Zooz ZST10 700 Z-Wave Stick
[ 213.352220] usb 1-1.3: Manufacturer: Silicon Labs
[ 213.352237] usb 1-1.3: SerialNumber: 0001
[ 213.436847] usbcore: registered new interface driver usbserial_generic
[ 213.436945] usbserial: USB Serial support registered for generic
[ 213.441946] usbcore: registered new interface driver cp210x
[ 213.442045] usbserial: USB Serial support registered for cp210x
[ 213.442238] cp210x 1-1.3:1.0: cp210x converter detected
[ 213.455863] usb 1-1.3: cp210x converter now attached to ttyUSB0
The tty is USB0, not AMA0. I set that on the Thing configuration and everything was fine.
That last line had shown up in the dmesg | grep tty result, but without knowing what cp210x is from the previous lines, it wasn’t helpful.
Update: The instructions that came with it are wrong: “The device will display as /dev/ttyACMxx where xx…” It was the ACMxx vs AMA0 difference that started me down the right path.
At this time, most 700-series controllers are not supported by the Z-Wave binding in openHAB (for a number of reasons discussed in other threads). There’s been some very recent success with the Razberry 7 Pro), but that’s the only one I’m aware of.
So if you got it to work, you might be the first one to do so. And if you haven’t gotten it to work, I wouldn’t expect that to be the case.
Note that 700-series devices will work (e.g. switches and sensors). The issue is only with controllers.
That might explain things. It “works” in the sense that it comes online and the motion sensor is detected. It doesn’t work in the sense that the motion sensor has no channels. I saw comments that sometimes it takes “a few days”, so I’m currently waiting. The sensor shows “online” in openhab and is blinking green, so I was hoping for the best. While I wait, I’ll order another (older) controller.
I use a Raspi 3 and OH4 2.
I set the two options as you described.
Then i used sudo raspi-config and i enabled the Serial Port there.
only then it worked.
(Setting in the Ui: SerialPort: /dev/ttyAMA0)
I found this thread now because I just migrated from a Raspi 3 to a Raspi 4 using a razberry hat.
Also installed the latest openhabian and have the latest release (5.0.1).
But I still could not get access to the razberry even when I checked both options on the openhabian-config.
After applying it the agetty service was disabled but I was adviced to reboot and after reboot the agetty was again running and the systemd unit was activated again. Not sure what else I need to do to make it permanent?
Now I disabled the service via systemctl, changed the group ownership and the access for the group manually but I fear that after a system reboot my z-wave will be offline again.
So I think something does still not work as expected or rather is not applied fully?
Is that the older Razberry2 hat?
If so you there are troubles with Debian bookworm.
Have a look on this thread:
Yes, it’s a Razberry2. I read it’s supposed to work on every Raspi (and it actually seems to do but may need some other adjustments).