Can imagine, will not do it again…
I moved the ebus near to my AP. I have an RSSI between 58-65dBm. Stability has improved a lot. But once or twice a week the Genius One crashes and says synchronizations….
never lost connection from wifi controller
I don’t remember if you have already added an external power supply to the adapter or are you using the bus energy to power up the adapter. If you are in the latter case please try to add a USB power supply and check if the error goes away.
I’ve looked again into your message dump and I’m afraid that the current tank temp is not broadcasted/sent on the bus, I’ve looked into my HVAC system menu (not a NUOS but my HP has the ability to produce DHW even if I have disabled it as I don’t have the tank) and I haven’t found any diagnostic menu to read that parameter.
It seems to me that the bus is used only to set thresholds and then the system runs autonomously. When the tank temp is below the current threshold (comfort vs. economy) it starts heating the water.
EDIT: I’ve taken a look at the wiring scheme for the NUOS, I’m not an electronic expert but it seems that the daughter board on the right is responsible for the running of the compressor and the fan, it also connect the tank probe so this in my eyes confirm that the board do autonomously the heating based on the temp setpoints. You may hook something in parallel with the built in tank probe, I won’t use the “native” one, even if it is as I think a normal NTC10K@20°C, because if you disconnect it the NUOS will complain and if you wire something in parallel you’ll alter the resistance thus having only false readings.
You can maybe hook up a temp sensor to an ESPsomething and send the tank temp to HA, have you noticed if the tank has a receptable for some kind of probe?
I already put the USB power supply in
Thanks for all your time and help! It seems it doesn’t send it indeed. I am however able to control the heatpump via SG1 and SG2 connectors (connected 2 Shelly’s there) so I am able to control it at least when I have Solar Power left.
I have three diagnostic-menus to read temperature: T Low, T High & T Dome.
I might look into if it’s possible to add a sensor somewhere myself. Thanks again for your help!
Hi, I have following error message when starting up eBusd, can’t figure out what is wrong with it? I have the ariston.csv and _templates.csv file in the config/ebusd folder. Starts apparently fine…
Thanks
2024-12-21 18:28:55.738 [main notice] ebusd 24.1.p20241110 started with broadcast scan on device: 192.168.1.125:3335, TCP, enhanced
2024-12-21 18:28:55.778 [bus notice] bus started with own address 31/36
2024-12-21 18:28:55.778 [device notice] reset
2024-12-21 18:28:55.779 [bus notice] signal acquired
2024-12-21 18:28:56.132 [mqtt notice] connection established
2024-12-21 18:28:56.147 [bus notice] new master 37, master count 2
2024-12-21 18:28:56.147 [update notice] received unknown BC cmd: 37fe2000027647
2024-12-21 18:28:56.224 [update notice] received update-read energymgr ext_temp QQ=37: 2.1
2024-12-21 18:28:56.864 [update notice] received unknown BC cmd: 37fe2000020220
2024-12-21 18:28:56.940 [update notice] received update-read energymgr dhw_status QQ=37: on
2024-12-21 18:28:57.099 [update notice] received update-read boiler boiler_status QQ=37: heating
2024-12-21 18:29:16.005 [update notice] store 3c ident: ERR: invalid position
2024-12-21 18:29:16.005 [update error] unable to parse scan-read scan.3c from 313c070400 / 00: ERR: invalid position
2024-12-21 18:29:16.006 [main error] scan config 3c: ERR: invalid position
2024-12-21 18:29:17.055 [mqtt error] decode scan.3c : ERR: invalid position
These seems to be error related to the standard ebus discovery process.
Ebus2 or BusBridgenet (Ariston Group ebus “dialect”) is not compliant with the standard so the discovery fails. You can ignore those errors.
Connected danielkucera esp-arduino-ebus v7.1 to nimbus r32. Also there is sensys + ariston wifi adapter connected to ebus. And looks like all devices can’t work at the same time (tried all wiring methods, usb powered adapter, pwm adjustments, latency is low < 10ms). If pwm ~130, adapter receives data from ebus, but sensys then has no data and even it screen starts flickering. If pwm > 170, then sensys works normal, but ebus adapter throws errors like [bus debug] ERR: read timeout during receive command, switching to skip, [bus debug] notify request: ERR: arbitration lost. Any suggestions what is wrong here?
If the screen start flickering then you probably have a power problem.
Try to power the adapter via external power supply.
Sorry I read the message too fast for my brain to connect.
It is surely a power problem, try to change adapter. I’d also try a different bus port.
Other test could be to change the bus address for ebusd to avoid conflict (even if the standard 31/36 should go because from the log I’ve seen so far Ariston doesn’t use that address).
Once powered indipendently from the bus please try to launch ebusctl info command once set a PWM of 130.
I’m curious how you connected the SG connectors to the Shelly’s. Do they need to receive power (eg 220v)?.
I have some smartplugs, so it might be interesting to use them as relays for these connectors by putting a plug on the cable connected to the SG1 and SG2.
They need power indeed, so just put 230V on them. Using smartplugs should work fine. I took shelly’s because I could put both of them inside the compartiment in the heat pump, no external wiring needed! You should take a good look at the manual on how this works, because they need specific setting in the heat pump menu to get them to do what you want. i have 1 that’s used to control day/night setting (45 or 55 degrees, switched to 45 from 23:00 to 10:00) and the other one to force 65 degrees when I am sending over 1kW back to the grid. Let me know if you need more info.
1 Like
Hello, thanks for all the sharing and advice !
I have 2 ariston nimbus S heat pumps next to each other, connected to 2 ariston light gateway / sensys.
Before connecting an ebus adaptor, I am wondering if I can connect only one gateway to both heat pumps to make things simpler. Since it is a bus I suppose this is possible. Any experience doing that?
thanks
Hi,
there is an high probability, bordering on certainty, that if you connect a single adapter to both machines (interconnecting the 2 different buses doing so) you’ll have big problems.
Address collision and double complete system hang would be the best outcome since you’ll get the error early on, if the discovery phase somewhat ends without major hangs you’ll have both HPs reporting to and being subjected to both energy managers…
For what I know Ariston Bus addresses are fixed so both HP will have the same 1e slave address and so on…
No, for your scenario you’ll need 2 adapters and 2 instances of ebusd running, the 2 ebusd should differ in the mqtt-hassio configuration separating (via different topic prefix) the MQTT messages, event ebusd parameters should differ if both instances will be running on the same host, given that ebusd itself exposes some TCP ports so there would be a conflict with 2 executions on the same system.
Let me know if you’ll instead test your luck with a single adapter… 
1 Like
Thanks a lot, fixed addresses seem so dumb , I’ll buy 2 adapters just to be sure but I will also try a single one for the sake of experiment If you don’t think I may break stuff, and report back.
so Chat seem to think it is possible we will know in a few days
:::
To connect two Ariston heat pumps to the Ariston Light Gateway, follow these detailed wiring instructions:
- Wiring: Use a 2x0.5 mm² wire with a maximum connection length of 50 meters. Connect the wire to the terminal by introducing it from the lower part after creating a suitable passage
- Gateway Installation: Install the gateway on the wall using the supplied screws. Ensure that the gateway is connected to the heating system via the BridgeNet BUS connection
- Connecting the First Heat Pump:
- Connect the first heat pump to the BridgeNet BUS terminal on the Light Gateway.
- Ensure that the connection is secure and that the heat pump is powered on.
- Connecting the Second Heat Pump:
- Connect the second heat pump to the same BridgeNet BUS terminal on the Light Gateway.
- Make sure that both heat pumps are properly connected and powered on.
- Configuration: Once the physical connections are established, you will need to configure the system to recognize and control both heat pumps. This typically involves accessing the system’s settings through the Ariston Sensys Net Wi-Fi Thermostat interface and adding the second heat pump to the network
For what I knon (and I’ll admit is not much) it won’t work but let’s wait and see.
BTW the scenario the AI is depicting is different from what you were suggesting before. 2 HP with 2 “thermostats” vs, 2 HP and a single “thermostat” (thermostat=Sensys+GW).
Let us know, now I’m really courious to see how it’ll work!!
Could you point me in the right direction, preferably with some examples, on how do I go from a list of entities under the MQTT integration, which I have now, to actually setting the parameters like temperature, operating mode , operating preset, etc?
I am trying to migrate from the cloud integration to local ebusd integration. The automatons are already working by reading and setting parameters on the boiler using the Ariston cloud integration. I have to migrate the communication with the boiler from cloud to local ebusd.
Hi,
if you want to send commands from HA to the boiler you should:
-
for the numeric settings values customize all the writable parameters via
customize:statements and set correct limits and stepping, a parameter written out of range can lead to strange behaviours (see in my repo for some example) -
the switch settings (on/off) should work out of the box, at least in my case they do (with my mqtt-hassio.cfg) so these are altready switch entities modifiable via automation, you may want to set more human readable names
-
the multi select settings, for the moment, even it write enabled, are discovered in HA as sensors, if you want you can try to develop the MQTT Select scenario I highlighted some post above
In general every write enabled parameter can be set from HA via a published MQTT message to the /set subtopic, so, as an example, if you want to modify Z1 day temp do 22°C you should write a suitable number (inside the allowed range and with the correct stepping, in this case 22.0 ) to the mqtt topic
ebusd/energymgr/z1_day_temp/set
Please note that the internal non volatile memory of the HVAC system/boiler can be not suited to contiuous writes so I’d limit the setting modifications to the bare minimum. These devices are usually set once and then remain untouched the entire winter.
As you anticipated, connecting both heat pumps to the same sensys resulted in a bus error (address conflict) both pumps (called heating managers or something similar) are shown in conflict and there does not seem to be a way to correct this. I guess this “2 pumps” scenario was not intended by Ariston at all. I will have to connect one adaptor to each pump as you said.