Moon rise/set times

[NeilAllison147]

In the overlay module, there are SUN_SUNRISE and SUN_SUNSET variables available to display on the overlay.
However, there are no corresponding values for the moon (I.E MOON_MOONRISE and MOON_MOONSET).
Is it possible to have these included?
As an astrophotographer, moon rise/set times are useful pieces of information to have.
I know this information is available in many mobile apps but to have it in allsky (if possible) would be pretty cool.

[Alex-developer]

Thats a good idea :-)

I am currently migrating the logic for the sun/moon and satellites to a new module (https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module/allsky_solarsystem)

If you checkout that branch and install the solarsystem module you can test the Moon times now. If you do install the module dont forget to disable the sun, moon and sats in the overlay options

Alex

[NeilAllison147]

Hi Alex

So, I copied the allsky_solar-system.py script to opt/allsky/modules and activated it in the Module manager (periodic jobs).
What next?
Sorry to come up with what must be very basic questions for you, but I'm still getting to grips with modules (as I'm sure many others are).

:)

[EricClaeys]

@NeilAllison147, it's good to ask questions when unsure. It let's @Alex-developer and me know what additional documentation is needed, or where to modify the code to improve the user experience.
Eric

[Alex-developer]

Hi Alex

So, I copied the allsky_solar-system.py script to opt/allsky/modules and activated it in the Module manager (periodic jobs). What next? Sorry to come up with what must be very basic questions for you, but I'm still getting to grips with modules (as I'm sure many others are).

:)

The idea behind 'modules' is that they can generate data for overlaying on the captured image and also modify the image. The modules exist within flows

Daytime capture flow - These module are only run during the day.
Nightime capture flow - These modules are only run during the night
Day to night flow - These modules are run when allsky transitions from daytime to nighttime capture
Night to day flow - These modules are run when allsky transitions from nighttime to daytime capture
Periodic jobs flow - These modules run independently of images being captured. Typically these are things that do not need to run for each captured image such as getting weather data, running them periodically is fine.

A module can generate data for use in the overlay editor, this is what the solar system module does. After you have added it to the flow clicking on its settings will allow you to specify which solar system objects you wish to have data calculate for. The module will write the data to a file in

~/allsky/config/overlay/extra/solarsystem.json

If you have activated the module and enabled some solar system objects have a look and see if the file is there and contains data, mine looks like this

{
    "AS_MOON_AZIMUTH": "11",
    "AS_MOON_ELEVATION": "-55.62",
    "AS_MOON_ILLUMINATION": "5.23",
    "AS_MOON_SYMBOL": "X",
    "AS_MOON_RISE_FULL": "Fri 29 Nov 2024 05:59:21 ",
    "AS_MOON_RISE_DATE": "29/11/24",
    "AS_MOON_RISE_TIME": "05:59:21",
    "AS_MOON_SET_FULL": "Fri 29 Nov 2024 14:26:08 ",
    "AS_MOON_SET_DATE": "29/11/24",
    "AS_MOON_SET_TIME": "14:26:08",
    "AS_MOON_NEXT_FULL_FULL": "Sun 15 Dec 2024 09:01:38 ",
    "AS_MOON_NEXT_FULL_DATE": "15/12/24",
    "AS_MOON_NEXT_FULL_TIME": "09:01:38",
    "AS_MOON_NEXT_NEW_FULL": "Mon 30 Dec 2024 22:26:44 ",
    "AS_MOON_NEXT_NEW_DATE": "30/12/24",
    "AS_MOON_NEXT_NEW_TIME": "22:26:44",
    "AS_SUN_DAWN": "20241129 07:04:12",
    "AS_SUN_SUNRISE": "20241129 07:44:58",
    "AS_SUN_NOON": "20241129 11:47:47",
    "AS_SUN_SUNSET": "20241128 15:50:41",
    "AS_SUN_DUSK": "20241128 16:31:18",
    "AS_SUN_AZIMUTH": "324",
    "AS_SUN_ELEVATION": "-55"
}

To use this data in an overlay you need to use the 'variable manager' in the Overlay Editor. In the 'variable manager' there are two tabs

Allsky Variables - These are the variables you can use in your overlays
All Variables - Think of this as a library of ALL variables available but to use them you must add them to the 'Allsky variables' tab using the + icon

So in the case of the solar system module you will find variables in the 'All variables' tab like 'AS_MOON_RISE_TIME' Click on the + symbol to add it to the 'Allsky variables; tab, you will need to give it a description but this can be anything you like.

After you had added the variable to the 'Allsky variables' tab you can click on the '+' symbol to add it to the overlay. Do not forget to Save the variables dialog after you have added variables.

The process of doing all of the above is covered in the documentation, see link below, BUT if you think it could be improved then please let us know

https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/overlays/overlays.html

Hope that helps but if not please feel free to ask any questions

Alex

[NeilAllison147]

Hi Alex I'm not getting a "~/allsky/config/overlay/extra/solarsystem.json" file created I tried to run the script via Thonny and got this error: - Traceback (most recent call last): File "/opt/allsky/modules/allsky_solarsystem.py", line 1, in <module> import allsky_shared as s ModuleNotFoundError: No module named 'allsky_shared' Do I have to install anything else as a prerequisite?

…

-- Thanks and Best Regards Neil

On Fri, Nov 29, 2024 at 9:36 AM Alex ***@***.***> wrote: Hi Alex So, I copied the allsky_solar-system.py script to opt/allsky/modules and activated it in the Module manager (periodic jobs). What next? Sorry to come up with what must be very basic questions for you, but I'm still getting to grips with modules (as I'm sure many others are). :) The idea behind 'modules' is that they can generate data for overlaying on the captured image and also modify the image. The modules exist within flows Daytime capture flow - These module are only run during the day. Nightime capture flow - These modules are only run during the night Day to night flow - These modules are run when allsky transitions from daytime to nighttime capture Night to day flow - These modules are run when allsky transitions from nighttime to daytime capture Periodic jobs flow - These modules run independently of images being captured. Typically these are things that do not need to run for each captured image such as getting weather data, running them periodically is fine. A module can generate data for use in the overlay editor, this is what the solar system module does. After you have added it to the flow clicking on its settings will allow you to specify which solar system objects you wish to have data calculate for. The module will write the data to a file in ~/allsky/config/overlay/extra/solarsystem.json If you have activated the module and enabled some solar system objects have a look and see if the file is there and contains data, mine looks like this { "AS_MOON_AZIMUTH": "11", "AS_MOON_ELEVATION": "-55.62", "AS_MOON_ILLUMINATION": "5.23", "AS_MOON_SYMBOL": "X", "AS_MOON_RISE_FULL": "Fri 29 Nov 2024 05:59:21 ", "AS_MOON_RISE_DATE": "29/11/24", "AS_MOON_RISE_TIME": "05:59:21", "AS_MOON_SET_FULL": "Fri 29 Nov 2024 14:26:08 ", "AS_MOON_SET_DATE": "29/11/24", "AS_MOON_SET_TIME": "14:26:08", "AS_MOON_NEXT_FULL_FULL": "Sun 15 Dec 2024 09:01:38 ", "AS_MOON_NEXT_FULL_DATE": "15/12/24", "AS_MOON_NEXT_FULL_TIME": "09:01:38", "AS_MOON_NEXT_NEW_FULL": "Mon 30 Dec 2024 22:26:44 ", "AS_MOON_NEXT_NEW_DATE": "30/12/24", "AS_MOON_NEXT_NEW_TIME": "22:26:44", "AS_SUN_DAWN": "20241129 07:04:12", "AS_SUN_SUNRISE": "20241129 07:44:58", "AS_SUN_NOON": "20241129 11:47:47", "AS_SUN_SUNSET": "20241128 15:50:41", "AS_SUN_DUSK": "20241128 16:31:18", "AS_SUN_AZIMUTH": "324", "AS_SUN_ELEVATION": "-55" } To use this data in an overlay you need to use the 'variable manager' in the Overlay Editor. In the 'variable manager' there are two tabs Allsky Variables - These are the variables you can use in your overlays All Variables - Think of this as a library of ALL variables available but to use them you must add them to the 'Allsky variables' tab using the + icon So in the case of the solar system module you will find variables in the 'All variables' tab like 'AS_MOON_RISE_TIME' Click on the + symbol to add it to the 'Allsky variables; tab, you will need to give it a description but this can be anything you like. After you had added the variable to the 'Allsky variables' tab you can click on the '+' symbol to add it to the overlay. Do not forget to Save the variables dialog after you have added variables. The process of doing all of the above is covered in the documentation, see link below, BUT if you think it could be improved then please let us know https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/overlays/overlays.html Hope that helps but if not please feel free to ask any questions Alex — Reply to this email directly, view it on GitHub <https://github.com/AllskyTeam/allsky/discussions/3957#discussioncomment-11410588>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNHK7HPIYNKCD5GPDV32C6LFVAVCNFSM6AAAAABRS2RPGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBRGA2TQOA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Alex-developer]

Ok a few things to try

1. Is the module installed correctly? The best way to install it would be as follows

cd /tmp
git clone https://github.com/AllskyTeam/allsky-modules.git
cd allsky-modules
git checkout 48-new-solar-system-module
./install

When presented with the list of modules ONLY install the solar system module

2. Is the module actually running?

Add the module to the periodic flow, click on the settings button and enable any features you need

Set the debug level to 4 in the allsky settings, after you have finished this test dont forget to set it back to whatever value it was

Run the following

tail -f /var/log/allskyperiodic.log

You should see something like the following

2024-11-30T16:47:40.949592+00:00 allsky allskperiodic[2566335]: INFO: --------------- Running Module allsky_solarsystem ---------------
2024-11-30T16:47:40.949607+00:00 allsky allskperiodic[2566335]: INFO: Downloading ephemeris data
2024-11-30T16:47:40.949637+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Mercury
2024-11-30T16:47:40.949656+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Venus
2024-11-30T16:47:40.949690+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Mars
2024-11-30T16:47:40.949709+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Jupiter
2024-11-30T16:47:40.949724+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Saturn
2024-11-30T16:47:40.949742+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Uranus
2024-11-30T16:47:40.949757+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Neptune
2024-11-30T16:47:40.949776+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Pluto
2024-11-30T16:47:40.949790+00:00 allsky allskperiodic[2566335]: INFO: Saving solarsystem.json

If you dont see this or you see any errors please paste them here

Thanks

Alex

[NeilAllison147]

Hi Alex I'm obviously doing something wrong :( This is what I get when I run tail -f /var/log/allskyperiodic.log Also, just a heads up, I'll be overseas for almost 2 weeks so won't be able to try anything else until nearly mid December. So if I don't respond, it's not because I'm ignoring you :) 2024-12-01T18:09:21.147206+11:00 hv-allsky allskperiodic[5443]: bash: deactivate: line 1: syntax error: unexpected end of file 2024-12-01T18:09:21.147256+11:00 hv-allsky allskperiodic[5443]: bash: error importing function definition for `deactivate' 2024-12-01T18:09:21.160918+11:00 hv-allsky allskperiodic[5419]: INFO: Loading config /home/neil/allsky/config/settings.json 2024-12-01T18:09:21.161328+11:00 hv-allsky allskperiodic[5419]: INFO: Running periodic flow... 2024-12-01T18:09:21.161466+11:00 hv-allsky allskperiodic[5419]: INFO: ----------------------- Running Module allsky_solarsystem.py ----------------------- 2024-12-01T18:09:21.166119+11:00 hv-allsky allskperiodic[5419]: INFO: Attempting to load allsky_solarsystem 2024-12-01T18:09:21.166366+11:00 hv-allsky allskperiodic[5419]: ERROR: Module allsky_solarsystem.py failed on line 224 - log() got an unexpected keyword argument 'sendToAllsky' 2024-12-01T18:09:21.166472+11:00 hv-allsky allskperiodic[5419]: INFO: Module allsky_solarsystem.py ran ok in 0.02s 2024-12-01T18:09:21.166542+11:00 hv-allsky allskperiodic[5419]: INFO: periodic flow Complete... 2024-12-01T18:09:21.414135+11:00 hv-allsky allskperiodic[5379]: INFO: Sleeping for 60 seconds 2024-12-01T18:10:22.309565+11:00 hv-allsky allskperiodic[5624]: bash: get_variable: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.309825+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `get_variable' 2024-12-01T18:10:22.309880+11:00 hv-allsky allskperiodic[5624]: bash: fix_settings_link: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.309930+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `fix_settings_link' 2024-12-01T18:10:22.309994+11:00 hv-allsky allskperiodic[5624]: bash: determineCommandToUse: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310043+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `determineCommandToUse' 2024-12-01T18:10:22.310099+11:00 hv-allsky allskperiodic[5624]: bash: convert_json_to_tabs: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310147+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `convert_json_to_tabs' 2024-12-01T18:10:22.310269+11:00 hv-allsky allskperiodic[5624]: bash: settings: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310318+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `settings' 2024-12-01T18:10:22.310368+11:00 hv-allsky allskperiodic[5624]: bash: one_instance: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310415+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `one_instance' 2024-12-01T18:10:22.310461+11:00 hv-allsky allskperiodic[5624]: bash: checkAndGetNewerFile: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310508+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `checkAndGetNewerFile' 2024-12-01T18:10:22.310555+11:00 hv-allsky allskperiodic[5624]: bash: activate_python_venv: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310602+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `activate_python_venv' 2024-12-01T18:10:22.310649+11:00 hv-allsky allskperiodic[5624]: bash: getJSONarrayIndex: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310695+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `getJSONarrayIndex' 2024-12-01T18:10:22.310744+11:00 hv-allsky allskperiodic[5624]: bash: update_json_file: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310791+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `update_json_file' 2024-12-01T18:10:22.310837+11:00 hv-allsky allskperiodic[5624]: bash: deactivate_python_venv: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310883+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `deactivate_python_venv' 2024-12-01T18:10:22.310929+11:00 hv-allsky allskperiodic[5624]: bash: check_settings_link: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.310975+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `check_settings_link' 2024-12-01T18:10:22.311025+11:00 hv-allsky allskperiodic[5624]: bash: convertLatLong: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.311071+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `convertLatLong' 2024-12-01T18:10:22.311118+11:00 hv-allsky allskperiodic[5624]: bash: make_thumbnail: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.311166+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `make_thumbnail' 2024-12-01T18:10:22.311216+11:00 hv-allsky allskperiodic[5624]: bash: whatWebsites: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.311264+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `whatWebsites' 2024-12-01T18:10:22.311321+11:00 hv-allsky allskperiodic[5624]: bash: indent: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.311369+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `indent' 2024-12-01T18:10:22.311417+11:00 hv-allsky allskperiodic[5624]: bash: checkPixelValue: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.311466+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `checkPixelValue' 2024-12-01T18:10:22.311514+11:00 hv-allsky allskperiodic[5624]: bash: checkCropValues: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.312250+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `checkCropValues' 2024-12-01T18:10:22.312492+11:00 hv-allsky allskperiodic[5624]: bash: get_sunrise_sunset: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.312601+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `get_sunrise_sunset' 2024-12-01T18:10:22.312694+11:00 hv-allsky allskperiodic[5624]: bash: reboot_needed: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.312843+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `reboot_needed' 2024-12-01T18:10:22.313062+11:00 hv-allsky allskperiodic[5624]: bash: doExit: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.313329+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `doExit' 2024-12-01T18:10:22.313507+11:00 hv-allsky allskperiodic[5624]: bash: get_links: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.313694+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `get_links' 2024-12-01T18:10:22.313854+11:00 hv-allsky allskperiodic[5624]: bash: deactivate: line 1: syntax error: unexpected end of file 2024-12-01T18:10:22.314007+11:00 hv-allsky allskperiodic[5624]: bash: error importing function definition for `deactivate' 2024-12-01T18:10:22.328777+11:00 hv-allsky allskperiodic[5619]: INFO: Loading config /home/neil/allsky/config/settings.json 2024-12-01T18:10:22.329925+11:00 hv-allsky allskperiodic[5619]: INFO: Running periodic flow... 2024-12-01T18:10:22.330828+11:00 hv-allsky allskperiodic[5619]: INFO: ----------------------- Running Module allsky_solarsystem.py ----------------------- 2024-12-01T18:10:22.331353+11:00 hv-allsky allskperiodic[5619]: INFO: Attempting to load allsky_solarsystem 2024-12-01T18:10:22.331411+11:00 hv-allsky allskperiodic[5619]: ERROR: Module allsky_solarsystem.py failed on line 224 - log() got an unexpected keyword argument 'sendToAllsky' 2024-12-01T18:10:22.331605+11:00 hv-allsky allskperiodic[5619]: INFO: Module allsky_solarsystem.py ran ok in 0.02s 2024-12-01T18:10:22.331684+11:00 hv-allsky allskperiodic[5619]: INFO: periodic flow Complete... 2024-12-01T18:10:22.632753+11:00 hv-allsky allskperiodic[5379]: INFO: Sleeping for 60 seconds 2024-12-01T18:11:23.406990+11:00 hv-allsky allskperiodic[5715]: bash: get_variable: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.407468+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `get_variable' 2024-12-01T18:11:23.407525+11:00 hv-allsky allskperiodic[5715]: bash: fix_settings_link: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.407628+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `fix_settings_link' 2024-12-01T18:11:23.407767+11:00 hv-allsky allskperiodic[5715]: bash: determineCommandToUse: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.407818+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `determineCommandToUse' 2024-12-01T18:11:23.407866+11:00 hv-allsky allskperiodic[5715]: bash: convert_json_to_tabs: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.407914+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `convert_json_to_tabs' 2024-12-01T18:11:23.407960+11:00 hv-allsky allskperiodic[5715]: bash: settings: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408007+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `settings' 2024-12-01T18:11:23.408058+11:00 hv-allsky allskperiodic[5715]: bash: one_instance: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408104+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `one_instance' 2024-12-01T18:11:23.408151+11:00 hv-allsky allskperiodic[5715]: bash: checkAndGetNewerFile: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408208+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `checkAndGetNewerFile' 2024-12-01T18:11:23.408263+11:00 hv-allsky allskperiodic[5715]: bash: activate_python_venv: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408317+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `activate_python_venv' 2024-12-01T18:11:23.408364+11:00 hv-allsky allskperiodic[5715]: bash: getJSONarrayIndex: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408411+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `getJSONarrayIndex' 2024-12-01T18:11:23.408462+11:00 hv-allsky allskperiodic[5715]: bash: update_json_file: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408509+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `update_json_file' 2024-12-01T18:11:23.408555+11:00 hv-allsky allskperiodic[5715]: bash: deactivate_python_venv: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408601+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `deactivate_python_venv' 2024-12-01T18:11:23.408647+11:00 hv-allsky allskperiodic[5715]: bash: check_settings_link: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408695+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `check_settings_link' 2024-12-01T18:11:23.408747+11:00 hv-allsky allskperiodic[5715]: bash: convertLatLong: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408796+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `convertLatLong' 2024-12-01T18:11:23.408846+11:00 hv-allsky allskperiodic[5715]: bash: make_thumbnail: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408895+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `make_thumbnail' 2024-12-01T18:11:23.408944+11:00 hv-allsky allskperiodic[5715]: bash: whatWebsites: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.408992+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `whatWebsites' 2024-12-01T18:11:23.409040+11:00 hv-allsky allskperiodic[5715]: bash: indent: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409088+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `indent' 2024-12-01T18:11:23.409137+11:00 hv-allsky allskperiodic[5715]: bash: checkPixelValue: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409185+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `checkPixelValue' 2024-12-01T18:11:23.409260+11:00 hv-allsky allskperiodic[5715]: bash: checkCropValues: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409311+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `checkCropValues' 2024-12-01T18:11:23.409359+11:00 hv-allsky allskperiodic[5715]: bash: get_sunrise_sunset: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409404+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `get_sunrise_sunset' 2024-12-01T18:11:23.409455+11:00 hv-allsky allskperiodic[5715]: bash: reboot_needed: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409502+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `reboot_needed' 2024-12-01T18:11:23.409558+11:00 hv-allsky allskperiodic[5715]: bash: doExit: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409604+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `doExit' 2024-12-01T18:11:23.409657+11:00 hv-allsky allskperiodic[5715]: bash: get_links: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409705+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `get_links' 2024-12-01T18:11:23.409755+11:00 hv-allsky allskperiodic[5715]: bash: deactivate: line 1: syntax error: unexpected end of file 2024-12-01T18:11:23.409802+11:00 hv-allsky allskperiodic[5715]: bash: error importing function definition for `deactivate' 2024-12-01T18:11:23.424845+11:00 hv-allsky allskperiodic[5710]: INFO: Loading config /home/neil/allsky/config/settings.json 2024-12-01T18:11:23.425314+11:00 hv-allsky allskperiodic[5710]: INFO: Running periodic flow... 2024-12-01T18:11:23.425442+11:00 hv-allsky allskperiodic[5710]: INFO: ----------------------- Running Module allsky_solarsystem.py ----------------------- 2024-12-01T18:11:23.425493+11:00 hv-allsky allskperiodic[5710]: INFO: Attempting to load allsky_solarsystem 2024-12-01T18:11:23.425541+11:00 hv-allsky allskperiodic[5710]: ERROR: Module allsky_solarsystem.py failed on line 224 - log() got an unexpected keyword argument 'sendToAllsky' 2024-12-01T18:11:23.425611+11:00 hv-allsky allskperiodic[5710]: INFO: Module allsky_solarsystem.py ran ok in 0.02s 2024-12-01T18:11:23.425660+11:00 hv-allsky allskperiodic[5710]: INFO: periodic flow Complete... 2024-12-01T18:11:23.710888+11:00 hv-allsky allskperiodic[5379]: INFO: Sleeping for 60 seconds

