All entities unavailable. about ariston-remotethermo-home-assistant-v3 HOT 66 CLOSED

I started working on an MQTT broker emulating the official one. I'll share it on Github, if I succeed.

from ariston-remotethermo-home-assistant-v3.

The following worked for me with my Velis Evo. First step is disabling the Ariston integration for about 2 hours and don't use the Ariston App in this time frame. Then enable it and make sure it's working again. After that apply the suggested scan intervals as mentioned above 180/60/600. The integration works for me now without spitting out the 429 exception for 15 hours. It seems Ariston has implemented a connection limit for device status requests on a time basis. Changing the ISP IP address didn't solve the problem so it must be a counter for each request that resets after an amount of time. In my opinion this makes sense to maintain the service and protect the Ariston Gateway from DoS attacks or excessive usage.

from ariston-remotethermo-home-assistant-v3.

from ariston-remotethermo-home-assistant-v3.

I started working on an MQTT broker emulating the official one. I'll share it on Github, if I succeed.

https://github.com/irsl/broker-ari

from ariston-remotethermo-home-assistant-v3.

same problem, I heard from ARISTON support, I was told they have no problems

from ariston-remotethermo-home-assistant-v3.

What is your recommended way to do that?

There are a couple of options.

1. When you enroll your device to the cloud using the official mobile phone app, you can choose whether you want to use DHCP or static IP configuration. If you select the static one, you should be able to specify DNS addresses. I didn't test this though.

2. To serve DNS, you can also use a proper DNS resolver, e.g. dnsmasq. It is able to resolve addresses and override certain entries. E.g. in this case a config entry would look like this:

address=/broker-ari.everyware-cloud.com/10.6.8.146

The con here is, it requires operating a DNS server on your network.

3. If you have a more powerful router, e.g. OpenWRT, then it could already feature overriding certain entries.

I need to set something in the real cloud and from the response I can see the parameters

Right, that's the way to learn which MQTT topics the official broker dispatches the actions to, and how the payload looks like.
There are so many different products and features, I already lost the motivation to reverse engineer everything properly:)

from ariston-remotethermo-home-assistant-v3.

Hi @irsl!

That's amazing! I really like the concept. I was able to run and even debug the project in my docker environment. Unfortunately I am not familiar with Go language nor MQTT, but I think I understand (almost) everything.

I have two questions:

1. I have VELIS Evo2 | Model 4 device and the "T_22.*" parameters are all 0. How can I find the correct polling parameters for my device? https://github.com/irsl/broker-ari/blob/c6d115be4684a1693a8ce3482a061ab2e9e08728/mqtt.go#L208
2. "You may do that by configuring static IP settings on the appliance and set the DNS resolver to the IP address where the DNS server of this software is listening" What is your recommended way to do that? I changed my DHCP in my router to serve my IP address as a DNS server, but that changed for all my network devices. How can I set only for my appliance?

You could add a new wifi router to your network and connect your Ariston-appliance to the new router and serve your IP address.

Something like this: Internet <-> WAN-router1-LAN <-> WAN-Router2-wifi <-----> appliance.

from ariston-remotethermo-home-assistant-v3.

One doesn't pay for a wifi module to face a 6 min lag with the updates. Vendors should not be allowed to sell products/services with limitations like this. The EU should pay attention to IoT instead of the damn cookie popups.

Idea: we could have a pool of credentials used in round robin manner having almost realtime updates again ;) this could probably be implemented as a simple proxy transparently to this integration.

from ariston-remotethermo-home-assistant-v3.

Nobody can make a guide for the broker for noobs? Please help us.

In a few steps:

• Clone the repository or download it
• Open a terminal and change the folder inside the broker-ari folder
• Install Go, minimum version 1.21
• Run inside your terminal these two commands go install google.golang.org/protobuf/cmd/[email protected] and go install -v github.com/go-delve/delve/cmd/dlv@latest
• Run CGO_ENABLED=0 go build -v -o broker-ari
• Create the SSL certs with openssl (make sure to have it installed)

openssl req -nodes -x509 -sha256 -newkey rsa:2048 \
  -keyout  broker-ari.everyware-cloud.com.key \
  -out  broker-ari.everyware-cloud.com.crt \
  -days 356 \
  -subj "/C=NL/ST=Zuid Holland/L=Rotterdam/O=ACME Corp/OU=IT Dept/CN=broker-ari.everyware-cloud.com"  \
  -addext "subjectAltName = DNS:broker-ari.everyware-cloud.com" 

• Copy the folder config from broker-ari into /
• Edit the config.json according to the previous post editing the ips with your machine one and the python-ariston-api's config

You should also reset your appliance and set a static address instead of DHCP, making sure to set the DNS to the machine's IP in which is running broker-ari

from ariston-remotethermo-home-assistant-v3.

It's really unbelievable. Main app is still down after so many days. The web interface however still seems to work.

