Comments on: WeatherFlow Tempest Log Collector

By: Holger Weis

Holger Weis — Sat, 26 Feb 2022 17:30:49 +0000

hi,
thanks for the docker container! I installed it on a synology and the interface goes up but without data. However I have some questions! Where and how do I enter the data for my Tempest weather station?
If I have understood correctly, the udp listener must be told where it should pick up the data.
Sorry something clueless, since I have never worked with docker.

By: Dave Schmid

Dave Schmid — Tue, 06 Apr 2021 06:11:42 +0000

In reply to Ffred.

Fred – you’re absolutely right – a typo in those up/down/stop scripts. As for the logs – are you talking about the JSON logs that are stored in Loki or a different one? I’m actually rebuilding the All In One now that I’ve added forecasts to it. With that effort, I’ve added better debug/info logging in general to the collectors.

By: Ffred

Ffred — Wed, 17 Mar 2021 02:09:40 +0000

Two more questions for you Dave.

The stop.sh and down.sh scripts appear to be the same. For stop.sh, shouldn’t the last line read docker-compose stop instead of docker-compose down?

How do I decrease the log level for the json.logs? Have one that grows quite large day by day. I believe the log level is set to info, but am unsure which configuration file might set it to warn or perhaps stop logging altogether.

By: thebaldgeek

thebaldgeek — Fri, 12 Mar 2021 13:25:27 +0000

Dave, thanks so much! We are up and running.
The only empty graph is Humidity…. Any pointers where I can look to add that? (I know my station has it, I can see it in the JSON stream).
BTW, your update was perfect, I don’t have a Tempest so was a bit worried it was no do-able, but your new version works great.

By: Dave Schmid

Dave Schmid — Wed, 10 Mar 2021 15:20:02 +0000

In reply to thebaldgeek.

Nice! Do you have Tempest or the Air & Sky? I just made updates to allow both to be seen. Like literally a few minutes ago. You can see the changes in v1.03 or you can grab the individual dashboard files. You can see the two files here: https://github.com/lux4rd0/weatherflow-dashboards-aio/tree/main/config/grafana/dashboards/weatherflow. If you do have a Tempest and it’s still not showing – certainly get back with me and we’ll troubleshoot it.

By: thebaldgeek

thebaldgeek — Wed, 10 Mar 2021 14:07:38 +0000

Update.
I am seeing battery voltage and RSSI and also Wind Direction (Rapid) and Wind Speed (Rapid / 60 Seconds). All other graphs are blank.
I see all the data in my Node-RED and also on the WeatherFlow forums Raspberry Pi 7 inch touch screen project.
Can you point me in the direction where Loki ingest is looking for the JSON data? I would like to get this going, but am not sure where the data is decoded from the WeatherFlow UDP stream.

By: thebaldgeek

thebaldgeek — Tue, 09 Mar 2021 00:25:14 +0000

Dave, thanks so much for your help…. I now see a little bit of data!!!
Using the ‘echo’ command, I know my UID and so added that to the yml as you said and it started with no errors.

The odd thing now is that I see device detail data, the RSSI and battery voltage graph is filling out as is the status for the hub and Tempest, but all other dashboards are blank with a simple ‘No data found in response’… My guess? WeatherFlow changed the UDP data format at some stage/firmware version and so the data collector is not seeing my data.

By: Dave Schmid

Dave Schmid — Mon, 08 Mar 2021 04:43:47 +0000

In reply to thebaldgeek. Hello! And thanks for spending some time trying to make this work. My hope was that for most, simply running the docker-compose and/or up.sh commands would just "work". But what I've seen is the permissions for running the containers tend to get messy. What I suspect is that Loki is trying to start up but doesn't like the permissions where the data files are being created and/or written. If you start the script up without the proper UID/GID the first time - that /data/loki gets created as root or doesn't get created at all. You may need to manually change the docker-compose.yml file to reflect the actual numbers of the user ID that you're running as. The "WARNING: The UID_GID variable is not set" would explain some of those errors. In the Loki stanza in the docker-compose.yml, can you change the user: "${UID_GID}" to something like user: "0:0" (if you're root) or whatever you actual user/group permissions on the file system are? Can you also share what OS/system you're trying to run it on? You can also (for sake of testing) comment out the " - ./data/loki:/tmp/loki:rw" and user to see if Loki starts up. I have that volume mount external to the container so that you don't lose the data if you "down" the container. Lastly - thanks for the 50022/50222 typo. I updated it!

By: thebaldgeek

thebaldgeek — Mon, 08 Mar 2021 04:04:27 +0000

Thanks so much for doing this. I have been looking for something like this for a while.
Spent about 2 hours trying to get it working to no success as yet.
Not sure how to set the UID.
The command ‘export UID_GID=”$(id -u):$(id -g)”‘ does nothing. So I added ‘echo’ to the front to find my UID.
Once I found that, I was able to edit the up, stop, down scrips as you suggest.
Had to launch them with sudo as doing it as a user fails due to permission issues.
Once running, I can view the Grafana dashboard, but there is no data. On each graph there is a red mark with ‘bad gateway’.
Also in the doc the weatherflow device is mentioned to be on UDP port 50022, but the yml file as the correct port of 50222.

When starting the docker, I get the following:

sudo docker-compose -f docker-compose.yml up -d
WARNING: The UID_GID variable is not set. Defaulting to a blank string.
Creating network “weatherflow-dashboards-aio-102_wxflowaio” with the default driver
Creating loki … done
Creating grafana … done
Creating weatherflow-listener … done

I know my weatherflow device is on UDP port 50222 as my Node-RED can see the data.

Any help you can offer to get the data to show would be greatly appreciated.
Thanks.

By: Fred

Fred — Mon, 08 Mar 2021 01:33:31 +0000

In reply to Fred.

Splendid charts, Dave! All appears to be working well on my Raspberry Pi 3 Model B Rev 1.2 running Raspbian GNU/Linux 10 (buster). I verified Loki and promtail were working together before running your up.sh script. When started from your script, Loki was not finding your config file but was looking for one in /etc/loki. cp weatherflow-dashboards-aio-1.02/config/loki-config.yml /etc/loki/ took care of that and my charts started populating with Tempest data.

Sometime I hope to move to the new PI OS, but I am glad Raspbian Buster is compatible.
PS Other Raspbian Buster users will find Docker installs easily but Docker-compose appears as a stumbling block since the Docker intall scripts aren’t compatible. PIP is the answer.

install via pip – https://dev.to/rohansawant/installing-docker-and-docker-compose-on-the-raspberry-pi-in-5-simple-steps-3mgl
 sudo apt-get install -y libffi-dev libssl-dev
sudo apt-get install -y python3 python3-pip
sudo apt-get remove python-configparser
sudo pip3 -v install docker-compose