Ariston Group integration via eBusd

70fe200f057118000100 = 8
70fe2010057118000100 = 67
7ffe2000027118 = 8

Nice suggestion! Will try tomorrow and let you know, thanks again c:

Edit:
With already available data I found this row that could be interesting, as
SIN 7118=6257, 18ff=-232, ff00=255, 0000=0
ff00 is the temperature multiplied by 10

I was able to retrieve the correct data!
I don’t know if you’d like a PR for these two values, in any case I’m leaving them here for other people with a Sensys HD thermostat

r,energymgr,z1_room_temp_sensys_hd,Z1 Room Temp,70,fe,2010,7118,,s,SIN,10,°C
r,energymgr,z1_room_humi,Z1 Room Humi,13,fe,2010,c9c1,,s,UIN,,%

While looking to integrate a thermostat entity, I noticed that each time I tried to set number.ebusd_energymgr_ebusd_energymgr_z1_cool_setpoint_temp_set or number.ebusd_energymgr_ebusd_energymgr_z1_heat_setpoint_temp_set nothing changed and neither there’s a log. What could I do to make it work?
sensor.ebusd_energymgr_ebusd_energymgr_z1_setpoint_temp receives the values correctly but the two numbers stays blank. Maybe I should look for different values also for them?

Edit:
Unluckily I’m not able to send more than 3 post as a new user.
Btw, @ilgio I had this sort of problems when the board was using power from the eBus, is your using an external power supply (like a Type-C)?



Freezed

Already answered:

Have you tested as I suggested to add the USB power to the adatper?.

And in general, please, if you want help you need to give context. I’m not a mind reader, although I’d like to be able to do it…

This integration is a nerdy one, not an off the shelf product that simply just plugs and plays.
If you want that kind of “error proof” stick with the Ariston App, that is guaranteed to be working. Sorry for being blunt.

Hi,
there is a misunderstading, the parameters you’re changing are not the Z1 desired room temp setpoints. These are the HVAC LWT water temp FIXED setpoint. If you have your HVAC system set to run at a fixed LWT setpoint these are the values you must set in advance, one for heating, the other for cooling.

If you want to act on the desired room temp you should modify z1_day_temp and z1_night_temp.

on the basis of the schedule you set on the Sensys the system decide if it needs to use the day temp or the night one, and then it broadcast the current room temp setpoint (z1_setpoint_temp, code 6571).
You MUST NOT change directly the 6571 parameter as it will undoubtedly be change soon after at the next calculation.

Ooops, my bad :sweat_smile:
Thanks again!

Hi everyone,

anyone here has experience with an Ariston Nimbus Pocket M Net system? I am in the point of receiving data via ebusd but certain messages are not understood yet.

What I receive via ebusd is the following:

docker run --rm -it -p 8888 -v /home/m4271n/proj/ebusd-configuration-ariston-bridgenet:/opt/ariston_config --name=ebusd john30/ebusd --scanconfig -d ens:192.168.0.15:9999 --latency=120 --configpath=/opt/ariston_config
2024-11-01 16:44:46.400 [bus notice] device status: transport opened
2024-11-01 16:44:46.400 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 192.168.0.15:9999, TCP, enhanced
2024-11-01 16:44:46.431 [bus notice] bus started with own address 31/36
2024-11-01 16:44:46.431 [bus notice] device status: reset, supports info
2024-11-01 16:44:46.431 [bus notice] signal acquired
2024-11-01 16:44:46.434 [bus notice] device status: extra info: firmware 1.1[4819].1[4819], jumpers 0x0b
2024-11-01 16:44:46.833 [bus notice] new master 13, master count 2
2024-11-01 16:44:46.848 [update notice] received unknown MS cmd: 131e20200dc33efbc44664cd46006a475802 / 00
2024-11-01 16:44:47.082 [update notice] received unknown MS cmd: 131e20200dce9c78d09c00d89c01659f3200 / 00
2024-11-01 16:44:47.185 [update notice] received unknown MS cmd: 131e202003d5f000 / 00
2024-11-01 16:44:47.389 [update notice] received unknown MS cmd: 131e20200c0b45001745001a45001ef300 / 00
2024-11-01 16:44:47.697 [bus notice] new master 10, master count 3
2024-11-01 16:44:47.698 [update notice] received unknown MS cmd: 1018200008160318031c11d140 / 050f00000007
2024-11-01 16:44:47.799 [update notice] received unknown BC cmd: 13fe20100cc2000000c74bbe00c94b0000
2024-11-01 16:44:48.866 [update notice] received update-read ignored ign5 QQ=10: 
2024-11-01 16:44:49.027 [bus notice] max. symbols per second: 135
2024-11-01 16:44:49.866 [update notice] received update-read ignored ign4 QQ=10: 
2024-11-01 16:44:50.031 [bus notice] new master 00, master count 4
2024-11-01 16:44:50.031 [update notice] received unknown BC cmd: 00fe203a011e
2024-11-01 16:44:50.807 [bus notice] new master 7f, master count 5
2024-11-01 16:44:50.807 [update notice] received unknown MS cmd: 1084200008d140cc4bc89ccc9a / 050f01020000
2024-11-01 16:44:51.195 [update notice] received unknown BC cmd: 7ffe2020030e9000
2024-11-01 16:44:51.320 [update notice] received unknown BC cmd: 7ffe207309000000000000000006
2024-11-01 16:44:51.895 [update notice] received unknown MS cmd: 131e20200dc33ef7c44664cd46006a475802 / 00
2024-11-01 16:44:52.067 [update notice] received unknown MS cmd: 131e20200dce9c78d09c00d89c01659f3200 / 00
2024-11-01 16:44:52.162 [update notice] received unknown MS cmd: 131e202003d5f000 / 00
2024-11-01 16:44:52.362 [update notice] received unknown MS cmd: 131e20200c0b45001745001a45001ef300 / 00
2024-11-01 16:44:52.720 [update notice] received unknown BC cmd: 13fe20100cc2000000c74bbe00c94b0000
2024-11-01 16:44:53.091 [update notice] received update-read energymgr heat_request: off;off;off
2024-11-01 16:44:53.243 [update notice] received update-read ignored ign6 QQ=13: 
2024-11-01 16:44:53.485 [update notice] received unknown MS cmd: 131e2000086e13ca46cb46d84b / 060f00000f0013
2024-11-01 16:44:53.755 [update notice] received read heatpump heatpump_flow_switch QQ=13: open
2024-11-01 16:44:55.867 [update notice] received update-read ignored ign5 QQ=10: 
2024-11-01 16:44:56.432 [main notice] starting initial broadcast scan
2024-11-01 16:44:56.518 [update notice] sent unknown BC cmd: 31fe07fe00
2024-11-01 16:44:56.863 [update notice] received unknown MS cmd: 131e20200dc33ef3c44664cd46006a475802 / 00
2024-11-01 16:44:56.950 [update notice] received update-read ignored ign4 QQ=10: 
2024-11-01 16:44:57.083 [update notice] received unknown MS cmd: 131e20200dce9c78d09c00d89c01659f3200 / 00
2024-11-01 16:44:57.177 [update notice] received unknown MS cmd: 131e202003d5f000 / 00

I am using the configuration from GitHub - wrongisthenewright/ebusd-configuration-ariston-bridgenet: Ebusd Configuration file for Ariston/Chaffoteaux/Elco Bridgenet Bus but I assume that I have to adapt it to my system, right? Do you have an suggestion how to proceed with this?

Thanks for the info.

sorry i didn’t mean to make you angry,
the work you did is fantastic and i thank you so much.
tomorrow i will try to connect the usb power supply.
thanks again

I assure you that I wasn’t angry, I was simply stating that this integration is not really plug and play and probably never will be.
It seems that every Ariston/Chaffoteaux/Elco BusBridgenet combination of devices and FW version change some message, or it may be that we weren’t able to reverse engineer it correctly. Almost every installation needs adjustment and customizations.

This first leads to the need of more details in the help requests. A post that says “It does’nt work” simply won’t lead you any nearer to the solution because at least I’ll need logs, message dumps etc. to be able to help .

Second, if you need something stable, that simply works “everytime” then the only way that I know is the native mobile app. That will be working as long as Ariston keeps it alive.

I’ll add a note in the OP

Hi,
my CSV isn’t able to decode all the messages traveling on the bus. the reasons are multiple:

  1. some messages are related to unknown parameters
  2. some messages are related to parameters alredy decoded by other lines in the CSV
  3. some messages are not decodable by ebusd because there are limits in its configuration (same source, destination, PBSB but different parameter codes)
  4. unknown strcture etc…

I’m happy with the results form my system configuration but, if you’re not, then I’d start to see what is correctly grabbed and see what you miss, then start from there.

