Logger: homeassistant.setup
Source: components/ebusd/__init__.py:70
First occurred: 21:26:38 (1 occurrences)
Last logged: 21:26:38
Error during setup of component ebusd
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/ebusdpy/ebusdpy.py", line 14, in init
sock.connect(address)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 235, in _async_setup_component
result = await task
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/ebusd/__init__.py", line 70, in setup
ebusdpy.init(server_address)
File "/usr/local/lib/python3.10/site-packages/ebusdpy/ebusdpy.py", line 18, in init
raise EBusError(socket.error)
ebusdpy.ebusdpy.EBusError: <class 'OSError'>
Any help on sorting this will be very much appreciated
OK thanks. I’ve parked this exercise for now as I’ve written a Python script that is reading the data I want and writing it to a file. I’ll come back to HA another time.
I am having the exact same problem.
I have installed the ebusd Add-On by Lukas Grebe and the ebusd Integration via HACS.
My ebusd hardware is connected to the LAN via WiFi, the Shield interface says “ebusd device string: ens:192.168.178.40:9999”
I do not know exactly how to configure the Add-On. I have tried two settings on the Configuration page: Mode: ens and Network Adapter Address: ens:192.168.178.40:9999 as well as
Mode: udp and Network Adapter Address: udp:192.168.178.40:9999, but both didn’t work, I keep getting the same error as Mike.
Hi.
I found the same connection refused problem as G8GYW when connecting via WiFi to the ebus adapter.
After a bit of trial, error and deduction I figured it could be something to do with the ‘9999’ port required by the hardware not being the default used by Home Assistant.
Sure enough, adding port: 9999 to the config section in configuration.yaml fixed the problem and the adapter gets added now in Devices and Services.
The whole config section looks like this: