john30 / ebusd-esp32 Goto Github PK

Hey @john30 ,

I managed to connect your ebusd adapter v5 wifi adapter to home-assistant ebusd add-on. It seems to work at least partially. I am getting some values sent via MQTT successfully.

On the adapter side I see following error in logs
my_client_socket_send: send: errno 11

I have no idea what that means and google does not help. Can you please tell me what that error means?

Build: 20230618
ebusd device string: ens:192.168.1.232:9999
WiFi station: ###redacted###, 192.168.1.232, 44% (-78dBm)
WiFi AP: inactive
Chip ID: dc5475ba43a0, ESP32-C3, rev 4
Hostname: ebus-ba43a0
Up time: 943930
Free heap: 117200
ebusd connected: yes
eBUS signal: acquired

I can see some errors on ebusd side as well but I am not sure if that is related or not

2023-07-15 12:57:13.099 [bus error] poll bai PrEnergyCountHc2 failed: ERR: wrong symbol received

2023-07-15 12:57:15.707 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:57:19.260 [update notice] sent poll-read bai PrEnergyCountHc3 QQ=31: 0
2023-07-15 12:57:20.689 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;37.0;47.0;off
2023-07-15 12:57:22.660 [update notice] received update-read broadcast vdatetime QQ=10: 13:01:46;15.07.2023
2023-07-15 12:57:25.290 [update notice] sent poll-read bai PrEnergyCountHwc1 QQ=31: 1993671
2023-07-15 12:57:25.720 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:57:30.727 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;37.0;47.0;off
2023-07-15 12:57:31.090 [bus error] poll bai PrEnergyCountHwc2 failed: ERR: SYN received
2023-07-15 12:57:32.740 [update notice] received read bai DateTime QQ=10: nosignal;03:24:09;-.-.-;-
2023-07-15 12:57:33.003 [update notice] received poll-read bai Status02 QQ=10: off;60;30.0;100;50.0
2023-07-15 12:57:35.700 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:57:37.106 [bus error] poll bai PrEnergyCountHwc3 failed: ERR: SYN received
2023-07-15 12:57:43.310 [update notice] sent poll-read bai PrEnergySumHc1 QQ=31: 4294967164
2023-07-15 12:57:45.744 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:57:49.293 [update notice] sent poll-read bai PrEnergySumHc2 QQ=31: 0
2023-07-15 12:57:50.770 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;37.0;47.0;off
2023-07-15 12:57:52.710 [update notice] received poll-read bai Status02 QQ=10: off;60;30.0;100;50.0
2023-07-15 12:57:55.119 [bus error] poll bai PrEnergySumHc3 failed: ERR: wrong symbol received
2023-07-15 12:57:55.830 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:58:00.771 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;36.0;47.0;off
2023-07-15 12:58:01.310 [update notice] sent poll-read bai PrEnergySumHwc1 QQ=31: 564866919
2023-07-15 12:58:02.750 [update notice] received read bai DateTime QQ=10: nosignal;03:24:40;-.-.-;-
2023-07-15 12:58:05.761 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:58:07.300 [update notice] sent poll-read bai PrEnergySumHwc2 QQ=31: 0
2023-07-15 12:58:10.780 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;36.0;47.0;off
2023-07-15 12:58:13.300 [update notice] sent poll-read bai PrEnergySumHwc3 QQ=31: 0
2023-07-15 12:58:15.774 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;0;0;0;0
2023-07-15 12:58:19.129 [bus error] poll bai PumpHours failed: ERR: wrong symbol received
2023-07-15 12:58:20.763 [update notice] received read bai Status01 QQ=10: 50.0;48.0;-;36.0;47.0;off
2023-07-15 12:58:22.771 [update notice] received update-read broadcast vdatetime QQ=10: 13:02:46;15.07.2023
2023-07-15 12:58:25.089 [bus error] poll bai ReturnTemp failed: ERR: SYN received`

Hi, ever since i installed the raspberrypi via the GPIO the ssh terminal seems to lag a bit. I guess it has to do with the GPIO interrupt? Any chance that it would work better over the raspberrypi USB port? Newest firmware, i followed your tutorial which is really good.

I've connected to the adapter via WIFI "ebus", configured both WIFI client (dynamic IP) AND network (using a USR-ES1) with static IP address, saved and rebooted and it works. But as soon as I disable the WIFI connection and reboot, the adapter is pingable on the fixed network address but the UI doesn't show up.
Enabling both the WIFI client (starting from scratch via "ebus" WIFI again) and enabling the network, the UI shows up on both IPs (network and WIFI).

Build: 20230903 Adapter V5, [ESP32-C3, rev 4]

I received my v5 in the mail yesterday but I am unable to connect it to my Wi-Fi network.
I installed firmware version 2023-06-18 and after select the Wi-Fi network and entering the password, I get the following screen:

Afterwards the connection times out:

I am 100% certain that the password is correct. My Wi-Fi network supports 2.4GHz and 5Ghz but the 5Ghz network is not stable. It support Wi-Fi N (not ac or ax). I run OpenWRT on my router.

Since this didn't work I tried connecting to the EBUS AP from my smartphone,
I can connect to the AP and was able to configure it successfully this way.

I try to access WebUI from internet via CloudFlare tunnel, but most of the time I get only "Header fields are too long".
If I try to run in PrivateMode to start without any saved cookies etc.. it loads but only once and then show same message.

Page is shown correctly if I access it directly via IP address.

Error is presented in both latest two FW (2023-10-15 and 2023-12-17).

Hi,

I would like to monitor some parameters of my Helioset but when I connect my ebus adapter v5 to the ebus port I don't get any signal. I read all the documentation of the device and I don't find any mention to ebus activation or something like that.

Has anyone had any experience with this kind of devices?

Thanks in advance.

Just received a new v5 board for use with Vaillant AroTherm Plus, but having significant issues with the USB serial connection. Wi-fi however works great..

I'm using this config for USB and Wi-Fi alternatives:

EBUSD_OPTS="--scanconfig --device=ens:/dev/ttyACM0 -c /etc/ebusd --latency=0"
#BUSD_OPTS="--scanconfig --device=ens:192.168.0.161:9999 -c /etc/ebusd --latency=10"

What I find is that when using Wi-Fi everything works great, scanning happens quickly and the config files are determined just as quickly. Also, when reading values via 'ebusctl' I don't see errors.

But, when using the USB connection I get numerous errors and scanning takes a long time (and sometimes doesn't succeed). Also, once csv's files are determined 60% (or more) of reads fail. I've switched the USB cable but observed the same. I also updated the firmware with no luck.

What debugging can I do to try to understand the cause of these errors and mitigate them?

The errors I see are as follows:

2023-09-01 12:19:15.755 [main debug] performing regular tasks
2023-09-01 12:19:15.755 [bus info] scan 05 cmd: 3105070400
2023-09-01 12:19:15.768 [bus debug] start request 31
2023-09-01 12:19:15.768 [bus debug] arbitration start with 31
2023-09-01 12:19:15.816 [bus debug] arbitration won
2023-09-01 12:19:15.816 [bus debug] arbitration delay 4 micros
2023-09-01 12:19:15.816 [bus info] arbitration delay 4 - 4 micros
2023-09-01 12:19:15.816 [bus debug] switching from ready to send command
2023-09-01 12:19:15.846 [bus debug] notify request: ERR: read timeout
2023-09-01 12:19:15.846 [main error] scan config 05: ERR: read timeout
2023-09-01 12:19:15.846 [bus debug] ERR: read timeout during send command, switching to skip

If I increase the --latency to 50ms I no longer see read timeouts but instead get:

2023-09-01 12:28:23.694 [bus debug] start request 31
2023-09-01 12:28:23.694 [bus debug] arbitration start with 31
2023-09-01 12:28:24.093 [bus debug] arbitration won
2023-09-01 12:28:24.093 [bus debug] arbitration delay 3 micros
2023-09-01 12:28:24.093 [bus debug] switching from ready to send command
2023-09-01 12:28:24.136 [bus debug] notify request: ERR: SYN received
2023-09-01 12:28:24.136 [bus debug] ERR: SYN received during send command, switching to ready
2023-09-01 12:28:24.136 [bus error] send to 15: ERR: SYN received, retry
2023-09-01 12:28:24.180 [bus debug] start request 31
2023-09-01 12:28:24.180 [bus debug] arbitration start with 31
2023-09-01 12:28:24.228 [bus debug] arbitration won
2023-09-01 12:28:24.229 [bus debug] arbitration delay 5 micros
2023-09-01 12:28:24.229 [bus debug] switching from ready to send command
2023-09-01 12:28:24.272 [bus debug] notify request: ERR: SYN received
2023-09-01 12:28:24.272 [bus debug] ERR: SYN received during send command, switching to ready
2023-09-01 12:28:24.272 [bus error] send to 15: ERR: SYN received
2023-09-01 12:28:24.272 [bus error] send message part 0: ERR: SYN received
2023-09-01 12:28:24.272 [main debug] <<< ERR: SYN received

Try to connect Revovair 260
Adapter ist Version 5

Only Blue and Green LED is on, red LED no activity. Also try to change Cable and firmware of Adapter

easi:
ebusd connected: yes (inactive)
eBUS signal: acquired

Ebusd:

ebusctl info
version: ebusd 23.2.23.2
update check: OK
device: 10.0.20.245:9999, enhanced, firmware 1.1[3501].1[3501]
access: *
signal: acquired
symbol rate: 23
max symbol rate: 32
scan: finished
reconnects: 2
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 04: slave #25, ebusd
address ff: master #25, ebusd

I managed to connect the ebusd and my Ariston Genus One heater (Ariston Genus One + Cube S Net + RPi4B + HAOS + eBUSd addon + ariston.csv provided by komw) and it creates entities that show parameters of the heater as sensors provided by the MQTT integration. My issue is how do I change parameters, like setting temperatures for example.

Hello,
I have installed, compiled and done everything from the "Build and install" manual.
At least, I get the Message "Failed to enable unit: Unit file ebusd.service does not exist." when I try to start the ebusd-service with
sudo systemctl enable ebusd
and
sudo service ebusd start
Greetings
Christoph

Currently I have an eBUS Adapter 2 connected to a Pi Zero.

Would it be possible to use the eBUS Adapter Shield v5 firmware on a generic ESP32-C3 (e.g. ESP32-C3 SuperMini from eBay) when connecting I/O 7 and 10 to an eBus Adapter 2?

I already have an adapter shield v5 on a seperate setup which seems to behave better than the PI+Adapter2 setup.

Hello,
this is a follow up for
#32 and john30/ebusd#1117

I own 2 adapter v5, both connected via USB to a raspberry pi 3B running raspbian. I tried connecting them to my Vaillant Recovair 260/4 and my Vaillant Auro Compact but I always get a no signal. Both run the latest firmware (2024-01-06) and I tried the latest host ebusd and docker version.

In Issue #32 it was implied that the ebus signal can be aquired after initializing the ebus adapter via the web interface and selecting USB input there. I tried these steps and was able to aquire a signal from both Vaillant devices!

I am getting the feeling that this is how it is supposed to work but honestly, I was expecting ebusd to support a direct USB connection out of the box. (Especially since /dev/ttyACM0 shows up right away). If this is the intended behavior, can you add the info that only 1 connection type is supported at a time and this needs to be configured first?

Log output from a freshly flashed (erased) adapter:

sudo ebusd -f --scanconfig=full --device=ens:/dev/ttyACM0 --lograwdata=bytes --log=all:debug --log=network:info
2024-01-20 15:34:17.897 [main info] configPath URL is valid
2024-01-20 15:34:17.899 [bus notice] device status: transport opened
2024-01-20 15:34:17.900 [main info] registering data handlers
2024-01-20 15:34:17.900 [main info] registered data handlers
2024-01-20 15:34:17.900 [main notice] ebusd 23.3.23.3 started with full scan on device: /dev/ttyACM0, serial high speed, enhanced
2024-01-20 15:34:17.900 [main info] loading configuration files from https://cfg.ebusd.eu/
2024-01-20 15:34:18.015 [main info] reading templates /
2024-01-20 15:34:18.131 [main info] read templates in /
2024-01-20 15:34:18.131 [main info] reading file broadcast.csv
2024-01-20 15:34:18.249 [main info] successfully read file broadcast.csv
2024-01-20 15:34:18.249 [main info] reading file memory.csv
2024-01-20 15:34:18.366 [main info] successfully read file memory.csv
2024-01-20 15:34:18.366 [main info] read config files, got 11 messages
2024-01-20 15:34:18.367 [bus notice] bus started with own address 31/36
2024-01-20 15:34:18.367 [bus notice] <73
2024-01-20 15:34:18.367 [bus notice] signal acquired
2024-01-20 15:34:18.367 [bus notice] <65
2024-01-20 15:34:18.368 [bus notice] <72
2024-01-20 15:34:18.368 [bus notice] <76
2024-01-20 15:34:18.368 [bus notice] <65
2024-01-20 15:34:18.368 [bus notice] <72
2024-01-20 15:34:18.368 [bus notice] <20
2024-01-20 15:34:18.368 [bus notice] <73
2024-01-20 15:34:18.368 [bus notice] <74
2024-01-20 15:34:18.368 [bus notice] <61
2024-01-20 15:34:18.368 [bus notice] <72
2024-01-20 15:34:18.368 [bus notice] <74
2024-01-20 15:34:18.368 [bus notice] <65
2024-01-20 15:34:18.368 [bus notice] <64
2024-01-20 15:34:18.368 [bus notice] <0d
2024-01-20 15:34:18.368 [bus notice] <0a
2024-01-20 15:34:18.368 [bus notice] <65
2024-01-20 15:34:18.368 [bus notice] <61
2024-01-20 15:34:18.368 [bus notice] <73
2024-01-20 15:34:18.368 [bus notice] <69
2024-01-20 15:34:18.368 [bus notice] <3e
2024-01-20 15:34:18.368 [bus notice] <20
2024-01-20 15:34:18.368 [bus notice] <0d
2024-01-20 15:34:18.368 [bus notice] <0a
2024-01-20 15:34:18.368 [bus notice] <65
2024-01-20 15:34:18.368 [bus notice] <61
2024-01-20 15:34:18.368 [bus notice] <73
2024-01-20 15:34:18.368 [bus notice] <69
2024-01-20 15:34:18.368 [bus notice] <3e
2024-01-20 15:34:18.368 [bus notice] <20
2024-01-20 15:34:18.368 [bus notice] <0d
2024-01-20 15:34:18.368 [bus notice] <0a
2024-01-20 15:34:18.369 [bus notice] <65
2024-01-20 15:34:18.369 [bus notice] <61
2024-01-20 15:34:18.369 [bus notice] <73
2024-01-20 15:34:18.369 [bus notice] <69
2024-01-20 15:34:18.369 [bus notice] <3e
2024-01-20 15:34:18.369 [bus notice] <20
2024-01-20 15:34:18.369 [bus notice] <0d
2024-01-20 15:34:18.369 [bus notice] <0a
2024-01-20 15:34:18.369 [bus notice] <65
2024-01-20 15:34:18.369 [bus notice] <61
2024-01-20 15:34:18.369 [bus notice] <73
2024-01-20 15:34:18.369 [bus notice] <69
2024-01-20 15:34:18.369 [bus notice] <3e
2024-01-20 15:34:18.369 [bus notice] device status: reset, supports info
2024-01-20 15:34:20.029 [bus debug] ERR: read timeout during skip, switching to no signal
2024-01-20 15:34:20.029 [bus error] signal lost
2024-01-20 15:34:28.369 [main debug] performing regular tasks
2024-01-20 15:34:38.369 [main debug] performing regular tasks

ebusctl:

localhost: info
version: ebusd 23.3.23.3
device: /dev/ttyACM0, serial high speed, enhanced
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

After selecting USB from the web interface and rebooting:

sudo ebusd -f --scanconfig=full --device=ens:/dev/ttyACM0 --lograwdata=bytes --log=all:debug --log=network:info
2024-01-20 15:37:29.354 [main info] configPath URL is valid
2024-01-20 15:37:29.355 [bus notice] device status: transport opened
2024-01-20 15:37:29.355 [main info] registering data handlers
2024-01-20 15:37:29.355 [main info] registered data handlers
2024-01-20 15:37:29.355 [main notice] ebusd 23.3.23.3 started with full scan on device: /dev/ttyACM0, serial high speed, enhanced
2024-01-20 15:37:29.356 [main info] loading configuration files from https://cfg.ebusd.eu/
2024-01-20 15:37:29.470 [main info] reading templates /
2024-01-20 15:37:29.588 [main info] read templates in /
2024-01-20 15:37:29.588 [main info] reading file broadcast.csv
2024-01-20 15:37:29.706 [main info] successfully read file broadcast.csv
2024-01-20 15:37:29.706 [main info] reading file memory.csv
2024-01-20 15:37:29.823 [main info] successfully read file memory.csv
2024-01-20 15:37:29.823 [main info] read config files, got 11 messages
2024-01-20 15:37:29.824 [bus notice] bus started with own address 31/36
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] signal acquired
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.824 [bus notice] <aa
2024-01-20 15:37:29.825 [bus notice] <aa
2024-01-20 15:37:29.825 [bus notice] <aa
2024-01-20 15:37:29.825 [bus notice] <aa
2024-01-20 15:37:29.865 [bus notice] <aa
2024-01-20 15:37:29.908 [bus notice] <aa
2024-01-20 15:37:29.950 [bus notice] <aa
2024-01-20 15:37:29.993 [bus notice] <aa
2024-01-20 15:37:30.003 [bus notice] device status: reset, supports info
2024-01-20 15:37:30.036 [bus notice] <aa
2024-01-20 15:37:30.080 [bus notice] <aa
2024-01-20 15:37:30.103 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x03
2024-01-20 15:37:30.122 [bus notice] <aa
2024-01-20 15:37:30.165 [bus notice] <aa
2024-01-20 15:37:30.207 [bus notice] <aa
2024-01-20 15:37:30.250 [bus notice] <aa
2024-01-20 15:37:30.293 [bus notice] <aa
2024-01-20 15:37:30.335 [bus notice] <aa
2024-01-20 15:37:30.379 [bus notice] <aa
2024-01-20 15:37:30.422 [bus notice] <aa
2024-01-20 15:37:30.464 [bus notice] <aa

ebusctl
localhost: info
version: ebusd 23.3.23.3
device: /dev/ttyACM0, serial high speed, enhanced, firmware 1.1[4106].1[4106]
signal: acquired
symbol rate: 8
max symbol rate: 29
min arbitration micros: 5
max arbitration micros: 23
min symbol latency: 4
max symbol latency: 5
scan: finished, some messages pending
reconnects: 0
masters: 2
messages: 12
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=recoV;SW=0229;HW=0203"
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning

Hello @john30,

First, thank you for this amazing device 👍

When I start the V5 adapter, the wifi is both in AP mode and in client mode.

At the startup time, I can access the web client through its client address.
About two minutes after, the web client becomes unresponsive.
I have to wait for approximately 10 minutes in order to have things become responsive again. At this time, the startup AP mode is reported as inactive.

The only thing I can imagine is some side effect of the default AP automatic disablement on the wifi client mode.

I'd really like to have a parameter to disable the AP mode at startup : keep it simply stupid :)
If I'm lost, I can come back to USB wire to take back control.
Moreover, it is a security hole at every startup (including after a power outage).

I've tried "ap --store --off", but it does not seem to work.

Thanks for reading !

In the previous version (15.8.23) there was a problem with accepting the the configuration of the web interface (WIFI station/client & credentials). The values includes were ignored.
With the new version (3.9.23) the behaviour is changed:

• the original configured data are active
• the fields in the configuration area are empty
• I've set the values again and tried to save it, but the box to enter password and credentials is only active for 5s
  Mostly I was to slow to enter password and credentials...
  One times I was quick enough and have changed the WIFI station/client values. At next request the values were listed, but password and credentials were deleted.
  Now I've set password and credentials again and save the changes. Next connection works, but the credentials will not be requested entering the configuration page. After power off cycle the adapter was not possible to reach again...

Hi John,

Thanks for the adapter. Looking forward to use it. For some reason I just can't connect the adapter to ebusd.

/var/log/ebusd.log is saying:
2023-07-22 12:08:58.722 [main notice] ebusd 3.0.595c7c0 started
2023-07-22 12:08:58.722 [main error] error reading config files: ERR: element not found, last error:
2023-07-22 12:08:58.722 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:08:58.723 [bus notice] bus started with own address 31/36
2023-07-22 12:09:08.723 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:09:18.723 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:09:28.723 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:09:38.724 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:09:48.724 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:09:58.724 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:08.724 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:18.724 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:28.725 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:38.725 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:48.725 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:10:58.726 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:11:08.726 [bus error] unable to open ens:/dev/ttyACM0: ERR: element not found
2023-07-22 12:11:08.832 [main error] update check error: 301 Moved Permanently

/etc/default/ebusd:
EBUSD_OPTS="--scanconfig -d ens:/dev/ttyACM0"

ls -la /dev/ttyACM0 retuns:
crw-rw---- 1 root dialout 166, 0 Jul 22 12:17 /dev/ttyACM0

Any idea? Thanks
Thilo

Hello,
my ebus adapter is online, but i can not run the docker image, get the following error message:

pi@raspberrypi:~ $ docker run -it --rm -p 8888 john30/ebusd --scanconfig --device=192.168.178.46:9999
1931-02-09 00:12:53.034 [network error] HTTP connect: 337047686=certificate verify failed
1931-02-09 00:12:53.034 [network error] HTTP new_ssl_conn: 336462231=shutdown while in init
1931-01-28 10:33:20.-1097 [main error] invalid configPath URL (connect)

Thank you very mush

Hi,

I'm trying to figure out if it's possible to have some basic authentication configured, so that I can prevent random people on my network from being able to connect to the adapter with ebusd and potentially mess with my heating device. Can I do that or do I need to run a separate tight WiFi network just for my ebus adapter?

Thanks!

Hi,
I'm using the standard options:
EBUSD_OPTS="--scanconfig -d ens:/dev/ttyACM0"

pi@raspberrypi:~ $ ebusctl i
version: ebusd 23.2.23.2
update check: invalid request
device: /dev/ttyACM0, enhanced high speed, firmware 1.1[3612].1[3612]
signal: acquired
symbol rate: 50
max symbol rate: 78
min arbitration micros: 16
max arbitration micros: 24
min symbol latency: 4
max symbol latency: 8
scan: finished
reconnects: 0
masters: 6
messages: 16
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11, scanned "MF=Kromschroeder;ID= 3B ;SW=" error: ERR: argument value out of valid range
address 10: master #2
address 15: slave #2, scanned "MF=Kromschroeder;ID= ;SW=0204;HW=-"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Kromschroeder;ID= ;SW=0204;HW=-"
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Kromschroeder;ID= ;SW=0227;HW=-"
address f1: master #10
address f6: slave #10, scanned "MF=Kromschroeder;ID= ;SW=0204;HW=-"

To me it seems, that data is received but it can't be interpreted. Sorry if it's a stupid question, but did I miss something in the configuration?
Thanks
Thilo

Hello,
I've started the ebusd-deamon with the following options:
EBUSD_OPTS="--device=IP-ADRESSE:9999 --scanconfig --configpath=/home/pi/ebusd-configuration/ebusd-2.1.x/de/ --receivetimeout=100000 --latency=50"
The command ebusctl i brings the following result:
version: ebusd 22.4.v22.4
update check: version 23.2 available
device: 192.168.0.112:9999
signal: acquired
symbol rate: 46
max symbol rate: 139
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd
and the Log-File-entry is:
2023-10-02 18:57:49.859 [main notice] ebusd 22.4.v22.4 started with auto scan on device IP-Adress:9999
2023-10-02 18:57:49.898 [bus notice] bus started with own address 31/36
2023-10-02 18:57:49.914 [bus notice] signal acquired
2023-10-02 18:58:09.036 [bus notice] max. symbols per second: 108
2023-10-02 18:58:39.005 [bus notice] max. symbols per second: 112
2023-10-02 18:58:40.025 [bus notice] max. symbols per second: 114
2023-10-02 18:59:40.005 [bus notice] max. symbols per second: 115
2023-10-02 18:59:56.518 [main notice] update check: version 23.2 available
2023-10-02 19:00:40.005 [bus notice] max. symbols per second: 119
2023-10-02 19:01:41.036 [bus notice] max. symbols per second: 131
2023-10-02 19:02:41.007 [bus notice] max. symbols per second: 137

No further Master oder Slaves where found

The WIFI-Signal is 100%. The Ebus-Line ist less than 1 meter

Greetings
Christoph

Hello!
I just installed the new adapter v5 to my Saunier Duval Genia Set 8 and it works well connected via TCP with ens protocol to a raspberry pi zero which is running the version 22.4 of the ebusd program.

The only "weird" thing is that I get the error my_client_socket_send: send: errno 11 in the adapater's log every one minute (more or less)

According with this other message john30/ebusd#921 apparently it could be that the WIFI signal is not good enough or the "queue is full"

Well, the wifi signal is stable in -74dBm

Do you consider that is a poor signal?

On the other hand, is there any way to know if the "queue is full"? just to discard things.

And finally, could the error be dangerous for the machine? Should I avoid use it until I resolver the problem?

Thanks in advance

Moved from john30/ebusd#1081 to this place as it's not an ebusd issue.

I added the proposed ethernet adapter W5500 to the Ebus Adapter V5 as described. Ethernet port shows link and other LED is flashing when network traffic is recieved/transmitted.

However, the Ethernet Module is not loaded during startup:

17:34:49Info execute: isio -l 9
17:34:49 IO 9 level 1 is unmet
17:34:49 Info execute: io -iu 6
17:34:49 IO 6 direction set to 01
17:34:49 IO 6 pull set to 00
17:34:49 IO 6 = 1
17:34:49 Info execute: var rpi 0
17:34:49 Info execute: if "isio -l 6" "var rpi 1"
17:34:49 Info execute: isio -l 6
17:34:49 IO 6 level 1 is unmet
17:34:49 Info execute: var isnew 1
17:34:49 Info execute: if "§isnvs ebus.host" "var isnew 0"
17:34:49 Info execute: isnvs ebus.host
17:34:49 Info execute: var isnew 0
17:34:49 Info execute: if "§isnvs sta.on" "var isnew 0"
17:34:49 Info execute: isnvs sta.on
17:34:49 Info execute: var isnew 0
17:34:49 Info execute: if "§isnvs eth.on" "var isnew 0"
17:34:49 Info execute: isnvs eth.on
17:34:49 Warning execute: command failed: isnvs eth.on = 1
17:34:49 Info execute: on -lo iol 9 "led 0 255" "led 1 255" "led 2 255" "sleep 500" restart
17:34:49 io trigger installed
17:34:49 Info execute: on iol 9 "led 2 50 0"
17:34:49 io trigger installed
17:34:49 Info execute: if "var skipstart" "led 0 255 0 5000" "led 2 50" "ap EBUS" server exit
17:34:49 Info execute: var skipstart
17:34:49 variable skipstart = 0
17:34:49 Info execute: function start server "led 0 10"
17:34:49 function installed
17:34:49 Info execute: on wifi 1 start
17:34:49 network trigger installed
17:34:49 Info execute: on eth 1 start
17:34:49 network trigger installed
17:34:49 Info execute: if "isnvs sta.on" "led 0 10 255 5000" "sleep 100" sta
17:34:49 Info execute: isnvs sta.on
17:34:49 Info execute: led 0 10 255 5000
17:34:49 Info execute: sleep 100
17:34:49 Info statusLedTimerFn: duty set to 10
17:34:49 Info execute: sta
17:34:49 Info pp: pp rom version: 9387209
17:34:49 Info net80211: net80211 rom version: 9387209
17:34:49 Info wifi_init: tcpip mbox: 32
17:34:49 Info wifi_init: udp mbox: 6
17:34:49 Info wifi_init: tcp mbox: 6
17:34:49 Info wifi_init: tcp tx win: 5744
17:34:49 Info wifi_init: tcp rx win: 5744
17:34:49 Info wifi_init: tcp mss: 1440
17:34:49 Info wifi_init: WiFi IRAM OP enabled
17:34:49 Info wifi_init: WiFi RX IRAM OP enabled
17:34:49 Info wifi_init: LWIP IRAM OP enabled
17:34:49 Info phy_init: phy_version 1130,b4e4b80,Sep 5 2023,11:09:30
17:34:49 sta connecting to 'IoT'
17:34:52 Info cmd_wifi: sta connect
17:34:53 Info esp_netif_handlers: sta ip: 192.168.42.143, mask: 255.255.255.0, gw: 192.168.42.1
17:34:53 Info cmd_wifi: sta got ip
17:34:53 Info repl_event_task: wifi event: 1
17:34:53 Info execute: led 0 50
17:34:53 Info execute: start
17:34:53 Info execute: server
17:34:53 Info esp-rest: Starting HTTP Server
17:34:53 server started
17:34:53 Info execute: led 0 10
17:34:53 Info execute: if "var isnew" "ap EBUS" else "if "isnvs ap.on" ap"
17:34:53 Info execute: var isnew
17:34:53 variable isnew = 0
17:34:53 Info execute: if "isnvs ap.on" ap
17:34:53 Info execute: isnvs ap.on
17:34:53 Info execute: var eth 0
17:34:53 Info execute: if "eth -t" "var eth 1" else "if "eth -wt" "var eth 2""
17:34:53 Info execute: eth -t
17:34:53 Error w5500.mac: W5500 version mismatched, expected 0x04, got 0x00
17:34:53 Error w5500.mac: emac_w5500_init(795): vefiry chip ID failed
17:34:53 Error esp_eth: esp_eth_driver_install(228): init mac failed
17:34:53 Error eth: initialise_ethernet(250): install driver
17:34:53 Ethernet on USR-ES1 not available
17:34:53 Warning execute: command failed: eth -t = 1
17:34:53 Info execute: if "eth -wt" "var eth 2"
17:34:53 Info execute: eth -wt
17:34:53 Error w5500.mac: W5500 version mismatched, expected 0x04, got 0x00
17:34:53 Error w5500.mac: emac_w5500_init(795): vefiry chip ID failed
17:34:53 Error esp_eth: esp_eth_driver_install(228): init mac failed
17:34:53 Error eth: initialise_ethernet(250): install driver
17:34:53 Ethernet on W5500 module not available
17:34:53 Warning execute: command failed: eth -wt = 1

Hi!
Ich habe jetzt meinen neuen eBUS Adapter angeschlossen. Ich habe das Home Assistant Addon getestet und und in einer Debian VM.

Ich erhalte diesen Fehler:
2023-10-05 21:00:28.073 [update notice] received unknown MS cmd: 1008b5110102 / 06033c96468278 2023-10-05 21:00:35.648 [bus notice] scan 08: ;Vaillant;BAI00;0807;7603 2023-10-05 21:00:35.648 [update notice] store 08 ident: done 2023-10-05 21:00:35.648 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0807;7603 2023-10-05 21:00:35.648 [bus notice] scan 08: ;Vaillant;BAI00;0807;7603 2023-10-05 21:00:36.164 [main notice] read common config file vaillant/broadcast.csv 2023-10-05 21:00:36.288 [main notice] read common config file vaillant/scan.csv 2023-10-05 21:00:36.412 [main notice] read common config file vaillant/general.csv 2023-10-05 21:00:36.536 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0807, HW7603 2023-10-05 21:00:36.783 [update notice] sent scan-read scan.08 id QQ=31: 2023-10-05 21:00:37.065 [update notice] sent scan-read scan.08 id QQ=31: 2023-10-05 21:00:37.397 [bus error] send to 08: ERR: read timeout, retry 2023-10-05 21:00:38.272 [bus error] send to 08: ERR: SYN received, retry 2023-10-05 21:00:38.346 [bus error] device status: eBUS comm error: overrun 2023-10-05 21:00:38.353 [bus error] arbitration start error 2023-10-05 21:00:38.368 [update notice] received unknown MS cmd: 1008b5100900002dffffff040000 / 0101 2023-10-05 21:00:38.392 [bus error] send to 08: ERR: SYN received 2023-10-05 21:00:38.392 [bus error] send message part 2: ERR: SYN received 2023-10-05 21:00:38.392 [main error] error reading message scan.08 id: ERR: SYN received 2023-10-05 21:00:38.614 [update notice] sent scan-read scan.08 id QQ=31: 2023-10-05 21:00:38.886 [update notice] sent scan-read scan.08 id QQ=31: 2023-10-05 21:00:39.172 [update notice] sent scan-read scan.08 id QQ=31: 2023-10-05 21:00:39.342 [bus error] device status: eBUS comm error: overrun 2023-10-05 21:00:39.444 [update notice] sent scan-read scan.08 id QQ=31: 21;22;44;0010022010;0001;017235;N0 2023-10-05 21:00:39.818 [main notice] found messages: 224 (3 conditional on 28 conditions, 0 poll, 10 update) 2023-10-05 21:00:40.117 [update notice] sent scan-read scan.08 id QQ=31: 21;22;44;0010022010;0001;017235;N0 2023-10-05 21:00:40.403 [update notice] sent scan-read scan.08 id QQ=31: 21;22;44;0010022010;0001;017235;N0 2023-10-05 21:00:40.676 [update notice] sent scan-read scan.08 id QQ=31: 21;22;44;0010022010;0001;017235;N0 2023-10-05 21:00:42.065 [update notice] sent poll-read bai CounterStartattempts1 QQ=31: 0 2023-10-05 21:00:43.050 [bus notice] scan 15: ;Vaillant;CTLV3;0612;3004 2023-10-05 21:00:43.050 [update notice] store 15 ident: done 2023-10-05 21:00:43.050 [update notice] sent scan-read scan.15 QQ=31: Vaillant;CTLV3;0612;3004 2023-10-05 21:00:43.050 [bus notice] scan 15: ;Vaillant;CTLV3;0612;3004 2023-10-05 21:00:43.345 [update notice] sent unknown MS cmd: 3115b5090124 / 09003231323233323030 2023-10-05 21:00:43.602 [update notice] sent scan-read scan.15 id QQ=31: 2023-10-05 21:00:43.881 [update notice] sent scan-read scan.15 id QQ=31: 2023-10-05 21:00:44.153 [update notice] sent scan-read scan.15 id QQ=31: 21;22;32;0010045485;0953;011543;N1 2023-10-05 21:00:44.153 [bus notice] scan 15: ;21;22;32;0010045485;0953;011543;N1 2023-10-05 21:00:44.277 [main error] unable to load scan config 15: no file from vaillant with prefix 15 matches ID "ctlv3", SW0612, HW3004 2023-10-05 21:00:44.277 [main error] scan config 15: ERR: element not found 2023-10-05 21:00:47.285 [update notice] sent poll-read bai CounterStartattempts2 QQ=31: 0 2023-10-05 21:00:47.581 [update notice] received poll-read bai Status01 QQ=10: 25.0;25.0;-;29.0;-;off 2023-10-05 21:00:47.861 [update notice] received update-write bai SetMode QQ=10: auto;22.5;-;-;0;0;1;0;0;0 2023-10-05 21:00:53.499 [bus error] poll bai CounterStartAttempts3 failed: ERR: SYN received 2023-10-05 21:00:53.914 [bus notice] arbitration won in invalid state ready

Ich sehe einige Temperaturen, aber ich kann nichts einstellen/ändern.

Wo und wie kann ich die richtige Config File einstellen?

Ich habe die Vaillant ecoTEC plus VC/VCW/VCI 1 mit dem VRT380.

scan id = no data stored scan.08 = Vaillant;BAI00;0807;7603 scan.08 id = 21;22;44;0010022010;0001;017235;N0 scan.15 = Vaillant;CTLV3;0612;3004 scan.15 id = 21;22;32;0010045485;0953;011543;N1

Betreibe den kürzlich bestellten ebus adapter 5 per USB an einer Raspberry Pi 4 mit Homematic Funkmodul und ConBee 2 USB Sender um Daten aus einer Vaillant WP auszulesen. Das Auslesen scheint auch ganz gut zu klappen aber sobald ich den Adapter anstecke stört er dermaßen das von Homematic verwendete Frequenzband (868MHz), dass das gesamte HomeMatic Funknetz ausfällt und HM Geräte resettet werden müssen. das WLAN Modul ausschalten hat leider auch nichts gebracht. Ist dieses Problem bekannt und wenn ja, gibt es irgendeine Möglichkeit, das Störsignal auszuschalten? Ich verdächtige das WLAN Modul aber das war eigentlich auch das erste, was ich ausgeschaltet habe. Habe auch schon verschiedene Aufstellorte im Haus ausprobiert. Bin für jeden Hinweis dankbar, denn so lässt sich der Adapter bei mir leider nicht einsetzen.

VG

Hallo,
nach der Konfigurationsänderung im Adapter (Host-Verbindung auf USB eingestellt) und Reboot via Webbrowser, wird der WIFI Access Point “EBUS” nicht mehr angezeigt. Ist das normal?
Nach dem erneuten Flashen der Firmware ist der AP wieder sichtbar.

eBUS Adapter 5, Version 2023-10-15

What will show on OLED 0.66 Shield?

Hi
Is any chance to implement to this version option update FW by WebUI (not by wire) ?

Hallo John

Ich habe vor einer Woche meinen Adapter v5 erhalten.
Vielen Dank dafür. Ist ein gut gelungener Adapter.

Um ihn zu testen und erste Erfahrungen zu sammeln habe ich ihn per WLAN mit dem eBUSd verbunden.
Dies lief alles gut und ich konnte den Adapter ohne weitere Probleme konfigurieren und einrichten.

Nun habe ich die Zeit gefunden um mir ein BUS Kabel zu meinem Home Assistant zu legen.

Als ich mein Adapter aber nun auf USB Seriell umstellen wollte endete es in einem Bootloop.
Ich habe beide Firmware ausprobiert. Mit WLAN funktioniert alles ohne Problem und mit USB funktioniert nichts mehr.
Ich muss anschliessend immer die Firmware neu flashen um überhaupt wider auf den Adapter zuzugreifen.

Was kann ich da machen? Was ist hier das Problem? Ist der Adapter defekt?

Hier noch der Log während dem Bootloop:
esp-web-tools-logs.txt

Vielen Dank für die Unterstützung.

Welcher PIN ist + und welcher - bei dem eBus Stecker?
In der Grafik fehlt diese Beschriftung. In der Doku habe ich auch nichts gefunden.
Ich frage lieber vorher :-)

Ich habe heute die HW bekommen und versucht zu konfigurieren. Die Standardadresse für das Webinterface habe ich so umgestellt, dass der ebus-Adapter sich in meinem existierendes WLAN anmeldet und dabei eine fixe IP hat. Zunächst konnte ich über diese IP nicht mit einem Browser zugreifen.
Wenn ich allerdings im seriellen Interface (via USB) den Befehl 'sta' ohne Parameter eingebe, ist die IP über den Browser (http, Port 80) erreichbar.

1. Allerdings wird für den Zugriff von Konfiguration und Log ein Benutzername und Passwort verlangt, auch wenn ich die Felder bei der Konfiguration leergelassen habe.
2. Nach einem Reboot ist die IP wieder nicht erreichbar, bis ich wieder über die 'serielle' Schnittstelle 'sta' eingebe.
3. Häufig kommt bei dem Webinterface häufig deiFehlermeldung "API retrieval failed for /status: timeout"

Was mache ich falsch?

Günter

Hello! I recently bought an ESP32 based ebusd adapter and have difficulty setting it up. My aim is to use it with Home Assistant (RPi 4B 8Gb) and an Ariston Genus One + Cube S Net. Si far I completed the following:

1. I connected the adapter to power and the ebus connection between the heater and the Cube S Net
2. I configured the WiFi and the IP settings on the adapter with TCP and enh protocol
3. I installed the eBUSd addon in Home Assistant and configured the port and ip settings
4. I placed a file called ariston.csv in the /config folder. The file was downloaded from https://github.com/komw/ariston-bus-bridgenet-ebusd
5. I set the configuration folder as /config

From what I understand from the logs, the addon connects to the adapter and two devices (ebusd and ebusd eBUS device) are created in home assistant. The problem is that no entities that relate to device sensors or options are created and at the same time it seems that most of the cmd messages are unknown.

The addon configuration is the following:

scanconfig: true
loglevel_all: notice
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
network_device: 192.168.1.95:9999
mode: enh
configpath: /config

Logs from addon:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=ohpeich6eipahngaequaijaiwithiekiephi8phahshi6aidaXo2bai4ol4eegah --scanconfig --mqttjson --configpath=/config --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=enh:192.168.1.95:9999 --log=all:notice
2023-12-18 20:15:18.726 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.1.95:9999, enhanced
2023-12-18 20:15:18.830 [bus notice] device status: resetting
2023-12-18 20:15:18.830 [bus notice] bus started with own address 31/36
2023-12-18 20:15:18.927 [bus notice] signal acquired
2023-12-18 20:15:18.986 [bus notice] new master 37, master count 2
2023-12-18 20:15:18.986 [update notice] received unknown BC cmd: 37fe2000020120
2023-12-18 20:15:19.026 [update notice] received unknown BC cmd: 37fe200f0401200100
2023-12-18 20:15:19.184 [update notice] received unknown BC cmd: 37fe201010c04b0200091901000a1901000b190000
2023-12-18 20:15:19.223 [bus notice] new master 7f, master count 3
2023-12-18 20:15:19.223 [update notice] received unknown BC cmd: 7ffe2001026226
2023-12-18 20:15:19.242 [mqtt notice] connection established
2023-12-18 20:15:19.322 [update notice] received unknown BC cmd: 37fe200e08622664006400e001
2023-12-18 20:15:19.385 [update notice] received unknown BC cmd: 7ffe2020030b9000
2023-12-18 20:15:19.506 [update notice] received unknown BC cmd: 37fe2010100c1900000d1900000e19000001910100
2023-12-18 20:15:19.580 [update notice] received unknown BC cmd: 7ffe207309000000000000000003
2023-12-18 20:15:19.736 [update notice] received unknown BC cmd: 37fe20101002910000039100000491000005910000
2023-12-18 20:15:19.747 [bus notice] new master 70, master count 4
2023-12-18 20:15:19.777 [update notice] received unknown MS cmd: 703c2000040e11d140 / 0303010b
2023-12-18 20:15:19.824 [bus notice] device status: reset, supports info
2023-12-18 20:15:19.872 [update notice] received unknown BC cmd: 37fe20100406910000
2023-12-18 20:15:19.935 [update notice] received unknown MS cmd: 7f3c20000475470e11 / 0403160001
2023-12-18 20:15:19.937 [bus notice] device status: extra info: firmware 1.1[3a0f].1[3a0f], jumpers 0x0f
2023-12-18 20:15:20.050 [update notice] received unknown MS cmd: 3784200006d140cc4bc89c / 0407010800
2023-12-18 20:15:20.086 [update notice] received unknown BC cmd: 7ffe2001026371
2023-12-18 20:15:20.179 [update notice] received unknown BC cmd: 37fe200e086371a00064002c01
2023-12-18 20:15:20.273 [update notice] received unknown BC cmd: 7ffe2001020120
2023-12-18 20:15:20.354 [update notice] received unknown BC cmd: 37fe200e050120010001
2023-12-18 20:15:20.453 [update notice] received unknown BC cmd: 37fe2000020220
2023-12-18 20:15:20.506 [update notice] received unknown BC cmd: 37fe200f0402200100
2023-12-18 20:15:20.594 [update notice] received unknown BC cmd: 7ffe2001020220
2023-12-18 20:15:20.678 [update notice] received unknown BC cmd: 37fe200e050220010001
2023-12-18 20:15:20.775 [update notice] received unknown BC cmd: 7ffe2001020f23
2023-12-18 20:15:20.850 [update notice] received unknown BC cmd: 37fe200e050f23000001
2023-12-18 20:15:20.950 [update notice] received unknown BC cmd: 7ffe2000027647
2023-12-18 20:15:21.004 [bus notice] max. symbols per second: 144
2023-12-18 20:15:21.045 [update notice] received unknown BC cmd: 37fe200f057647370000
2023-12-18 20:15:21.130 [update notice] received unknown BC cmd: 7ffe2001026471
2023-12-18 20:15:21.229 [update notice] received unknown BC cmd: 37fe200e08647174ff74ff8c00
2023-12-18 20:15:21.407 [update notice] received unknown BC cmd: 7ffe2001026271

Hello,

I notice that this repository is empty.
Is it on purpose that the source code is not released ?

Thanks

Hello people, I am having problems connecting the ebus adapter to Hassio.
I have been running the home assistant server on a raspberry pi and the web interface with the ebus adapter and the correct firmware is also up and running.
Only I have no idea how to get MQTT working now. I have been looking up the necessary information for a few days now, but I have no idea how to approach this now. Do I have to do something in the web interface of the ebus adapter or do I have to get started in hassio. anyone have any ideas?

Hi,
I've just unpacked the new adapter v5 hardware v.1.24, started a docker container but something goes wrong:

$ docker run --rm -it -p 8888 john30/ebusd --scanconfig -d ens:10.1.1.33:9999 --latency=20
2024-02-16 07:36:22.166 [bus notice] device status: transport opened
2024-02-16 07:36:22.166 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 10.1.1.33:9999, TCP, enhanced
2024-02-16 07:36:29.019 [network error] HTTP recv: timed out after 1 sec
2024-02-16 07:36:29.019 [main error] HTTP failure: receive error (headers)
2024-02-16 07:36:29.019 [main error] error reading config files from https://cfg.ebusd.eu/: ERR: element not found, last error:
2024-02-16 07:36:29.019 [bus notice] bus started with own address 31/36
2024-02-16 07:36:31.385 [bus error] device status: transport closed
2024-02-16 07:36:31.385 [bus notice] device invalid
2024-02-16 07:36:36.417 [bus notice] device status: transport opened
2024-02-16 07:36:36.417 [bus notice] re-opened 10.1.1.33:9999
2024-02-16 07:36:36.692 [bus notice] device status: reset, supports info
2024-02-16 07:36:36.804 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f
2024-02-16 07:37:01.013 [bus error] device status: transport closed
2024-02-16 07:37:01.013 [bus notice] device invalid
2024-02-16 07:37:06.052 [bus notice] device status: transport opened
2024-02-16 07:37:06.052 [bus notice] re-opened 10.1.1.33:9999
2024-02-16 07:37:06.696 [bus notice] device status: reset, supports info
2024-02-16 07:37:06.801 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f
2024-02-16 07:37:49.941 [bus error] device status: transport closed
2024-02-16 07:37:49.941 [bus notice] device invalid
2024-02-16 07:37:55.861 [bus error] device status: transport closed
2024-02-16 07:37:55.861 [bus notice] re-opened 10.1.1.33:9999
2024-02-16 07:37:55.861 [bus notice] device invalid
2024-02-16 07:38:00.862 [bus error] device status: transport closed
2024-02-16 07:38:00.862 [bus notice] re-opened 10.1.1.33:9999
2024-02-16 07:38:00.862 [bus notice] device invalid

I could reach https://cfg.ebusd.eu/ but seems that the adapter cannot, also firmware update test seems to fail, what can I do now?
Thanks, BR

I have a vaillant VRC700/6 controlling a VSC206/4-5 90 E.
I am using an eBus adapter shield version 5.

The problem: ebusd doesn't detect my vaillant devices correctly.
ebusctl info gives me:

version: ebusd 23.2.23.2-10-g76184c76
update check: revision 23.2 available
device: 192.168.34.5:9999
signal: acquired
symbol rate: 46
max symbol rate: 175
min arbitration micros: 12
max arbitration micros: 247
min symbol latency: 12
max symbol latency: 53
scan: finished
reconnects: 0
masters: 2
messages: 1
conditional: 0
poll: 0
update: 0
address 10: master #2
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning

Looking at the hex dump of the messages (ebusd-logfile), I see a lot of 'c6' even inserted in the maybe correct readouts of the bus messages:

2023-09-30 12:38:32.046 [bus notice] <c6
2023-09-30 12:38:32.088 [bus notice] <c6
2023-09-30 12:38:32.129 [bus notice] <c6
2023-09-30 12:38:32.178 [bus notice] <c6
2023-09-30 12:38:32.218 [bus notice] <c6
2023-09-30 12:38:32.310 [bus notice] <1008c6b5110101c68900094947c79010445600003bc7a800c6
2023-09-30 12:38:32.359 [bus notice] <c6
2023-09-30 12:38:32.399 [bus notice] <c6
2023-09-30 12:38:32.447 [bus notice] <c6
2023-09-30 12:38:32.489 [bus notice] <c6
2023-09-30 12:38:32.582 [bus notice] <1008c6b51009000000c7bfc7bfc7bf01000026000101c69a00c6
2023-09-30 12:38:32.630 [bus notice] <c6
2023-09-30 12:38:32.679 [bus notice] <c6

What could be the reason for not recognizing the vaillant hardware?

Günter

It looks like the ethernet module USR-ES1 is no longer recognized correctly. The webinterface is still accessible via ethernet but the ebus device string is only offered for USB.

With old version 2023-10-15 it works again.

Hallo, ich betreibe den v5 Adapter an einer Vaillant Wärmepumpe. Das Ganze ist via WIFI mit MQTT an HA angebunden. Funktionierte seit mehreren Wochen ganz gut.

Nach einem Stromausfall funktionierte der Adapter nicht mehr richtig. Bei einem:

ebusctl w -c hwc OperatingMode auto

kommt nur

ERR: SYN received

zurück. Vorher ging es ohne Probleme. (ebusctl w -c mc OperatingMode auto, funktioniert wie gehabt.)

Einmaliges Warmwasser funktioniert (zum Glück) noch.

ebusctl w -c hwc load on
done

Aber wie bekomme ich mein OperatingMode für hwc zurück? Wo fange ich mit der Fehlersuche an?

Ein paar Daten:

ebusctl

ebusctl find r | grep OperatingMode
hwc OperatingMode = no data stored
mc OperatingMode = on

ebusctl scan result
08;Vaillant;EHP00;0344;7201
15;Vaillant;UIH00;0226;6901
25;Vaillant;EHP00;0344;7201
50;Vaillant;EHP00;0344;7201

ebusctl info
version: ebusd 23.2.23.2
update check: OK, device firmware 1[3a0f] available
device: 10.30.0.70:9999, enhanced, firmware 1.8[0139].15[0139]
access: *
signal: acquired
symbol rate: 21
max symbol rate: 127
min arbitration micros: 0
max arbitration micros: 350
min symbol latency: 10
max symbol latency: 60
scan: finished
reconnects: 3
masters: 4
messages: 533
conditional: 194
poll: 96
update: 60
address 00: master #1
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/08.ehp.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=UIH00;SW=0226;HW=6901"
address 23: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/23.ehp.cc.csv"
address 25: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/25.ehp.hwc.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning
address 50: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/50.ehp.mc.csv"

ebusd-Log

2023-11-27 07:39:22.312 [update notice] received read ehp Status QQ=10: 36.38;1.889;0.000;heat;2c
2023-11-27 07:39:22.526 [update notice] received read ehp Status02 QQ=10: disabled;0;100.0;0;100.0
2023-11-27 07:39:22.935 [update notice] received write ehp EnergyBalancingRelease QQ=10: on
2023-11-27 07:39:24.401 [update notice] received poll-read hwc Mode QQ=10: 38;auto;disabled;hwc;00;4
2023-11-27 07:39:24.577 [update notice] received poll-read hwc Status QQ=10: 0;on;36.38;52
2023-11-27 07:39:25.181 [bus error] poll ehp DeltaTempT6T7 failed: ERR: wrong symbol received
2023-11-27 07:39:28.380 [update notice] received update-read broadcast hwcStatus QQ=10: off;36;off
2023-11-27 07:39:30.449 [update notice] received unknown MS cmd: 1025b505072b000100000000 / 00
2023-11-27 07:39:30.932 [update notice] received read ehp Status QQ=10: 36.19;1.893;0.000;heat;2c
2023-11-27 07:39:31.116 [update notice] received read ehp Status02 QQ=10: disabled;0;100.0;0;100.0
2023-11-27 07:39:32.180 [update notice] received read mc DateTime QQ=10: valid;08:39:32;27.11.2023;0.562
2023-11-27 07:39:32.190 [main error] scan config 05: ERR: SYN received
2023-11-27 07:39:32.757 [update notice] received write ehp EnergyBalancingRelease QQ=10: on
2023-11-27 07:39:34.473 [update notice] received poll-read cc Mode QQ=10: 23;auto;disabled;circulation;00;night
2023-11-27 07:39:34.614 [update notice] received poll-read cc Status QQ=10: 0;off;-;0
2023-11-27 07:39:34.788 [update notice] received update-read ehp FlowTemp QQ=10: 33.38;ok
2023-11-27 07:39:36.134 [bus error] poll ehp FlowtempCoolingMin failed: ERR: SYN received
2023-11-27 07:39:38.384 [update notice] received read ehp currenterror QQ=10: 580;-;-;-;-
2023-11-27 07:39:38.526 [update notice] received update-read broadcast hwcStatus QQ=10: off;36;off
2023-11-27 07:39:38.978 [update notice] received update-read ehp SourceTempInput QQ=10: 3.88;ok
2023-11-27 07:39:39.140 [update notice] received update-read ehp ActualEnvironmentPowerPercentage QQ=10: 100
2023-11-27 07:39:39.307 [update notice] received update-read ehp ActualEnvironmentPower QQ=10: 7
2023-11-27 07:39:40.443 [update notice] received unknown MS cmd: 1023b505072b000100000000 / 00
2023-11-27 07:39:41.028 [update notice] received read ehp Status QQ=10: 35.81;1.890;0.000;heat;2c
2023-11-27 07:39:42.315 [update notice] received read ehp Status02 QQ=10: disabled;0;100.0;0;100.0
2023-11-27 07:39:42.553 [update notice] received read ehp errorhistory QQ=10: 1;2;19:25;26.11.2023;580
2023-11-27 07:39:42.967 [update notice] received write ehp EnergyBalancingRelease QQ=10: on
2023-11-27 07:39:44.435 [update notice] received read mc Mode QQ=10: 20;on;0;0;disabled;pool;night
2023-11-27 07:39:44.602 [update notice] received read mc Status QQ=10: 30;off;33.31;20
2023-11-27 07:39:46.505 [update notice] received write mc RoomTempOffset QQ=10: 0.00
2023-11-27 07:39:47.176 [bus error] poll ehp SourcePumpPrerunTime failed: ERR: SYN received
2023-11-27 07:39:48.420 [update notice] received update-read broadcast hwcStatus QQ=10: off;35;off
2023-11-27 07:39:50.574 [update notice] received unknown MS cmd: 1050b505072b000100000000 / 00
2023-11-27 07:39:51.077 [update notice] received read ehp Status QQ=10: 35.44;1.891;0.000;heat;2c
2023-11-27 07:39:51.260 [update notice] received read ehp Status02 QQ=10: disabled;0;100.0;0;100.0
2023-11-27 07:39:52.079 [update notice] received read ehp errorhistory QQ=10: 2;2;16:07;26.11.2023;580
2023-11-27 07:39:52.688 [update notice] received write ehp EnergyBalancingRelease QQ=10: on
2023-11-27 07:39:52.904 [update notice] received update-read ehp FlowTemp QQ=10: 33.19;ok
2023-11-27 07:39:54.509 [update notice] received poll-read hwc Mode QQ=10: 38;auto;disabled;hwc;00;4
2023-11-27 07:39:54.733 [update notice] received poll-read hwc Status QQ=10: 0;on;35.44;52
2023-11-27 07:39:56.478 [update notice] received update-read ehp TimeOfNextPredictedPowerCut QQ=10: -:-:-
2023-11-27 07:39:58.124 [bus error] poll ehp SourceTempOutput failed: ERR: SYN received
2023-11-27 07:39:58.519 [update notice] received write ehp PowerCutPreloading QQ=10: off
2023-11-27 07:39:59.066 [update notice] received update-read broadcast hwcStatus QQ=10: off;35;off
2023-11-27 07:40:00.467 [update notice] received unknown MS cmd: 1025b505072b000100000000 / 00
2023-11-27 07:40:00.813 [update notice] received read ehp Status02 QQ=10: disabled;0;100.0;0;100.0
2023-11-27 07:40:01.013 [update notice] received update-read ehp SourceTempInput QQ=10: 3.88;ok
2023-11-27 07:40:01.140 [update notice] received update-read ehp ActualEnvironmentPowerPercentage QQ=10: 100
2023-11-27 07:40:01.313 [update notice] received update-read ehp ActualEnvironmentPower QQ=10: 7
2023-11-27 07:40:02.160 [update notice] received read ehp errorhistory QQ=10: 3;2;15:48;26.11.2023;580
2023-11-27 07:40:02.641 [update notice] received read mc DateTime QQ=10: valid;08:40:03;27.11.2023;0.562
2023-11-27 07:40:03.015 [update notice] received write ehp EnergyBalancingRelease QQ=10: on
2023-11-27 07:40:04.475 [update notice] received poll-read cc Mode QQ=10: 23;auto;disabled;circulation;00;night
2023-11-27 07:40:04.664 [update notice] received poll-read cc Status QQ=10: 0;off;-;0
2023-11-27 07:40:08.412 [update notice] received update-read broadcast hwcStatus QQ=10: off;35;off
2023-11-27 07:40:09.175 [bus error] poll ehp SourceTempOutputOffset failed: ERR: SYN received

v5 Log:

Danke

Hi
I use your adapter v5 and setup authorization. I use user as: " admin" and password "16 characters (7 letters + 8 digits + special character)". After that i can not login to my adapter. I try many times login and then flash adapter and again setup and the same problem.

Hi!

Das Ebus V5 Shield hängt an einer WTU CPU-B1 von Weishaupt, bekommt aber keinerlei Kommunikation. Anschluss passt 100%. Der ebusd läuft auf einer Debian 12 VM und ist verbunden.

Kann ich den Adapter durchmessen? Multimeter, Labornetzgerät und Elektrikerkenntnisse vorhanden.

Hier einige Logs und Infos

ebus Adapter info:

Chip ID: 58cf79e6f978, ESP32-C3, rev 3 Hostname: ebus-weishaupt PCB: 22.1 Flash: 4194304 Version: v5.2-dev-3318-g8fc8f3f479 Reset reason: 5 eBUS r/w: 1/0 Host r/w: 4/20 Up time: 45 Free heap: 102372 ebusd connected: yes (inactive) eBUS signal: no signal

eBus Adapter Log:

ebusd.log
root@ebusd:~# tail -f /var/log/ebusd.log 2023-10-20 20:52:51.555 [main info] successfully read file broadcast.csv 2023-10-20 20:52:51.555 [main info] reading file memory.csv 2023-10-20 20:52:51.555 [main info] successfully read file memory.csv 2023-10-20 20:52:51.555 [main info] read config files, got 11 messages 2023-10-20 20:52:51.587 [bus notice] device status: resetting 2023-10-20 20:52:51.587 [main info] registering data handlers 2023-10-20 20:52:51.587 [main info] registered data handlers 2023-10-20 20:52:51.587 [bus notice] bus started with own address 31/36 2023-10-20 20:52:51.849 [bus notice] device status: reset, supports info 2023-10-20 20:52:51.956 [bus notice] device status: extra info: firmware 1.1[3a0f].1[3a0f], jumpers 0x0f

ebusctl:

`
root@ebusd:~# ebusctl -p 9000
localhost: info
version: ebusd 23.2.23.2
device: 192.168.178.119:9999, enhanced, firmware 1.1[3a0f].1[3a0f]
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