You must disable the integration in HA.
And wait 2 hours
Because the integration still try to connect to the API and block the connection.

from ariston-remotethermo-home-assistant-v3.

I started working on an MQTT broker emulating the official one. I'll share it on Github, if I succeed.

https://github.com/irsl/broker-ari

Good idea irls!
Good luck
I wait for more news.

from ariston-remotethermo-home-assistant-v3.

Disable the integration for about 2 hours, not using the Ariston App and Try 400, 60, 800, it's works for me no error since 4 days.
I also disable the entities that I don't need, the energy ones.

Actually, this one worked just fine for me. Thank you!

from ariston-remotethermo-home-assistant-v3.

Hi emanueldobrin
How do you do your nice gauge?

Edit gauge from the dashboard -> Show code editor -> insert the one from below. Be careful at indentation.

`type: gauge
entity: sensor.ariston_outside_temp
name: Outside Temp
needle: true
min: -20
max: 50
color gradient: true
segments:

• color: '#2B00FF'
  from: -20
  to: -19.31
• color: '#2907FF'
  from: -19.31
  to: -18.62
• color: '#280EFF'
  from: -18.62
  to: -17.93
• color: '#2616FF'
  from: -17.93
  to: -17.24
• color: '#251DFF'
  from: -17.24
  to: -16.55
• color: '#2324FF'
  from: -16.55
  to: -15.86
• color: '#222CFF'
  from: -15.86
  to: -15.17
• color: '#2033FF'
  from: -15.17
  to: -14.48
• color: '#1F3AFF'
  from: -14.48
  to: -13.79
• color: '#1D42FF'
  from: -13.79
  to: -13.1
• color: '#1C49FF'
  from: -13.1
  to: -12.41
• color: '#1A50FF'
  from: -12.41
  to: -11.72
• color: '#1958FF'
  from: -11.72
  to: -11.03
• color: '#175FFF'
  from: -11.03
  to: -10.34
• color: '#1666FF'
  from: -10.34
  to: -9.66
• color: '#146EFF'
  from: -9.66
  to: -8.97
• color: '#1375FF'
  from: -8.97
  to: -8.28
• color: '#117CFF'
  from: -8.28
  to: -7.59
• color: '#1084FF'
  from: -7.59
  to: -6.9
• color: '#0E8BFF'
  from: -6.9
  to: -6.21
• color: '#0D92FF'
  from: -6.21
  to: -5.52
• color: '#0B9AFF'
  from: -5.52
  to: -4.83
• color: '#0AA1FF'
  from: -4.83
  to: -4.14
• color: '#08A8FF'
  from: -4.14
  to: -3.45
• color: '#07B0FF'
  from: -3.45
  to: -2.76
• color: '#05B7FF'
  from: -2.76
  to: -2.07
• color: '#04BEFF'
  from: -2.07
  to: -1.38
• color: '#02C6FF'
  from: -1.38
  to: -0.69
• color: '#01CDFF'
  from: -0.69
  to: 0
• color: '#00D5FF'
  from: 0
  to: 0.17
• color: '#00D6F6'
  from: 0.17
  to: 0.34
• color: '#01D7ED'
  from: 0.34
  to: 0.52
• color: '#01D9E4'
  from: 0.52
  to: 0.69
• color: '#02DADB'
  from: 0.69
  to: 0.86
• color: '#02DCD3'
  from: 0.86
  to: 1.03
• color: '#03DDCA'
  from: 1.03
  to: 1.21
• color: '#04DFC1'
  from: 1.21
  to: 1.38
• color: '#04E0B8'
  from: 1.38
  to: 1.55
• color: '#05E2AF'
  from: 1.55
  to: 1.72
• color: '#05E3A7'
  from: 1.72
  to: 1.9
• color: '#06E49E'
  from: 1.9
  to: 2.07
• color: '#07E695'
  from: 2.07
  to: 2.24
• color: '#07E78C'
  from: 2.24
  to: 2.41
• color: '#08E983'
  from: 2.41
  to: 2.59
• color: '#08EA7B'
  from: 2.59
  to: 2.76
• color: '#09EC72'
  from: 2.76
  to: 2.93
• color: '#09ED69'
  from: 2.93
  to: 3.1
• color: '#0AEF60'
  from: 3.1
  to: 3.28
• color: '#0BF057'
  from: 3.28
  to: 3.45
• color: '#0BF14F'
  from: 3.45
  to: 3.62
• color: '#0CF346'
  from: 3.62
  to: 3.79
• color: '#0CF43D'
  from: 3.79
  to: 3.97
• color: '#0DF634'
  from: 3.97
  to: 4.14
• color: '#0EF72B'
  from: 4.14
  to: 4.31
• color: '#0EF923'
  from: 4.31
  to: 4.48
• color: '#0FFA1A'
  from: 4.48
  to: 4.66
• color: '#0FFC11'
  from: 4.66
  to: 4.83
• color: '#10FD08'
  from: 4.83
  to: 5
• color: '#11FF00'
  from: 5
  to: 5.17
• color: '#19FF00'
  from: 5.17
  to: 5.34
• color: '#21FF00'
  from: 5.34
  to: 5.52
• color: '#29FF00'
  from: 5.52
  to: 5.69
• color: '#31FF00'
  from: 5.69
  to: 5.86
• color: '#39FF00'
  from: 5.86
  to: 6.03
• color: '#41FF00'
  from: 6.03
  to: 6.21
• color: '#49FF00'
  from: 6.21
  to: 6.38
• color: '#51FF00'
  from: 6.38
  to: 6.55
• color: '#59FF00'
  from: 6.55
  to: 6.72
• color: '#61FF00'
  from: 6.72
  to: 6.9
• color: '#69FF00'
  from: 6.9
  to: 7.07
• color: '#71FF00'
  from: 7.07
  to: 7.24
• color: '#79FF00'
  from: 7.24
  to: 7.41
• color: '#81FF00'
  from: 7.41
  to: 7.59
• color: '#8AFF00'
  from: 7.59
  to: 7.76
• color: '#92FF00'
  from: 7.76
  to: 7.93
• color: '#9AFF00'
  from: 7.93
  to: 8.1
• color: '#A2FF00'
  from: 8.1
  to: 8.28
• color: '#AAFF00'
  from: 8.28
  to: 8.45
• color: '#B2FF00'
  from: 8.45
  to: 8.62
• color: '#BAFF00'
  from: 8.62
  to: 8.79
• color: '#C2FF00'
  from: 8.79
  to: 8.97
• color: '#CAFF00'
  from: 8.97
  to: 9.14
• color: '#D2FF00'
  from: 9.14
  to: 9.31
• color: '#DAFF00'
  from: 9.31
  to: 9.48
• color: '#E2FF00'
  from: 9.48
  to: 9.66
• color: '#EAFF00'
  from: 9.66
  to: 9.83
• color: '#F2FF00'
  from: 9.83
  to: 10
• color: '#FBFF00'
  from: 10
  to: 10.38
• color: '#FBF800'
  from: 10.38
  to: 10.77
• color: '#FBF100'
  from: 10.77
  to: 11.15
• color: '#FBEB00'
  from: 11.15
  to: 11.54
• color: '#FBE400'
  from: 11.54
  to: 11.92
• color: '#FBDE00'
  from: 11.92
  to: 12.31
• color: '#FBD700'
  from: 12.31
  to: 12.69
• color: '#FBD100'
  from: 12.69
  to: 13.08
• color: '#FBCA00'
  from: 13.08
  to: 13.46
• color: '#FBC400'
  from: 13.46
  to: 13.85
• color: '#FCBD00'
  from: 13.85
  to: 14.23
• color: '#FCB700'
  from: 14.23
  to: 14.62
• color: '#FCB000'
  from: 14.62
  to: 15
• color: '#FCAA00'
  from: 15
  to: 15.38
• color: '#FCA300'
  from: 15.38
  to: 15.77
• color: '#FC9C00'
  from: 15.77
  to: 16.15
• color: '#FC9600'
  from: 16.15
  to: 16.54
• color: '#FC8F00'
  from: 16.54
  to: 16.92
• color: '#FC8900'
  from: 16.92
  to: 17.31
• color: '#FC8200'
  from: 17.31
  to: 17.69
• color: '#FD7C00'
  from: 17.69
  to: 18.08
• color: '#FD7500'
  from: 18.08
  to: 18.46
• color: '#FD6F00'
  from: 18.46
  to: 18.85
• color: '#FD6800'
  from: 18.85
  to: 19.23
• color: '#FD6200'
  from: 19.23
  to: 19.62
• color: '#FD5B00'
  from: 19.62
  to: 20
• color: '#FD5500'
  from: 20
  to: 20.38
• color: '#FD4E00'
  from: 20.38
  to: 20.77
• color: '#FD4700'
  from: 20.77
  to: 21.15
• color: '#FD4100'
  from: 21.15
  to: 21.54
• color: '#FE3A00'
  from: 21.54
  to: 21.92
• color: '#FE3400'
  from: 21.92
  to: 22.31
• color: '#FE2D00'
  from: 22.31
  to: 22.69
• color: '#FE2700'
  from: 22.69
  to: 23.08
• color: '#FE2000'
  from: 23.08
  to: 23.46
• color: '#FE1A00'
  from: 23.46
  to: 23.85
• color: '#FE1300'
  from: 23.85
  to: 24.23
• color: '#FE0D00'
  from: 24.23
  to: 24.62
• color: '#FE0600'
  from: 24.62
  to: 25
• color: '#FF0000'
  from: 25
  to: 26.43
• color: '#FF000B'
  from: 26.43
  to: 27.86
• color: '#FF0017'
  from: 27.86
  to: 29.29
• color: '#FF0022'
  from: 29.29
  to: 30.71
• color: '#FF002E'
  from: 30.71
  to: 32.14
• color: '#FF0039'
  from: 32.14
  to: 33.57
• color: '#FF0045'
  from: 33.57
  to: 35
• color: '#FF0051'
  from: 35
  to: 36.43
• color: '#FF005C'
  from: 36.43
  to: 37.86
• color: '#FF0068'
  from: 37.86
  to: 39.29
• color: '#FF0073'
  from: 39.29
  to: 40.71
• color: '#FF007F'
  from: 40.71
  to: 42.14
• color: '#FF008A'
  from: 42.14
  to: 43.57
• color: '#FF0096'
  from: 43.57
  to: 45
• color: '#FF00A2'
  from: 45
  to: null
  `

