Home assistant + Adapter Shield V5

[silviopen]

I apologize if I ask a trivial question, but I'm a beginner in this field and I'm trying to understand how ebusd and the "eBUS Adapter Shield v5" card works.
If connected directly to the Raspberry PI4 is it necessary to configure it in any way?
I understand that by recognizing the direct connection I don't have to configure the wifi part because it will communicate with Home Assistant (on the RPI) via serial.
My intention is to use Home Assistant to integrate the heat pump but I can't find step by step instructions for newbies like me.

[Koky05]

It is necessary to use some type of deamon. In your case it would be HA Addon ebusd from LukasGrebe.

[silviopen]

The shield v5 has no jumpers to set, and in the wiki you pointed to I don't see where it says it should be set.
Maybe it's me who didn't understand what you mean, can you give me more details on how it's done?

[JonesGW-MGD]

Can you clarify what your mean by 'directly'? You have options to connect via USB or via the GPIO pins - I would suggest: Try for now to connect via USB. Try selecting 'enh' mode. Ensure there are no other usb devices are connected on your pi for now (i.e disconnect Modbus (what are you using this for on this pi - is this some kind of RS485 serial adapter?). You can try starting/re-starting with the ebsud adapter v5 plugged in and not plugged in to confirm it is seeng the correct device

[silviopen]

When I talk about connecting it directly I mean via GPIO.
I will also try the USB connection, without the other device (it is a USB/RS485 Modbus adapter)

[Koky05]

Sorry, my bad. I was starting with adapter v3 (jumper settings) and v5 I run for more like half year without any problem. I use WiFi version.

[JonesGW-MGD]

To be honest, I first tried to get my adapter connected via GPIO on my Pi - but failed. I only gave it 10-20 mins of investigation though as I was impatient to try ebusd!

I followed the instructions here: https://adapter.ebusd.eu/v5/raspberrypi.en but I couldn't see Serial0 configured at all. My googling seemed to suggest that dtparam=uart0 in config.txt , enables UART0/ttyAMA0 on GPIOs 14 & 15 but I couldn't find /boot/config.txt - I suspected it had something to do with HAOS being some kind of version of BalenaOS/ResinOS - to run the container architecture and therefore the usual linux-y stuff wasn't evident. (multiple mounts, so not the standard disk layout?)

But this was all starting to get above my 'technical paygrade' and my incredibly limited 'linux foo'!

I believe you can remove the SD card, and use a PC to find /boot/ config.txt and that might help you assign serial0?

https://community.home-assistant.io/t/enable-serial-port-ttyama0/347503

But I was happy frankly that it worked in seconds connecting to USB and I've not tried to use GPIO again! Good luck!

[pvyleta]

I successfully connected the shield to my HomeAssistant running on Rpi4. Forget the pins and shield - connecting the V5 shiled to wifi is really easy, and then you can connect to it from HA addon easily. In general folow https://adapter.ebusd.eu/v5/steps.en.html.

1. the adapter creates EBUS wifi. connect to it
2. open browser and type in http://192.168.4.1/ which will open the adapter configuration page
3. on top select configuration, and configure the adapter to connect to your home wifi - the one your HomeAssistant is connected to. Might work with IP given by DHCP, but I did not try that and instead I selected some Static IP
4. you can optionally update FW here, disable the EBUS wifi AP etc. but that does not need to be done right now
5. Install the https://github.com/LukasGrebe/ha-addons on your HA
6. go that addon configuration page in HA, set 'mode' to 'ens' and place in the IP and port of your device, e.g. '192.168.100.60:9999'

That should be it

[Olninyo]

Thank you so much for posting this, was starting to worry that the easiest part of setup was already kicking my ass.
I kept getting
unknown, error: ESP_ERR_HTTP_CONNECT
when testing the WiFi connection from the easi configuration page through the EBUS WiFi access point. But actually it looks like it's connecting fine to the router. I have also assigned it a static IP.

Hopefully the next step goes smoother 🤞🏻🤞🏻
(I am so far out of my depth)

[silviopen]

Thank you all for the responses that allowed me to take some steps forward!
These days (evenings)These days (evenings) I have been trying to figure out how to configure my adapter.
Thanks to @JonesGW-MGD I found a way to edit the /boot/config.txt file that is on the SD card but to read it you need to stop the RPI and plug it into a PC.
There it was enough to de-comment 2 lines to enable the serial ttyAMA0 which "magically" appeared in the ebusd configuration tab.
Thanks to @pvyleta's advice I went into the configuration of the ebus shield v5 and enabled the connection to the RPI PINs, which was not enabled by default, although from the information I had it appears to be self-configuring.
Finally after some testing I set the "ens" option (enhanced with high speed) which seems to be the one that gives the least errors in my case.

Unfortunately, I can only see ebusd data and practically none of the sensors that I imagined I would find

Here's what I did

From https://github.com/wrongisthenewright/ebusd-configuration-ariston-bridgenet:
-I copied the ariston.csv file and set the "config path" to /config/ebusd/ariston.csv
-I copied the mqtt-hassio.cfg file and set mqtt integration file to "/config/ebusd/mqtt-hassio.cfg"

I attach a part of the log file where you see error messages and other unknown data,hoping that someone can help me to understand what is wrong

2024-03-05 21:59:57.004 [update notice] received unknown MS cmd: 131e20200c0b45001745001a45001ef300 / 00
2024-03-05 21:59:57.100 [update notice] received unknown BC cmd: 0ffe20100f79970000007a970000007b97000000
2024-03-05 21:59:57.254 [update notice] received unknown MS cmd: 0f1e20000462476347 / 050300000000
2024-03-05 21:59:57.371 [update notice] received unknown BC cmd: 13fe20100cc2000100c74b1400c94b0400
2024-03-05 21:59:57.710 [update notice] received unknown BC cmd: 13fe20101001910000029100000391000004910000
2024-03-05 21:59:57.828 [update notice] received unknown BC cmd: 13fe20100c059100000691000007910000
2024-03-05 21:59:57.886 [update notice] received unknown BC cmd: 10fe20700702160503021801
2024-03-05 21:59:58.057 [update notice] received unknown MS cmd: 131e2000086e13ca46cb46d84b / 060fe600034d0f
2024-03-05 21:59:58.292 [update notice] received unknown MS cmd: 131e2000020c45 / 020101
2024-03-05 21:59:58.595 [update notice] received unknown MS cmd: 1018200002d140 / 020100
2024-03-05 21:59:59.460 [update notice] received unknown BC cmd: 0ffe20100c011900000219000003190000
2024-03-05 22:00:00.897 [update notice] received unknown BC cmd: 10fe20500b0000080200000000000000
2024-03-05 22:00:01.541 [update notice] received unknown MS cmd: 131e20200dc33efec44664cd46036a475802 / 00
2024-03-05 22:00:01.679 [update notice] received unknown MS cmd: 131e20200dce9c78d09c02d89c00659f3200 / 00
2024-03-05 22:00:01.773 [update notice] received unknown MS cmd: 131e202003d5f000 / 00
2024-03-05 22:00:01.894 [update notice] received unknown BC cmd: 10fe20510e1207000000005555555555550000
2024-03-05 22:00:02.024 [update notice] received unknown MS cmd: 131e20200c0b45001745001a45001ef300 / 00
2024-03-05 22:00:02.346 [update notice] received unknown BC cmd: 13fe20100cc2000100c74b1400c94b0400
2024-03-05 22:00:02.668 [update notice] received unknown BC cmd: 10fe20380501640d0708
2024-03-05 22:00:02.799 [update notice] received unknown BC cmd: 13fe20101001910000029100000391000004910000
2024-03-05 22:00:02.916 [update notice] received unknown BC cmd: 13fe20100c059100000691000007910000
2024-03-05 22:00:03.126 [update notice] received unknown MS cmd: 131e2000086e13ca46cb46d84b / 060fe500034d0f
2024-03-05 22:00:03.232 [update notice] received unknown MS cmd: 1018200008150318031c117017 / 060f0000008101
2024-03-05 22:00:03.365 [update notice] received unknown MS cmd: 131e2000020c45 / 020101
2024-03-05 22:00:03.672 [update notice] received unknown MS cmd: 1018200008ca46060107011403 / 050f03000000
2024-03-05 22:00:04.472 [update notice] received unknown BC cmd: 0ffe20100c011900000219000003190000

2024-03-05 22:15:33.604 [update notice] received unknown BC cmd: 10fe20510e1603555555555555555555555555
2024-03-05 22:15:33.718 [update notice] received unknown BC cmd: 13fe20100cc2000000c74bbe00c94b0000
2024-03-05 22:15:34.056 [update notice] received unknown BC cmd: 13fe20101001910000029100000391000004910000
2024-03-05 22:15:34.174 [update notice] received unknown BC cmd: 13fe20100c059100000691000007910000
2024-03-05 22:15:34.384 [update notice] received unknown MS cmd: 131e2000086e13ca46cb46d84b / 060f00000f0013
2024-03-05 22:15:34.653 [update notice] received unknown MS cmd: 131e2000020c45 / 020100
2024-03-05 22:15:35.231 [update notice] received unknown MS cmd: 10182000080601070114031603 / 050f01000000
2024-03-05 22:15:35.351 [update notice] received unknown MS cmd: 10182000047017d140 / 0403d00100
2024-03-05 22:15:35.434 [update notice] received unknown BC cmd: 0ffe20100c011900000219000003190000
2024-03-05 22:15:35.995 [main error] scan config 05: ERR: element not found
2024-03-05 22:15:36.689 [update notice] received unknown MS cmd: 1014200002d140 / 020108
2024-03-05 22:15:37.406 [update notice] received unknown MS cmd: 131e20200dc33eecc44664cd46006a475802 / 00
2024-03-05 22:15:37.579 [update notice] received unknown MS cmd: 131e20200dce9c78d09c00d89c00659f3200 / 00
2024-03-05 22:15:37.637 [update notice] received unknown BC cmd: 10fe20700712160503021801
2024-03-05 22:15:37.728 [update notice] received unknown MS cmd: 131e202003d5f000 / 00
2024-03-05 22:15:37.761 [update notice] received unknown BC cmd: 00fe203a011e
2024-03-05 22:15:37.925 [update notice] received unknown MS cmd: 131e20200c0b45001745001a45001ef300 / 00
2024-03-05 22:15:37.996 [main error] scan config 08: ERR: element not found
2024-03-05 22:15:38.281 [update notice] received unknown BC cmd: 13fe20100cc2000000c74bbe00c94b0000
2024-03-05 22:15:38.620 [update notice] received unknown BC cmd: 13fe20101001910000029100000391000004910000
2024-03-05 22:15:38.737 [update notice] received unknown BC cmd: 13fe20100c059100000691000007910000
2024-03-05 22:15:38.981 [update notice] received unknown MS cmd: 131e2000086e13ca46cb46d84b / 060f00000f0013
2024-03-05 22:15:39.249 [update notice] received unknown MS cmd: 131e2000020c45 / 020100
2024-03-05 22:15:39.597 [update notice] received unknown BC cmd: 10fe20500b5555040300000000000000
2024-03-05 22:15:39.996 [main error] scan config 14: ERR: element not found
2024-03-05 22:15:40.288 [update notice] received unknown BC cmd: 0ffe20100c011900000219000003190000
2024-03-05 22:15:40.613 [update notice] received unknown BC cmd: 10fe20510e1604555555555555555555555555

[pvyleta]

difficult to say, your CSV file may be broken, not loaded, not correctly paired with the device... I suggest enabling debug logging and capture what the startup of the addon looks like.

[pvyleta]

Also, it seems you are having the same issue as a different user of presumably the same CSV file (I am guessing just based on the name). I suggest to discuss this with the CSV file authors.

[silviopen]

I found the error: a file was missing 🤦🏼‍♂️
I had also forgotten to copy the _templates.csv file to the same folder as ariston.csv and mqtt-hassio.cfg

I will now study all the data that is coming from the bus and again thank you for the support, you were great!