Hi Zolli,
I got the same adapter, what value did you put for the PWM? I see the led shows activity on the ebusd (blinking) but I kind of got stuck at this phase.
I highly appreciate the effort Fabyano put in this, but so far the instructions are not that clear to me.
Kind regards,
Tash
Hey Tash, it worked fine with the default value. (130 I think)
In the meanwhile I switched the official ebusd adapter because wifi can cause a lot of read error if you don’t have a very-very consistent low ping time, and I don’t have an AP closely located to my indoor unit. Because ebus is a multi-master protocol it uses arbitration to figure out who can send data in the bus.
The official ebus adapter can be ordered from elecrow as well and offer a very nice USB serial interface, so if you connect it to a low power pc it can see it as a serial port and ebusd able to talk with the adapter without any delay basically, the latency for the MQTT connection does not matter.
Hi Zolli, thank you very much for the detailed response. I noticed that the designs of the boards are quite similar and the prices are almost identical. I will look into this to see which option is best for me. I do have an access point in the basement, but I’m not convinced that the signal is strong enough since the walls are quite thick.
Your solution looks quite promising, although I feel it brings complexity.
If not mistaken there is an ariston integration for the cloud solution, was not easier for you to connect to the nimbus that way?
Somehow off topic, how happy are you with the nimbus system. I’m still on gas (ariston genus premium) and exploring the options for going for a heat pump. I can add a heat pump boiler to the system or replace the genus with a nimbus compact or similar.
TBC
Kind regards,
Tash
Hi Tash,
as I wrote in the OP the cloud integration works…as long as Ariston keeps online his cloud servers and as log as Ariston keeps the current cloud architecture/backend.
If Ariston goes bankrupt or if simply Ariston decides to change radically their cloud infrastructure that kind of integration will no longer work (or at least until someone else did another reverse engineering).
Tapping into the bus bypass all that. Taking into accont the fact that an HVAC system lasts usually decades that is a plus in my eyes.
As per the heatpump, having a Genus boiler you should be able to integrate a Nimbus HP (even the newer R32 appliances) with the Ariston Hybrid module. Ask an Ariston reseller for details and compatibility.
I have an hybrid system (Genus+Nimbus+Hybrid module) and I’m really impressed from the quality and price/performance/features ratios.
I have an ariston genus one with the Ariston Hybrid module.
where do I connect the bus on the pdc?
should I buy this adapter? does it work for the purpose?
Rapid reply because I’m a little busy ATM.
The adapter is ok I used one from the same shop but without the usb port but had some problem caused by tension loss(I think).
You should test it with and without external usb power to check how it behaves in your case.
You can connect the adapter in parallel in one of the different ports you have .
1)in the boiler
2)in the hybrid module
3)in the hp
4)in the sensys/gateway
5) cutting and “y” cabling one of the above connections
If using WiFi choose the place where you have the better coverage/lower latency.
Hi, I have successfully installed Ebus adapter and configured PWM, instaled ebusd on HA, and put csv and cfg file in ebusd config directory, but I’m unable to get any data from it. Any ideas what I’m doing wrong? Do I need to edit cfg and csv files for my own system?
Thanks
You don’t need USB connection. Only two wires on BUS terminal
Yes try with and without UBS power. Let the test last at least 3 or 4 days and see if the other devices connected to that bus “line” throw some errors.
In my case, without usb power, I got random bus resets. With usb power those resets disappeared.
As I wrote before it depends. It works even without usb power but if the bus power draw from that port is too high then you may get bus resets. At least that’s what I experienced in my configuration.
It depends on what kind of ha installation do you have. If you’re on HAOS then the only way it’s to use the ebusd addon available on hacks I think (I’ve got the core version running on docker, so my help here is a little shaky).
If you’re on docker like me you can find a basic script to run e use in my git repo.
Once you have ebusd running you must copy the Ariston.csv and mqtt-hassio.cfg in the config folder of ebusd. If using the addon I don’t rightly know where that folder is, you may ask in the ebusd thread in this forum
I’m on HA Yellow, and I have installed ebusd add on, but trying to configure it and read something is a nightmare.
Yeah I did find HAOS a little unforgiving with integration like these that needs a little “manipulation” to work correctly.
Find how to copy mi file in the right folder of the addon and restart it
This is the log that I get
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 --httpport=8889 --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=fahS6dahwiL1eex2Dorahtha1pooshiek9EPae4zohf5EiC3FieGeiNgae8Tuuni --scanconfig --mqttjson --configpath=/config/ebusd/ --latency=10 --pollinterval=5 --mqttint=/config/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.1.95 --log=all:notice
2024-10-03 21:21:06.884 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.1.95, enhanced high speed
2024-10-03 21:21:06.911 [bus error] unable to open 192.168.1.95: ERR: element not found
2024-10-03 21:21:06.911 [bus notice] bus started with own address 31/36
2024-10-03 21:21:06.911 [bus notice] device invalid
2024-10-03 21:21:07.405 [mqtt notice] connection established
2024-10-03 21:21:11.912 [bus error] unable to open 192.168.1.95: ERR: element not found
2024-10-03 21:21:11.912 [bus notice] device invalid
2024-10-03 21:21:16.912 [bus error] unable to open 192.168.1.95: ERR: element not found
2024-10-03 21:21:16.912 [bus notice] device invalid
OK, Ebusd is not able to communicate with the adapter:
- check if the adapter IP is right (from ssh shell:
telnet ADAPTER_IP 5555should give you some basic info) - check if the ebusd settings are right , the device definition in recent ebusd version is tricky, try these 3 possibilities
ens:ADAPTER-IP:3333
enh:ADAPTER-IP:3333
ADAPTER-IP:3333
3333 is the port for Kucera’s adapter, or 9999 for John’s “original” one
I use Kucera’s adapter, and the IP address is correct. I can telnet to that address and see some binary data comming.
I tried to change some configuration in ebusd but still not able to run it.
Today I have this error:
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=fahS6dahwiL1eex2Dorahtha1pooshiek9EPae4zohf5EiC3FieGeiNgae8Tuuni --scanconfig --mqttjson --configpath=/config/ --latency=10 --pollinterval=5 --mqttint=/config/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.1.95:3333 --log=all:notice
2024-10-04 09:16:12.105 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.1.95:3333, enhanced
2024-10-04 09:16:12.106 [main error] error reading config files from /config/: ERR: element not found, last error: ariston.csv:23: ERR: element not found, field type ONOFF in field 0
2024-10-04 09:16:12.221 [bus notice] device status: resetting
2024-10-04 09:16:12.221 [bus notice] bus started with own address 31/36
2024-10-04 09:16:12.247 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.247 [bus error] device status: unexpected available enhanced byte 2
2024-10-04 09:16:12.344 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.344 [bus notice] signal acquired
2024-10-04 09:16:12.356 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.400 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.400 [bus error] device status: unexpected available enhanced byte 2
2024-10-04 09:16:12.415 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.436 [bus error] device status: unexpected available enhanced byte 2
2024-10-04 09:16:12.471 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.502 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.518 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.535 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.554 [bus error] device status: unexpected available enhanced following byte 1
2024-10-04 09:16:12.556 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.569 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.602 [bus error] device status: unexpected available enhanced byte 2
2024-10-04 09:16:12.619 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.633 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.668 [bus error] device status: unexpected enhanced command 0x06
2024-10-04 09:16:12.705 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.722 [mqtt notice] connection established
2024-10-04 09:16:12.736 [bus error] device status: unexpected enhanced byte 2
2024-10-04 09:16:12.755 [bus error] device status: missing enhanced byte 2
2024-10-04 09:16:12.767 [bus notice] device status: reset
2024-10-04 09:16:12.818 [bus notice] device status: reset
Have you tried all 3 device definition lines that I suggested?
Yes, I didn’t see any difference. Is there something that I need to edit in ariston.csv or in mqtt-hassio.cfg file?
No.As fae as I can tell it’s an ebusd <—> adapter communication issue. You should ask for support on the GitHub repo of Daniel kucera firmware or on John ebusd repo. I’d start with te first.