from ariston-remotethermo-home-assistant-v3.

The service has been completely down for me for for days. This is after increasing the polling interval had resolved the issue to an acceptable level.

Under the hood, now I see them returning the following internal error:

GET https://www.ariston-net.remotethermo.com/api/v2/velis/sePlantData/80646FEA7AEC/plantSettings
b'":-( M2M platform error from 80[redacted]EC (Http status: 0 - Timeout) (FailureId: 170624154834)"'

Has anyone else seen the same? Any ideas? (Besides using my own broker?) I feel I got blacklisted.

from ariston-remotethermo-home-assistant-v3.

With the help of 5 guest accounts, I'm at 60 second polling again, so far so good ;) https://github.com/irsl/pool-ari

from ariston-remotethermo-home-assistant-v3.

I was playing with your code. Now it works perfectly fine with my velis evo2 device. 30/30/600 Except the bus errors. I don't understand how it works, but I don't really need it.

This is awesome! Have you got time/motivation to implement support for additional models as well? With the help of users of course, e.g. if they provide the T ids with example values for their model.

https://github.com/fustom/broker-ari/tree/support_lydos_hybrid

from ariston-remotethermo-home-assistant-v3.

https://github.com/fustom/broker-ari/tree/support_lydos_hybrid

I just gave it a try; the features I tested were working correctly. I'll wait a bit more for some additional userbase before I switch to using it permanently :)

