Stefan de Lange

@lostanlen Thank you for your quick answer. From the metadata I read the following: `xi = meta['xi'][order1]` : ``` [[0.48376008 nan] [0.4733941 nan] [0.46325024 nan] [0.45332374 nan] [0.44360995 nan] [0.4341043...

I see, that makes more sense. I looked at my plot again and found a small mistake, the pseudo-frequencies are correct. ps. If you want I can send in a...

@itzg not sure if this is still relevant, but I found that if I interacted with the docker commandline directly from my Ubuntu WSL2 machine I did not get any...

I think I got it. It's because the volumes are stored in the windows filesystem rather than the linux filesystem. When using a WSL2 backend with files stored in the...

Thanks, that's useful information. What about the properties that are listed here? [weather/#forecast](https://developers.home-assistant.io/docs/core/entity/weather/#forecast) Because it does not mention anything about expanding it with other fields.

Yes I get that. I am not working on a custom component, but on an addon. The addon takes a HA weather entity as input to get weather forecast data....

Yep, exactly. As for how to use it, the `forecast` attribute is basically just a list with dicts in it, one for each timestamp. So `{{ state_attr('weather.pirateweather', 'forecast') }}` will...

Awesome! I think the property name should be slightly changed, it should be `cloud_coverage` according to [core/entity/weather/#properties](https://developers.home-assistant.io/docs/core/entity/weather/#properties). I see the pirateweather integration named it `cloud_cover` :)

> I'm going to close this issue for cleanup but if there are still properties you'd like added to the integration feel free to create a new issue using the...

Has anyone tried getting this to run on steam deck? It starts up, I see the main menu and then after 3 seconds I get 'assertion failed', and 'nested exception'...