WeatherFlow Weather

Share your Projects!
#29

The forecast data is an array, so to get specific data points from that you can use a Template sensor or similar. Let us say you want to get the condition value from the second day in the forecast, then you would use:

{{ state_attr('weather.weatherflow_day_based_forecast', 'forecast')[1].condition }}

Note the number 1: As this is a zero based array, 1 is the second item in the list. So just change the day number and the field name, to get what you need. Hope this pushes you in the right direction.

2 Likes
#30

@briis and @tom_l - ah thanks!! Let me try that! I made a super quick command-line JSON template to fetch the forecast data and toss it into some sensors - incrementing a forecast from 0, 1, 2, 3 - etc. for each day I wanted to use the attributes from. If I can make this kind of template example work that would be great! I was missing the syntax example for sure!! Will share the results shortly…

wf_forecast
wf_forecast1920×1440 247 KB

1 Like
#31

test_attribute
test_attribute635×731 68.7 KB

Yep!! Good to go!!! Thanks for the help on this!! :slight_smile:

1 Like
#32

If the days are always in order that makes it easy. Nicely designed.

Just FYI you can also fill all the sensors in one resource call with the new rest integration.

Nice display too!

2 Likes
#33

I really like your dashboard :slight_smile:

I have a couple of questions:

  • how do you pull “Rain Last Hour”?
  • do you save the “daily rain” separately to then present it in the diagram?
  • how do you pull “Weatherflow is Lightning”?
  • how do you pull “Weatherflow is raining”?
  • how do you extend “Battery Level” over a couple of days and not only one day?
  • and lastly, how do you present that nice wind direction arrow?

Thanks a lot! :+1:

#34

It’s one of the available sensors from the integration.
No, I just use Apexcharts to create a weekly graph grouped by day. All the data comes from the recorder database.
It’s one of the available sensors from the integration.
It’s one of the available sensors from the integration.
I use the mini-graph card to graph a week’s worth of data from the recorder database.
With this Compass Card - Points you in the right direction 🧭

1 Like
#35

Thank you. I use weatherflow2mqtt and just found, that not all entities that you have with weatherflow weather, also exist in the weatherflow2mqtt integration.

That compass card is beautiful, thx

#36

The integration being discussed is not weatherflow2mqtt. It has more sensors. See the first post in this topic.

#37

@briis and @tom_l - I ran down a rabbit hole with the details that you provided. Thank you so much!! I’m now almost finished with a few more screen pages.

e-ink_1
e-ink_11920×1160 190 KB

I still have a little more work to do to clean some things up. I think I’m also almost at the limits of how many sensors I can reliably grab from HA as well since I have to baby the firmware updates and some other interesting configurations. But it’s been fun!!

1 Like
#38

Looks really good, thanks for sharing. What is the HW you are doing this on? (Can’t remember if you already posted that)

#39

A post was merged into an existing topic: WeatherFlow to MQTT Setup

#40

3 posts were split to a new topic: WeatherFlow to MQTT Setup

#41

Hi @tom_l, this is a very nice dashboard, I love it. I’m trying to rebuild it and have already been able to implement some of it.
Would you be so kind and maybe explain how you realized the middle cards with min, max and the time? Did you also use the Mini-Graph-Cards for this? How would the YAML code look like? Could you post an example? I am very new to Home Assistant and unfortunately have no programming skills.

Best regards
Dirk

#42

Yes, mini-graph card:

color_thresholds:
  - color: '#e45e65'
    value: 30
  - color: '#e0b400'
    value: 20
  - color: '#0da035'
    value: 10
  - color: '#039BE5'
    value: -50
color_thresholds_transition: hard
entities:
  - entity: sensor.weatherflow_wind_speed_knots
    name: Wind Speed
group: false
hour24: true
line_width: 4
points_per_hour: 4
show:
  extrema: true
  fill: fade
  icon: true
  labels: false
  name: true
  state: true
type: custom:mini-graph-card
2 Likes
#43

Great, thank you so much! :+1:t3:

#44

@Lux4rd0 This really looks awesome! do you have the yaml for this available ?

#45

@tom_l, another question.
How did you managed the layout. I think I have tried all the possibilities already.
The first and the last column I created with “Vertical stack”, but I can’t get the middle part right.
This is what I already tried:
– 4 grids with one vertical stack each
– 2 grids with two vertical stacks each
– 1 grid with four vertical stacks
(with square cards)

The middle cards are always squeezed together. What I’m doing wrong?

#46

Start a new topic in the frontend category, This is off topic.

#47

@kasdk3 I’ll be posting shortly in a new thread the YAML and project that I’m working on. I’ve redone the four screens to fit a smaller Lilygo device rather than the larger Waveshare screen due to some ease of use. I’m hoping to get something finished up for a first publication in the next week or so. Thanks!

eink1
eink11008×756 347 KB

eink2

1 Like
#48

Hi,
Newbie here, so sorry if this has been covered before.
.
I’m trying to use the integration and while it looked promising, once I add my Tempest Station-ID and Personal Use Token for my data it seems to finish OK as it finds my Tempest station… On closer look however I get this logbook notification which shows up in the integration panel too… Something’s probably wrong in my config but what’s it telling me?

Config entry 'WeatherFlow Tempest' for weatherflow integration not ready yet: Error while retreiving data: Timeout fetching weatherflow data.; Retrying in background 4:42:02 PM – (WARNING) config_entries.py - message first occurred at 4:29:38 PM and shows up 2 times

Thanks,
Chuck