…

-- Thanks and Best Regards Neil

On Sun, Dec 1, 2024 at 3:49 AM Alex ***@***.***> wrote: Ok a few things to try 1. Is the module installed correctly? The best way to install it would be as follows cd /tmp git clone https://github.com/AllskyTeam/allsky-modules.git cd allsky-modules git checkout 48-new-solar-system-module ./install When presented with the list of modules ONLY install the solar system module 2. Is the module actually running? Add the module to the periodic flow, click on the settings button and enable any features you need Set the debug level to 4 in the allsky settings, after you have finished this test dont forget to set it back to whatever value it was Run the following tail -f /var/log/allskyperiodic.log You should see something like the following 2024-11-30T16:47:40.949592+00:00 allsky allskperiodic[2566335]: INFO: --------------- Running Module allsky_solarsystem --------------- 2024-11-30T16:47:40.949607+00:00 allsky allskperiodic[2566335]: INFO: Downloading ephemeris data 2024-11-30T16:47:40.949637+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Mercury 2024-11-30T16:47:40.949656+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Venus 2024-11-30T16:47:40.949690+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Mars 2024-11-30T16:47:40.949709+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Jupiter 2024-11-30T16:47:40.949724+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Saturn 2024-11-30T16:47:40.949742+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Uranus 2024-11-30T16:47:40.949757+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Neptune 2024-11-30T16:47:40.949776+00:00 allsky allskperiodic[2566335]: INFO: Calculating position of Pluto 2024-11-30T16:47:40.949790+00:00 allsky allskperiodic[2566335]: INFO: Saving solarsystem.json If you dont see this or you see any errors please paste them here Thanks Alex — Reply to this email directly, view it on GitHub <https://github.com/AllskyTeam/allsky/discussions/3957#discussioncomment-11422947>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNB6LP6QIW3DHRVUBOT2DHUBTAVCNFSM6AAAAABRS2RPGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBSGI4TINY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Alex-developer]

Sorry that was my fault !

I am using a feature in the module thats only available in the next release of Allsky.

The new version will be out next weekend so perhaps you can upgrade Allsky and the modules when you are back,

I'll leave this open for now

Alex

[NeilAllison147]

Hi @Alex-developer
Long time no speak.

So..... I've done a completely new (I.E clean) install of AllSky and it's now running v2024.12.06_02
I have the AllSky Solar system module installed and enabled for the Sun and Moon only.
Rebooted the PI and I'm not getting a solarsystem.json file created in ~/allsky/config/overlay/extra

Any thoughts?

[Alex-developer]

