I took the plunge and replaced the HACS Weatherflow with the core application and noticed a few binary.sensors are missing, in particular:
- Binary_sensor.is_lightning
- Binary_sensor.is_raining
Am I not looking in the correct place?
Thatās correct, these are not available.
https://www.home-assistant.io/integrations/weatherflow/
You do have the percipitation type which is ānoneā if not raining and a lightning count which is non zero when lightning occurs.
Iām more worried about the daily rain amount as I now need to figure out how to count that using most likely a riemann sensor and utility meter somehow.
I would also like to see daily rain amount. Thank you.
I ran into the same āUDP Discovery Errorā when adding the WeatherFlow core integration. I run Home Assistant in Docker and it turns out there was another container already using UDP port 50222. The only options Iām aware of are removing the other container or look at adding another network adapter to my Docker host. Good luck!
Firstly - @briis and @jeeftor - WOW. Donāt think I can say enough about how cool it is what youāve done here AND the collaboration between you both. Just awesome job!
@briis can you please help me understand whatās being used for your new HACS integration? Clearly Iām using direct conversations with my new Tempest using the @jeeftor integration (which looks to be talking with UDP port 50222) - so thatās giving me direct access to those data. FANTASTIC. However, with yours Iām using an API key to my Cloud based data that the product is using, but also getting Forecast dataā¦How are those data provided? Is there a document on that? How is my specific product used there, or is it not and itās pulling something from the WeatherFlow company using all of the Tempest and TempestOne devices data that they are storing? A bit lost on whatās coming from where and how. I certainly donāt want you to spend your valued time answering here if you can just point me to some document that youāve already written (or someone has).
Thanks in advance
@huberj001
I will do my very best to explain 
WeatherFlow has, from the start, had several open and well documented APIās, and each of them uses a different approach to retrieve data from the Weather Stations.
As you correctly mentioned, the core integration @jeeftor released is using UDP as its communication protocol, and as such is 100% local š«¶š». The downside to that API is that you can āonlyā get the raw data that the weather station delivers and as such a more limited set of data.
While the Station communicate using UDP, it, at the same time, sends the data to WeatherFlows servers, and from there they can be retrieved using one of the other communication protocols. (REST API or Websocket)
The HACS integration uses the REST API to retrieve its data, and therefore you need and API Key/Token to get the data from their servers. The advantage of the REST API is that it can deliver a weather forecast, taking your own data in to account, and you can also get a more comprehensive numbers of sensors, as WeatherFlow make some calculated sensors on their servers. (Besides from what they do, I then do a few more calculated sensors that they do not deliver). The disadvantage is clearly that now you need the internet to be up and running, and you depend on a cloud service.
You can play with their APIās and get more knowledge on what is there, by going to this website
I hope this clarifies things, else feel free to ask again.
2 Likes
Ultimately there should be two integrations:
weatherflow
and
weatherflow_rest https://github.com/home-assistant/core/pull/106615
I currently have a PR open for the forecast module of the REST integration.
I guess we could also have a websocket one ultimately - since I think thats also supported but its a bit bonkers.
If you open the PR there is a discussion about why I went with two separate versions instead of a unified integration - the answer is UDP and REST are VERY different implementationsā¦
I started with porting @briisās work - but ended up just rewriting the backing module
You are a MONSTER. Yes, this makes perfect sense and validates what I āassumedā - which is never a good word. One last questionā¦ is there a way to get the weekday forecast from the API like what I see on the tempestwx site (below)? Much like Accuweather presents with the increased integer names that they provide? I didnāt find it in their API docs - so Iām thinking no ;(
I read through it - it all makes sense - and is working very well thanks!
This can not be delivered directly from the Integration, as dates and times have to be in a very specific format not to throw an error.
However with Templates you can format almost anything. I think I need a specific use case to see if I can come up with an example on how to do this.
Let me try to work it outā¦I saw this API endpoint
Which has mad crazy information so Iām going to see if I can use that (unless your code already does - Iāll check) and then see if I can integrate it to a Platinum Weather Card or use a Template like you suggested. Once I get something worthwhile Iāll post it here so people can use itā¦ OR LAUGH AT IT 
Good luck 
Looking forward to see what you come up with.
@briis - congrats on getting your integration into HA core!
Are there any differences between the HACS and core version? what and how would you recommend switching to core from HACS. Not yet or ready to go!
I did not make the Core Integration, that is all the work of @jeeftor
I have not upgraded yet, so I am not sure what the difference is, between the HACS version and the Core Integration.
But I am sure @jeeftor can elaborate
Honestly ā you probably want to stay with the HACS integration for the next few releasesā¦ its very slow going to migrate into core 
@briis can move WAY faster
Well in that case congrats to you @jeeftor - I have heard it is hard work to meet all the requirements for core so top work!
I will continue (happily) to use the HACS integrations work great.
The more stuff we get into core the better if you want you should be able to run both side-by-side. I donāt have sensors in yet which is why I say itās probably better to stick with hacs for now.
I think it took me about two years to get the UDP weather, flow thingy added.
In the next release, I expect will get sensors in
And then Iām considering adding a socket connection to pull a lightning strikes, as well as precipitation, start events
1 Like
Here is what Iām working on currently for the next release at which point weāll have a better setup.
Not sure I love the 3x pressure readings but whateverā¦ I may hide some by default.
Iāve got a PR that should fix the forecast bugs in now
3 Likes
Hello! Iām using WeatherFlow and do not have a weather entity. How can I add it?