Perfectly right, the documentation is wrong. It needs to be
what you write is exactly what the docs are saying, but this doesn’t work.
sudo a2enconf weatherradio
Hm, strange. What happens if you place a symbolic link into /etc/apache2/conf-enabled and restart apache:
cd /etc/apache2/conf-enabled/ ln -s ../conf-available/weatherradio.conf . sudo systemctl restart apache2.service
Could you post the section of your firmware that recognizes the DHT sensor? In the weather radio header file it looks like this:
Now it is showing up but no data and with "DHT init: false". Pin is right, typ selection too. I have a model with a resistor on the little board. ?
#include "DHT.h" DHT dht(DHTPIN, DHTTYPE);
Hm, seems like it is not in the right place. Did you really place it under /etc/apache2/conf-available ?
Another issue I do have with the add-on and the module activation in apache2. sudo a2enmod weatherradio fails all the time.
"ERROR: Module weatherradio does not exist!" How does a mod looks like? I do have weatherradio.conf in the right place.
please take a look into the Firmware Configuration section of the Readme .
I assume you are familiar with the Arduino IDE. When you open the weatherradio.ino firmware, there are several header files included. All configurations should be placed in config.h:
// DHT sensor family #define DHTPIN 3 // Digital pin connected to the DHT sensor //#define DHTTYPE DHT11 // DHT 11 - Uncomment whatever type you're using! #define DHTTYPE DHT22 // DHT 22 (AM2302), AM2321 - Uncomment whatever type you're using!
There is indeed an option to integrate the INDI webmanager into apache.
First install the WSGI module for apache:
sudo apt install libapache2-mod-wsgi
sudo systemctl restart apache2.service
The GEO_... stuff should be irrelevant for connecting. Nevertheless please set at least GEO_COORD_ELEV to the correct value of your location, since this value is used to calculate sea level air pressure.
Are you 100% sure that the serial device is the same as EKOS sets? Sometimes EKOS uses autodetect and changes the value.
The rest of the configuration looks reasonable...
Version 1.7 is OK, the only changes in 1.8 is that it supports multiple instances of Weather Radio. And the Arduino version does not matter.
For further analysis, try the python debugger pdb:
OK, that's not that suprising. In the second log you see the INDI communication in case that a client connects to the INDI server after the INDI server has connected successfully to the Weather Radio device.
Client 0 in the second log comes from EKOS and client 5 is your other RPi connecting with the python script.
The core question: why does the python script does cannot connect successfully. Could you please take a look into the configuration wr_config.py? Maybe the device parameters INDIDEVICEMODE and NDIDEVICEPORT are set to different values than you use via EKOS.
Hm, strange. Maybe it makes sense if you increase the verbosity on the INDI server and see whether the CONNECT command is received.
If this does not help, I would recommend to step through with the python debugger pdb.
And by the way: I've grabbed a RG11 from eBay and I will try to implement this in the next weeks (or months :-/ )
P.S. I may have a question for you on the Avalon Stargo driver regarding remote azimuth-altitude control (M-Zero OBS)
G_Gagnon wrote: Wolfgang, the home PC does not run an indiserver, it runs KStars and Ekos and connects to the indiserver running on the observatory and the one running on the mount (via driver@obsy and driver@mount instances). No slew problem whatsoever.