Campatibility issue with RaspberryMatic #107
Comments
|
Hm, the most likely cause is the added support for permission updates via run with #92. In theory, the behavior should not change on Supervised. @ciB89 can you try 1.3.0 and see if that fails too? Also, is Maybe you have to rerun the Supervised installer, specifically the switch to cgroups v1 needs to execute properly: https://github.com/home-assistant/supervised-installer/blob/0779e8d745d59d9c1cfbc9087071b7cfd489850a/homeassistant-supervised/DEBIAN/postinst#L143-L162 /cc @jens-maus |
|
1.3.0 has the same issue. Btw, since I come from Raspbian, this version of the installer script would not have worked since the cmdline.txt is located at |
|
Same issue here. Works up to 1.2.2. |
|
Yes, I can see the same problem |
|
Since I am not running Debian but PiOS, I presume that I won't get any support on this matter. Is anyone else who is having this issue running Debian or Home Assistant OS? |
|
@ciB89 running Debian bullseye here. |
|
Running Raspberry Pi OS (64-bit), which actually is a Debian 11 (bullseye) |
PiOS it's nevertheless not officially supported. |
|
Since there has not been any progress on this, is there anything we can do to debug this? |
|
I've just reviewed the difference between 1.2.2 and 1.3.0, and it really should behave the same as long as Can you double check if |
|
Can you also provide the logs of the OS Agent ( |
As already has been mentioned, Im am currently not home, so I cannot provide the output till next week. |
I know, that is why I said "double check" 😄 It would explain it all. Because if that file is not present, the very same code is used as in 1.2.2, so I am really confused why it is no longer working for you. Maybe the logs help to better understand. I am waiting for the logs. |
double checked, still not present ;) Here is the log output before upgrading (running on 1.2.2): After upgrading to 1.4.1: Interestingly, RaspberryMatic kept on running without any issues after upgrading to 1.4.1, only after restarting the addon/container, I had the issue. I check the logs of OS Agent again after restarting RaspberryMatic: |
|
In case it has any relevance (which I doubt), the container ID of RaspberryMatic is: |
|
Hm, it seems to use |
Merged
|
Updated to 1.5.1 and can confirm there aren't any issues now anymore. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Describe the issue you are experiencing
I have restarted my host (home assistant supervised) after updating os-agent to latest version (1.4.1) und suddenly the addon would not work properly anymore.
Logs show:
I tried
sudo service pivccu-dkms startandsudo modprobe eq3_char_loopagain, now the logs of the addon changed a little bit:Describe the behavior you expected
Add-on working normally without throwing errors during startup.
Steps to reproduce the issue
-upgrade os-agent to 1.4.1
-start the addon with a hmip device
What is the version this bug report is based on?
3.65.11.20221005 of addon, 1.4.1 of os-agent
Which base platform are you running?
rpi4 (RaspberryPi4)
Which HomeMatic/homematicIP radio module are you using?
HmIP-RFUSB
Anything in the logs that might be useful for us?
Supervisor logs after rerunning modprobe:
Additional information
Downgrading back to version 1.2.2 "fixed" the issue.
Link to Raspberrymatic issue: jens-maus/RaspberryMatic#2019
The text was updated successfully, but these errors were encountered: