Scrape date from Home Network into Sensor

Hello all,

I am a proud owner of a Synology NAS with HomeAssistant as VM since a few days. In the future, I want to manage my whole smartHome with this powerful system. Now I would like to first integrate my heating system in the best possible way. It is a wood boiler with buffer tank from the company ETA.

I can either access the data via a portal of the company (meinETA.at), or directly query various variables in the network.
IP heating boiler: 192.168.178.48

Available variables / commands query (All sensor data)
view-source:
…192.168.178.48:8080/user/menu

Query temperature boiler on top:
http://192.168.178.48:8080/user/var//120/10251/0/0/12242

Optimal would be if I can ask Alexa:
“Alexa, what is the temperature of the buffer tank”.
First, however, I need to get the data in HomeAssistant. For this I need to create a sensor which scrapes the data from my network.
I think this I can realize with //scrape.

I have already copied the sample codes into /config/configuration.yaml and tested it. Works perfectly.

Now I unfortunately don’t manage to get the corresponding variables from my home network. I don’t know much about programming. Maybe someone can explain how I have to fill out the field “Select”? Do I have to work here with appropriate CSS elements? Is it even possible to use “Scrape” to retrieve data from this sensor in the home network or only from public websites? Is there a more elegant way? And last but not least: how can I let Alexa query the data without using HomeAssistent Cloud?

Thank you in advance!

Best regards
Hendrik (from Germany)

No ideas? from anyone?

Try using one of the css selector tools.
I would probably use regex to get the value, I assume that means you should use the value template.
But I don’t know if that works.

Hi I recently found this German explaination about how to include meinETA data. Basically you just need a rest platform like you see in this example:

Like this post explains home-assistant already converts XML to JSON so it’s only a matter of the right Jinja2 templating and pipeing to convert the values.

I hope this helps you too :slight_smile: