HomeConnect plugin

[gvandick]

Raspberry P3
Domoticz 2026.3

https://github.com/domoticz/home-connect plugin

I install the plugin and follow all instructions. I use a No-ip DDNS. Port forwarding raspberry server.
I tried also my own IP.

log error
2026-08-18 11:11:10.459 Error: Bosch homeconnect: CConnection_disconnect, disconnection request from 'Bosch homeconnect' ignored. Transport does not exist.
2026-08-18 11:11:10.463 Status: Bosch homeconnect: Exiting work loop.

Reply in browser
{
"error": "unauthorized_client",
"error_description": "client or redirection URI not authorized"
}

With browser access to domoticz-server URL from developeraccount http://mysite.com:portnr/callback

log error domoticz
2026-08-18 16:23:47.723 Error: Bosch homeconnect: Listen directive received, action initiation failed.
2026-08-18 16:23:47.724 Error: Bosch homeconnect: HomeConnect: Failed to bind OAuth callback server on port 9500: bind: Address already in use [system:98 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind']




no matter what I try no result working. Someone an idea?

[gvandick]

log domoticz

2026-08-22 10:13:15.131 Error: Bosch Home: Listen directive received, action initiation failed.
2026-08-22 10:13:15.131 Error: Bosch Home: HomeConnect: Failed to bind OAuth callback server on port 8040: bind: Address already in use [system:98 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind']

I uses the domoticz app and this works so port forwarding works also. I don't understand what the problem is and how to solve it.

Maybe someone a suggestion.

[gvandick]

Domoticz 2026.3 (docker); Raspberry P3, Zigbee2mqtt Frontend, Rflink; DZGA

I would like to know if there are any Domoticz users who have the HomeConnect plugin working on a Raspberry Pi.

I am using a No-IP account. I haven't found a solution to the problem online; all search results point to an issue with the Domoticz port.
I have tried configuring various ports, updating the settings in the plugin, Domoticz, and the HomeConnect developer account accordingly each time.

I also use the Domoticz app and it works fine, so port forwarding should be set up correctly.
Furthermore, when I access Domoticz via a web browser using the No-IP address, the login page loads successfully; this leads me to conclude that port forwarding is working correctly.

In the HomeConnect app, the dryer and dishwasher are linked and functioning properly.

I have also linked HomeConnect in the HomeWizard app, and that works fine too. (Unlinking it there has no effect on my attempt to get HomeConnect operational in Domoticz.)

The error message is: `Failed to bind OAuth callback server on port 8040: bind: Address already in use [system:98 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind']`

It seems possible to me that the plugin or Domoticz has a bug preventing it from working by failing to release the port (in time).


I would like to know if there are any Domoticz users who have the HomeConnect plugin working on a Raspberry Pi.

I am using a No-IP account. I haven't found a solution to the problem online; all search results point to an issue with the Domoticz port.
I have tried configuring various ports, updating the settings in the plugin, Domoticz, and the HomeConnect developer account accordingly each time.

I also use the Domoticz app and it works fine, so port forwarding should be set up correctly.
Furthermore, when I access Domoticz via a web browser using the No-IP address, the login page loads successfully; this leads me to conclude that port forwarding is working correctly.

In the HomeConnect app, the dryer and dishwasher are linked and functioning properly.

I have also linked HomeConnect in the HomeWizard app, and that works fine too. (Unlinking it there has no effect on my attempt to get HomeConnect operational in Domoticz.)

The error message is: `Failed to bind OAuth callback server on port 8040: bind: Address already in use [system:98 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind']`

It seems possible to me that the plugin or Domoticz has a bug preventing it from working by failing to release the port (in time).

[NomadIoT]

I see the message "Address, in use" and that usually means another process is already using that port. You can run the command "netstat -tulpn | grep 8040" to find out which process is using it. Once you know the PID kill that process. Then restart Domoticz immediately. That should free the port.

[jannl]

You only need the port for the first register at the home connect website. As soon as the hardware is enabled you see an url in the logging which you need to paste in a browser.

Finally I used claude ai which gives much better answers when IT related

I use Domoticz in a docker on a pi5, via a remote proxy on my synology NAS. For registering home connect I added a different port. Make sure the same port is configured in the settings in home connect.

[gvandick]

I tried all your suggestions already. If I change the external port to a different port then the Domoticz port the error port in use also appear.
kill the port and restart i used also many times before. (chatgpt)

I also connect by mail to Homeconnect and they answer:

GET authCode request (endpoint = /security/oauth/authorize). As I see there is a mistake for redirect_uri parameter.

Thanks for your comments; if you have any further ideas, I’d love to hear them. I try for a long time to get it working.

[NomadIoT]

If HomeConnect flags the redirect_uri that's your real blocker. HomeConnect will not let the redirect happen unless the redirect_uri matches exactly what is listed in your developer account, including (http or https the port, the /callback path and no trailing slash). In Docker you must also publish that port so that HomeConnect can reach it.

[NomadIoT]

Hope you manage to sort this out.

[gvandick]

No result. I modified the Docker ports. I tried making changes after stopping Docker. No matter what I adjust, the "port already in use" error persists, citing the specific port number I assigned at that moment. I am making these adjustments in the router, Home Connect Developer, and Home Connect Domoticz each time.

The results are the same even when I use my public internet IP address.

[jannl]

The ports in docker should be the same you configured in the plugin amd they should be the same in de home connect configiration. Don't forget to route that port in your router. Do not worry about security, as soon as the connection is there the forwarding in the router can be disabled again.

[gvandick]

Jannl gave me the idea to use AI. Thanks to everyone for the feedback.

Solved using AI. I worked through the problem step-by-step via Q&A and made adjustments to the Docker YAML file. The authorization link suggested by the AI ​​contained errors. I modified the field in the Home Connect plugin to exclude "http://" and the callback URL, using only the DDNS address instead. I'm curious to see if it keeps working. The devices are now registered in Domoticz.

[jannl]

When you are registered you do not need the connection. I would recommend to stop forwarding in your router for that port.

[gvandick]

Thx I did it already