hm… ok, I don’t think, that it is an issue with the Addon / Integration when devices become unavailable.
Secondly: The communication is much more efficient and can handle more values and variables. Additionally, HASS has received some more information from the RaspberryMatic (at least that’s what I understood).
I don’t think so.
I also had the RaspberryMatic Addon installed - but decided to go with its own VM in proxmox, since the addon was more unreliable - in my case, I always got errors for unavailable devices when HA restarted, because the Addon took a bit longer to start.
Now, I only get these when the RaspberryMatic VM needs a restart, which is not as often as HA (with monthly updates and patches)
Also, I don’t see any issue with the efficiancy comparing the VM installation and the Addon installation.
In addition to that, I’m still getting all relevant information from RaspberryMatic through the integration Homematic(IP)_local …
Finally, to address your issue:
Can you please check the following guideline from Jens (sorry, just copy & paste from the git - so it is in german)
The guide is based on the installation on a RPi4 - but at least the solution with the USB dongle should still be valid.
You should use an USB extension cable - and also, check the CarrierSense Level within RaspberryMatic
Wie schon oft hier und in vielen Diskussionsbeiträge in Diskussionsforen thematisiert wird auch dies hier ein Resultat des Umstandes sein, das der RaspberryPi4 als massiver Funkstörer bekannt ist. Hier hilft nur entweder auf einen nicht-RaspberryPi4 wechseln oder massiven Abstand zwischen RaspberryPi bzw. anderer potentziell störender Technik wie einer SSD und dem eigentlichen Funkmodul (HmIP-RFUSB) schaffen! Auch hilft ein Blick auf den CarrierSense Wert. Dieser MUSS dauerhaft < 10% liegen sonst liegen irgendwelche Funkstörungen in der näheren Umgebung des Funkmodules vor!