Please, please, please, add the option to automatically load a plugin specified in the URL. It's annoying to always need to find my plugin in the list and open it manually. Also, it's hard to refer a plugin to other people, I need to give them instructions instead of just a URL.

I understand that there are some security concerns but can you allow this at least for the official plugins that show in the UI?

When doing it, please allow loading more plugins at the same time, the URL could be e.g. windy.com/?plugin=pg-mapa&plugin=airspaces.

This layer is extremely over-optimistic. It predicts heights for 1000 m or more higher than they are predicted by other methods (and then they really are). Take a look at the screenshot: The Thermals layer predicts 3200 m (which is extremely rare in Czechia) whereas it will actually be around 1890 m (as predicted by another method).

The method used by my plugin has its “proof” in the diagram:

I have no idea how the number coming from the Thermals layer is computed but it's most certainly wrong.

Please remove my plugin Aladin wind (windy-plugin-aladin). The data source is gone and it's not probable that it will be back.

Please also remove the plugin Paragliding flyability (windy-plugin-pg) which is not mine. Its data source is also gone, https://pg-api.ovh/ is not even in the DNS anymore. This plugin didn't work for long periods in the past. I've contacted the author several times which always helped only for a short time.

There's also - and + (or =) to zoom the map.

@ivo The plugins are great. Would it be possible to persist the plugins I loaded? Either by storing the loaded plugins in Local Storage or at least by putting the loaded plugins into URL (something like /?plugin=windy-plugin-pg).

windy-plugin-flymet: Displays layers useful for glider pilots from FLYMET in Czechia.

windy-plugin-aladin: Displays wind direction and speed in the picker according to the Aladin forecast in Czechia.

It works for me now too.

Let us know if we should add your plugin to the list

I've created windy-plugin-pg-mapa. I would like it to be published. Please let me know if you need me to do something else.

There's also a Windy API version at https://pg.vrana.cz/mapa/ which works only with GFS but it's available on mobiles too.

I've created a poor man solution to load the plugins I always use with a bookmarklet. Create a browser bookmark with this URL (strip the newlines if need to but e.g. Chrome does that automatically, keep javascript:):

javascript:
function loadPlugin(id) {
  document.querySelector('[href="#load"]').click();
  setTimeout(() => {
    const input = document.querySelector('[placeholder="Example: windy-plugin-hello-world"]');
    input.value = id;
    input.dispatchEvent(new InputEvent('input'));
    input.nextElementSibling.children[1].click();
  });
}
loadPlugin('windy-plugin-pg-mapa');
setTimeout(() => {
  W.broadcast.fire('rqstOpen', 'plugins');
  setTimeout(() => loadPlugin('windy-plugin-flymet'));
}, 3000);

Then open https://www.windy.com/plugins and click this bookmark. It will open the plugins I use.

It's fixed now, thanks.

I get the forecast data by getMeteogramForecastData. There are many keys like dewpoint-150h and there also used to be temp-surface. It now disappeared. Please add it back.

I've updated the Flymet plugin and published. Please review and approve.

@Suty Is this at least automatic when I publish a new version? Or do I need to always notify you?

@Suty Does every new version need to be approved?

@Suty I've published the plugin: https://github.com/vrana/windy-plugin-pg-mapa/actions/runs/8658990874

How long does it take to appear in Windy?

@Suty I've updated the plugin to the new system. It works in the dev mode. It still says it's not compatible. What do I need to do to re-enable it in Windy plugins list?

There's a wrong link at https://docs.windy-plugins.com/getting-started/.

It leads to https://github.com/windycom/windy-plugin-teplate.git (M is missing in template).

Almost all the plugins now say “not compatible”. What should we do to make it compatible? Is there some announcement?

@jakubvrana, it now lives in @windy/fetch as getPointForecastData.

Before doing any API change, can you scan the plugins if they use the old API and either send pull requests to fix them or at least inform us? It's really not pleasant if my plugin keeps breaking because of these changes.