Cronweatherflow can't open local file for writing

Ask a Question
, , ,
1

I am using Cronweather flow 9.0 which I run as ADMIN
I am using WeatherDisplay 10.37S Build 152
I am also running on Windows 11
and I am using a Tempest from Weatherflow

I just installed a new replacement Weatherflow. However when I went to set it up in WD it did not come back with the Sensor numbers to use.

I checked with Cronweatherflow and it keeps coming back with Can’t open local file for writing, so I am not able to get it to accept the station ID

Also, maybe unrelated, I noticed that the “Enabled” radio button where you set up the Tempest in WD is already enabled and can’t be cleared. Its also for me been empty until I fill it like the instructions state.

Any advice would be greatly apprecated
Brian B
W4BJB

2

I tried uninstalling and then reinstalling everything again. I deleted the entire directory.

No change

3

You might need to contact Brian directly by email to have him look at this. It’s possible that the code doesn’t handle adding a new device correctly.

4

I shall do that. It’s extremely frustrating since it’s the exact same weather station model.

5

What ever happened with this? I have a new WeatherFlow sensor and hub and consolewd/cronweatherflowconsole do weird things (but not good things). I am getting an error that weatherflowdataip.txt doesn’t exist. Well that must be created by cronweatherflowconsole and that isn’t anything I have control over. Then the process hangs. What did you learn from Brian?

I’d really like to know exactly how consolewd and cronweatherflowconsole work, and how they are supposed to be run as a service on a linux box. Any advice would be appreciated.

6

You might need to contact Brian direct, too. . .

7

Running consolewd in the Background Using serviced explains how to run consolewd as a service. I’ve never seen anyone discuss running other related processes as a service so I assume consolewd runs any it needs for itself.