×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Weather radio don't want connect

  • Posts: 89
  • Thank you received: 16
In case anyone else has tried allsky on the pi you are running weatherradio on you may find that weatherradio suddenly stops serving webpages

One workaround is;
Ensure apache is running.

sudo systemclt status apache2

If you installed allsky it will install lighttpd and that will grab port 80 so apache can't run unless you change the port it listens to to something other than 80.

I changed it to port 81

Then you would access weather radio as

http://weather radio:81/weatherradio

A better solution would be to get weatherradio to run on lighttpd or to get allsky to run on apache
3 years 4 months ago #63413

Please Log in or Create an account to join the conversation.

  • Posts: 250
  • Thank you received: 3

Replied by Porchet on topic Weather radio crash

hello
I have a small problem with WeatherRadio, not serious but recurring.
I don't know for what but each time, after a certain time I have the weather crashing.
So I have to restart the serverindi of the weather, it can take a week or sometimes less or more.
Who has an idea of where the problem can come from.
I have version 1.8
3 years 4 months ago #63524

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Hm, strange, haven't seen that in my setup. Mine is running for weeks without a problem.

Do you have a log file available?
3 years 4 months ago #63526

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Absolutely. If there is somebody out there having a config file for lighthttpd, it would be great to share it. Then I could include it into the next release.

Btw, it should not be that complicated, since it simply serves some files.
3 years 4 months ago #63528

Please Log in or Create an account to join the conversation.

  • Posts: 250
  • Thank you received: 3

Replied by Porchet on topic Weather radio crash

<strong>Do you have a log file available?</strong>

how do I give you the log file ?
or how a fact for log file ?
Last edit: 3 years 4 months ago by Porchet.
3 years 4 months ago #63529

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Depends how you start weather radio. Do you start it directly or do you use KStars?
3 years 4 months ago #63530

Please Log in or Create an account to join the conversation.

  • Posts: 250
  • Thank you received: 3

Replied by Porchet on topic Weather radio crash

then no, it runs on a dedicated tinkerboard only for WeatherRadio.
I'm putting the error I have into you



● indi-weatherradio.service - INDI server for weather radio
Loaded: loaded (/etc/systemd/system/indi-weatherradio.service; enabled; vendo
Active: failed (Result: exit-code) since Wed 2020-11-25 15:54:02 CET; 3 days
Process: 13859 ExecStart=/usr/bin/indiserver -v indi_weatherradio (code=exited
Main PID: 13859 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomple
3 years 4 months ago #63531

Please Log in or Create an account to join the conversation.

  • Posts: 108
  • Thank you received: 4
Hi gents,

I'm almost thru with the installation but a new issue occured. And I hope again of any ideas from you. Thank you in advance.

Last puzzles are the camera but more of interest now is the data collection for the dashboard (based on rrd-database. And there is my problem.
the Python scripts in /usr/share/weatherradio/bin require a config. (see below)
I set it up to my best knowledge.

My current setup is like that:
1. RPi4 (192.168.178.29:7624) runs dedicated Stellarmate OS, indiservers are running, devices are connected
2. a second RPi4 ("allsky",192.168.178.20, basis for the Weatherradio) is connected via ethernet to a NodeMCU8266 microcontroller (192.168.178.75:80) witch has all the sensors.
3. the webservers (Apache2 (port 80) and tinxtdp (port 8080) are also running on the seconf RPi4.

According to Readme-WeatherRadio.md one should generate manually weatherdata (also for testing) by: /usr/share/weatherradio/bin/wr_rrd_update.py and so on.
But in my setup I get an error message:

pi@allsky:/usr/share/weatherradio $ ./bin/wr_rrd_update.py
Updating data from "Weather Radio"@192.168.178.20:7624 FAILED!

further down please see the indiserver startup log. And the driver reports decently all data very reliable.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# INDI server delivering weather data
INDISERVER="192.168.178.29"
#INDISERVER="RPI41"
INDIPORT="7624"

# configure INDI devices - separate multiple devices with ","

# INDI device name
INDIDEVICE="Weather Radio"
# INDI device connection mode: "Ethernet" or "Serial"
#INDIDEVICEMODE="Serial"
INDIDEVICEMODE="Ethernet"
# INDI serial device port (only necessary for Serial mode)
#INDIDEVICEPORT="/dev/ttyUSB0"
# INDI IP address (only necessary for Ethernet mode)
INDI_IP_ADDRESS="192.168.178.75"
# INDI IP port (only necessary for Ethernet mode)
INDI_IP_PORT="80"
# Geo Coordinates - Latitude (as decimal)
GEO_COORD_LAT="51.4797726"
........

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

indiserver startup log:
2020-11-29T09:18:48: startup: indiserver -m 100 -vv indi_weatherradio
2020-11-29T09:18:48: Driver indi_weatherradio: pid=22250 rfd=3 wfd=6 efd=7
2020-11-29T09:18:48: listening to port 7624 on fd 4
2020-11-29T09:18:48: Driver indi_weatherradio: sending <getProperties version='1.7'/>

2020-11-29T09:18:48: Driver indi_weatherradio: read <getProperties device='GPS Simulator' name='GEOGRAPHIC_COORD'>
2020-11-29T09:18:48: Driver indi_weatherradio: snooping on GPS Simulator.GEOGRAPHIC_COORD
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='CONNECTION'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defTextVector device='Weather Radio' name='DRIVER_INFO'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='CONFIG_PROCESS'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='DEBUG'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='CONNECTION_MODE'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defTextVector device='Weather Radio' name='DEVICE_PORT'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='DEVICE_BAUD_RATE'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='DEVICE_AUTO_SEARCH'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='DEVICE_PORT_SCAN'>
2020-11-29T09:18:48: Driver indi_weatherradio: read <defSwitchVector device='Weather Radio' name='SYSTEM_PORTS'>
3 years 3 months ago #63559

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
As the journal says, the information has disappeared. Either check the rotated log or - next time - please call this command earlier.

Maybe additionally you could start indiserver with "-v -v" obtaining more informations.

HTH
Wolfgang
3 years 3 months ago #63560

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370

That looks weird. Did you really post the correct config file? Your config file claims that the indiserver is running on ...29, in fact the script connects to ...20.

Maybe there is another config file hanging around somewhere that has the correct INDISERVER, but has an incorrect device configuration.
3 years 3 months ago #63561

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16
Hi ggtux

I may not understand your setup correctly but;
if you are running

on allsky (192.168.178.20)

Then wr_config.py on allsky should be
INDISERVER="192.168.178.20"
or
INDISERVER="localhost"

and not

INDISERVER="192.168.178.29"


The python scripts in
pi@allsky:/usr/share/weatherradio/bin
will then contact the server on allsky and update the rrd file.

If you want to contact the server on allsky from another box you can chain servers by adding
Remote:Weather Radio@allsky
in addition to your connection to stellarOS connected to your other gear
to the EKOS profile, thats if you are using kstars.
Last edit: 3 years 3 months ago by Adrian. Reason: ggtux
3 years 3 months ago #63579

Please Log in or Create an account to join the conversation.

  • Posts: 108
  • Thank you received: 4
Hi Wolfgang,
you Shaw ist. I tricked a bit with the indiserver log. As I wrote this today I could not copy the log from RPI41. But be sure the indiserver is running and perfectly reporting sensor data.
The config file is the correct one and my description of the setup is also ok.
When I change the IP the error reports the exactly this IP back.
3 years 3 months ago #63580

Please Log in or Create an account to join the conversation.

Time to create page: 1.065 seconds