Hiya :-)

Set the debug level to 4 in the min allsky settings then from a command prompt run

tail -f /var/log/allskyperiodic.log

See if ny errors are being generted

[NeilAllison147]

Hi Alex [image: image.png] This is what I get: - ***@***.***:~ $ tail -f /var/log/allskyperiodic.log 2025-04-24T15:49:11.051982+10:00 hv-allsky allskperiodic[439561]: INFO: --------------- Running Module allsky_solar-system --------------- 2025-04-24T15:49:11.052091+10:00 hv-allsky allskperiodic[439561]: ERROR: Failed to import module allsky_solar-system.py: module 'allsky_solar-system' has no attribute 'solar-system'; ignoring. 2025-04-24T15:49:11.053536+10:00 hv-allsky allskperiodic[439561]: INFO: ===== periodic flow complete. 2025-04-24T15:49:11.304553+10:00 hv-allsky allskperiodic[439538]: INFO: Sleeping for 60 seconds 2025-04-24T15:50:12.151951+10:00 hv-allsky allskperiodic[440340]: INFO: Loading /home/neil/allsky/config/settings.json 2025-04-24T15:50:12.152602+10:00 hv-allsky allskperiodic[440340]: INFO: ===== Running periodic flow... 2025-04-24T15:50:12.152966+10:00 hv-allsky allskperiodic[440340]: INFO: --------------- Running Module allsky_solar-system --------------- 2025-04-24T15:50:12.153185+10:00 hv-allsky allskperiodic[440340]: ERROR: Failed to import module allsky_solar-system.py: module 'allsky_solar-system' has no attribute 'solar-system'; ignoring. 2025-04-24T15:50:12.153513+10:00 hv-allsky allskperiodic[440340]: INFO: ===== periodic flow complete. 2025-04-24T15:50:12.401611+10:00 hv-allsky allskperiodic[439538]: INFO: Sleeping for 60 seconds 2025-04-24T15:51:13.363217+10:00 hv-allsky allskperiodic[440985]: INFO: Loading /home/neil/allsky/config/settings.json 2025-04-24T15:51:13.363616+10:00 hv-allsky allskperiodic[440985]: INFO: ===== Running periodic flow... 2025-04-24T15:51:13.363704+10:00 hv-allsky allskperiodic[440985]: INFO: --------------- Running Module allsky_solar-system --------------- 2025-04-24T15:51:13.363755+10:00 hv-allsky allskperiodic[440985]: ERROR: Failed to import module allsky_solar-system.py: module 'allsky_solar-system' has no attribute 'solar-system'; ignoring. 2025-04-24T15:51:13.363859+10:00 hv-allsky allskperiodic[440985]: INFO: ===== periodic flow complete. 2025-04-24T15:51:13.631024+10:00 hv-allsky allskperiodic[439538]: INFO: Sleeping for 60 seconds 2025-04-24T15:52:14.637443+10:00 hv-allsky allskperiodic[441641]: INFO: Loading /home/neil/allsky/config/settings.json 2025-04-24T15:52:14.637910+10:00 hv-allsky allskperiodic[441641]: INFO: ===== Running periodic flow... 2025-04-24T15:52:14.638087+10:00 hv-allsky allskperiodic[441641]: INFO: --------------- Running Module allsky_solar-system --------------- 2025-04-24T15:52:14.638146+10:00 hv-allsky allskperiodic[441641]: ERROR: Failed to import module allsky_solar-system.py: module 'allsky_solar-system' has no attribute 'solar-system'; ignoring. 2025-04-24T15:52:14.638683+10:00 hv-allsky allskperiodic[441641]: INFO: ===== periodic flow complete. 2025-04-24T15:52:14.920953+10:00 hv-allsky allskperiodic[439538]: INFO: Sleeping for 60 seconds

…

-- Thanks and Best Regards Neil

On Thu, Apr 24, 2025 at 9:11 AM Alex ***@***.***> wrote: Hiya :-) Set the debug level to 4 in the min allsky settings then from a command prompt run tail -f /var/log/allskyperiodic.log See if ny errors are being generted — Reply to this email directly, view it on GitHub <#190 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNAQDPVVIEEZQCWUIMT23AM3FAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJSHA2TANQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[EricClaeys]

@NeilAllison147,
GitHub doesn't accept attachments via email so it's not in your post. You'll need to log in to GitHub and attach it.
This "feature" has bitten all of us.

[NeilAllison147]

Ahh yes. I forgot about that. The attachment was just a screenshot of the debug level set to 4, so not really important.

…

-- Thanks and Best Regards Neil

On Fri, 25 Apr 2025, 12:31 am Eric Claeys, ***@***.***> wrote: @NeilAllison147 <https://github.com/NeilAllison147>, GitHub doesn't accept attachments via email so it's not in your post. You'll need to log in to GitHub and attach it. This "feature" has bitten all of us. — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNFZS6OKJ3VJK3WAOZD23DYSVAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJTGYZDMOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[NeilAllison147]

Any update on this, Alex?

…

-- Thanks and Best Regards Neil

On Fri, Apr 25, 2025 at 6:43 AM Neil Allison ***@***.***> wrote: Ahh yes. I forgot about that. The attachment was just a screenshot of the debug level set to 4, so not really important. -- Thanks and Best Regards Neil On Fri, 25 Apr 2025, 12:31 am Eric Claeys, ***@***.***> wrote: > @NeilAllison147 <https://github.com/NeilAllison147>, > GitHub doesn't accept attachments via email so it's not in your post. > You'll need to log in to GitHub and attach it. > This "feature" has bitten all of us. > > — > Reply to this email directly, view it on GitHub > <#190 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/APT5YNFZS6OKJ3VJK3WAOZD23DYSVAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJTGYZDMOI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.*** > com> >

[Alex-developer]

