Overlay not visible - Modules issue (?)

[evripidis]

Hello,

I was trying to install on a partially supported system (Lubuntu) the module for PWS WeatherCloud integration. The module never worked (it always returns False).

Since then , or while I was messing around to make it work, I've "lost" my overlay. All overlays are visible in the Editor but none of them is visible online.

support-none-20250305001723.zip

[EricClaeys]

@evripidis,
There are a lot of errors I've never seen, and I don't think are from Allsky, in /var/log/lighttpd/error.log. One indicates a permissions issue, but it may not be related to your missing overlays. To be safe, though, run: ls -ld ~/allsky/config/modules.

If you don't see drwxrwxr-x in the output run chmod 775 ~/allsky/config/modules.

Also, please ATTACH /var/log/allsky.log. The one in the zip file was empty, which is unusual.

[evripidis]

Good day @EricClaeys

Yes, it is empty and it is strange indeed. I've mentioned that to @Alex-developer too here AllskyTeam/allsky-modules#249 (comment)

I'm "struggling" not to use my RPI again...it is sooo much snappier the mini pc :-(

[EricClaeys]

It's possible Ubuntu does logging differently than Pi OS. It'll be hard to troubleshoot without a valid log file. Perhaps you could search the Internet for where Ubuntu stores log files.

Try running sudo systemctl status allsky

[Alex-developer]

I found some time tonight so have got things 'mostly' running on Ubuntu without having to modify any code.

I also got the 'ERROR:' from the Wunderground module and am diagnosing that. For now can you replace the relevant parts in this url and see if it works in a browser?

https://api.weather.com/v2/pws/observations/current?stationId=STATIONID&format=json&units=e&apiKey=APIKEY)

replace STATIONID with your station id from the Wunderground website
Replace APIKEY with your APIKEY from the Wunderground website

Thanks

Alex

[Alex-developer]

Ok got mine working. The problem for me was the wrong api key !!

pi@alex-ubuntu:~/allsky/scripts$ journalctl -u allskyperiodic -f
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: Loading /home/pi/allsky/config/settings.json
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: ===== Running periodic flow...
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: --------------- Running Module allsky_weatherunderground ---------------
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: <wunderground_pws.api.WUndergroundAPI object at 0xffff72412a20>
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: {'AS_WUSTATIONID': 'IELY53', 'AS_WUOBSTIME': '2025-03-06 22:27:11', 'AS_WURADIATION': 0.0, 'AS_WUUV': 0.0, 'AS_WUWINDDIR': 154, 'AS_WUWINDCARDINAL': 'SSE', 'AS_WUTEMP': 9, 'AS_WUHEATINDEX': 9, 'AS_WUDEWPOINT': 4, 'AS_WUWINDCHILL': 9, 'AS_WUWINDGUST': 13, 'AS_WUWINDSPEED': 7, 'AS_WUPRECIPRATE': 0.0, 'AS_WUPRECIPTOTAL': 0.0, 'AS_WUELEVATION': 0, 'AS_WUQNH': 1000.1, 'AS_WUQFE': '1000.1'}
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: Data acquired and written to extra data file wunderground.json
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: ERROR: Data acquired and written to extra data file wunderground.json
Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: ===== periodic flow complete.
Mar 06 22:27:28 alex-ubuntu allskperiodic[5573]: INFO: Sleeping for 60 seconds

You can use the url I posted above to check if your api key is working

I'll do a more comprehensive update on the Ubuntu setup at the weekend

[evripidis]

https://api.weather.com/v2/pws/observations/current?stationId=STATIONID&format=json&units=e&apiKey=APIKEY)

Yeap, it's working, I can see my observations data as text.

[evripidis]

> pi@alex-ubuntu:~/allsky/scripts$ journalctl -u allskyperiodic -f
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: Loading /home/pi/allsky/config/settings.json
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: ===== Running periodic flow...
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: --------------- Running Module allsky_weatherunderground ---------------
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: <wunderground_pws.api.WUndergroundAPI object at 0xffff72412a20>
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: {'AS_WUSTATIONID': 'IELY53', 'AS_WUOBSTIME': '2025-03-06 22:27:11', 'AS_WURADIATION': 0.0, 'AS_WUUV': 0.0, 'AS_WUWINDDIR': 154, 'AS_WUWINDCARDINAL': 'SSE', 'AS_WUTEMP': 9, 'AS_WUHEATINDEX': 9, 'AS_WUDEWPOINT': 4, 'AS_WUWINDCHILL': 9, 'AS_WUWINDGUST': 13, 'AS_WUWINDSPEED': 7, 'AS_WUPRECIPRATE': 0.0, 'AS_WUPRECIPTOTAL': 0.0, 'AS_WUELEVATION': 0, 'AS_WUQNH': 1000.1, 'AS_WUQFE': '1000.1'}
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: Data acquired and written to extra data file wunderground.json
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: ERROR: Data acquired and written to extra data file wunderground.json
> Mar 06 22:27:28 alex-ubuntu allskperiodic[8811]: INFO: ===== periodic flow complete.
> Mar 06 22:27:28 alex-ubuntu allskperiodic[5573]: INFO: Sleeping for 60 seconds

Here I am, after activating again the modules:

> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: Loading /home/lubuntu/allsky/config/settings.json
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: ===== Running periodic flow...
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: --------------- Running Module allsky_openweathermap ---------------
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: URL - https://api.openweathermap.org/data/2.5/weather?lat=40.6436&lon=22.9309&units=metric&appid=58d4b6ceebc518d700f334932501f223
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: Data acquired and written to extra data file openweather.json
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: INFO: --------------- Running Module allsky_weatherunderground ---------------
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: Traceback (most recent call last):                        
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:   File "/opt/allsky/modules/allsky_weatherunderground.py", line 136, in weatherunderground
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:     shouldRun, diff = s.shouldRun(module, period)
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:                       ^
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: NameError: name 's' is not defined
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: During handling of the above exception, another exception occurred:
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: Traceback (most recent call last):
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:   File "/home/lubuntu/allsky/scripts/flow-runner.py", line 209, in <module>
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:     result = globals()[method](arguments, shared.args.event)
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:   File "/opt/allsky/modules/allsky_weatherunderground.py", line 172, in weatherunderground
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:     s.log(0, f"ERROR: Module weatherunderground failed on line {eTraceback.tb_lineno} - {e}")
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]:     ^
> Mar 07 01:18:43 lubuntu-ami allskperiodic[848380]: NameError: name 's' is not defined
> Mar 07 01:18:43 lubuntu-ami allskperiodic[1767]: INFO: Sleeping for 60 seconds

In the Open Weather Map settings, it says :

There is only one openweather.json file and is located in /home/lubuntu/allsky/config/overlay/extra

[Alex-developer]

https://api.weather.com/v2/pws/observations/current?stationId=STATIONID&format=json&units=e&apiKey=APIKEY)

Yeap, it's working, I can see my observations data as text.

Have you made any changes to the module or the module installer?

If so I would revert the changes, reclone the modules repo and do the following

source ~/venv/bin/activate
pip3 install gpiozero
pip3 install lgpio
pip3 install rpi-gpio

That will allow the module installer to run without errors

The next problem is that the flow manager will not run as it uses the release name to determine if a python virtual environment should be activated so look in ~/allsky/scripts/function.sh for the 'activate_python_venv' function

Change this line

if [[ ${PI_OS} == "bookworm" ]]; then

To

if [[ ${PI_OS} == "bookworm" || ${PI_OS} == "noble" ]]; then

That's the process I used on 24.04LTS and its all working fine so far

[evripidis]

Hello @Alex-developer thank you once again for your time on this, but unfortunately honestly I think that it is getting more and more complicated..

While I pip3 install lgpio, I get :

(venv) lubuntu@lubuntu-ami:~/allsky/venv/bin$ pip3 install lgpio
Defaulting to user installation because normal site-packages is not writeable
Collecting lgpio
  Using cached lgpio-0.2.2.0.tar.gz (90 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: lgpio
  Building wheel for lgpio (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Building wheel for lgpio (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [14 lines of output]
      running bdist_wheel
      running build
      running build_py
      running build_ext
      building '_lgpio' extension
      swigging lgpio.i to lgpio_wrap.c
      swig -python -o lgpio_wrap.c lgpio.i
      creating build/temp.linux-x86_64-cpython-313
      gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC -Isrc -I/usr/local/include/python3.13 -c lgpio_wrap.c -o build/temp.linux-x86_64-cpython-313/lgpio_wrap.o
      creating build/lib.linux-x86_64-cpython-313
      gcc -shared build/temp.linux-x86_64-cpython-313/lgpio_wrap.o -llgpio -o build/lib.linux-x86_64-cpython-313/_lgpio.cpython-313-x86_64-linux-gnu.so
      /usr/bin/ld: cannot find -llgpio: No such file or directory
      collect2: error: ld returned 1 exit status
      error: command '/usr/bin/gcc' failed with exit code 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lgpio
Failed to build lgpio                                                                                                             
ERROR: Failed to build installable wheels for some pyproject.toml based projects (lgpio)

I've moved even further and while I was trying to install/remove modules :

/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from lgpio: No module named 'lgpio'
  warnings.warn(
/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from rpigpio: This module can only be run on a Raspberry Pi!
  warnings.warn(
/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from pigpio: No module named 'pigpio'
  warnings.warn(
/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from native: unable to locate Pi revision in /proc/device-tree or /proc/cpuinfo
  warnings.warn(
Traceback (most recent call last):
  File "/home/lubuntu/allsky-modules/module-installer.py", line 483, in <module>
    moduleInstaller.run()
    ~~~~~~~~~~~~~~~~~~~^^
  File "/home/lubuntu/allsky-modules/module-installer.py", line 475, in run
    self._doInstall()
    ~~~~~~~~~~~~~~~^^
  File "/home/lubuntu/allsky-modules/module-installer.py", line 238, in _doInstall
    self._check_gpio_status()
    ~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/lubuntu/allsky-modules/module-installer.py", line 381, in _check_gpio_status
    pi_version = self._getPiVersion()
  File "/home/lubuntu/allsky-modules/module-installer.py", line 392, in _getPiVersion
    Device.ensure_pin_factory()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py", line 270, in ensure_pin_factory
    Device.pin_factory = Device._default_pin_factory()
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/lubuntu/.local/lib/python3.13/site-packages/gpiozero/devices.py", line 302, in _default_pin_factory
    raise BadPinFactory('Unable to load any default pin factory!')
gpiozero.exc.BadPinFactory: Unable to load any default pin factory!