localhost: scan
empty

localhost: find
broadcast datetime = no data stored
broadcast error = no data stored
broadcast id = no data stored
broadcast id = no data stored
broadcast signoflife = no data stored
memory eeprom = no data stored
memory ram = no data stored

localhost:
`

ebusd Optionen

EBUSD_OPTS=" --device=ens:192.168.178.119:9999 -p 9000 --latency=10000 --receivetimeout=25000 --loglevel=info -l /var/log/ebusd.log --lograwdatafile=/var/log/ebusrawdata.log --httpport=9001 --htmlpath=/var/www/ebus/html/ --configpath=/etc/ebusd/config/ --scanconfig"

Vielen Dank für das Projekt und die Mühe

Hi,

i am using the ebus adapter V5 via wifi. Ebusd is installed on an ubuntu 20.04.6
Ebusd has a working connection and I get a list of all devices with command ebusctl find:

e.g.:

broadcast load = no data stored
broadcast outsidetemp = 21.438
broadcast signoflife = no data stored
broadcast vdatetime = 08:55:09;12.06.2023
general valuerange = no data stored
memory eeprom = no data stored
memory ram = no data stored
scan id = no data stored
scan.04 = no data stored
scan.05 = Vaillant;VR921;2801;5703
scan.05 id = no data stored
scan.08 = Vaillant;BAI00;0807;7603
scan.08 id = 21;22;43;0010022008;0001;009276;N7
scan.15 = Vaillant;70000;0614;6903
scan.15 id = 21;22;37;0020266797;0082;057078;N4
scan.26 = Vaillant;VR_71;0100;5904
scan.26 id = 21;22;40;0020184846;0082;023631;N1
vr_71 currenterror = -;-;-;-;-
vr_71 errorhistory = no data stored
vr_71 SensorData1 = 23.44;-;-;-;59.06;49.44;52.00;54 00
vr_71 SensorData2 = 25.12;-;-;-;-895.81;0.00;80 54 04

now I try to do ebusctl read vr_71 SensorData1

and it returns
ERR: element not found

what am I doing wrong here?

Hello, forgive my super basic and noob question but I need to buy a power adapter to power the device via USB. Which specs should I look for? Volts, ampere, etc...

Would it be possible to populate some eBus Adapeter info into ebusd and then read them in KNX / HA?
For example WiFi strength or FW version?

this is a continuation of john30/ebusd#891 as it was misplaced there.

the recently released firmware is capable of analysing the signal wrt bitrate and arbitration delay.

in order to use that feature, the adapter needs to be udpated and then the following steps need to be performed:

• connect to ebus
• don't run an ebusd connected to it (in order to really analyse only the target and not the adapter itself)
• open the REPL (e.g. via web UI)
• enter "ebus -v" there several times in short intervals

the interesting part of the output after each "ebus -v" will look like this:

init_ebus: detected: 2412 Hz on 6 edges with 1990 +/1990 - edge width, 995 H/994 L pulse width, i.e. 415 us H/414 us L period
init_ebus: master 8 0x31 delay=197 us [193-198]
init_ebus: master 25 0xff delay=197 us [196-205]

the first line shows bitrate measurement details with the calculated bitrate, min. clock counts for consecutive pos/neg edges, min. clock counts for H/L pulse widths, as well as calculated H/L pulse widths in microseconds.

the 2400 Bd target a H/L pulse width of 416 us which is basically 1000 clock counts. the minimal pos/neg edge width is targeted at 2000.
so in the above example it looks like the actual bitrate on the line is a little bit higher than it should be, i.e. 2412 Bd instead of 2400, which is 0.5%. this is still tolerable, but when it exceeds 1.2% it might be problematic.

anyway, the firmware now also allows to adhere such situations by using the new bitrate deviation option in the web UI. this way, a slightly higher bitrate can be set which will then be used for transmission as well as reception.

the other 2 lines reveal the seen master addresses, independent of whether the message was valid wrt CRC, so when arbitration errors occur, "fantasy" master addresses would appear here.
anyway, for each master it shows its current arbitration delay as well as the minimum and maximum seen for it since boot.

this allows for using the second feature of the adapter: to adjust the arbitration delay.
the default for the delay is 200 us, but when other participants have a lower delay, then this should be adjusted accordingly.

Please add a basic authentication for the easi> Interface.

I have version 5 of the module, and I have to use an Ethernet connection because I am not getting a signal from the router via WiFi. Besides, I prefer a wired connection (as more reliable) than a radio connection.
Unfortunately, after connecting the module and setting the correct configuration , the module is not detected (it has the status not available).
After repeated attempts to reset and change the WiFi configuration ( switching on, off ) finally the module was "noticed" and it started to work somehow. The USR-ES1 module I am using is HanRun HR961160C 2315.
Unfortunately today it stopped and I decided it was best to report it.

Pins configuration:

My logs with adapter:

Ich versuche nun seit einigen Wochen meinen ebus adapter v5 mit meiner Vaillant Heizung in Betrieb zu nehmen. Leider ohne Erfolg.

Firmware auf dem ebus-adapter: 2023-10-15
Ebusd version: ebusd 23.2.23.2-52-gb9012326

Vaillant-Komponenten:

• Vaillant auromatic 560
• Vaillant ecoTec Plus mit calorMATIC VRC 470/4

Bei der auromatic verwende ich die beiden mittleren Pins des RJ11 Buchse und bei der Gasheizung die Bus-Klemmen auf der Platine. Ich habe beide Bus-Leitungen gemessen.

Bei der auromatic 560 habe ich konstant ca. 22 Volt

Bei der Gasheizung sehe ich ein Rechtecksignal.

ebusd wird mit folgenden Parametern gestartet: --scanconfig=full --device ens:/dev/ttyACM0 --loglevel=debug -p 8888 -l /var/log/ebusd.log

Die grüne LED auf der Platine leuchtet, sonst tut sich aber nicht viel. "ebusctl info" gibt mir die folgenden Werte aus;
version: ebusd 23.2.23.2-52-gb9012326
device: /dev/ttyACM0, enhanced high speed
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

Da ich aktuell keine Ahnung mehr habe, woran es liegen könnte, wäre ich für jeden Tipp dankbar.

EDIT: Bislang habe ich die beiden Vaillant-Geräte jeweils einzeln ausprobiert. Könnte ich beide Geräte über den ebus mit dem ebus Adapter verbinden oder müsste ich einen zweiten Adapter kaufen?

==================================================================
english version:

Since a couple of weeks, I am trying to connect my ebus adapter v5 to a Vaillant heating system but with no sccuess.

Firmware of the ebus-adapter: 2023-10-15
Ebusd version: ebusd 23.2.23.2-52-gb9012326

Vaillant-components:

• Vaillant auromatic 560
• Vaillant ecoTec Plus with calorMATIC VRC 470/4

From the auromatic I am using the middle pins of the rj11 connector and from the gas heating I am using the bus connectors from the pcb. both bus connections have been meassured.

auromatic 560 shows constant 22 volt

gas heating is showing a square signal

ebusd is started with followin parameters: --scanconfig=full --device ens:/dev/ttyACM0 --loglevel=debug -p 8888 -l /var/log/ebusd.log

Die green led of the ebus adapter is on. "ebusctl info" retruns the following values:
version: ebusd 23.2.23.2-52-gb9012326
device: /dev/ttyACM0, enhanced high speed
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

At the moment I have no idea why I do not get a signal. I would be happy for any help.

At the moment, I connect either the auromatic or the gas heating to the ebus adapter. Would it be possible to connect both vaillant devices to one ebus adapter or would I need a second one?

Beim Versuch die neue Firmware zu schreiben, taucht der Adapter bei mir immer nur als unbekanntes Gerät im Gerätemanager auf. Ob der der Button beim Powern gedrückt wurde, macht keinen Unterschied. Muss ich noch bestimmte Treiber installieren?

Hello,

I have already got the eBUS Adapter v5 running completely under the following configuration and have generated data points under ioBroker.

• eBUS Adapter v5 mounted on GPIO strip of a Raspberry Pi 3b
• Raspberry Pi OS (Legacy - Debian 11)

Now I have plugged eBUS Adapter v5 onto a Raspberry Pi 5 (Raspberry Pi OS (Debian 12)).
Then set everything up as described in the instructions at https://github.com/john30.
Unfortunately I get no signal at ebusctl info.

When restarting (power), the blue LED only flashes once for 0.5s. The green and red LEDs do not light up at all!
When the button is pressed, only the blue LED lights up (voltage present).
I have activated and set up both Wifi Station/Clien and WiFi Access Point in the interface ("easi>").
A connection is established if the eBUS adapter is mounted on the Raspberry Pi 3b or is only operated separately with a 5V power supply unit.
If the adapter is mounted on the Raspberry Pi 5, a connection can no longer be established.

I suspect that the eBUS Adapter v5 is not booting correctly when it is mounted on the Raspberry Pi 5.
I used a Siemens 5V/3A control cabinet power supply.

ls -l /dev

dmesg | grep ttyAMA

pinctrl get 0-15

I would be grateful for any suggestions and hope the translation from german to english is reasonably understandable.

Hi, I have updated the build on the ESP device and configured the Wifi.
The status says: eBUS signal acquired. ebusd connected: no

How do I go from here? The 'first steps to start using the adapter' does not help me any further. I installed ebusd on a separate device. Now what?

Please help.

Regards,
Arie

moved from john30/ebusd#1201

Running through the configuration, wifi connection was a breeze.
Connected the adapter to the ebus lines of my heatpump installation, status reads:

ebusd connected: no
eBUS signal: acquired

I found out that you also need to install a deamon on a rpi or something to handle the communication between the adapter and for say, MQTT. Correct?

Now the problem, since I moved to a new home (which ran mostly node red for all automatitions) I also moved to Home assistant, but hassio is not suited to install any non HA applications like the deamon, right? Do I need to revert back to Raspverry PI OS and put HA in a Docker, or is there another solution (I do I mistunderstand the installation guidelines)