Ariston Group integration via eBusd

Third party integrations
370

Its not clear what you’re referring to….
“My” CSV exposes write enabled parameters from ebusd, if you’re using a MQTT-hassio.cfg file that have the filter removed as per instructions you should be able to have writable entities in HA via native discovery.

You can try to create a custom/manual MQTT entity to test the write, the read topic is ebusd/……/entity
The write one is the same with appended a /set suffix.

You can also manually publish a MQTT message to the write topic and check if the write goes as planned

371

I succeeded. In the ebusd addon I added the writing line and now all the controls appeared except that I only have the Ariston Genus One boiler. I don’t have a hybrid system. Now I will have to find a way to not have so many entities. Thanks for the work done

372

Hello all,
i read all the thread, i’m the owner of ELCO AEROTOP MONO 11kw, heat pump, i tried with the web app\api integration and i am not satisfied with the data retreived.
i would like to integrate it via ebusd, and i think i understood what to do:

  • buy a ebus adapter C6 eBUS Adapter Shield from ebusd.eu

  • attach it to the “BUS” connector to the heat pump (the same where the heat pump contro panel is attached, and the same where the gateway for the app is connected) ex img:

    hp
    hp870×492 51.8 KB

  • enable via home assistant the ebus integration + the csv for the ariston heat pump

could anyone of you please confirm if i understood correctly? i am missing any step?
the hardware linked is enough, and need no raspberry or other part to work, right?
the BUS eletrical connection is safe? do i risk anything connecting the extra hardware to the heat pump BUS? there is no need for any extra wire?
thanks a lot for the help…

373

The whole process is described here and on the Github repo but you got the macro steps covered. The step you’re missing is configuring ebusd to talk to the adapter, this depends on how you’re running ebusd. If on native docker there is a config, if using the HAOS addon you need to look for info as I don’t use it.

If you’ll run ebusd on the same machine as HA (either as a separate docker or as an addon) then you won’t need any new HW

Yes, it is safe. The adapter you’re buying is octo isolated so the risk of interference with the bus is low, I’m using it since years without any issue.

I stress that even if it is a safe modification you are wiring something “external” on the proprietary bus. In case of any problem the first thing to do will be disconnect the adapter and see if the problem persists before calling the Ariston/Elco Service.

In some cases (in particular after an entire home power loss due to grid failures/cutoffs) my adapter needs to be rebooted because otherwise the bus goes into a loop of discovery that never ends, in this case my HP and Boiler did not work.
I think the problem is connected to the restarting sequence of the various elements, in my case is so sporadic that I have not invested time in diagnosis, when it happens I simply log into the adapter web gui and execute a reboot.

The adapter will need a solid USB-C power adapter and a couple of wires to connect to the bus port, if the length of wire from the adapter to the port is long you should evaluate the use of a shielded signal wire. I’m not an expert and I did not need it, the bus speed is rather low but the latency of the whole HA<–>bus communication must be as lower as possible.

You can try an then adapt if needed.

375

Is this ebus working on a ariston nuos plus s2 boiler?

376

It does work on an Ariston Nuos Split.

378

4662
46621200×1052 270 KB

Which settings on the Ariston nuos s2 boiler?
System - on → Cascade no?
System on → cascade yes → master?
System on → cascade yes → slave?

And power on the ebus from the aristion boiler?

manual:
P33 EBUS POWER ON (function enabled) - OFF (function disabled)

379

The ebus adapter (Willkommen zum eBUS Adapter Shield - eBUS Adapter Shield C6) needs it’s own power supply. I do not have parameter p33 on my water heater so I don’t know how to set it. Starting with p33 off and when no contact p33 on, would be the smartest approach.
I think the setting should be System: No as the ebus adapter functions as a remote control.

380

That should be the setting.

System YES → The boiler will talk on the bus so hopefully it will accept commands from it

Cascade NO → You have only one system so there should be no need of cascading the settings to other devices

I think the System setting could be either YES (as stated before) or NO (as it will accept a remote control in this state). Try both configs.

The power setting I think could be left off, either the boiler and the adapter have their own power sources. If you install a remote control panel you chould set it to ON as the panel usually pick its juice from the bus cables.

Try with bus power off, the boiler and the adapter have their own

381

hello! here we go :slight_smile:

wiring from heat pump was successful, ebus is connected and working fine,
mqtt entities are created

unfortunately, there are a lot of values not showing up:

immagine
immagine328×738 27.2 KB

could anyone help me how can i figure out or debug this?
my main goal is to retreive energy consumption / working temps ° for circuits and puffer\dhw storage / working hour / pump flow rate /

heat pump model is: elco aerotop mono 11kw, it should be the twin sister of nimbus pocket m net

