API Trial suitable for home use?
-
@Suty What do you mean monitor :(
How much more interest do you need? There is more than enough interest in this. Please discuss this with your colleagues. We all want this! Make it happen! Please :)
-
@Suty +1 another interested premium user.
Unsure if you're aware but there is a large base of potential future Windy premium subscribers if you made this available: https://analytics.home-assistant.io/ (and these stats are only of folks who have opted-in!)
In case you were not aware, Home Assistant ranks as one of the top open source projects on GitHub: https://github.blog/news-insights/octoverse/octoverse-2024/#the-state-of-open-source with extensive Developer Documentation ( https://developers.home-assistant.io/docs/development_index/ ) and a big community of developers who typically take care of all the integration work to get it all up and running in HA in their own free time. It would just require this affordable access to your API.
Any other convincing you need?
-
I would buy a Premium account if integration into Home Assistant
-
after discovering your program
https://www.windy.com/-Hurricane-tracker/hurricanes/alfred?-26.118,150.741,8,m:cVtakpC
I have now installed it on my phones , and would love to have "Home Assistant" integration and use your forecast models for tweaking my automatons
I have automated window shutters to try and stop rain entering server room , I try and keep them open for as long as I can because it gets soo hot ,
also have automation to export hard drives and spin them down to cut down power usage to prolong battery time period for poor solar days , grid failure
these take quite some time to shutdown correctly especially when their is a stubborn program still accessing a file somewhere ... -
I would also subscribe to Premium if the API could be used for HomeAssistant. Locking to, e.g., a single address for forecasts would seem OK.
-
+1
My use case is energy accumulation planning for a home photovoltaic system. I.e. one forecast location would be sufficient.
-
Windy's Trial API does modify data, so it might work for general forecasts but not for precise automation. A lower-cost Home API tier would be great for users like you, offering limited accurate requests without the high cost of a Pro plan.
As for Premium users getting free API access, it’s a solid idea—worth suggesting to Windy directly. Meanwhile, you might check Home Assistant weather integrations or other APIs like OpenWeatherMap. Hope Windy considers this! 🌦️
-
+1
Even a few extra euros a year for having the option to access basic home data would be worth it. Wind, rain and sun predictions for home automation projects are clearly in demand and that demand will grow I am sure.
-
“Strangely, the GFS is showing 22 km. Let’s wait for the upcoming upgrades—changes to the American model are expected.”
And here’s the follow-up I gave, also in English:
⸻
You’re absolutely right, Weather Analyst Helail. The 22 km resolution currently shown by the GFS gives us a rough idea, but it’s still not fully accurate—especially with this relatively long forecast range.
Upcoming upgrades to the model could make a noticeable difference, especially if they include changes to the physical parameters or improvements in resolving the lower atmospheric layers. That’s something we could very well see during this Wasm season.
Model shifts with the GFS usually become clearer within the 144-hour range or less—that’s when moisture profiles and upper-level trough dynamics start aligning better, and the model becomes more consistent between runs.
Have you noticed if the ECMWF (European model) has started to pick up signals more clearly than the GFS? Or maybe you’re seeing interesting patterns in the Canadian or ICON models you’d like to compare?
⸻
Let me know if you’d like it in a more technical tone or if you want it posted somewhere.
image url))) -
Hello Windy Team,
I’m a regular user and weather analyst from Saudi Arabia. I truly appreciate the accuracy and performance of the ECMWF model on your platform. However, I noticed that the update delay between the model release and its availability on Windy is quite significant, especially for non-premium users.
Since timely data is crucial for tracking short-term severe weather patterns, I kindly ask if it’s possible to minimize this delay or provide faster update windows, even if partially, for free users or allow early access with limited layers.
Thank you for your great work and continuous improvements to the platform.
Best regards,
Helail — Weather Analyst
(Tabuq Region, Saudi Arabia)
-
Add another +1 to the requests for access for Home Assistant users. I am also a premium Windy subscriber and would make good use of this.
An admin asked how it might be used... here are some examples in my home:
-
Smoke: I was recently told by another admin elsewhere in this forum that a smoke model is coming to windy! Very needed in my part of the world. I could use that data to remind our household to shut the windows (via mobile notifications and smart speakers), as well as trigger the HVAC to turn on.
-
Tornado warnings: flash lights, play audible alarms when a tornado warning is posted.
-
Lightning nearby: notify the house when lighting is nearby to disconnect certain devices
-
Humidity: use outside humidity data to help regulate.maintain consistent humidity inside the house
etc etc etc
Some kind of access would make sense for premium subscribers, don't you think?
-
-
Adding my voice to this - as a Home assistant user I desperately need a small scale API from you to drive Powerwall backup level as the Tesla weather prediction sucks.
Pretty sure you'll get a lot of new premium subscribers from ranks of Home assistent users if you implement this. -
Hello i'm interestedfor access for Home Assistant user to so +1. I realy like your forecast and woul like to use it in home assistant.
-
I am also very interested.
-
@Suty a version of the full API that's locked to a single location for home use would be lovely! I see there is consistent interest in this thread, people who will pay for a home version of the API.
Any updates or internal movement around this request?
