Cumulus Support

I recently installed a WeatherFlow Tempest system. Whilst I am happy so far, it does not have an inside temperature sensor. Does anyone have a solution to this problem and if so, how would I install such a sensor? P.S. this supersedes my previous post as the subject was too broad!

I don't have any suggestions for your problem but I am planning on switching my station from a Fine Offset clone to a Weatherflow Tempest system and wondered if you had any suggestions on how I should proceed with the change.

TIA
Garry Ehman

I did exactly the same and the changeover was easy and smooth.

Great, thanks for the quick reply. My new station is on the way. I am happy to have someone to talk to if I have any problems.

Garry

When I first installed my WeatherFlow Tempest, I had to seek help for the following Cumulus error message:-

Error downloading tempest history: {"status":{"status_code":401,"status_message":"UNAUTHORIZED"}}
Normally indicates incorrect Token

when starting Cumulus.

The reply from another kind user was:-

If you go to the tempest site online: https://tempestwx.com/settings (and login)

Down at the bottom you will see a "Data Authorizations" section. Click on that and then click on "Create Token". This is the token that you'll need to enter in the "Security Token" field in order to retrieve historical data.

You'll also need the "Device ID" of your Tempest station which can be found by going to the same site, then "Settings", "Stations", (select your station), "Status". Then down in the bottom section of the page is the "Device ID" field.

Best of luck!

I'm having trouble linking CumulusMS and my Tempest system.

Looking in the logs I get the error (the gap in ht tp is show the bb does not treat it as a hyperlink and it is visible)

2023-02-05 17:36:58.592 GetRestPacket: Requesting from URL - ht tps://swd.weatherflow.com/swd/rest/observations/device/96144?token=<<token>>&time_start=1675618560&time_end=1675618618
followed by
Error downloading tempest history: {"status":{"status_code":404,"status_message":"NOT FOUND"}}

The token is entered into Cumulus, and it is unique for this application.

I also use Home Assistant which has successfully linked through the API.

I have tried both the letest pi image and the Windows version, and they both return the same error.

The message would indicate the token is not being passed to the call.

Has anyone seen this or can offer any assistance?

A 404 error, is a not found error, if the token was missing, I would expect a 401 authorisation error.

Does it work if you enter the URL into a browser? - substituting the proper token of course.

Thanks - that helped me find it

I had put in the Station ID and it needed the Device ID.

Now it does the first download of data fine, but no more,

Back to the logs....

Well, after a day of trying, I am no further forward with CumulusMX on pi with Weatherflow Tempest.

The rest calls work for device and station.
I have disabled the Home Assistant integration, and it had no effect.
I have created a new clean install from the pi image for cmx - no effect.
I have setup CumulusMX on Windows, and it behaves exactly the same, so it must be something I have setup incorrectly.

The logs show no errors

The logs show the data being imported.

The graphs and stats show the data has been collected from swd.weatherflow.com and it all displays fine.

The first rest call appears to be fine as the figures are the same as on the weatherflow app.

Then no further REST calls appear to be make and the end of the log file shows as below.

Does anyone have any further ideas of what I can look at to find what I have setup wrong?

Thanks in anticipation....

Jan

