Stable upgrade 2025.1->2025.2 issue...
Posted: Sunday 01 March 2026 15:38
Hello,
I have had an issue in december on a full upgrade (new SD built on Debian 13 & reinstalled all Domoticz from scratch with Z4D plugin going to python venv etc ; everything else remained as-is, for instance zwave legacy inegration and any other domoticz core integrations). At the moment, no time to ding into this, unfortunately + system is headless & this looks to be a brutal kernel hang.
Today, after disabling services & restored a DB with Z4D plugin disabled (as this was the biggest integration change, with venv, on top of raspbian 11 -> 13 move due to openssl3, this was IMO most likely an issue there but looks I was wrong) & somoticz service start disabled as well to be able to start is manually & see some logs directly on console (crash is so sudden that no system/domoticz logs are on a SD after restart).
Maybe a good catch: Last log is about "Motherboard sensors" integration I had for ages... So the question is: Is there known issue there (maybe specific to PI3B) that rings a bell to someone??? If this is known to cause issue, maybe on last raspbian, IMO starting this may be disabled with a deprecation warning in the log as that's not easy to figure-out what's wrong due to the brutal hang that does not even allow logs to be written on storage for post-mortem check.
I have had an issue in december on a full upgrade (new SD built on Debian 13 & reinstalled all Domoticz from scratch with Z4D plugin going to python venv etc ; everything else remained as-is, for instance zwave legacy inegration and any other domoticz core integrations). At the moment, no time to ding into this, unfortunately + system is headless & this looks to be a brutal kernel hang.
Today, after disabling services & restored a DB with Z4D plugin disabled (as this was the biggest integration change, with venv, on top of raspbian 11 -> 13 move due to openssl3, this was IMO most likely an issue there but looks I was wrong) & somoticz service start disabled as well to be able to start is manually & see some logs directly on console (crash is so sudden that no system/domoticz logs are on a SD after restart).
Maybe a good catch: Last log is about "Motherboard sensors" integration I had for ages... So the question is: Is there known issue there (maybe specific to PI3B) that rings a bell to someone??? If this is known to cause issue, maybe on last raspbian, IMO starting this may be disabled with a deprecation warning in the log as that's not easy to figure-out what's wrong due to the brutal hang that does not even allow logs to be written on storage for post-mortem check.