Any update on this, Alex?
…
-- Thanks and Best Regards Neil
On Fri, Apr 25, 2025 at 6:43 AM Neil Allison @.> wrote: Ahh yes. I forgot about that. The attachment was just a screenshot of the debug level set to 4, so not really important. -- Thanks and Best Regards Neil On Fri, 25 Apr 2025, 12:31 am Eric Claeys, @.> wrote: > @NeilAllison147 https://github.com/NeilAllison147, > GitHub doesn't accept attachments via email so it's not in your post. > You'll need to log in to GitHub and attach it. > This "feature" has bitten all of us. > > — > Reply to this email directly, view it on GitHub > <#190 (reply in thread)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/APT5YNFZS6OKJ3VJK3WAOZD23DYSVAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJTGYZDMOI > . > You are receiving this because you were mentioned.Message ID: > @.*** > com> >

Sorry I am on vacation so have limited access to the internet

Looks like the solar system module may be the wrong one. There is an error being generated.

2025-04-24T15:51:13.363755+10:00 hv-allsky allskperiodic[440985]: ERROR:
Failed to import module allsky_solar-system.py: module
'allsky_solar-system' has no attribute 'solar-system'; ignoring.

Do you recall where you got the module from?

Thanks

Alex

[NeilAllison147]

Hi Alex Unfortunately, I don't. Sorry. If I need to reinstall, let me know where to get it from and exactly what to do. It's not beyond the realms of possibility that I'm doing something wrong :P

…

-- Thanks and Best Regards Neil

On Wed, Apr 30, 2025 at 1:34 AM Alex ***@***.***> wrote: Any update on this, Alex? … <#m_7953621943161608363_> -- Thanks and Best Regards Neil On Fri, Apr 25, 2025 at 6:43 AM Neil Allison *@*.*> wrote: Ahh yes. I forgot about that. The attachment was just a screenshot of the debug level set to 4, so not really important. -- Thanks and Best Regards Neil On Fri, 25 Apr 2025, 12:31 am Eric Claeys, @.*> wrote: > @NeilAllison147 <https://github.com/NeilAllison147> https://github.com/NeilAllison147, > GitHub doesn't accept attachments via email so it's not in your post. > You'll need to log in to GitHub and attach it. > This "feature" has bitten all of us. > > — > Reply to this email directly, view it on GitHub > <#190 (reply in thread) <#190 (reply in thread)>>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/APT5YNFZS6OKJ3VJK3WAOZD23DYSVAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJTGYZDMOI > . > You are receiving this because you were mentioned.Message ID: > *@*.*** > com> > Sorry I am on vacation so have limited access to the internet Looks like the solar system module may be the wrong one. There is an error being generated. 2025-04-24T15:51:13.363755+10:00 hv-allsky allskperiodic[440985]: ERROR: Failed to import module allsky_solar-system.py: module 'allsky_solar-system' has no attribute 'solar-system'; ignoring. Do you recall where you got the module from? Thanks Alex — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNE2AZKM5IFN67DEV3T236LX5AVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYGI3DEMI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[Alex-developer]

I would try the following

1. Remove the offending solar system module, it will be in /opt/allsky/modules
2. Re install the module following the instructions in the modules repo

Cheers

Alex

[NeilAllison147]

Can you send me the link to the modules repo, please? For the life of me, I can't find it. :(

…

-- Thanks and Best Regards Neil

On Wed, Apr 30, 2025 at 1:36 PM Alex ***@***.***> wrote: I would try the following 1. Remove the offending solar system module, it will be in /opt/allsky/modules 2. Re install the module following the instructions in the modules repo Cheers Alex — Reply to this email directly, view it on GitHub <#190 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNGSS7BUMQSMOKX7KN324BANLAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYG44DOOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

https://github.com/AllskyTeam/allsky-modules

[NeilAllison147]

Curiouser and curiouser So, I removed the existing module from opt/allsky/modules Then from a command line, I ran git clone https://github.com/AllskyTeam/allsky-modules.git cd allsky-modules ./install.sh There is no solarsystem module showing in the list.

…

-- Thanks and Best Regards Neil

On Wed, Apr 30, 2025 at 3:24 PM Eric Claeys ***@***.***> wrote: https://github.com/AllskyTeam/allsky-modules — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[Alex-developer]

Curiouser and curiouser So, I removed the existing module from opt/allsky/modules Then from a command line, I ran git clone https://github.com/AllskyTeam/allsky-modules.git cd allsky-modules ./install.sh There is no solarsystem module showing in the list.
…
-- Thanks and Best Regards Neil
On Wed, Apr 30, 2025 at 3:24 PM Eric Claeys @.> wrote: https://github.com/AllskyTeam/allsky-modules — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY . You are receiving this because you were mentioned.Message ID: @. com>

Apologies its in they branch https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module

Checkout that code and ONLY install the solar system module from it

Alex

[NeilAllison147]

Hi Alex I think I'm just gonna put this in the too hard basket and give up. The instructions on that page are the same as the instructions on the original page [image: image.png]

…

-- Thanks and Best Regards Neil

On Fri, May 2, 2025 at 2:08 AM Alex ***@***.***> wrote: Curiouser and curiouser So, I removed the existing module from opt/allsky/modules Then from a command line, I ran git clone https://github.com/AllskyTeam/allsky-modules.git cd allsky-modules ./install.sh There is no solarsystem module showing in the list. … <#m_8185941949016279397_> -- Thanks and Best Regards Neil On Wed, Apr 30, 2025 at 3:24 PM Eric Claeys *@*.*> wrote: https://github.com/AllskyTeam/allsky-modules <https://github.com/AllskyTeam/allsky-modules> — Reply to this email directly, view it on GitHub <#190 (reply in thread) <#190 (reply in thread)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY <https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY> . You are receiving this because you were mentioned.Message ID: @.* com> Apologies its in they branch https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module Checkout that code and ONLY install the solar system module from it Alex — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNCN7GADANQJR6CWDXD24JBGPAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBQGU2TCOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[Alex-developer]

Hi Alex I think I'm just gonna put this in the too hard basket and give up. The instructions on that page are the same as the instructions on the original page [image: image.png]
…
-- Thanks and Best Regards Neil
On Fri, May 2, 2025 at 2:08 AM Alex @.> wrote: Curiouser and curiouser So, I removed the existing module from opt/allsky/modules Then from a command line, I ran git clone https://github.com/AllskyTeam/allsky-modules.git cd allsky-modules ./install.sh There is no solarsystem module showing in the list. … <#m_8185941949016279397_> -- Thanks and Best Regards Neil On Wed, Apr 30, 2025 at 3:24 PM Eric Claeys @.> wrote: https://github.com/AllskyTeam/allsky-modules https://github.com/AllskyTeam/allsky-modules — Reply to this email directly, view it on GitHub <#190 (reply in thread) <#190 (reply in thread)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY . You are receiving this because you were mentioned.Message ID: @. com> Apologies its in they branch https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module Checkout that code and ONLY install the solar system module from it Alex — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCN7GADANQJR6CWDXD24JBGPAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBQGU2TCOI . You are receiving this because you were mentioned.Message ID: @.** com>

Its pretty straightforward

Try the following

cd /tmp
git clone https://github.com/AllskyTeam/allsky-modules.git
cd all sky-modules
git checkout 48-new-solar-system-module
./install.sh

The above will checkout the code in a temporary folder then switch to the branch with the solar system module in it and then run the installer. If you do this ONLY install the solar system module from the branch

I m back from vacation in the next few days so will merge the module into the master branch which will make it easier.

Cheers

Alex

[NeilAllison147]

Hi Alex The good news is that the install seems to have worked insofar as the module (allsky_solarsystem.py) is back in the opt/allsky/modules folder. I thought the name of the module was allsky_solar-system, not allsky_solarsystem. Which should it be? However, in the Module Manager, it is not appearing anywhere. Periodic jobs contains absolutely nothing (and this is where I would have expected to see it). Don't be looking at this whilst you're on vacation. though.

…

-- Thanks and Best Regards Neil

On Sat, May 3, 2025 at 11:50 AM Alex ***@***.***> wrote: Hi Alex I think I'm just gonna put this in the too hard basket and give up. The instructions on that page are the same as the instructions on the original page [image: image.png] … <#m_-1174876275514931540_> -- Thanks and Best Regards Neil On Fri, May 2, 2025 at 2:08 AM Alex *@*.*> wrote: Curiouser and curiouser So, I removed the existing module from opt/allsky/modules Then from a command line, I ran git clone https://github.com/AllskyTeam/allsky-modules.git <https://github.com/AllskyTeam/allsky-modules.git> cd allsky-modules ./install.sh There is no solarsystem module showing in the list. … <#m_8185941949016279397_> -- Thanks and Best Regards Neil On Wed, Apr 30, 2025 at 3:24 PM Eric Claeys @.> wrote: https://github.com/AllskyTeam/allsky-modules <https://github.com/AllskyTeam/allsky-modules> https://github.com/AllskyTeam/allsky-modules <https://github.com/AllskyTeam/allsky-modules> — Reply to this email directly, view it on GitHub <#190 <#190> (reply in thread) <#190 (reply in thread) <#190 (reply in thread)>>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY <https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY> https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY <https://github.com/notifications/unsubscribe-auth/APT5YNCJQLOKLHFUZKJTUJT24BNAHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYHA2DENY> . You are receiving this because you were mentioned.Message ID: @. com> Apologies its in they branch https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module <https://github.com/AllskyTeam/allsky-modules/tree/48-new-solar-system-module> Checkout that code and ONLY install the solar system module from it Alex — Reply to this email directly, view it on GitHub <#190 (reply in thread) <#190 (reply in thread)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APT5YNCN7GADANQJR6CWDXD24JBGPAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBQGU2TCOI <https://github.com/notifications/unsubscribe-auth/APT5YNCN7GADANQJR6CWDXD24JBGPAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBQGU2TCOI> . You are receiving this because you were mentioned.Message ID: @.*** com> Its pretty straightforward Try the following cd /tmp git clone https://github.com/AllskyTeam/allsky-modules.git cd all sky-modules git checkout 48-new-solar-system-module ./install.sh The above will checkout the code in a temporary folder then switch to the branch with the solar system module in it and then run the installer. If you do this ONLY install the solar system module from the branch I m back from vacation in the next few days so will merge the module into the master branch which will make it easier. Cheers Alex — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNATVCSGT543BYEXH4T24QOHZAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBSGAZTQMI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[Alex-developer]

Hiya

Back from vacation now.

The module is called allsky_solarsystem.

It should only appear in the periodic flow.

If you are running the latest version of allsky could you please attach the support info

Thanks

Alex

[NeilAllison147]

Hi Alex I'm going to pause this issue. The reason being, my AllSky system keeps stopping every night due to "*** capture_RPi: ERROR: maximum number of consecutive errors of 4 reached; capture program stopped. Total errors=5." (See discussion #4537) I will try and revert back to an older version of AllSky as a last resort (assuming that's even possible). My previous version was v2023.05.01_04 and it never had the issue. How would I go about installing the older version?

…

-- Thanks and Best Regards Neil

On Sun, May 11, 2025 at 8:08 AM Alex ***@***.***> wrote: Hiya Back from vacation now. The module is called allsky_solarsystem. It should only appear in the periodic flow. If you are running the latest version of allsky could you please attach the support info Thanks Alex — Reply to this email directly, view it on GitHub <#190 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNDS2RI6V7V26ETB36L25Z2HNAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJQGMZDCNY> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

@NeilAllison147,
The next time you get the errors, look in ~/allsky/tmp/capture_RPi_debug.txt BEFORE restarting Allsky, and let me know what it says.
After that, run libcamera-hello and see if it works. If not, installing a different Allsky release is unlikely to make any difference, since the problem is with the camera software, not with Allsky.

[NeilAllison147]

