in my setup I have a HA OS instance running on an RPi 4 and RaspberryMatic on the same system with a RF-USB.
Until I’ve updated the Core and RaspberryMatic four days ago to the newest versions everything worked as intended. Now my Homematic based sensors got unavailable in HA, while they still work in the RasperryMatic plugin, where I can observe the changes of the entities.
In an attempt to solve the problem I saw, that the Homematic(IP) Local custom integration is failing to connect now, but I don’t know why.
I tried by open up the RaspberryMatic firewall (Firewall policy to “Ports open”, Homematic XML-RPC API & Remote Homematic script API to “Full access”), but that didn’t solve the connection error.
The integration is not able to connect to the Addon.
Restart the RM Addon, wait 5 Minutes and restart HA.
Looks like the Addon has a problem after a HAOS Update.
I restarted as suggested the RM Addon and 5 minutes later HA again, but that didn’t change anything. I still get the “HOMEMATICIP_LOCAL-Interface not reachable. No connection to interface RaspberryMatic Ctrl-HmIP-RF” and “HOMEMATICIP_LOCAL-Interface not reachable. No connection to interface RaspberryMatic Ctrl-BidCos-RF” notifications.
Please create an issue here.
Please fill out the issue template, and add as much information as possible.
Also add the HA logs(press on full logs), an do not delete lines, only overwrite sensible informations like usernames and password.
Additionally: Activate the debug mode of the integration (right click on the integration), and add the log with debug information as well. Some iterations of the above mentioned warnings should be part of the log data.
I’ve had the very same issue - after Updating Home Assistant all my homematic devices went unavailable, yet they were fully working within the RaspberryMatic Addon. I’ve opened an issue both on the homematic local integration repository and on the raspberryMatic Addon repository as i wasn’t sure which one is causing the issue.
Turned out that i was using a -TK USB stick, which isn’t Bidcos compatible. Although this wasn’t an issue before updating HA, this became apparently one after i did upgrade. After i disabled the bidcos checkbox in the configuration workflow of the ingration, all my devices were instantly available afterwards. Check the linked issue - unfortunatelly we switched to german. If you dont understand german, i’m pretty sure google translate will help you out (or follow my steps above, maybe it helps aswell).
Thanks for pointing me there @ElGaucho. The behaviour with my installation was similar, but I couldn’t uncheck the “enable Homematic (Bidcos-RF)” box, as it was selected again any time I’ve tried an (un)successful connection. But anyway my stick is not an “-TK” one.
Adding a new integration wasn’t possible as well, but this process pointed me to the insight that the IP of the RaspberryMatic Addon changed (during update?). After inserting the correct one to “CCU Hostname/IP-Address” I could connect again. But the IP change shouldn’t happen, or? @SukramJ No issue necessary anymore, as the problem was solved by changing the IP address in the Homematic(IP) Local integration. Thanks for your attention anyway.
I had the same issue since 3 days. Obv. linked wiht an HA update…
… Tried “all”…
Thanks to your hint (and the following one , not to use the IP adress , to use the hostname, ) it worked suddenly.
Thanks to all of you.
It was also serious for me, having some iportant gadget connected to it…