from ariston-remotethermo-home-assistant-v3.

https://github.com/fustom/broker-ari/tree/support_lydos_hybrid

I just gave it a try; the features I tested were working correctly. I'll wait a bit more for some additional userbase before I switch to using it permanently :)

Hello irsl,
Can you tell us a detailed explanation of how you have implemented your solution, because many of us are noobs.
I try myself but I am lost.
Thanks in advance

The link won't work

from ariston-remotethermo-home-assistant-v3.

No problem, feel free to ask if something isn't clear!

Also, if I did something wrong, feel free to correct me c:

from ariston-remotethermo-home-assistant-v3.

I got the same problem right now.
When I try to open the url https://www.ariston-net.remotethermo.com/api/v2/ I'm getting an error 404

from ariston-remotethermo-home-assistant-v3.

hi. i have the same problem right now

from ariston-remotethermo-home-assistant-v3.

I think that the Ariston service is either broken or there was an update of the API version

from ariston-remotethermo-home-assistant-v3.

I hope the problem will be corrected quickly. on the other hand I can access the web interface without problem.

from ariston-remotethermo-home-assistant-v3.

#331 (comment)

from ariston-remotethermo-home-assistant-v3.

Hi,
With the settings proposed here the problem persist.

from ariston-remotethermo-home-assistant-v3.

The suggested scan intervals of 180/60/600 might be the reason if you have only one device. However, in my case, I have three Ariston devices, and the problem still persists.

from ariston-remotethermo-home-assistant-v3.

The main app is also broken. It's likely a service outage

It's really unbelievable. Main app is still down after so many days. The web interface however still seems to work.

from ariston-remotethermo-home-assistant-v3.

It's really unbelievable. Main app is still down after so many days. The web interface however still seems to work.

You must disable the integration in HA. And wait 2 hours Because the integration still try to connect to the API and block the connection.

I agree the solution at this moment is in slowing down. I doubled the time values in the config and during the last hour I did get responses. Still too early to draw conclusions.

from ariston-remotethermo-home-assistant-v3.

I increased to the suggested 180/50/600

Also switched off some time.

Now the “available” times are longer, but not always.

What is the strangest to me is the irregularity in the available / unavailable timeslots.

from ariston-remotethermo-home-assistant-v3.

same problem, I heard from ARISTON support, I was told they have no problems

It's really unbelievable. Main app is still down after so many days. The web interface however still seems to work.

You must disable the integration in HA. And wait 2 hours Because the integration still try to connect to the API and block the connection.

I agree the solution at this moment is in slowing down. I doubled the time values in the config and during the last hour I did get responses. Still too early to draw conclusions.