thanks for the support

382

Please open an issue on the GitHub repo attaching the output of:

  • ebusctl info (if available/able please identify the bus participant devices)
  • ebusctl grab result all
  • ebusctl find

And describe your system with emphasis on the bus attached devices list (HP, WiFi GW, remote control etc)

If we find a solution will post also here the results.

383

@FransO did you get the kWh value from ebusd? If yes, could you share the value in the CSV. BTW in preset/mode the value 3 is “i-Memory”. I have a Nuos WiFi 250

384

@szappanyos No I never managed to get any energy readings from the device. I installed a power monitoring plug instead.

1 Like
385

Why is there a sensor for power created and for boost and preheat not?
mqtt messages (with data) for boost and preheat are created (cheched via a mqtt client).

r2,dhw,power,On/Off,fe,2001,0220
b,dhw,power,On/Off,fe,200e,0220,value,s,BCD,0=off;1=on
w,dhw,power,On/Off,fe,200e,0220,value,s,BCD,0=off;1=on
r2,dhw,preheat,On/Off,7c,2000,0c88,s,IGN:1,value,s,BCD,0=off;1=on
w,dhw,preheat,On/Off,7c,2020,0c88,value,m,BCD,0=off;1=on
r2,dhw,boost,On/Off,7c,2000,1a21,s,IGN:1,value,s,BCD,0=off;1=on
w,dhw,boost,On/Off,7c,2020,1a21,value,m,BCD,0=off;1=on

image
image326×877 26.2 KB

386

I do not use the auto discovery, so I don’t know why the one is discovered as a sensor and others - presumably - as switches. I have defined power, boost and preheat in home assistant all as switches, not sensors.

387

Do you have an example code for a switch?

388

This is the discovery topic of the power switch, you will have to adapt it to the naming in your ebusd config file:

homeassistant/switch/power_value/config

The payload of the discovery message is:

{
  "object_id": "ebusd_dhw_power_value",
  "unique_id": "ebusd_dhw_power_value",
  "device": {
    "identifiers": [
      "ebusd"
    ],
    "model": "Nuos 200 Split",
    "manufacturer": "Ariston",
    "name": "Ariston Nuos"
  },
  "state_topic": "ebusd/dhw/power/value",
  "icon": "mdi:toggle-switch",
  "state_on": "on",
  "state_off": "off",
  "command_topic": "ebusd/dhw/power/value/set",
  "payload_on": "on",
  "payload_off": "off",
  "name": "power_value"
}

You can of course also define the switch in your configuration.yaml.

object_id: ebusd_dhw_power_value
unique_id: ebusd_dhw_power_value
device:
  identifiers:
    - ebusd
  model: Nuos 200 Split
  manufacturer: Ariston
  name: Ariston Nuos
state_topic: ebusd/dhw/power/value
icon: mdi:toggle-switch
state_on: 'on'
state_off: 'off'
command_topic: ebusd/dhw/power/value/set
payload_on: 'on'
payload_off: 'off'
name: power_value
389

I updated ebusd 26.x… and now it gives me an error and it doesn’t see the boiler anymore

2026-03-18 10:16:27.616 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:28.616 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:29.523 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:16:29.523 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:16:39.524 [main notice] starting initial broadcast scan
2026-03-18 10:16:40.058 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:42.494 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:43.468 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:16:43.468 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:16:53.469 [main notice] starting initial broadcast scan
2026-03-18 10:16:54.220 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:54.940 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:16:55.462 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:16:55.462 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:16:57.002 [bus notice] max. symbols per second: 266
2026-03-18 10:17:05.462 [main notice] starting initial broadcast scan
2026-03-18 10:17:05.978 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:06.747 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:07.932 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:17:07.932 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:17:17.933 [main notice] starting initial broadcast scan
2026-03-18 10:17:19.569 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:20.080 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:20.559 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:17:20.559 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:17:30.560 [main notice] starting initial broadcast scan
2026-03-18 10:17:31.228 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:32.043 [bus error] send to fe: ERR: arbitration lost, retry
2026-03-18 10:17:34.660 [bus error] send to fe: ERR: arbitration lost
2026-03-18 10:17:34.660 [main error] initial scan failed: ERR: arbitration lost
2026-03-18 10:17:44.660 [main notice] starting initial broadcast scan
2026-03-18 10:17:45.184 [bus error] send to fe: ERR: arbitration lost, retry
1 Like
390

The arbitration lost error is probably related to a modification in the starting parameters, not the ebusd version. Check the latency settings.

You can revert back to 25.x version to check if that’s the case…

391

yes I went back to 25.1 and it works perfectly