Raspberrymatic not working with os-agent 1.4.1 for aarch64 in HA

[Rainerlan]

Hi,
not sure what are the dependencies and if this can be called a bug...

I went from a raspi 4 running 32bit bullseye (+HA incl. Rasperrymatic) to 64bit bullseye (+HA incl. Rasperrymatic).
After restoring the HA backup in the new OS and HA instance, raspberrymatic did not start up properly - Find below the log output - The log contained:
Starting multimacd: ...........ERROR: couldn't setup /dev/mmd_* devices
After switching back from
os-agent_1.4.1_linux_aarch64.deb to os-agent_1.2.2_linux_aarch64.deb, raspberrymatic is working fine again.

Is it worth to create an issue to either os-agent or raspberrymatic - or can this be solved by an OS configuration?
(I am not a Linux specialist and hence don't know things like apparmor in detail)

The Raspberrymatic log, taken with os-agent 1.4.1:

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: no hardware found
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.2, OK
Identifying Homematic RF-Hardware: ....HmRF: HM-MOD-RPI-PCB/[email protected], HmIP: HM-MOD-RPI-PCB/[email protected], OK
Updating Homematic RF-Hardware: HM-MOD-RPI-PCB: 2.8.6, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: ...........ERROR: couldn't setup /dev/mmd_* devices
Starting rfd: ......OK
Starting HMIPServer: .......................................................................................................................................................ERROR
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.65.11.20221005 (raspmatic_oci_arm64)

log taken with os-agent 1.2.2:

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: no hardware found
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.3, OK
Identifying Homematic RF-Hardware: ....HmRF: HM-MOD-RPI-PCB/[email protected], HmIP: HM-MOD-RPI-PCB/[email protected], OK
Updating Homematic RF-Hardware: HM-MOD-RPI-PCB: 2.8.6, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: .......OK
Starting rfd: ..OK
Starting HMIPServer: ..............OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.65.11.20221218 (raspmatic_oci_arm64)```

[maierei]

Same error here after switching from a Raspberry Pi 4 with Supervised installation on Debian 11, 64 Bit to a small Linux server with Supervised installation on Debian 11, 64 Bit.
Also after downgrading the OS-Agent to 1.2.2 RaspberryMatic works again.