In the last 24 hours it switched online/offline 27 times. So I guess playing with the config values in fact doesn't solve anything.

from ariston-remotethermo-home-assistant-v3.

I tried increasing the scan, now let's see how it goes

from ariston-remotethermo-home-assistant-v3.

Hello,

I'm with the configuration below but still get errors. How is this working for you? Is there any solution?

from ariston-remotethermo-home-assistant-v3.

Hello,

I'm with the configuration below but still get errors. How is this working for you? Is there any solution?

Disable the integration for about 2 hours, not using the Ariston App and Try 400, 60, 800, it's works for me no error since 4 days.
I also disable the entities that I don't need, the energy ones.

from ariston-remotethermo-home-assistant-v3.

Hi @irsl!

That's amazing! I really like the concept. I was able to run and even debug the project in my docker environment. Unfortunately I am not familiar with Go language nor MQTT, but I think I understand (almost) everything.

I have two questions:

1. I have VELIS Evo2 | Model 4 device and the "T_22.*" parameters are all 0. How can I find the correct polling parameters for my device? https://github.com/irsl/broker-ari/blob/c6d115be4684a1693a8ce3482a061ab2e9e08728/mqtt.go#L208
2. "You may do that by configuring static IP settings on the appliance and set the DNS resolver to the IP address where the DNS server of this software is listening" What is your recommended way to do that? I changed my DHCP in my router to serve my IP address as a DNS server, but that changed for all my network devices. How can I set only for my appliance?

from ariston-remotethermo-home-assistant-v3.

1. Ahh ok. I am stupid. I need to set something in the real cloud and from the response I can see the parameters:
   "2024/05/14 09:08:14 proto decoded as: map[T_18.0.0:1 T_18.0.1:1 T_18.0.2:1 T_18.0.3:0 T_18.1.0:400 T_18.3.0:0 T_18.3.1:1 T_18.3.2:0 T_18.3.3:378 T_18.3.5:0 T_18.3.6:400 response.code:200]"

from ariston-remotethermo-home-assistant-v3.

Disable the integration for about 2 hours, not using the Ariston App and Try 400, 60, 800, it's works for me no error since 4 days.
I also disable the entities that I don't need, the energy ones.

It worked for me for some days, now, since yesterday I'm not able to conect via HA or even the mobile ariston app. Does anyone has the same error or is it working for you?

Of course that I have the integration disabled.

from ariston-remotethermo-home-assistant-v3.

Still works for me.

from ariston-remotethermo-home-assistant-v3.

It worked for me for some days, now, since yesterday I'm not able to conect via HA or even the mobile ariston app. Does anyone has the same error or is it working for you?

I have some errors yesterday afternoon until today afternoon, but now it's working.

from ariston-remotethermo-home-assistant-v3.

Still works for me.

Hi emanueldobrin
How do you do your nice gauge?

from ariston-remotethermo-home-assistant-v3.

That's amazing! I really like the concept. I was able to run and even debug the project in my docker environment. Unfortunately I am not familiar with Go language nor MQTT, but I think I understand (almost) everything.

Hi fustom,
How do you do this,
I created a virtual Docker in my Proxmox server, but I don't know how to use irsl's mqtt broker

from ariston-remotethermo-home-assistant-v3.

For us it wasn't working properly since may 1st.
I can confirm that increasing times to this level makes it work more reliably:

So yes, probably they added some traffic throttling to their API and the default settings poll too frequently. Cheers!

from ariston-remotethermo-home-assistant-v3.

One more idea that could help fighting against this aggressive throttling: creating a dedicated account for the HA integration (so that the official mobile app uses a different one).

from ariston-remotethermo-home-assistant-v3.

@irsl , are they allowing multiple accounts for same appliance?

from ariston-remotethermo-home-assistant-v3.

Edit gauge from the dashboard -> Show code editor -> insert the one from below. Be careful at indentation.

Thank you very much!

from ariston-remotethermo-home-assistant-v3.

@irsl , are they allowing multiple accounts for same appliance?

You can share your appliance with guest accounts and based on the description ("Your guests will be able to manage your appliance") it should work just fine with this integration.

from ariston-remotethermo-home-assistant-v3.

One more idea that could help fighting against this aggressive throttling: creating a dedicated account for the HA integration (so that the official mobile app uses a different one).

Not working with guests email the app won't work when errors 429 in HA.
It's not possible to have two different accounts for one thermostat.

from ariston-remotethermo-home-assistant-v3.

from ariston-remotethermo-home-assistant-v3.

Works with 400,60,800 in configuration.

from ariston-remotethermo-home-assistant-v3.

@irsl , are they allowing multiple accounts for same appliance?

You can share your appliance with guest accounts and based on the description ("Your guests will be able to manage your appliance") it should work just fine with this integration.