2023-02-06 16:49:59.217 TempestDoRainHist: Total Precip for Day: 0
2023-02-06 16:49:59.217 Windrun: 1mph for 1 minutes = 0.0miles
2023-02-06 16:49:59.217 DoLogFile: Writing log entry for 06/02/2023 16:47:00
2023-02-06 16:49:59.218 DoLogFile: log entry for 06/02/2023 16:47:00 written
2023-02-06 16:49:59.219 Writing today.ini, LastUpdateTime = 06/02/2023 16:47:00 raindaystart = 0 rain counte r = 0
2023-02-06 16:49:59.232 Processing data for 06/02/2023 16:48:00
2023-02-06 16:49:59.233 TempestDoRainHist: New Precip: 0, Type: None, Rate: 0, LocalDayRain: 0, LocalRainChe cked: 0, FinalRainChecked: 0
2023-02-06 16:49:59.233 TempestDoRainHist: Total Precip for Day: 0
2023-02-06 16:49:59.233 Windrun: 1mph for 1 minutes = 0.0miles
2023-02-06 16:49:59.233 DoLogFile: Writing log entry for 06/02/2023 16:48:00
2023-02-06 16:49:59.234 DoLogFile: log entry for 06/02/2023 16:48:00 written
2023-02-06 16:49:59.235 Writing today.ini, LastUpdateTime = 06/02/2023 16:48:00 raindaystart = 0 rain counte r = 0
2023-02-06 16:49:59.246 Processing data for 06/02/2023 16:49:00
2023-02-06 16:49:59.246 TempestDoRainHist: New Precip: 0, Type: None, Rate: 0, LocalDayRain: 0, LocalRainChe cked: 0, FinalRainChecked: 0
2023-02-06 16:49:59.247 TempestDoRainHist: Total Precip for Day: 0
2023-02-06 16:49:59.247 Windrun: 2mph for 1 minutes = 0.0miles
2023-02-06 16:49:59.247 DoLogFile: Writing log entry for 06/02/2023 16:49:00
2023-02-06 16:49:59.247 DoLogFile: log entry for 06/02/2023 16:49:00 written
2023-02-06 16:49:59.249 Writing today.ini, LastUpdateTime = 06/02/2023 16:49:00 raindaystart = 0 rain counte r = 0
2023-02-06 16:49:59.259 End processing history data. Rate: 52.63/second
2023-02-06 16:49:59.267 Start Extra Sensors
2023-02-06 16:49:59.267 Start Timers
2023-02-06 16:49:59.267 Starting 1-minute timer
2023-02-06 16:49:59.271 Data logging interval = 2 (10 mins)
2023-02-06 16:49:59.271 Realtime not enabled
2023-02-06 16:49:59.274 Normal running
2023-02-06 16:50:00.357 DoLogFile: Writing log entry for 06/02/2023 16:50:00
2023-02-06 16:50:00.357 DoLogFile: log entry for 06/02/2023 16:50:00 written
2023-02-06 16:50:00.360 Writing today.ini, LastUpdateTime = 06/02/2023 16:50:00 raindaystart = 0 rain counte r = 0
2023-02-06 16:51:00.280 *** Data input appears to have stopped
2023-02-06 16:52:00.291 Alarm (Data Stopped): Triggered, value = 0
2023-02-06 16:52:00.291 *** Data input appears to have stopped
2023-02-06 16:53:00.301 *** Data input appears to have stopped
2023-02-06 16:54:00.310 *** Data input appears to have stopped

I'm not familiar with the Tempest station. But from what I can see CMX just sits there waiting to receive UDP messages from the station.

The only REST involved seems to be requesting the historic data at start-up.

So, do you have a firewall blocking the UDP packets? - The rPi doesn't have enabled by default.

Is there anything you need to configure on the station to enable the transmission of this UDP data?

The Tempest will broadcast those packets by default. I'm not aware of any way to disable that.

@mcrossley is correct. The only REST calls will be on startup trying to grab any data since the last received by Cumulus.

My first guess would be that a firewall is blocking them. If not that, then I believe the Tempest has to be on the same subnet otherwise those broadcast packets won't be routed and you won't see them on any other subnet.

If you're using linux, you can use socat to dump the received data to stdout.

$ socat UDP-RECV:50222 STDOUT


The udp packets should start being logged to the terminal about every 3 or 4 seconds.

jokerboy wrote: ↑Mon 06 Feb 2023 6:16 pm My first guess would be that a firewall is blocking them. If not that, then I believe the Tempest has to be on the same subnet otherwise those broadcast packets won't be routed and you won't see them on any other subnet.

Do you know is it broadcast or multicast that is sent? If it is multicast, then some routers/switches may not forward it to all ports depending on their settings. Also if one or both (temperst and rpi) are connected to a guest wifi, some routers hide them from each other but the internet still works (client isolation).

Do you know is it broadcast or multicast that is sent?

I don't know, sorry.

jokerboy wrote: ↑Mon 06 Feb 2023 6:54 pm

Do you know is it broadcast or multicast that is sent?

I don't know, sorry.

No problem, in any case hopefully these comments can lead Jan to the roots of the problem. Further debugging would probably need exact knowledge about his network design, used devices and their settings.