Describe the bug
I tried to use allsky_publishdata with MQTT.
Configure in Module Manger:
Server: 192.168.8.1
MQTT Port: 1883
Topic: Allsky
Username and Passwort

I run tcpdump to see what is happen. It holds a tcp connection with my server, but sends
a different MQTT Topic and states a data I guess from a different module. The clearsky module
is definitely not running.
What should I do?

Expected behaviour
A clear and concise description of what you expected to happen.

Screenshots
tail -f /var/log/allsky.log
Feb 16 23:57:14 allsky allsky[819]: STARTING EXPOSURE at: 2024-02-16 23:57:14 @ 30.0 sec
Feb 16 23:57:49 allsky allsky[819]: > Saving NIGHT image 'image-20240216235714.jpg'
Feb 16 23:58:01 allsky allsky[2326]: ERROR: Module allsky_publishdata.py failed on line 224 - [Errno 104] Connection reset by peer....

TCPdump:allsky.lan.50835 > 192.168.8.1.1883: Flags [S], cksum 0x2ff4 (correct), seq 3238881066, win 64240, options [mss 1460,sackOK,TS val 2326663658 ecr 0,nop,wscale 6], length 0
192.168.8.1.1883 > allsky.lan.50835: Flags [S.], cksum 0xc2d1 (correct), seq 969868372, ack 3238881067, win 28960, options [mss 1286,sackOK,TS val 1200452061 ecr 2326663658,nop,wscale 8], length 0
allsky.lan.50835 > 192.168.8.1.1883: Flags [.], cksum 0x5dfb (correct), seq 1, ack 1, win 1004, options [nop,nop,TS val 2326663700 ecr 1200452061], length 0
allsky.lan.50835 > 192.168.8.1.1883: Flags [P.], cksum 0x4c4a (correct), seq 1:224, ack 1, win 1004, options [nop,nop,TS val 2326663700 ecr 1200452061], length 223
192.168.8.1.1883 > allsky.lan.50835: Flags [.], cksum 0x606c (correct), seq 1, ack 224, win 118, options [nop,nop,TS val 1200452099 ecr 2326663700], length 0
192.168.8.1.1883 > allsky.lan.50835: Flags [R.], cksum 0x6068 (correct), seq 1, ack 224, win 118, options [nop,nop,TS val 1200452099 ecr 2326663700], length 0
{"available":{"clearsky":{"module":"allsky_clearsky.py","metadata":{"name":"Clear Sky Alarm","description":"Clear Sky Alarm","module":"allsky_clearsky","version":"v1.0.0","events":{"0":"day","1":"night"},"experimental":true,"arguments":{"detectionThreshold":0.55,"distanceThreshold":20,"annotate":"false","template1":6,"mask":"","debug":"false","clearvalue":10,"roi":"","roifallback":5,"mqttenable":"False","mqttbroker":"","mqttport":1883,"mqttusername":"","mqttpassword":"","mqtttopic":"SKYSTATE","debugimage":""},"argumentdetails":{"roi":{"required":"true","description":"Region of Interest","help":"The area of the image to check for clear skies. Format is x1,y1,x2,y2","type":{"fieldtype":"roi"}},"roifallback":{"required":"true","description":"Fallback %","help":"If no ROI is set then this % of the image, from the center will be used","type":{"fieldtype":"spinner","min":1,"max":100,"step":1}},"clearvalue":{"required":"true","description":"Clear Sky","help":"If more than this number of stars are found the sky will be considered clear","type":{"fieldtyp [|http]
allsky.lan.43977 > 192.168.8.1.1883: Flags [S], cksum 0xa1bd (correct), seq 2178699516, win 64240, options [mss 1460,sackOK,TS val 2326728777 ecr 0,nop,wscale 6], length 0
192.168.8.1.1883 > allsky.lan.43977: Flags [S.], cksum 0x7ec7 (correct), seq 209643806, ack 2178699517, win 28960, options [mss 1286,sackOK,TS val 1200517174 ecr 2326728777,nop,wscale 8], length 0
allsky.lan.43977 > 192.168.8.1.1883: Flags [.], cksum 0x1a01 (correct), seq 1, ack 1, win 1004, options [nop,nop,TS val 2326728803 ecr 1200517174], length 0
allsky.lan.43977 > 192.168.8.1.1883: Flags [P.], cksum 0x46c1 (correct), seq 1:224, ack 1, win 1004, options [nop,nop,TS val 2326728803 ecr 1200517174], length 223

Allsky Information:

• OS: [name, 64/32bit and Full/lite]
• Allsky Version: Version: v2023.05.01_04, allsky-module repository cloned at 16.02.24
• Pi model: [Include RAM] Pi 3 Model A+ Revision 1.0 (512 MB)
• Camera: [Full details of the camera being used] Raspberry PI HQ

Sensors
If using sensors please outline the sensors being used, include i2c addresses if applicable

Additional context
Add any other context about the problem here.

The module states the MLX90614 sensor - would it be possible to use an MLX90615 on I2c port 0x5b?

Describe the bug
Hello,
I use the module Rain. When I install the module Rain, I have these values in the allskyrain.json (for example).
{
"AS_RAINSTATE": "Raining",
"AS_ALLSKYRAINFLAG": "True"
}

I see the variable on the Overlays Editor :

But I can't show this information on the Live view ?

This is the variable :

An idea ?

Frank

Allsky Information:

• OS: [VERSION="12 (bookworm)" 64b]
• Allsky Version: 2023.05.01_04
• Pi model: [Raspberry Pi 4 Model B Rev 1.2 4go]
• Camera: [RPI HQ]

Sensors
DTH22 + LM393 (rain)

Additional context

The free API doesnt return the dew point but it can be easily calculated from the data returned

I think the Fritzing schematic for the dewheater module ist wrong. I2C-Bus wires for SDA and SCL are mixed up.
https://raw.githubusercontent.com/thomasjacquin/allsky/master/html/documentation/modules/dew-heater.png
This should by right:

Provide more options for the satellite data i.e.

• swap the deg text for a degrees symbol
• Provide decimal values

This is a short term fix before the full satellite module is implemented see #47

Please make InfluxDB Module available in periodic flows in the module manager.
Thanks Thomas

This module will allow tasks to be run outside of the Allsky flows. This could be used for things like

• More detailed star detection
• More detailed meteor detection
• Fisheye to Pano conversions
• Noise reduction

• Ensure all errors are caught
• Inform user if device missing (in log files)

Where do you mount the temperature sensor? In the dome? or to the outside of the camera?
In the dome, the heating is triggered. Is it possible to set hysteresis?

The allsky_ai module does not correctly record the activation setting. I activated the module in the module manager and saved the setting correctly. However, the next day, if I return to the module manager, I find the modules deactivated, both for day and night.

Hello, I'd like to suggest a new feature being: a projection from fisheye to panorama view option that could be added to live view web page. I have my old allsky cam running on ALLSkEye software and plan to change it over to a RPi setup. I will miss the horizon projection view feature in AllSkEye.
cheers CS!

(I love the allsky program, thanks for all your hard work!!!)

Hi,

the installation instruction are no longer available, new instructions from:

https://www.influxdata.com/blog/linux-package-signing-key-rotation/?_gl=1*1t2eak4*_ga*NjE4MTg5Mzc2LjE2ODY2ODEyNjY.*_ga_CNWQ54SDD8*MTY4ODg0MzI0MS44LjEuMTY4ODg0NDMzMC41NC4wLjA.

• wget -q https://repos.influxdata.com/influxdata-archive_compat.key
• gpg --with-fingerprint --show-keys ./influxdata-archive_compat.key
• cat influxdata-archive_compat.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg > /dev/null
• echo 'deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list
• sudo rm -f /etc/apt/trusted.gpg.d/influxdb.gpg

David

Discussed in #96

Discussed in #65

Discussed in #38

I have installed a new camera on a RPI4 / bookworm and everything went fine.

I then downloaded and installed all available modules according to the installation description which seemed to have worked as well.

Now after this all no modules are visible in the WebUI. They are, however, present in the /allsky-modules folder.

Any help to this?

This is the log-file:

uw@meteotux:~/allsky-modules $ sudo cat moduleinstalldebug.log

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
python3-pip is already the newest version (23.0.1+dfsg-1+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: packaging in /home/uw/allsky/venv/lib/python3.11/site-packages (23.2)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: gitpython in /home/uw/allsky/venv/lib/python3.11/site-packages (3.1.41)
Requirement already satisfied: gitdb<5,>=4.0.1 in /home/uw/allsky/venv/lib/python3.11/site-packages (from gitpython) (4.0.11)
Requirement already satisfied: smmap<6,>=3.0.1 in /home/uw/allsky/venv/lib/python3.11/site-packages (from gitdb<5,>=4.0.1->gitpython) (5.0.1)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: whiptail-dialogs in /home/uw/allsky/venv/lib/python3.11/site-packages (0.4.0)
Requirement already satisfied: domdf-python-tools>=1.7.0 in /home/uw/allsky/venv/lib/python3.11/site-packages (from whiptail-dialogs) (3.8.0.post2)
Requirement already satisfied: typing-extensions>=4.1.1 in /home/uw/allsky/venv/lib/python3.11/site-packages (from whiptail-dialogs) (4.9.0)
Requirement already satisfied: natsort>=7.0.1 in /home/uw/allsky/venv/lib/python3.11/site-packages (from domdf-python-tools>=1.7.0->whiptail-dialogs) (8.4.0)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: smbus in /home/uw/allsky/venv/lib/python3.11/site-packages (1.1.post2)

This behaviour has been described before: @ #80

Scenario: Using the BME280 chip with the Dew script works well and provides the system variables, but doesn't provide the chip's available Pressure value. This makes the user require a second script to query the BME280 in order to pull this variable - on my system having this exact setup, the Dew & Secondary script can both attempt to run at the same time causing one of them to error out because it can't find the chip because it's in use.

Is it possible to pull/store the value for use in the overlay editor, even if its not necessarily needed for the dew function?

I'm not sure if this is by design or not, but I cannot get non-numeric values to InfluxDB. For example:

• AS_DEWCONTROLHEATER has On/Off values that I'd like to show on my Grafana dashboards
• AS_MOON_ELEVATION has the º symbol in the value e.g. 36º and it also gets skipped
• AS_DISKFREE has the unit next to the number e.g. 20.68G and it's not sent

How can I get those string values into InfluxDB, or sanitize them to be numeric?

Discussed in #37

Hi

Discussed in #66

Add structured changelog data to the module meta data. This will allow

1. Details of the module changes to be displayed in the module manager
2. Contributors to be credited

NOTE: This will require changes to the core Allsky code as well to display the changelog

Example json

changelog": { 
        "v1.0.0" : [  
            {
                "author": "Alex Greenland",
                "authorurl": "https://github.com/allskyteam",
                "change": "Initial Release"
            }
        ],
        "v1.0.1" : [
            {
                "author": "Damian Grocholski (Mr-Groch)",
                "authorurl": "https://github.com/Mr-Groch",
                "changes": [
                    "Added extra pin that is triggered with heater pin",
                    "Fixed dhtxxdelay (was not implemented)",
                    "Fixed max heater time (was not implemented)"
                ]
            }
        ],
        "v1.0.2" : [
            {
                "author": "Alex Greenland",
                "authorurl": "https://github.com/allskyteam",
                "change": "Initial Release"
            }
        ],
        "v1.0.3" : [
            {
                "author": "Alex Greenland",
                "authorurl": "https://github.com/allskyteam",
                "change": "Add AHTx0 i2c sensor"
            }
        ],
        "v1.0.4" : [
            {
                "author": "Alder6907",
                "authorurl": "https://github.com/Adler6907",
                "change": "Added Solo Cloudwatcher"
            }
        ]                                
    }

I use the MQTT Data Publish Module to export environment data to a remote server. It has a influxDB to store and Grafana to visualize this data.

Is your feature request related to a problem? Please describe.

I had to place a NODE-RED instance in front of this because numeric date come as string.
Example: "AS_DEWCONTROLAMBIENT": "23.7"

Describe the solution you'd like

Is it possible to provide numeric as numeric, string as string and boolean as boolean.

Thomas

I've read this conversation and I'd be really interested to replicate a similar Grafana dashboard for our AllSky setup! The discussion is thorough but I miss some starting points, e.g. which modules to use (if avaialble) or what is needed to install on the Raspberry and ultimately if the dashboard is anywhere available to download.

Is a guide available to create such setup?

Describe the bug
When utilizing only the timelapse posting feature of allsky_discordsend.py, and if only the timelapse webhook URL is populated, the script will fail and log ERROR: Module allsky_discordsend.py failed on line 224 - can only concatenate str (not "NoneType") to str

To Reproduce
Steps to reproduce the behaviour:

1. Go to the settings of the DiscordSend module in the allsky web UI
2. Enable only the "Post timelapse videos" checkbox
3. Add a valid discord webhook URL to only the "The webhook url for Timelapses"
4. Ensure other posting options and webhook fields are disabled or blank
5. Run ./endOfNight.sh or wait for the script to run normally
6. Check /var/log/allsky.log for the above error

Expected behaviour
The script should either warn the user to fill out all webhook fields or only check and concatenate webhook fields of enabled features. Instead, the script fails and logs to /var/log/allsky.log.

When all webhook fields are filled, and the timelapse post feature is enabled, the script completes successfully upon running ./endOfNight.sh

Allsky Information:

• OS: Raspbian GNU/Linux 11 (bullseye) lite | Linux 6.1.21-v7l+
• Allsky Version: v2023.05.01_04
• Pi model: Pi 4 4GB
• Camera: RPi HQ with Arducam M25156H18

Sensors
SHT31

Discussed in #98

Neither the Export nor the Clear Sky modules can be activated and saved in my configuration. Also the settings are not accessible.
In fact none of the available modules can be selected and saved.

Currently I am using - besides the standard ones - two modules: light and AllSKY Export. The corresponding json files are located here:

/home/pi/allsky/config/overlay/extra/allskylight.json

/home/pi/allsky/html/allskydata.json

Since I would want to export those json-files to a server it would be nice to have them all in one directory - in my case in ${ALLSKY_WEBUI}, i.e. /home/pi/allsky/html/.

Is there a way to set this pathway om the light module?

Describe the bug
I cannot write data in my InfluxDB (v2.7.6)

To Reproduce
Simply leave the field InfluxDB Access Token blank results in:

Apr 23 20:53:59 allsky allskperiodic[6440]: The batch item wasn't processed successfully because: (401)
Apr 23 20:53:59 allsky allskperiodic[6440]: Reason: Unauthorized
Apr 23 20:53:59 allsky allskperiodic[6440]: HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json; charset=utf-8', 'X-Influxdb-Build': 'OSS', 'X-Influxdb-Version': 'v2.7.6', 'X-Platform-Error-Code': 'unauthorized', 'Date': 'Tue, 23 Apr 2024 18:54:03 GMT', 'Content-Length': '55'})
Apr 23 20:53:59 allsky allskperiodic[6440]: HTTP response body: {"code":"unauthorized","message":"unauthorized access"}
Apr 23 20:53:59 allsky allskperiodic[6440]: INFO: PI Status Data Written
Apr 23 20:53:59 allsky allskperiodic[6440]: INFO: Turning Fans OFF
Apr 23 20:53:59 allsky allskperiodic[6440]: INFO: CPU Temp is 32.6 and lower then set limit of 60, Fans are Off via fan pin 14
Apr 23 20:53:59 allsky allskperiodic[6440]: INFO: Rain State: Its Not Raining.......

Inserting my API Token results in no log at all?

Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: PI Status Data Written
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: Turning Fans OFF
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: CPU Temp is 33.1 and lower then set limit of 60, Fans are Off via fan pin 14
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: Rain State: Its Not Raining
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: Temperature below forced level 15
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: Turning Heater on using pin 4
Apr 23 20:55:01 allsky allskperiodic[6542]: INFO: Sensor SHT31 read. Temperature 8.0 Humidity 62.57 Relative Humidity None Dew Point 1.3 Heat Index -16.98 Pressure None Altitude None

needless to say, I saved my changes in the module manager. A reboot does not change this behavour.

Allsky Information:

• OS:

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye

• Allsky Version:
• Pi model: 4

Sensors
If using sensors please outline the sensors being used, include i2c addresses if applicable

Additional context
Add any other context about the problem here.

Add clearer process for adding new modules

Add a custom path for users to save images in, this could be in a tmpfs

Also see #40 as this needs to be done at the same time

This will replace the satellite logic in the overlay module.

The new module will allow for more data to be displayed

It will also implement the new json structure for the overlay

Generic module to read upto 3 temperature sensors

The Value of the "Dewheater" Module is shown on the Overlay Editor in "Display Sample Data" Mode, but not on the Saved Frame m- only ???

Describe the bug
I am at least no IT Guy and struggle to bring everything to work. So i Found out that the "Dewheater" Module not only set a Relay, it will Display the DHT22 Sensor Data and Heater Status on the Frame. So i Installed the Modules and Activate in Allsky the Module. I Conigurate it and in the Overlay Screen it work with the correct Data!
But in the Saved Frame only ???

Allsky Information:

• Bookworm 64bit - Lite
• Allsky Version: v2023.05.01_04
• Pi model: Pi 4 Rev B 4 Gig
• Camera: RasPi HD Cam

Sensors
DHT22 (on Gpio 15)

Additional context
I Wonder that it work on the Overlay Screen but not in the Final saved Frame.
As i Mentioed - i am at least no IT Guy and have Problems with all of the Linux and Python Stuff. So i think - for a Windows Guy - the Problem is shurly only a click that is missed......
My Item for Temperature is " Temp: ${DEWCONTROLAMBIENT} °C "

If Anyone give me a bit of help i would be happy

Thx

Skplgi

Discussed in #82

When installing a module keep the dependencies file on the pi. This will allow the main Allsky installer to add the dependencies when doing an upgrade with a venv.

Currently since the venv is created each time an upgrade is done there are no module dependencies in the venv which causes the flow upgrader to fail when attempting to load a module with dependencies.

I have added a short term 'fix' to the main Allsky installer so that it copies over the old venv folder when doing an upgrade, this is done without overwrite so as not to break any updated code !

Also add additional functions to the installer

1. An option to display module information
2. A system check

two new folders will be created in the /opt/allsky/modules folder

dependencies - This will hold the apt and pip files
info - Any readme.txt file available for a module

I have a TSL2561 sensor on the standard 0x29 address.

Unfortunately no json-file is created:

Any testing I could do?

I have used a simple python code and it gives me this:
pi@meteotux:~/scripts $ sudo python3 TSL2561.py
Full Spectrum(IR + Visible) :17 lux
Infrared Value :4 lux
Visible Value :13 lux

Hi Alex, I've installed a fresh Dev branch of allsky and have come here to fetch the extra modules.

The clone has worked, chmod'd the install script and ran it.

I get the error message:

AllSky does not seem to be installed. The /opt/allsky directory does not exist. Please install AllSky before installing the modules

Allsky is installed, so what do I need to check?

Discussed in #29

Create a new module that can extract data from various types of weather stations. This data would then be used for

• The dew heater module (NOTE: This new module would need to run before the dewheater module)
• Displaying on the overlay

Supported weather stations to include

• Ecowitt (Fine offset)
• Davis
• Netatmo
• DIY (Will require data to be written to a specific location is a defined format)
• ???

Describe the bug
On a fresh setup of Allsky the default modules are all present in the module manager. After following the installation instructions and installing the extra modules via https://github.com/AllskyTeam/allsky-modules.git I get an empty list of modules in the module manager in the web UI. All python files are still found in both /opt/allsky/modules and /home/pi/allsky/scripts/modules/.

To Reproduce
Steps to reproduce the behaviour:

1. git clone https://github.com/AllskyTeam/allsky-modules.git to home directory on pi.
2. cd into cloned allsky-modules directory
3. run ./install.sh
4. after python venv starts navigate to "Install/Remove Modules"
5. Select all and press enter. Wait for install to finish
6. Restart Pi
7. Go to module manager on webUI and the list is now empty.

Expected behaviour
Expected to see additional modules listed alongside original default modules in the webUi manager.

Screenshots
I

Allsky Information:

• OS: [Raspberry Pi OS, 64bit, lite, version 12 Bookworm]
• Allsky Version: v2023.05.01_04
• Pi model: Raspberry Pi 4 Model B 8GB
• Camera: ZWO ASI224MC

Additional context
This was all done on a fresh installation of Raspberry Pi OS. As a test i wiped the SD card and ran through the setup again with the same outcome.

Discussed in #111

Describe the bug
When trying to publish data to MQTT broker the module throws the exception in allsky.log:
ERROR: Module allsky_publishdata.py failed on line 224 - Client.init() missing 1 required positional argument: 'callback_api_version'
Nothing beeing published to MQTT.

To Reproduce
Steps to reproduce the behaviour:

1. install BookWorm 32 bit lite on Rasberry pi
2. install Allsky
3. install publishdata module
4. configure MQTT broker
5. Activate publishdata module
6. Restrt Allsky
7. Waith for the 1st picture publication
8. See error in /var/logs/allsky.log

Expected behaviour
No error in log
data been published

Allsky Information:

• OS: Linux allsky 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64
• Allsky Version: 2023.05.01_04
• Pi model: Model 4B Revision 1.4 (2 GB)
• Camera: HQ

Additional context
It seams thst this is typical behavior on BookWorm Rasbian.
I had the same issue with my code and solved it by: client = paho.Client(paho.CallbackAPIVersion.VERSION1)

Hello, good afternoon.
I have a question about the operation of the SQM module. I have it activated but I don't see any changes or any option that calculates anything.
Do you have the operating instructions for it?
All the best.

New module to replace the Sun, Moon and Planets logic in the overlay module

When the AllSkyCam is in day mode, no moonrise or moonset is displayed. Everything is ok in night mode. Is there a solution for this?

Logged from AllskyTeam/allsky#3324

Discussed in #123

In the meta data add a field defining which, if any buses are require i.e. i2c by the module

This will be used in the installer to verify that the relevant busses are enabled