Hi Troon,
Amazing, this works again. Probably the solution to this downside is to store the json output in a file and have separate sensors using this file.
For now, I will use this set-up and call this source 3x every 10 minutes.
By the way, how would you now solve the {{ now()|as_timestamp|int }} at the end of the weblink?
command: can be a template (docs). I was just being lazy in my test.
You might be able to use json_attributes_path and json_attributes to pull the info into attributes in this sensor, then read that into template sensors with units of measurement to get around the need to call the API multiple times.
Totally untested:
json_attributes_path: "$.winddata[0]"
json_attributes:
- windsnelheidMS
- windstotenMS
- windrichtingGR