This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Raspberry Pi 3B+ Upgrades breaks ZwaveJS-UI Container #3639
Comments
|
I encounter exactly the same issue since yesterday after a reboot (same raspberry. How to solve that ? |
|
@pdobrien3 Could you give me some error logs please? |
|
due to the fact the pi becomes unresponsive this is all I could get: and this through dmesg: and docker logs: |
|
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. |
|
@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... |
|
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. |
|
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 |
|
@Nathan-Weber What kernel are you running? (uname -a) |
|
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). |
|
Another data point. I just installed a Zooz S2 Stick 700 on a pi 3 running Debian 12, and it started just fine. |
|
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 |
|
@kpine I was suspecting it being more of an issue from 6.1 -> 6.6. What zwave controller are you running? |
|
SiLabs UZB7 and 800 dev kit, no Gen5/Gen5+ to test with. Would be pretty wild if it were limited to the Aeotec. |
|
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 |
|
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 |
|
Has anyone tried robertsLando's suggestions or reported elsewhere? |
|
I just turned off soft reset and upgraded. There were some docker upgrades along with the kernel upgrade. Raspi 3B+ boots fine and zwavejs-ui up and running.
|
|
looks like I called it to soon. The first boot was fine, subsequent boots resulted in same crash. Not sure if soft reset is automatically turned on somehow? |
|
I am also having issues with a Zooz ZST39 LR though |
|
I have not had time to look into this any further. I think the next step is to get kernel crash dumps enabled, reproduce it, and then report it to rpi (not sure what the process is there). |
I think that's the way, in the meanwhile you could consider alternatives way to run the zui? Maybe the packaged or the snap version? You can find the packaged one on releases here on gh. You just have to download the package, unzip it and run like a normal exec, the store dir will be created next to the exec and you can place there your store backup and it will work as before. This could be also a nice try in order to see if the bug is strictly related to docker |
|
That's an important bit to know, for sure. I should have time to look at this later in the week. If someone else can get to it sooner, all the better. |
|
Hello I have the same problem... Have you a solution please |
Hello have you soluce ? |
|
Installed zwave-js-ui via snap and ported my config into /var/snap/zwave-js-ui/. As soon as it started it locked up exacly as it did when running under docker. |
|
Hello I have test in snap, in docker it s the same problem. Block at startup in 30 seconds, 1 minute. Have you an solution plesae |
|
I haven't had time to go further on this. In the meantime, I have my pi running on Debian 11 instead of 12. The only thing it does is zwave-js-ui, so that wasn't a big deal for me. I would do that until this is figured out. |
|
I just upgraded to pi5 with an ssd hat and ssd :-) running 64bit Debian 12. Would still like to see some resolution though as my pi3 can still be a backup. |
|
I wait a solution, because I can't change pi3 to pi 5 because I have 3 pi3 on spare... |
|
Hi guys I'm sorry that I cannot help you much on this, does anyone found some reference issue on debian/raspbian forums? |
|
Hello, When I upgrade the rpi, it hangs again. When I revert to the above kernel. It works again. Hopefully this help |
Hello yes it a good new |
|
Yes, I have the command from https://forums.raspberrypi.com/viewtopic.php?t=361116&start=50 |
Thank you very much |
Hello it s works. |
|
Just to be clear, seems this is a problem starting from kernel version 6.2 right? |
|
I don t know, but firmware 6.1.77 work perfectly |
|
I also don't know, because I don't know how to test another version of a kernel on a pi3. |
The problem appears to have surfaced when Debian 12 moved from Kernel 6.1 to 6.6. @pdobrien3 upgraded to a rpi 5 and is not having the issue even with those versions. It appears this issue is isolated to the rpi 3b+. It could be on other rpi models as well, but there's no way to know until someone makes a report. |
|
so the solution is to downgrade the kernel? |
|
I have no clue if this is related, but I just tried a fresh zwave-js-ui + new Zooz800 USB + fresh Debian 12 install on a Raspi 2B, and Debian would hang every time I clicked Save after changing the zwave device setting away from /dev/zwave to the Zooz by-id choice. I did the same thing with the same setup except a fresh Debian 11 install, and things went off without a hitch. Zwave-js-ui + ancient RaZberry zwave pi hat + fresh Debian 12 also worked great. I did that install first to issue a hard reset and to start fresh with my zwave network. Edit: Bare metal installs via package for all. |
The issue seems to happen when there is an access to the serial port so |
|
Same issue : EDIT : Following this manuel for Domoticz https://www.domoticz.com/wiki/Zwave-JS-UI And now it works what i did : I tried to access MQTT with MQTT Explorer, it was working. docker compose down docker compose down docker compose up -d Followinf the Domoticz instruction, I put One by one the information in the form and then saved the config each time. And now it works... Very very strange... |
|
I was experiencing similar issues. RPi 3B Every time ZWaveJs-UI accessed the serial port the raspberry pi froze After downgrading using the command below te device keeps running and stays up so far: As far as I know the Aeotec Z-Stick Gen 5 has two versions, not sure which one I have: https://aeotec.freshdesk.com/support/solutions/articles/6000167094-z-stick-gen5-technical-specifications- |
|
I just experienced the same issue. The only difference I have compared to previous reports is that I installed via NPM. No containers of any sort. |
|
Same issue on
Solves the issue |
|
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. |
|
@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 |
|
same problem and same solution... thx ! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Checklist
Deploy method
Docker
Z-Wave JS UI version
9.9.1
ZwaveJS version
12.4.4
Describe the bug
Recent 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]
linux-headers-rpi-v7/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
linux-headers-rpi-v7l/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
linux-image-rpi-v6/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
linux-image-rpi-v7/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
linux-image-rpi-v7l/stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
linux-image-rpi-v8/stable 1:6.6.20-1+rpt1 arm64 [upgradable from: 1:6.1.73-1+rpt1]
linux-libc-dev/stable,stable 1:6.6.20-1+rpt1 armhf [upgradable from: 1:6.1.73-1+rpt1]
To Reproduce
start 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 behavior
stable awave network through docker on a pi 3b+ with an aeotec gen5 zwace stick
Additional context
No response
The text was updated successfully, but these errors were encountered: