Weatherflow Tempest integration

Third party integrations
42

I messaged them and they had to manually adjust the shipping to be able to include the bird deterrent.

43

Would it not be easy to use some UV resistant cable ties on the top unit to create the same effect for virtually free?

Is there an indoor temp/humidity sensor in the gateway unit maybe? Like for the Ecowitt? My wind vane and rain collector is acting up and I feel I should move to something requiring less maintenance

44

There are no sensors in the hub.

45

Is it still the HACS integration that should be used? Not intregrated into core yet?

The current i integration is dependent on the cloud?

46

The current integration is not dependent on the cloud, except for forecast. No currently integrated into core, I know someone was working on it with an older fork, I havenā€™t seen any updates in awhile thou.

47

Thank you. That sounds great.

48

IMHO:

49

When will the Weatherflow Tempest integration (Pull Request #75530) be added to Home Assistant core?

50

I Keep Getting this messaged This stops working in version 2024.3.0. Please address before upgrading.

The integration weatherflow is using the deprecated forecast attribute.

Please report it to the custom integration authorā€¦

51

The developer (Me) knows. It will still work until 2024.3, so there is time to fix it.

1 Like
52

I think Iā€™m really really close to getting the UDP/Local integration added into core. Iā€™m hoping once thatā€™s done I/We can lean on one @briis to work on adding some of the cloud featuresā€¦ :slight_smile: and/or maybe Iā€™ll just slowly start porting them overā€¦ (HA has some pretty strict requirements on how integrations need to be formatted for anybody thats been painfully following my PR process)ā€¦

2 Likes
53

@briis - Looks like we might make it into beta with the UDP integration. We should talk to figure out how to pull some of your cloud based features into the integration because I think that would be really great to get the forecasts inā€¦

1 Like
54

Such great timing. My Tempest weather station arrived today and is up and running. Keen to get it integrated with HA so I will start with the UDP/local integration.

@jeeftor - sorry for the dumb question but what does it mean when you are in beta for core? Should I wait for core or use HACS?

55

It means that in a week when the next release comes out it will have native weather flow support.

1 Like
56

Is there an easy way to run both the Cloud custom integration and the new local integration at the same time?

Iā€™m running the latest beta, but it appears that the custom_component is replacing the new core one

57

Hi @jeeftor
Yes I saw that the code is now in the beta, so congratulation on that.

How we integrate the cloud based stuff, is a good question. Because I do think that many in this community loves that the new core integration is 100% local, and in my opinion it should stay so. That doesnā€™t mean there canā€™t be some calculated values, which I also do in the WeatherFlow2MQTT addon.

I actually already did some of the work, but in a separate custom integration with the domain name weatherflow_forecast to avoid conflicts. This is currently in beta, and supports the new Forecast implementation required as of HA 2023.9. If anyone want to test it out, you can find instructions here on Github. I have submitted a Brand Icon, so that will show up, once it is merged.
I would really love some people who live in a different timezone than me (Central European Time), and who uses Imperial units, to do some testing. Specifically:

  • is the Hourly and daily forecast times and dates correct
  • are the values correct

I have also been asked to migrate the remaining sensors, that the UDP API does not provide, and I am currently evaluating that option.

2 Likes
58

No, and that is why I gave the new, Weather Entity only, Integration a new domain name. This can co-oexist with the core weatherflow integration

1 Like
59

Oddly enough this is what I was thinking about yesterday walking the dog on whether we need a separate weather-only entity or if we could look into a hybrid local/cloud integration (something I"m considering for my IntelliFireplace integration). In my case for some strange reason the IoT Module on my fireplace seems to prioritize cloud traffic at the cost of unreliable LAN connections (which makes no sense).

I think the thing is - that some of the ā€œcloudā€ sensors are different from local because I believe they take other stations into account ā€¦

I sort of envisioned an options-flow where you select

USE CLOUD DATA / USE LOCAL DATA

or something ā†’ but Iā€™m not sure if that works in the HA context

60

The integration sends too much data for hourly forecasts. HA gives us a warning.


template:

# DonnƩes reƧus de Tempest WeatherFlow

# Obtenir les pƩvisions horaires
          
  - trigger:
      - platform: time_pattern
        hours: /1
    action:
      - service: weather.get_forecast
        data:
          type: hourly
        target:
          entity_id: weather.forecast_shawinigan_sud
        response_variable: previsionshoraires
    sensor:
      - name: PrƩvisions mƩtƩorologiques horaires
        unique_id: previsions_meteorologiques_horaires
        state: "{{ now().isoformat() }}"
        icon: mdi:hours-24
        attributes:
          forecast: "{{ previsionshoraires.forecast }}"

IMG_7757
IMG_77572455Ɨ502 105 KB

61

@briis (Can HA support Hybrid - Local / Cloud Entities Ā· home-assistant/architecture Ā· Discussion #977 Ā· GitHub)

  • It sounds like if we want to work together (in conjunction) we can work on a Hybrid Entry
  • Alternatively we could go with a separate entry

Personally - the idea of a Hybrid entry kind of appeals to me although it might be more complex to write it would be a 1-stop-shop for folksā€¦

(Community ā€¦ thoughts?)