And what happens without the "-v" flag? Try running

this:
root@heidenrod-obs:/usr/share/weatherradio# python -m pdb /usr/share/weatherradio/bin/wr_rrd_update.py
> /usr/share/weatherradio/bin/wr_rrd_update.py(16)<module>()
-> import sys
(Pdb) n
> /usr/share/weatherradio/bin/wr_rrd_update.py(17)<module>()
-> from indiclient import *
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(18)<module>()
-> from weatherradio import *
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(19)<module>()
-> from os import path
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(20)<module>()
-> import argparse
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(21)<module>()
-> from pid.decorator import pidfile
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(22)<module>()
-> from pid import PidFileError
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(25)<module>()
-> @pidfile()
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(26)<module>()
-> def update(args, indi=None):
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(66)<module>()
-> if __name__ == "__main__":
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(67)<module>()
-> parser = argparse.ArgumentParser(description="Fetch weather data and store it into the RRD file")
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(68)<module>()
-> parser.add_argument("-v", "--verbose", action='store_true',
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(69)<module>()
-> help="Display progress information")
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(68)<module>()
-> parser.add_argument("-v", "--verbose", action='store_true',
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(70)<module>()
-> parser.add_argument("rrdfile", nargs='?', default=RRDFILE,
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(71)<module>()
-> help="RRD file holding all time series")
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(70)<module>()
-> parser.add_argument("rrdfile", nargs='?', default=RRDFILE,
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(72)<module>()
-> parser.add_argument("rrdsensorsfile", nargs='?', default=RRDSENSORSFILE,
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(73)<module>()
-> help="RRD file holding all sensor data time series")
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(72)<module>()
-> parser.add_argument("rrdsensorsfile", nargs='?', default=RRDSENSORSFILE,
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(75)<module>()
-> args = parser.parse_args()
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(77)<module>()
-> try:
(Pdb)
> /usr/share/weatherradio/bin/wr_rrd_update.py(78)<module>()
-> update(args)
(Pdb)
--Return--
> /usr/share/weatherradio/bin/wr_rrd_update.py(78)<module>()->None
-> update(args)
(Pdb)
--Return--
> <string>(1)<module>()->None
(Pdb)
The program finished and will be restarted

Interesting, I get no output this time.

root@heidenrod-obs:/usr/share/weatherradio# /usr/share/weatherradio/bin/wr_rrd_update.py
root@heidenrod-obs:/usr/share/weatherradio#

the rrd files are not being updated

using python 3.8 by the way

:/usr/share/weatherradio# python -V
Python 3.8.5

I've spent a fair bit of time on this issue, without the -v it does not connect and I am unable to get any data in the weather.rdd file (just a bunch of 0's)

I have tried to flash the board for 9600 and 115200 speed, tried python debugging, tried strace it. I cannot see what's going on.

Interesting find:

root@heidenrod-obs:/usr/share/weatherradio/html/data# ll RTdata_*
-rw-r--r-- 1 root root 22684 Mar 26 15:00 RTdata_1d.json
-rw-r--r-- 1 root root 732 Mar 26 00:00 RTdata_30d.json
-rw-r--r-- 1 root root 27598 Mar 26 15:00 RTdata_6h.json
-rw-r--r-- 1 root root 5674 Mar 26 15:00 RTdata_7d.json
-rw-r--r-- 1 root root 275 Mar 26 15:00 RTdata_lastupdate.json
root@heidenrod-obs:/usr/share/weatherradio/html/data#

all bar the RTdata_lastupdate.json are being populated, and if I understand correctly, the RTdata_ files are the ones used on the weatherradio.html page...

It's really awkward. What about shifting our communication to PN?

I would set a breakpoint at line 42 of wr_rrd_update.py and step through carefully.

HTH
Wolfgang

You have a private message

So after hours of debugging and trying to figure out why it wasn't working as it should, I've figured it out. In my case it was about the unit file itself.
On the Odroid C4 running Ubuntu 20.04 I have to slightly change it.

From the doc :
[Unit]
Description=INDI server for weather radio
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=root
ExecStart=/usr/bin/indiserver -v indi_weatherradio

[Install]
WantedBy=multi-user.target

While mine is:
[Unit]
Description=INDI server for weather radio
After=multi-user.target

[Service]
Type=idle
User=root
ExecStart=/usr/bin/indi_weather -p 7625 -v indi_weatherradio

[Install]
WantedBy=multi-user.target


I was only able to fix it out after testing the python scripts against indiserver running off the command line and not as a service.
The data is being recorded and shown on the webpage.

Hello
I had to change my router for my observatory, but I have a problem.
How do I open the webradio page to access it from a PC that is not in the network?
I remember that I have to make the IP fixed and open a port, but I don't remember how to do it, who can help me?
Thanks

Hello
I have a question, I would like to redo my assembly for my weather station and I was going to put a Nano Evry, but I can't upload the program METEORADIO_VERSION "1.5" on it.
I have this error
"" avrdude: jtagmkII_getsync(): sign-on command: status -1 """

I'm not sure if it's possible to install it on this card ?

Thank you very much for your help.

Hi Gilles,

after more than 2 years I'd like to ask you what have you accomplished? I'm following this weatherradio threat since about 2 years but still struggling with the data transfer to the webpage.
I run two RPi 4B one on the OTA rig the other in the observatory. Please find the attachement.
Even the last version of weatherradio will not cooperate . with the rrd-database and theire scritps. wr_rrd_update.py comes back with"ERROR 11 Resource temporarily not available".
The drivers in Ekos all connect and working. Data are presented and the wifi transmission (JSON pretty print of sensor data "/p") also works fine.
It was also possible to combine the relatively new indi-allsky programm and the "observatory" indi-drivers on different indi ports. So they stoped fighting and concurring about the several devices.

I'm very interested having this system working.

best regards ggtux