To add to this: the guest account first needs to be created on the Ariston or Atag site. No need to add an appliance.
After account creation the account can be added to the Ariston/atag app by it's account email address.

from ariston-remotethermo-home-assistant-v3.

Initially same issues with error 429 here, finally i've done the following:
1 . Created 2 more new accounts at Ariston and associated them as Guest in Main account (Main account only for Web access in case of needed/emergency, 2nd for integration in HA, 3rd account for App)
2. As still having error increased scan intervals to 400,60,800
3. Working well so far

On top of that you can add "Ariston Genus One System 35" to list of working equipment it's working well (let me know if need further details)

from ariston-remotethermo-home-assistant-v3.

https://github.com/irsl/broker-ari

I was playing with your code. Now it works perfectly fine with my velis evo2 device. 30/30/600
Except the bus errors. I don't understand how it works, but I don't really need it.

https://github.com/fustom/broker-ari/tree/support_velis_evo2

When you enroll your device to the cloud using the official mobile phone app, you can choose whether you want to use DHCP or static IP configuration. If you select the static one, you should be able to specify DNS addresses. I didn't test this though.

I use that way to add the DNS server address and it works. :)

from ariston-remotethermo-home-assistant-v3.

I was playing with your code. Now it works perfectly fine with my velis evo2 device. 30/30/600 Except the bus errors. I don't understand how it works, but I don't really need it.

This is awesome! Have you got time/motivation to implement support for additional models as well? With the help of users of course, e.g. if they provide the T ids with example values for their model.

from ariston-remotethermo-home-assistant-v3.

https://github.com/fustom/broker-ari/tree/support_lydos_hybrid

I just gave it a try; the features I tested were working correctly. I'll wait a bit more for some additional userbase before I switch to using it permanently :)

Hello irsl, Can you tell us a detailed explanation of how you have implemented your solution, because many of us are noobs. I try myself but I am lost. Thanks in advance

The link won't work

I would also like a guide on this

from ariston-remotethermo-home-assistant-v3.

https://github.com/fustom/broker-ari

Can confirm that the fork from fustom works very well with my Velis Evo 2. Some rough information about my implementation on Gentoo.

Local Server and Network Gateway 10.10.10.1
Velis Evo 2 Mac ac:67:b2:xx:xx:xx

Init Script
#!/sbin/openrc-run
description="Ariston MQTT Broker"
command="/somepath/ariston/broker-ari"
command_user="${RC_SVCNAME}:${RC_SVCNAME}"
directory="/somepath/ariston"
command_background=yes
pidfile=/run/${RC_SVCNAME}.pid

Iptables
Appropriate Incoming/outgoing rules (123/2080/5300/8883) and DNAT rules
iptables -t nat -A PREROUTING -i br0 -p udp -m mac --mac-source ac:67:b2:xx:xx:xx --dport domain -j DNAT --to 10.10.10.1:5300
iptables -t nat -A PREROUTING -i br0 -p tcp -m mac --mac-source ac:67:b2:xx:xx:xx --dport 8883 -j DNAT --to 10.10.10.1:8883

homeassistant
core.config_entries
"username": "someusername",
"password": "somepassword",
"api_url_setting": "http://10.10.10.1:2080/",

broker-ari
{
"Api_debug": false,
"Api_listener": "10.10.10.1:2080",
"Api_password": "somepassword",
"Api_username": "someusername",
"Dns_listener": "10.10.10.1:5300",
"Dns_resolve_to": "10.10.10.1",
"Ntp_resolve_to": "162.159.200.1",
"Mqtt_broker_certificate_path": "/somepath/ariston/config/server.pem",
"Mqtt_broker_clear_listener": "",
"Mqtt_broker_private_key_path": "/somepath/ariston/config/server.key",
"Mqtt_broker_tls_listener": "10.10.10.1:8883",
"Mqtt_proxy_upstream": "ssl://broker-ari.everyware-cloud.com:8883",
"Poll_frequency": 60,
"Consumption_poll_frequency": 600,
"Devices":
[
{
"GwID": "AC67B2XXXXXX",
"Sys": 4,
"WheType": 6,
"WheModelType": 4,
"Name": "",
"ConsumptionTyp": "2",
"ConsumptionOffset": 0
},
{
"GwID": "",
"Sys": 4,
"WheType": 2,
"Name": "",
"ConsumptionTyp": "7,8",
"ConsumptionOffset": 1
}
]
}

from ariston-remotethermo-home-assistant-v3.

Hi! I just tried with a Nimbus (an heat pump that should be similar to the Galevo) and I wasn't able to set it up.
The DNS should be fine, a nslookup on my laptop works well and resetted the network settings in order to set a static DNS, but the logs and the topics aren't logging anything useful and the integration in HASS says that wasn't able to find devices.

Finally, I wasn't sure about the parameters at the end of the config file:

