#WeatherFlow / Tempest / WeatherFlow2Mqtt

10 messages · Page 1 of 1 (latest)

tepid flare
#

Hey guys I haven't really been able to get the now native intergration for weatherflow to work. I am using a docker container running WeatherFlow2MQTT and it is working and seems reliable. I use the current conditions (rainy and foggy) as well as illuminance to determine if it is dark outside and operate some lights in my home. I noticed some bizarre behavior the other day where it was bright and sunny out and wanted to see why my helper for dark was positive. I noticed that the current conditions were wrong - showing rainy when there hasn't been nor rain was in the forecast. I noticed on the Weatherflow / Tempest app that the conditions showed clear. My only assumption is that there's some bug in the WeatherFlow2MQTT but it looks like development for that program is over since Home Assistant has integrated its own integration? I guess the question would be getting help with the native version which logs only provide a vague async error. Any suggestions or recommendations would be great. I've since setup a log of the condition changes (I exclude tempest data from the logbook since I don't need to keep that data). Thanks!

#

I just looked at my logs and its some bizarre behavior:

January 21, 08:35 AM - Tempest Current Conditions changed to:  partlycloudy
January 21, 08:37 AM - Tempest Current Conditions changed to:  sunny
January 21, 08:39 AM - Tempest Current Conditions changed to:  snowy```
tepid flare
#

This is the error on my beta install of HA:

Logger: aiohttp.server
Source: runner.py:189
First occurred: 12:22:52 PM (1 occurrences)
Last logged: 12:22:52 PM

Error handling request```
tepid flare
#

anyone have any ideas?

tepid flare
tepid flare
#

I did get the native version working

#

with network_mode: host - somehow

#

the problem is the difference between the github vs the include integrations are very different

#

current_conditions are not there with the built in - integration