Homematic(IP) Local failed to connect to RaspberryMatic

Hi,

I am new to HA and am trying to set up Homematic on ODROID supervised HA install. I followed the install and got stuck on setting up the integration and connect to the RaspberryMatic.

The firewall has been opened and I searched the forum but my error seems different, here is the log:

Logger: hahomematic.central
Source: custom_components/homematicip_local/control_unit.py:770
Integration: homematicip_local ([documentation](https://github.com/danielperna84/custom_homematic), [issues](https://github.com/danielperna84/hahomematic/issues))
First occurred: January 6, 2024 at 21:16:29 (16 occurrences)
Last logged: 10:22:11

* ()
* URL can't contain control characters. ' de838cd8-raspberrymatic' (found at least ' ')
* OSError on temporary_instance-BidCos-RF: (-5, 'Name has no usable address')
* OSError on temporary_instance-BidCos-Wired: (-5, 'Name has no usable address')

I tried to enter the hostname manually, by copying and from 2 different browsers but result stays the same.

Tom

You have a space somewhere in your configuration of either raspberrymatic or the homematic_local connection setup.

Tried reinstalling everything, the error is now only that first empty entry

This error originated from a custom integration.

Logger: hahomematic.central
Source: custom_components/homematicip_local/control_unit.py:770
Integration: homematicip_local (documentation, issues)
First occurred: 13:20:16 (3 occurrences)
Last logged: 13:28:59

()

Not much to go on …

I think @danielperna84 might need to help there. :slight_smile:

There must be something missing from your logs. In any case, read the docs very carefully. Make sure the firewall and username + password match the documented specifications.

Thanks for the help but is there a way to turn on more verbose logging? I can’t spot any error in configuration.

  • Hostname is correct & up, responds to ping
  • Ports 80, 2000, 2001, 2010 all listening
  • CCU admin user/password is simple/correct to avoid any character issues
  • CCU Firewall set to ‘full access’ (nothing in the ‘Port opening’ box - left default)

I tried replacing hostname by the IP but no luck, same log entry appears.

Im having the exact same problem, read the docu, triple checked everything.
When I enable debug logging, I get the following output (same warning message in last line and setup fails):

2024-04-03 13:11:46.436 DEBUG (SyncWorker_2) [hahomematic.central] GET_LOCAL_IP: Got local ip: 172.30.X.X
2024-04-03 13:11:46.437 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('system.listMethods', ())
2024-04-03 13:11:46.464 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('getVersion', ())
2024-04-03 13:11:46.468 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_AUTH_ENABLED: Getting the flag auth_enabled
2024-04-03 13:11:46.499 DEBUG (MainThread) [hahomematic.client.json_rpc] DO_LOGIN: method: Session.login [None]
2024-04-03 13:11:46.522 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SUPPORTED_METHODS: Getting the supported methods
2024-04-03 13:11:46.544 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: CCU.getAuthEnabled
2024-04-03 13:11:46.544 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_AVAILABLE_INTERFACES: Getting all available interfaces
2024-04-03 13:11:46.566 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Interface.listInterfaces
2024-04-03 13:11:46.566 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_HTTPS_REDIRECT_ENABLED: Getting the flag https_redirect_enabled
2024-04-03 13:11:46.587 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: CCU.getHttpsRedirectEnabled
2024-04-03 13:11:46.587 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SERIAL: Getting the backend serial
2024-04-03 13:11:46.617 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_serial.fn]
2024-04-03 13:11:46.617 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('system.listMethods', ())
2024-04-03 13:11:46.620 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('system.listMethods', ())
2024-04-03 13:11:46.623 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ('temporary_instance-HmIP-RF',))
2024-04-03 13:11:46.626 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('system.listMethods', ())
2024-04-03 13:11:46.628 WARNING (MainThread) [hahomematic.central] ()

What device are you using to communicate with the Homematic devices?
Im using HA OS in a VM and pass a USB HmIP-RFUSB-TK through.
HmIP-RFUSB-TK is a third party RFUSB by Telekom for their router and there is some information online that it does not have the exact same featureset/firmware as the standard HmIP-RFUSB.
Maybe that is the reason why it fails @danielperna84 ?

I use debmatic for the CCU software and they have this about the Telekom stick.

HmIP-RFUSB-TK (Telekom Version, nur HmIP Funk, Firmware Updates nicht möglich, Funktionalität nicht dauerhaft sichergestellt.

It says that only Homematic IP is available. That updates of the stick is not possible and that all the features in the CCU have not been tested on the stick, so it is uncertain what is supported.

1 Like

I am using a HA supervised install on Odroid hardware, with Raspberrian on same environment, and HM-Lan-GW to connect with HomeMatic Wired devices on RS485. I still have the same issue and with Debug logging on I only get what you see below.

All devices are operating in Raspberrian, another HA setup where I used the earlier integration also works fine, but for some reason I can’t get past this step.

2024-04-05 10:17:45.581 WARNING (MainThread) [hahomematic.central] ()
2024-04-05 10:19:33.971 DEBUG (MainThread) [custom_components.hacs] Nothing in the queue

any resolution you found @MoritzF - I am facing the same issue!

Today my HmIP-RFUSB arrived and now Homematic IP local works perfectly fine. I didn’t even need to change any other configurations, just swapped the USB.
So for me using the HmIP-RFUSB-TK was the problem, even if Raspberrymatic worked without any issues before.

While this may not be helpful towards fixing things, it shows that the issue probably lies within the used RF module/GW.

The -TK version is a stick bought as a white-label product by Telekom together with a range of the Homematic IP products and then labeled as a Telekom brand.
It was meant to be a clsoed ecosystem and not part of the Homematic one.