{
    "GwID": "1C9XXXXXXXXX",
    "Sys": 3,
    "WheType": -1,
    "WheModelType": -1,
    "Name": "",
    "ConsumptionTyp": "1,3",
    "ConsumptionOffset": 0
 }

Probably this isn't supported in the fustom's fork, but I hoped to find anyway something useful inside the available topics

from ariston-remotethermo-home-assistant-v3.

Nobody can make a guide for the broker for noobs?
Please help us.

from ariston-remotethermo-home-assistant-v3.

Nobody can make a guide for the broker for noobs? Please help us.

In a few steps:

• Clone the repository or download it
• Open a terminal and change the folder inside the broker-ari folder
• Install Go, minimum version 1.21
• Run inside your terminal these two commands go install google.golang.org/protobuf/cmd/[email protected] and go install -v github.com/go-delve/delve/cmd/dlv@latest
• Run CGO_ENABLED=0 go build -v -o broker-ari
• Create the SSL certs with openssl (make sure to have it installed)

openssl req -nodes -x509 -sha256 -newkey rsa:2048 \
  -keyout  broker-ari.everyware-cloud.com.key \
  -out  broker-ari.everyware-cloud.com.crt \
  -days 356 \
  -subj "/C=NL/ST=Zuid Holland/L=Rotterdam/O=ACME Corp/OU=IT Dept/CN=broker-ari.everyware-cloud.com"  \
  -addext "subjectAltName = DNS:broker-ari.everyware-cloud.com" 

• Copy the folder config from broker-ari into /
• Edit the config.json according to the previous post editing the ips with your machine one and the python-ariston-api's config

You should also reset your appliance and set a static address instead of DHCP, making sure to set the DNS to the machine's IP in which is running broker-ari

Thank you [domenicoblanco]
I will try

from ariston-remotethermo-home-assistant-v3.

Small update for anyone that's trying something similar: I dug a bit in the logs and noticed that my heat pump is requesting for a different endpoint (connect.iot.remotethermo.com). I was able to receive the requests from the heat pump but I'm unable to resend data into the upstream broker.
Because of this I wasn't able to retrieve the parameters of my heat pump

from ariston-remotethermo-home-assistant-v3.

...a different endpoint (connect.iot.remotethermo.com). I was able to receive the requests from the heat pump ...

Just to avoid misunderstandings: you mean you got some MQTT traffic? If so, would you mind sharing the logs?

from ariston-remotethermo-home-assistant-v3.

When I tried I was able to obtain some messages in the logs like

OnPublish on the local broker by inline: $EDC/ari/mqtt-explorer-76439da9/ar1/GET/Menu/Par, CJOp1Oa63KztF8K4AhAKAlAxEAVCCFRfMTguMC4wwrgCEAoCUDIQBUIIVF8xOC4wLjHCuAIQCgJQMxAFQghUXzE4LjAuMsK4AhAKAlA0EAVCCFRfMTguMC4zwrgCEAoCUDUQBUIIVF8xOC4wLjXCuAIQCgJQNhAFQghUXzE4LjEuMMK4AhAKAlA3EAVCCFRfMTguMS4zwrxOC4zLjDCuAIQCgJQORAFQghUXzE4LjMuMcK4AAhEKA1AxMRAFQghUXzE4LjMuM8K4AhEKA1AxMhAFQghUXzE4LjMuNcK4AhEKA1AxMxAFQghUXzE4LjMuNsK4Ah8KE3JlcXVlc3Rlci5jbGllbnQuaWQQBUIGaW5saW5lwrgCFgoKcmVxdWVzdC5pZBAFQgZwYXJhbXM=
2024/06/20 13:28:18 timestamp:1718882898722231443 params:{key:"P1" something1:5 value_s:"T_18.0.0"} params:{key:"P2" something1:5 value_s:"T_18.0.1"} params:{key:"P3" something1:5 value_s:"T_18.0.2"} params:{key:"P4" something1:5 value_s:"T_18.0.3"} params:{key:"P5" something1:5 value_s:"T_18.0.5"} params:{key:"P6" something1:5 value_s:"T_18.1.0"} params:{key:"P7" something1:5 value_s:"T_18.1.3"} params:{key:"P8" something1:5 value_s:"T_18.3.0"} params:{key:"P9" something1:5 value_s:"T_18.3.1"} params:{key:"P10" something1:5 value_s:"T_18.3.2"} params:{key:"P11" something1:5 value_s:"T_18.3.3"} params:{key:"P12" something1:5 value_s:"T_18.3.5"} params:{key:"P13" something1:5 value_s:"T_18.3.6"} params:{key:"requester.client.id" something1:5 value_s:"inline"} params:{key:"request.id" something1:5 value_s:"params"}

Now I'm noticing that the topic is the one from MQTT Explorer, so either my device isn't using the MQTT broker or is connecting in another way to the official API

Edit:
Of course I had to tweak a bit the code in order to not contact the official broker and prevent the use in any case of the client data stored in ClientsMap