I see from rhe brief log that you have a device in your bus network that has master address 0x10, I haven’t such device. One investigtion could be to identify its’ role, issue a ebusctl info command and then disconnect from the bus (or power off) a single device at time (start with the termostat/system interface, then to the wifi GW, then the boiler, then the HP (obviously don’t disconnect the one at which you connected the adapter) and restart ebusd, then issue a ebusctl info command and see what master address is missing.

EDIT: working on a hint, 0x10 could be the master address of the control interface (Sensys for Ariston brand) you can try to adapt my file changing the 0x70 address to 0x10 in the file, only in the portion of the CSV lines where sender and receiver addresses are specified eg change

b,broadcast,gw_serial_number,GWSerial,70,fe,2031,,value,m,STR:12
b,heatpump,water_pump_info,Heatpump Water Pump Data,70,18,2000,c2000601,,s,IGN:1,,,,main_pump_status,s,BCD,0=off;1=on,,,heat_dhw_valve_mode,s,BCD,0=dhw;1=heat

to

b,broadcast,gw_serial_number,GWSerial,10,fe,2031,,value,m,STR:12
g,heatpump,water_pump_info,Heatpump Water Pump Data,10,18,2000,c2000601,,s,IGN:1,,,,main_pump_status,s,BCD,0=off;1=on,,,heat_dhw_valve_mode,s,BCD,0=dhw;1=heat

and see what happens

I tried connecting a 5v 1A USB power supply. but it continues to initialize and recognize the device

How is the WiFi coverage where you placed the adapter? Can you improve it moving the adapter nearer to the router?
Can you check the WiFi latency (ping adapter-IP)?

the wifi, it receives quite well


Screenshot 2024-11-04 alle 10.16.47

Hi,
the wifi coverage where the adapter is placed is not as good as ou think. The reason for this is that altough you’re not losing any ping request the latency (time=xxx last column ot the pings) is on average more than 50ms, some even over 100ms.

I’m not a real expert but eBus (the bus protocol, not the software that is ebusd) is a real time protocol where latencies have a direct role in the functioning of the system.
Based on how ebusd is functioning every single byte that travel on the bus, even the ones that are sent betweeen “Ariston” devices, is sent by the adapter via Wifi to the ebusd daemon, there it get translated and if needed a reply is sent back.

What I think it’s happening in your case is that in some instance the ebus protocol waits a reply from ebusd (that has it’s own master address on the bus) and didn’t get a reply in time, after some retry the bus start a full discovery. In my case, with a similar configuration (adapter with very high latencies) this discovery did not end/hang and I was required to disconnect the adapter from the bus and restart everything with a power cycle.

Since then I’ve moved the adapter from the technical room, where it was connected to the boiler, and placed it inside the apartement, connected to the Sensys. Now I have very low latencies (below 1.5ms on average) and, in addition to the USB power to the adapter, this completely solved my reconfiguration/discovery problems.

PING 192.168.1.167 (192.168.1.167) 56(84) bytes of data.
64 bytes from 192.168.1.167: icmp_seq=1 ttl=64 time=1.69 ms
64 bytes from 192.168.1.167: icmp_seq=2 ttl=64 time=1.64 ms
64 bytes from 192.168.1.167: icmp_seq=3 ttl=64 time=1.55 ms
64 bytes from 192.168.1.167: icmp_seq=4 ttl=64 time=1.42 ms
64 bytes from 192.168.1.167: icmp_seq=5 ttl=64 time=1.65 ms
64 bytes from 192.168.1.167: icmp_seq=6 ttl=64 time=1.44 ms
64 bytes from 192.168.1.167: icmp_seq=7 ttl=64 time=1.48 ms
64 bytes from 192.168.1.167: icmp_seq=8 ttl=64 time=1.51 ms
64 bytes from 192.168.1.167: icmp_seq=9 ttl=64 time=1.49 ms
64 bytes from 192.168.1.167: icmp_seq=10 ttl=64 time=1.62 ms

If you have the adapter near the boiler or near the HP I think you should do as I did and move the adapter nearer to the wifi router, try to get a rssi of about -50dbm (mine is -52dBm), the lower (in absolute valute) the better.

how do you reset it?
it only connects to a farther ubiquiti AP, I can’t figure out why it doesn’t connect to the closest ubiquiti AP

If you’re asking how to reset the adapter, the only way I know is to power cycle it (remove power)
If you instead are asking on how to factory reset it there should be instructions on Daniel esp ebus GitHub repository. when I used the same adapter I used a empty tin can and inserted the adapter inside the can during a power cycle. The adapter started it’s one AP

Config reset

  • check which RESET_PIN is used in your adapter (see hardware revisions)

    • note: RESET_PIN has been changing in different software versions. The defined value refers to latest software revision. If the value doesn’t work, you may try also pin ESP-RX/FROM-EBUS
  • disconnect device from bus

  • connect RESET_PIN and GND pins using a wire

  • connect device to bus

  • wait 5 seconds

  • disconnect the wire

  • RESET_PIN: TO-EBUS (GPIO20)


I have the same revision and I’m able to change the Wi-Fi network from the web interface