Hey,

My pluging (flyXC soundings) do the user selected model to compute the sounding data. As such I do not need to have a separate model switcher in the UI (on desktops).

It looks like mblue has been added in 51 but there does not seem to be a way to select that model

Is this coming or are there limitation preventing it to be added to the list (i.e. tiles not generated, ...)

Thanks

@rboulaire said in Feature request — allow (at least trusted/reviewed) plugins in the native mobile apps + lateral drag for the mobile panel:

Native app support

This has been supported for a few months now.
Make sure you have the latest version the app installed

Looks like it is working now with the latest version of the app

@Pierre-MICHELOT-2 I'll be back from vacation and looking at that next week as soon as the windy team is able to help

@Pierre-MICHELOT-2 I don't thin t5k it's avaiable in the app and the current version of the app broke the plugin anyway.
Your best chance is to install the plugin (normally, not via URL) on a browser either on mobile or desktop

@Suty hopefully that will fix it.

For the record, it's the second time windy breaks my plugin in a week :(
I don't like to complain because I know the team is working hard to offer the plugin framework but at least the first breakage could have been very easily avoided

@Suty hopefully the windy team can help rather ;)

The mobile app does not work but the web site works on both mobile and desktop.

It has always been a pain to debug the app, hopefully they can provide some guidance - I contacted them on slack

@PieroMa Unfortunately the windy team had no time today to approve the plugin and publish it :(

But you can use the URL to install the plugin - when you install plugins there is an option to "Load plugin directly from URL", you could paste the URL to the new version https://windy-plugins.com/726021/windy-plugin-fxc-soundings/4.2.1/plugin.min.js

Again the plugin broke because of unannounced updates in windy - I hope they can find a better way to work with plugin authors in the future.

@Suty I would appreciate a confirmation of my understanding on slack so that I can implement a fix.
Thanks for your help

@Suty As I posted on Slack, it seems to be related to changes made by the windy team w/o any warning to plugin devs. Hopefully they can find a way to better communicate those and avoid breaking plugins (which should both be easy)

@PieroMa what's your problem? On what computer/phone.

It works right now on my phone and I use it daily on my computer.

@francescogola the plugins update automatically (for the past few months)

It's related to a windy.com change.

v4.1.13 was released to fix this, updating should fix any issues.

Let me know otherwise.

@nrbray I commented about this here.

TL;DR Plugins have access to data at different level, the lower one being gh-1000. There is a gh-surface but I'm not sure if we should use this for soundings - they are about the air mass not the ground. I'm not exactly sure what sh-surface is. I asked on the thread I linked above but got not reply.

@ghuyt-rfffgh-fhiij-xiagua I guess the question is what would you like to see that the current 3D does not do?

Hey @Rubilin

I'm the author of the "flyXC soundings" plugin.

I believe this is a bug in the built-in soundings. I recently updated the code of the plugin to fix this - @marekd told me to add {extended: "true"} when fetching the forecast data. After I updated my code the plugin was able to access the full time range.

The technical details in this post are not aiming at confusing you but to help the windy team fix the issue quickly. @Suty might be also to help route to the right person.

In the meantime you can use the flyXC soundings plugin, the zoomed out view is similar to a regular sounding.

Turns out the Chrome package repository was disabled when I upgraded to Ubuntu 24.04. I have re-enabled it and updated Chrome. Everything works like a charm now.

I have released v4.0.0 of the plugin yesterday.

It's now called flyXC soundings.

There are many improvements to the UI and even more changes under the hood.

I have written a longer post on the flyXC facebook page.

I'm pasting the last sections of the post below:

There are a few ways you can help the project:

• the README linked above is succinct. I would love some help with writing a nicer documentation
• you can also contribute code if there a feature you would like to see added - if you do not know how to code, you can still contribute ideas
• lastly you can sponsor the project. While the sounding plugin (as well as flyxc.app) is open source, it's nice to get some money to compensate the hours spent developing it

Do not hesitate to message me if you want to help.

Many thanks to windy.com for their awesome website and maintaining the plugin framework. Many thanks to John Kealy, his SkewT plugin released in 2019 was a great source of inspiration.

The plugin just shows heights; are these heights just calculated from temp-1000h, temp-900h

They are calculated using the gh-1000h, ... (geopotential height)

Regardless, if it is valid, is there any data missing or is it still possible to calculate the points on the diagram?

Yes, it's possible to compute those values and it's called a weather model ;)

Can the model elevation be used for the surface data? (The builtin sounding shows the model elevation, but perhaps the plugin doesn't have access to this?)

The plugin has access to the same data. But again I don't think surface can be used (to be verified)

The Meteoblue temperature and dew point lines always starts at 1000hPa, and it also shows a horizontal surface pressure line. All the other examples start at the surface pressure, whatever that is for the particular location and time.

I think some models provide a temp-100m, ... which could be helpful. This is not part of the data provided by windy.

Maybe @marekd knows more?

Thanks for the screenshots, the ensemble graph on ECMWF gave me the idea to overlay multiple models on the sounding.

@vicb

I did clear all the site data and still see the issue. I traced it down.

On logout, we enter

which calls

e === null and returning a resolved promise crashes the tab.

I checked in Firefox and this yield b1() works fine.

Probably a chrome bug?