-
Checklist
Deploy methodDocker Z-Wave JS UI version9.9.1 ZwaveJS version12.4.4 Describe the bugRecent Raspberry Pi kernel updates breaks ZWaveJS container installs and ultimately crashes the Raspberry Pi 3B+. My Raspberry Pi is up to date minus the following: linux-headers-rpi-v6/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1] To Reproducestart the container. after about 13 seconds, the container will crash and the pi will be unreachable either through ssh or connected directly through a keyboard/mouse and monitor. if you unplug the zwave stick and stop the container, and reboot, everything works fine including other docker containers initially reported here (home-assistant/core#113592) but closed due to being told to report to zwace-js-ui. further described here ( Any debugging is listed in discord starting at https://discord.com/channels/330944238910963714/332357267364249621/1217772010025779252) Expected behaviorstable awave network through docker on a pi 3b+ with an aeotec gen5 zwace stick Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 58 comments 13 replies
-
|
I encounter exactly the same issue since yesterday after a reboot (same raspberry. How to solve that ? |
Beta Was this translation helpful? Give feedback.
-
|
@pdobrien3 Could you give me some error logs please? |
Beta Was this translation helpful? Give feedback.
-
|
due to the fact the pi becomes unresponsive this is all I could get: and this through dmesg: and docker logs: |
Beta Was this translation helpful? Give feedback.
-
|
I'm experiencing this exact same Issue on a fresh install of Bookworm 12 on a Rpi 3+ with an Aeotec Gen5. I had to replace an sd card, so I just decided to use the latest version of the OS. I can confirm this definitely locks the machine hard. Normally I'd set up kdump and get it to crash and see if I can tell generally where the problem is, but it looks like that involves compiling a new kernel, which I don't have time to do at the moment. That said, I don't think this is a problem with zwavejsui. This appears to be a problem with the 6.6.20 kernel on Debian. I'm only piling on here because I think as more people upgrade this is going to be reported more. I just reinstalled Bullseye, re-ran my ansible playbook on the host, restored my zwave-js-ui backup and it's up and running like nothing changed. |
Beta Was this translation helpful? Give feedback.
-
|
@swstraus @pdobrien3 does anyone have any clue why this could happen? Because I don't have an RPI 3 to try reproducing this and I also dunno what from where to start searching what could cause this problem... |
Beta Was this translation helpful? Give feedback.
-
|
No idea. I'm suspecting a usb related issue here. If i try to boot with the controller inserted, it hangs during boot (with docker disabled btw). If I take the controller out, it boots fine. If I insert the controller after the unit is fully booted, everything is ok. I have another Pi 3+ I can use to test this. I also have another fresh zwave stick that's not an aeotec that I can use to try to reproduce if this is something specific with the aeotec. @pdobrien3 can you confirm what your previous kernel was? I'm running 6.1.21 on my working Debian 11 install. I'm pretty sure Debian 12 was on a 6.1 kernel as well prior to this 6.6.20 update. The only way I can think of to proceed further is to get working kernel crashdumps going, but I'm not 100% sure this is even a kernel panic. Another interesting thing to try would be doing this on a non-raspberry pi but with Debian 12 to see if this is anything specific to the pi or to the kernel. |
Beta Was this translation helpful? Give feedback.
-
|
I am affected by this as well, below is a timeline best I can remember of the problem manifesting itself. March 14th March 15th March 17 or 18th March 20 I'm going to try some different combinations of Bookworm and ZWave-JS versions tonight and see if I can narrow down what change is causing the Pi to lock up. It was working between March 15 & 17 and I don't believe I updated any other software on the Pi during that time. Let me know if you need any more information |
Beta Was this translation helpful? Give feedback.
-
|
@Nathan-Weber What kernel are you running? (uname -a) |
Beta Was this translation helpful? Give feedback.
-
|
No issues so far on x86_64 with Debian 12 and latest available kernel (bookworm-backports): $ cat /etc/debian_version
12.5
$ uname -a
Linux koro 6.6.13+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.13-1~bpo12+1 (2024-02-15) x86_64 GNU/Linux6.6.20 is not available for Debian 12, that's specific to Raspberry Pi OS. http://archive.raspberrypi.org/debian/pool/main/l/linux/ I would suspect the issue is related to Raspberry Pi more so than than a difference between kernels 6.6.13 and 6.6.20, but can't say for certain. I have two instances of ZUI (two USB controllers) running on this server for testing (in Docker). |
Beta Was this translation helpful? Give feedback.
-
|
Another data point. I just installed a Zooz S2 Stick 700 on a pi 3 running Debian 12, and it started just fine. |
Beta Was this translation helpful? Give feedback.
-
|
Linux RaspberryPi3ZWave 6.1.0-rpi8-rpi-v7 #1 SMP Raspbian 1:6.1.73-1+rpt1 (2024-01-25) armv7l GNU/Linux but i rolled back after having the issue |
Beta Was this translation helpful? Give feedback.
-
|
@kpine I was suspecting it being more of an issue from 6.1 -> 6.6. What zwave controller are you running? |
Beta Was this translation helpful? Give feedback.
-
|
SiLabs UZB7 and 800 dev kit, no Gen5/Gen5+ to test with. Would be pretty wild if it were limited to the Aeotec. |
Beta Was this translation helpful? Give feedback.
-
|
Firing the zooz stick up with no configuration wasn't a valid test. I did the same thing with the aeotec on the test pi and there were no issues. I restored my zwave-js-ui configuration backup and reproduced the crash again with the aeotec. I would have to transfer my zwave network backup onto the the zooz stick and try it out. The Firmware transaction timeout message in @pdobrien3 's screenshot above seems to indicate a problem with this kernel and the rpi firmware maybe? I ran |
Beta Was this translation helpful? Give feedback.
-
|
Thanks everyone for adding more details to this issue. Unfortunately I don't think there is much I can do on ZUI side in order to fix this. Another try I could suggest is to try disabling soft-reset from settings to see if that makes it work considering it locked just after that by looking at the logs. Soft reset is seen by the os like unplugging and plug back the stick so IMO that could be a possible root cause of the problem. The OS should handle it for sure and this should be reported to raspbian/debian IMO but at least this could be a solution to the ones expecting this issue. I'm also wondering if this is just something related to docker or if this happens also when using snap or any other deploy method |
Beta Was this translation helpful? Give feedback.
-
|
Same issue, downgraded kernel. However, I have to ask if this might be somehow related; #3777, closed with "Deprecated packages are not always bad if they do some really basic thing and they don't have any open security issue." However, when I see something like "This module is not supported, and leaks memory. Do not use it." I have to wonder if this isn't somehow related. I simply do not have the time to investigate this. |
Beta Was this translation helpful? Give feedback.
-
|
@sgtchains Deps have been bumped a while ago, anyway most of those packages are used by dev deps, nothing that could cause this issue anyway. This is just a bug with the kernel |
Beta Was this translation helpful? Give feedback.
-
|
same problem and same solution... thx ! |
Beta Was this translation helpful? Give feedback.
-
|
So yes, downgrading the kernel works, but somehow the kernel is updating more often than i would like. Is there a real root cause and/or solution for that? |
Beta Was this translation helpful? Give feedback.
-
|
The solution will come once they fix the issue on the kernel, it's not something we can fix on our side sadly |
Beta Was this translation helpful? Give feedback.
-
|
Ah ok. Is there any issue to track that you know off? Have to find a way to block kernel update then. |
Beta Was this translation helpful? Give feedback.
-
|
For the record, this issue persists with the List of commits: |
Beta Was this translation helpful? Give feedback.
-
|
I'm using 6.6.74+rpt-rpi-v8 with the latest version of Debian GNU/Linux 12 (bookworm) So far so good, but I'll keep monitoring |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Someone to test this solution ? Raspberry pi file Regards. |
Beta Was this translation helpful? Give feedback.
-
|
I have marked this as answer now, thanks @clomipax |
Beta Was this translation helpful? Give feedback.
-
|
Maybe specify to add it under |
Beta Was this translation helpful? Give feedback.
-
|
I have updated the comment |
Beta Was this translation helpful? Give feedback.
-
|
Can we confirm the actual solutions? I see three versions mentioned in this answer thread...? |
Beta Was this translation helpful? Give feedback.
-
|
Hello I just had a look to /boot/firmware/config.txt on afresh install. At the end of the file theri is a [all] entry. The actual and normal solution should be : Raspberry pi file |
Beta Was this translation helpful? Give feedback.
-
|
We may have a solution here: |
Beta Was this translation helpful? Give feedback.
-
|
Adding |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that dtoverlay=dwc2 solves the issue for Alpine 3.2.1 running Kernel 6.12.13-0-rpi. One thing I noted is that the dwc2 module slightly delays the instantiation of network devices causing network configuration to fail hard (i.e. no retries) at least 60% of reboots. A small script that forced the network startup to wait until the network device instantiated solved the issue. This may also be an issue with other light-weight distributions. |
Beta Was this translation helpful? Give feedback.
-
|
I am using Ansible to manage about 10 raspberry Pis with ZwaveJS; here is my code for deployment, if this helps anyone Also note that on bookworm the location of the boot file is /boot/firmware/config.txt# Make sure the following two lines are present in the /boot/firmware/config.txt file:
# Zwave Stick USB hang
# dtoverlay=dwc2
- name: Ensure Zwave Stick USB hang configuration is present in config.txt
blockinfile:
path: /boot/firmware/config.txt
block: |
# Zwave Stick USB hang
dtoverlay=dwc2
insertafter: '^\[all\]$'
marker: "# {mark} ANSIBLE MANAGED BLOCK - Zwave USB Configuration"
state: present
create: yes
register: boot_config_changed
- name: Reboot machine if configuration was changed
reboot:
reboot_timeout: 300 # 5 minutes timeout
when: boot_config_changed.changed |
Beta Was this translation helpful? Give feedback.
-
|
I manage mine in ansible as well, but I like your solution better than mine. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
update worked but ZwaveJS stopped working after one day with kernel 6.6 (error: Unable to enumerate USB device) but running for months with kernel 6.1.77 |
Beta Was this translation helpful? Give feedback.
-
|
here a fresh install on a pi3B+ with the same problem of crashes as soon as i chenged serial port and hit save. !! YES !! |
Beta Was this translation helpful? Give feedback.
-
|
I was facing the same issue with a RPI-3B+, old Z-wave Gen5 (upgraded from 3.95 to 6.07) but with Trixie (testing). The dtoverlay worked for me. |
Beta Was this translation helpful? Give feedback.
-
|
how does the final solution really look like?
best
Michael ***@***.***> schrieb am Mi., 13. Aug. 2025, 10:35:
… Can we confirm the actual solutions? I see three versions mentioned in
this answer thread...?
—
Reply to this email directly, view it on GitHub
<#3880 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHYY7LSFWQXLJBYGTSWBJML3NL2DXAVCNFSM6AAAAABSBO5XEWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBZGA2TKMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
Hi,
Someone to test this solution ?
(and report if it works)
(Refer to : home-assistant/operating-system#3362)
Raspberry pi file
/boot/firmware/config.txt
add last line under
[all]:Regards.