Thank you for your extensive example.
It works great! now I can heat my water through solar panels.
If the temperature is too low, the gas boiler takes over.
1 Like
Thanks! That is greath! Can you share your cards config?
Really great stuff. I will have a look at how an integration should look like, and what is needed for it.
As I have no boiler/heater yet, it will be difficult to test. I will have a first look at simulating a boiler. Maybe I can find the Tesy firmware, and put it in an ESP device have a stub test device.
Hi Jos,what type Tesy boiler/heater do you own? Is it the same one (Modeco cloud)?
Hi William,
Great, I did not find out how to send commands towards the boiler.
Thanks a lot!
Is there a specific reason that you chose to use an automation for rest?
I found out that the boiler didn’t like a lot of frequent rest commands (I used to have each attribute in a seperate entity). Had to turn it off every 2 to 3 weeks because it became unresponsive.
I use this currently:
- platform: rest
name: boiler
resource: http://boiler/status
json_attributes:
- gradus
- ref_gradus
- heater_state
- boost
- power_sw
value_template: "{{ value_json.boiler }}"
scan_interval: 60
- platform: template
sensors:
gradus:
friendly_name: "Huidige temperatuur"
value_template: "{{ state_attr('sensor.boiler', 'gradus') }}"
device_class: temperature
unit_of_measurement: "°C"
ref_gradus:
friendly_name: "Ingestelde temperatuur"
value_template: "{{ state_attr('sensor.boiler', 'ref_gradus') }}"
device_class: temperature
unit_of_measurement: "°C"
heater_state:
friendly_name: "Verwarm status"
value_template: "{{ state_attr('sensor.boiler', 'heater_state') }}"
boost:
friendly_name: "Boost status"
value_template: "{{ state_attr('sensor.boiler', 'boost') }}"
power_sw:
friendly_name: "Apparaat status"
value_template: "{{ state_attr('sensor.boiler', 'power_sw') }}"
- platform: rest
name: boiler_power
resource: http://boiler/calcRes
value_template: '{{ value_json.sum | title }}'
scan_interval: 60
- platform: template
sensors:
boiler_power_usage:
friendly_name: "Totaal stroomverbruik boiler"
unit_of_measurement: 'kWh'
device_class: power
icon_template: mdi:power-plug
value_template: "{{ ((states('sensor.boiler_power') | float / 3600000) * 2400) | round(2) }}"
And to get it on the energy dashboard, I use an utility meter
utility_meter:
daily_energy:
name: boiler_energy-daily
source: sensor.boiler_power_usage
cycle: daily
net_consumption: false
Regarding the power calculation, I think you have a newer (firmware) version.
My boiler has a weird calculation of power usage, hence the calculation in the template
It is formatted like this (output from /calcRes)
{"sum":"1695972","resetDate":"2022-01-01 02:43:41","volume":"100","watt":"2400"}
My latest yaml can be found here:
I use rest because it is what the app and the webinterface are using if you go to the local IP, And it spams the boiler if you look at the traffic!
So unless you send the wrong command I have not been able to make the boiler upset.
(been there 
, but also its has not been 3 weeks yet 
)
Perhaps you should post a screen shot or 2 for the power usage on the boilers website! (power/version)
A JSON output of calcRes would also be of interest
Did anyone find a download page for the boiler firmwares? I am unable sofar and send a request for this via their website, but no answer yet.
Hey fellas, first off GREAT work William! I see that a lot of people are happy with it.
I do have some issues with the rest requests however.
Initially I tried with the simplest command to just gather the heater’s status just like the first comment you wrote, what I got as response was the following :
Error parsing value: 'value_json' is undefined (value: <html><meta http-equiv="refresh" content="0; URL='/'" /><body>File Not Found</body></html>, template: {{ value_json['gradus'] == '1' }})
Then I tried with the entire config.yaml from GIT again with no luck.
All the requests were failing with “File Not Found”
Just to add that I’ve changed the IP to match my water heater one.
The Heater itself is Tesy Belissimo
Anyone else has similar issue and did you manage to find a working solution?
@belastingvormulier, so nice to see this is getting the attention it so desperately needs!!! Also really good to see that more people show interest! Thanks for all your effort already.
@ronnie_j, can’t wait to see an integration coming to life!!!
Now, I just should buy a Tessy boiler asap 
Please open the boiler in your browser and inspect element f12? and see the traffic that is floating from your browser to the boiler.
It might need different requests as the modeco one.
As for the firmware I highly doubt it you will get your hands on it, but one brave soul should/could extract it from the boiler itsefl
Its a pricy item to buy
But it is available
Better buy the right one 
It seems to be very model specific so far 
1 Like
Sorry, I misread, you are using the automation for inputting the temperature into an entity 
It was already late last night (facepalm)
I’ve been using rest for a year or 2 now too, based on my findings from GitHub - gummiboll/tesytalk: cli tool/library to talk to tesy water heaters
So seeing that you discovered the other commands really pleased me.
I wasn’t able to find it, how did you do it? Because I’m not able to control it through its own web interface.
When I started using it, I had 1 rest command per attribute, so it really flooded the boiler with requests… Thats why I’m now also using the scan_interval: 60
I also do not need the &_=16xxxxxxxx id’s to get it working by the way.
You can see the output of /calcRes in my previous post, that’s the complete output, also noted it below again.
As you see it has different attributes than you use in yours, hence the calculation I had to do to get it in to proper kWh.
{"sum":"1695972","resetDate":"2022-01-01 02:43:41","volume":"100","watt":"2400"}
And the screenshot of the energy dashboard, including the daily power usage
Thanks for the suggestion. This will probably lead me to the solution, because opening the boiler IP in the browser shows only a textfield with “IoT” in it. Currently I’ve been controlling the boiler with the TesyCloud app, which probably blocked the local connection with the boiler.
Will try to revert to factory setting and start over to see what will happen.
1 Like
Hi Valeri,
What happens if you go to http:// ip of boiler /status?
Thanks for the suggestion.
It removes the /status part like a redirect
And the result page is this, a blank page with “IoT” as text 
Ohh and yes, I tried with https (Which doesn’t make sense, but still)
And you do have the Modeco smart/cloud boiler with tesy app?
If you just visit the IP-address of the boiler do you see anything similar like this?
Hah weird, tesyCloud app, which in theory is the official app in Bulgaria for Tesy does not really provide you with any information. The only thing you can do in Settings is Logout…
Apart from that, the app has some sort of Local Boiler Control, which is stuck on Loading (Yes I am connected on my local Lan) I Even tried it on browser from PC connected with LAN to the router.
Did you download this MODECO from Google Play or from a third-party?
Perhaps you have an older firmware or maybe a slightly different product than we have.
William’s web interface also looks different from mine.
On the web interface of the boiler itself I can only specify Timezone, Wifi, Volume, see the FW version (FW15.2N@M) and specify my MyTesy account.
I can’t control it through it’s own web interface.
But my boiler firmware version, does have some pages reporting JSON through for example http:// boiler IP /status.
And with the URL’s / pages William discovered, I am able to ‘control it’ locally.
Control (for me) of the boiler goes through the mobile app or web, found here:
tesyCloud (mytesy.com)
Exactly the same app / webpage as I have. I’ll let you know what will happen when I retry with factory reset tomorrow.
But I have one more question. How did you connect your boiler to the wifi? What I did is to follow tesyCloud app steps. (And I believe here is my mistake, it’s probably locking the web interface)
Another steps are to access the boiler web-page during initialisation on 10.0.0.1 (Which I’ll try tomorrow)
Thanks a lot for the support @Jjesper
Incoming with updates soon, they might help someone else