~/allsky/tmp/capture_RPi_debug.txt contains: - Mode selection for 2028:1520:12:P SRGGB10_CSI2P,1332x990/0 - Score: 3456.22 SRGGB12_CSI2P,2028x1080/0 - Score: 1083.84 SRGGB12_CSI2P,2028x1520/0 - Score: 0 SRGGB12_CSI2P,4056x3040/0 - Score: 887 Mode selection for 4056:3040:12:P SRGGB10_CSI2P,1332x990/0 - Score: 10552.2 SRGGB12_CSI2P,2028x1080/0 - Score: 8179.84 SRGGB12_CSI2P,2028x1520/0 - Score: 7096 SRGGB12_CSI2P,4056x3040/0 - Score: 0 dmaHeap allocation failure for rpicam-apps0 ERROR: *** failed to allocate capture buffers for stream *** libcamera-hello results in the following: - ***@***.***:~ $ libcamera-hello [18:57:33.781844661] [37638] INFO Camera camera_manager.cpp:326 libcamera v0.5.0+59-d83ff0a4 [18:57:33.832593158] [37644] WARN RPiSdn sdn.cpp:40 Using legacy SDN tuning - please consider moving SDN inside rpi.denoise [18:57:33.834893875] [37644] INFO RPI vc4.cpp:447 Registered camera ***@***.******@***.*** to Unicam device /dev/media0 and ISP device /dev/media2 [18:57:33.835128485] [37644] INFO RPI pipeline_base.cpp:1121 Using configuration file '/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml' Made X/EGL preview window Mode selection for 2028:1520:12:P SRGGB10_CSI2P,1332x990/0 - Score: 3456.22 SRGGB12_CSI2P,2028x1080/0 - Score: 1083.84 SRGGB12_CSI2P,2028x1520/0 - Score: 0 SRGGB12_CSI2P,4056x3040/0 - Score: 887 [18:57:34.362351207] [37638] INFO Camera camera.cpp:1205 configuring streams: (0) 2028x1520-YUV420 (1) 2028x1520-SBGGR12_CSI2P [18:57:34.362778335] [37644] INFO RPI vc4.cpp:622 Sensor: ***@***.******@***.*** - Selected sensor format: 2028x1520-SBGGR12_1X12 - Selected unicam format: 2028x1520-pBCC

…

-- Thanks and Best Regards Neil

On Mon, May 12, 2025 at 1:31 PM Eric Claeys ***@***.***> wrote: @NeilAllison147 <https://github.com/NeilAllison147>, The next time you get the errors, look in ~/allsky/tmp/capture_RPi_debug.txt BEFORE restarting Allsky, and let me know what it says. After that, run libcamera-hello and see if it works. If not, installing a different Allsky release is unlikely to make any difference, since the problem is with the camera software, not with Allsky. — Reply to this email directly, view it on GitHub <#190 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNEGDCIEHLWV4QBC74326AIZ3AVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRGIZDAMA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

@NeilAllison147,
Thanks. The dmaHeap allocation failure for rpicam-apps0. ERROR: *** failed to allocate capture buffers for stream *** message indicates a problem with the camera's software, not Allsky.
Did libcamera-hello display an image? If so, it probably needs to be run right after the error in order to fail.

[NeilAllison147]

Yes, it did display an image (very red, though). I'd have to sit and watch it constantly to run it immediately after it fails :(

…

-- Thanks and Best Regards Neil

On Mon, May 12, 2025 at 4:08 PM Eric Claeys ***@***.***> wrote: @NeilAllison147 <https://github.com/NeilAllison147>, Thanks. The dmaHeap allocation failure for rpicam-apps0. ERROR: *** failed to allocate capture buffers for stream *** message indicates a problem with the camera's software, not Allsky. Did libcamera-hello display an image? If so, it probably needs to be run right after the error in order to fail. — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNFTM6WT2OAVTWUOSZ326A3FHAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRGMZTCMQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

You can run libcamera-hello after you get ERROR: maximum number of consecutive errors of 4 reached... and Allsky stops.

[NeilAllison147]

You said " it probably needs to be run right after the error in order to fail" which suggests to me it should be run immediately after the failure. Sitting up potentially for hours isn't an option for me. If it fails through the night, can I run the command in the morning or is that too late?

…

-- Thanks and Best Regards Neil

On Mon, May 12, 2025 at 5:16 PM Eric Claeys ***@***.***> wrote: You can run libcamera-hello after you get ERROR: maximum number of consecutive errors of 4 reached... and Allsky stops. — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNHMFY5OQVXGJ23SOCD26BDDNAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRGQYTEOA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

Sorry, when I said, "right after the error" I meant "after the error and before anything else happens, like restarting Allsky."

The closer you run libcamera-hello to when Allsky failed to get an image, the better, but running it in the morning, or whenever you notice Allsky stopped, is probably ok.

[NeilAllison147]

I don't know if this is relevant, but it only gets this error during the night. I have my day time settings to capture exposures but not to save them, so it looks like it's the saving of the images that could be the root cause.

…

-- Thanks and Best Regards Neil

On Tue, May 13, 2025 at 1:50 AM Eric Claeys ***@***.***> wrote: Sorry, when I said, "right after the error" I meant "after the error and before anything else happens, like restarting Allsky." The closer you run libcamera-hello to when Allsky failed to get an image, the better, but running it in the morning, or whenever you notice Allsky stopped, is probably ok. — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNGUDOR5QG44KWE65PD26C7NTAVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJSGAZTEOA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[EricClaeys]

@NeilAllison147,

That's interesting. I supposed when Allsky is running it's using some Linux resource which doesn't leave enough for the libcamera-still command.

Would you please follow the instructions on the Getting Support page and upload the file it produces? That'll tell us what's on your Pi. I'll be gone for a few days and when I get back, I'll enter an Issue for the libcamera development team to see what they say.
Also, the next point release of Allsky (v2024.12.06_03) will be out in a couple days and it adds the contents of ~/allsky/tmp/capture_RPi_debug.txt to the Allsky log file every time it happens, so we can see if every failure has the same cause. When that release is out, would you please upgrade to it?

Thanks - Eric

[EricClaeys]

@NeilAllison147,
Is this "dmaHeap" problem the same one in Discussion #4537?
If so, let's use that for all future notes on that problem, and continue with this Discussion for any Moon rise/set notes.

[NeilAllison147]

Yes, it is Eric

…

-- Thanks and Best Regards Neil

On Thu, May 22, 2025 at 8:21 PM Eric Claeys ***@***.***> wrote: @NeilAllison147 <https://github.com/NeilAllison147>, Is this "dmaHeap" problem the same one in Discussion #4537 <AllskyTeam/allsky#4537>? If so, let's use that for all future notes on that problem, and continue with this Discussion for any Moon rise/set notes. — Reply to this email directly, view it on GitHub <#190 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNABL2FMUI3IRSFCXKL27WQK5AVCNFSM6AAAAAB3VRZ64GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRTGI4DEMI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>