Closed nilvanis closed 2 years ago
How does the solar elevation look? Solar Insulation is proportional to solar elevation, so if there is an issue with elevation then it would be shown on Solar Insulation.
Please post your docker run command. Feel free to replace lat/long/station id/api key with 'xxxx'. See the Zambretti issue for an example.
I'll probably ask more questions when I get back to my computer.
Do you use MQTT explorer? It will allow you to see all MQTT postings without have to rely on HA auto or manual sensors.
Hi Glenn, Solar elevation has exactly the same issue. But I did noticed one thing. All sensors I checked are affected the same way except current wind speed I have uploaded few more screenshots including solar elevation here: https://imgur.com/a/5sHprRN
my docker-compose.yaml
version: "2"
services:
weatherflow2mqtt:
image: briis/weatherflow2mqtt:latest
restart: unless-stopped
environment:
- TZ=<cut>
- UNIT_SYSTEM=metric
- LANGUAGE=en
- RAPID_WIND_INTERVAL=0
- DEBUG=False
- ELEVATION=67
- LATITUDE=<cut>
- LONGITUDE=<cut>
- ZAMBRETTI_MIN_PRESSURE=960
- ZAMBRETTI_MAX_PRESSURE=1060
- WF_HOST=0.0.0.0
- WF_PORT=50222
- MQTT_HOST=<cut>
- MQTT_PORT=1883
- MQTT_USERNAME=<cut>
- MQTT_PASSWORD=<cut>
- MQTT_DEBUG=False
- STATION_ID=<cut>
- STATION_TOKEN=<cut>
- FORECAST_INTERVAL=30
volumes:
- /var/docker_containers_data/weatherflow2mqtt:/data
ports:
- 0.0.0.0:50222:50222/udp
Do you get a Zambretti output?
Do you get a Zambretti output?
Normally? yes During the ~30min freeze? no
Screenshots of Zambretti history from the same timespan as previous ones: https://imgur.com/a/degtW5Q
I managed to solve it. It looks like it was a sensor - hub communication problem. I've moved the hub to another location and I don't have these 30min freezes ever since.
I was misleaded by the fact I was receiving current wind speed without a problem all the time and historically all the data were present on the weatherflow website. Like these were 'cached' on the sensor and resent until it receive acknowledgment.
Home Assistant Version?
2022.6.7
Add-On or Self Hosted?
Self managed Container
Weatherflow2MQTT version?
3.1.1
What happened?
Hello, First of all I'd like to take the opportunity and thank you so much for this piece of software - amazing work, I'm so glad I can pull all my WF Tempest data to HA that easily.
I've set up this just yesterday, but I noticed one thing I cannot figure out the root cause.
I'm using W2M in a docker container on an rpi4, WF HUB is in the same network as rpi. I also run mosquitto MQTT server as an addon in HA. W2M is not my only MQTT client, but is using dedicated credentials to authenticate. One of the other clients is in another docker container on the same rpi. Between rpi & HA there is a hardware firewall so I have visibility over the traffic going over it.
Normally everything seems to work as expected, entities are updated every few seconds in HA. However, every few hours I can see a ~30min freeze in data collection just for WF entities. Other MQTT sensors update normally. It's easiest visible on the solar insolation sensor, but basically all sensors have 'straight line' for the same period. You can see it here: https://imgur.com/U89lmpl
In the same time Weatherflow Tempest data on the web are updating normally. I have also checked the firewall logs and I don't see any new network sessions during 'freeze times' and no teardown/timeout sessions as well.
Anyone have a clue what can cause this behavior?
Relevant log output