from ariston-remotethermo-home-assistant-v3.

Nobody can make a guide for the broker for noobs? Please help us.

In a few steps:

• Clone the repository or download it
• Open a terminal and change the folder inside the broker-ari folder
• Install Go, minimum version 1.21
• Run inside your terminal these two commands go install google.golang.org/protobuf/cmd/[email protected] and go install -v github.com/go-delve/delve/cmd/dlv@latest
• Run CGO_ENABLED=0 go build -v -o broker-ari
• Create the SSL certs with openssl (make sure to have it installed)

openssl req -nodes -x509 -sha256 -newkey rsa:2048 \
  -keyout  broker-ari.everyware-cloud.com.key \
  -out  broker-ari.everyware-cloud.com.crt \
  -days 356 \
  -subj "/C=NL/ST=Zuid Holland/L=Rotterdam/O=ACME Corp/OU=IT Dept/CN=broker-ari.everyware-cloud.com"  \
  -addext "subjectAltName = DNS:broker-ari.everyware-cloud.com" 

• Copy the folder config from broker-ari into /
• Edit the config.json according to the previous post editing the ips with your machine one and the python-ariston-api's config

You should also reset your appliance and set a static address instead of DHCP, making sure to set the DNS to the machine's IP in which is running broker-ari

I want to install it in a docker container the command wont work: -bash: go: command not found

from ariston-remotethermo-home-assistant-v3.

I want to install it in a docker container the command wont work: -bash: go: command not found
If it's Debian based try with a RUN apt install [email protected] or RUN apt install [email protected]

from ariston-remotethermo-home-assistant-v3.

install [email protected]

Same problem -bash: RUN: command not found

from ariston-remotethermo-home-assistant-v3.

RUN is only if you use in the Dockerfile, if you’re doing it inside an already running container just remove the initial RUN

from ariston-remotethermo-home-assistant-v3.

Now I'm noticing that the topic is the one from MQTT Explorer, so either my device isn't using the MQTT broker or is connecting in another way to the official API

Edit: Of course I had to tweak a bit the code in order to not contact the official broker and prevent the use in any case of the client data stored in ClientsMap

Just checked, connect.iot.remotethermo.com is listening on port 8883 (just like broker-ari.everyware-cloud.com), so with some luck the protocol won't be entirely different. The Lydos devices do verify the common name/SAN of the certificate, but don't have a trust anchor. Did you try generating a certificate with the hostname your heat pump expects?

from ariston-remotethermo-home-assistant-v3.

I tried with

openssl req -nodes -x509 -sha256 -newkey rsa:2048 \
  -keyout  broker-ari.everyware-cloud.com.key \
  -out  broker-ari.everyware-cloud.com.crt \
  -days 356 \
  -subj "/C=NL/ST=Zuid Holland/L=Rotterdam/O=ACME Corp/OU=IT Dept/CN=connect.iot.remotethermo.com"  \
  -addext "subjectAltName = DNS:connect.iot.remotethermo.com" 

But I don't know if it's correct and how to check if the heat pump accepts it, anyway there's another problem with the upstream broker as it refuses my credentials

Edit:
I just googled and found that openssl has something to see more informations about a remote cert. I'll try to generate a new certificate, hoping to receive at least something in my local broker

Edit 2:
Maybe this one could work

openssl req -nodes -x509 -sha256 -newkey rsa:2048 \
  -keyout  broker-ari.everyware-cloud.com.key \
  -out  broker-ari.everyware-cloud.com.crt \
  -days 356 \
  -subj "/C=US/O=Amazon/CN=connect.iot.remotethermo.com"  \
  -addext "subjectAltName = DNS:connect.iot.remotethermo.com"

Edit 3:
It didn't as the heat pump was still reachable from remotenet

Edit 4:
I tried again with the following cert and I still receive listener=t1s error="read connection: remote error: tls: unknown certificate authority"

openssl genrsa -out private.key 2048 \
&& openssl req -new -key private.key -out certificate.csr -subj "/C=US/O=Amazon/CN=iot.remotethermo.com" \
&& echo -e "[req]\ndistinguished_name = req_distinguished_name\nx509_extensions = v3_ca\nprompt = no\n[req_distinguished_name]\nC = US\nO = Amazon\nCN = Amazon RSA 2048 M02\n[v3_ca]\nbasicConstraints = CA:TRUE\nsubjectKeyIdentifier = hash\nauthorityKeyIdentifier = keyid:always,issuer:always" > ca.conf \
&& openssl req -x509 -new -nodes -key private.key -days 365 -out ca.crt -config ca.conf \
&& openssl x509 -req -in certificate.csr -CA ca.crt -CAkey private.key -CAcreateserial -out certificate.crt -days 365 -extfile ca.conf -extensions v3_ca

Probably it checks the trustchain and it will not work with this method :/

from ariston-remotethermo-home-assistant-v3.