Thanks @studioIngrid for sharing! I archieved almost the same but this version is much simpler. I created two python scripts for Buienradar and Buienalarm and format it’s output for Apexcharts.
To only use buienradar, just only include that entity under series.
What do you mean by ‘only today’? Buienradar service supplies two data files, one for the next 3 hours and one for the next few days, I can image there is some difference in accuracy between the two. So do you mean you would like to use the forecast for the next 3 hours?
Yes, the forecast for the next 3 hours would be great. I now use the ‘custom:neerslag-card’ from aex351, but sometimes the card is not visible. It’s not working fine, so I would like to have your ApexChart solution !. Tried myself but I don’t have enough knowledge to get the data into Apex
UPDATE 20-03-2023
I encountered the following error: “State attributes for sensor.weather_buienradar_hourly exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored”.
I updated the command line sensors, to truncate the JSON strings before storing them.
@GertJan
I didn’t have time to test it thoroughly. But here you go.
I have included both buienradar and buienalarm. If you would like to use only one, just delete the other under series.
If you have the neerslag-card, then I assume that you have a buienradar sensor? For those who don’t have the 2h forcast sensors yet, use these:
@studioIngrid,
Super that you are helping me out! great!
I think the card is almost working, but there is one problem:
Something is wrong with the scaling.Please take al look at the examples:
buienradar website card
your card
neerslag-card from aex351
at 12:35 there should be .1 mm/u rain. In your card it is .8 mm/u
This is de data from the buienradar website. Looks like 077 does not stand for mm/u
077|12:35
087|12:40
077|12:45
000|12:50
000|12:55
000|13:00
000|13:05
As you might recall, the data format of the 24h sensors are different.
If you want to learn more, find your own sensor in developer tools and look and the data format.
The field key is “precipitationmm”, another assumption from my side, but I thought that would represent mm.
You can learn a lot from these requests. However, unless the site/organization has a dedicated developer page, I rarely find documentation. It’s a deduction game, and then trial and error mostly.
Thanks for the heads-up, I did notice, but didn’t connect the dots jet.
The gpsapi changed and no longer accepts extra parameters. The original request used &c= […] str(random.randint(0,999999999999999), to disable caching. It’s not pretty, but it works.
I thought the solution was to change that: change the command_line sensor, change the “command” to:
Hi @studioIngrid,
I was analyzing the entity sensor.weather_buiradar_hourly. The data retrieved via forecast.buienradar.nl. (Simply out of curosity)
I saw that the entity is filled with 2 weeks of information. That’s why I was working on adjusting the code in the data_generator so that I can retrieve data over several days. Unfortunately, I have not been able to do that so far Do you know if there is a tool that can be used to generate the code based on the entity? That would be nice. I also saw that it not only contains the rain information, but much more information. I hope you have some tips for me. Thanks in advance!
Hi Ingrid
thanks for this project! One question about buienalarm, the graph remains at 0, so no data is shown in the graph.
The rain radar does work.
any idea what this is related to?
the sensor works and gives data in the attributes: