Sun (and Moon) add-on

[ea1ii]

This is currently work in progress.

A lot of debugging still to be done (basically checking that it works properly for different times of the year and latitudes)
Basic features:
At the bottom: darkness graph for 24 hrs. (user can choose -12hrs to +12hrs or 0 to +24hrs). Size, location, transparency and colors can be customized. Shows suns transit and anti-transit as well as sunrise and sunset (astronomical, nautical, civil, true)

At the top: Sun (white) and Moon (blue-ish) elevations.

Not yet decided weather to merge both graphs into a single one.

Any suggestions are welcome

[Alex-developer]

Interesting idea. What is it written in?

The next release of Allsky has some features that may allow you to develop this as an addon.

Cheers

Alex

[ea1ii]

Python. Just a few milliseconds to execute.

[Alex-developer]

The next release of AllSky has a module system and its possible for people to write custom modules in Python that can alter the captured image.
I am currently looking for someone to have a go at writing a new module and this looks like a good candidate

[ea1ii]

I'm happy to join in Alex. Shall I wait (carrying on with developement in the meanwhile) until current dev branch goes main?

[Alex-developer]

I am more than happy for you to have a play with it now.

If you goto the main wiki page and at the bottom right there is a link to the new documentation. Have a look at the modules documentation.

This is a direct link to it https://htmlpreview.github.io/?https://raw.githubusercontent.com/thomasjacquin/allsky/dev/html/documentation/modules/modules.html

The new module system works by running a series of 'modules' after an image is captured, there is a shared python module that fives you access to things like the captured image and a load of helper functions to do stuff !

So for something like this you would

• get the users lat/lon using the shared module, get the TZ from the pi
• draw your content on the captured image

The module system will take care of saving the image. You can also specify options for the module via a metadata variable.

Its pretty simple once you get the hang of it

Cheers

Alex

[ea1ii]

Hi Alex,

Just installed 'dev' branch. Still a bit of exploring and tunning left before going back to my add-on. Had a few issues installing dev branch for ASwebsite but I thing I got it.

Worth pointing out that I got stuck for a while as my setup would not ftp to a remote server. Still did not have had the time to investigate further but managed to get it running by commenting out like.

I'll keep you posted. ATM, since I work 4-on-4-off nights, it's gonna be a few days till next chance.

Cheers

Carlos

[EricClaeys]

@ea1ii. Carlos, when you get a chance please provide error messages, screenshots, and anything else that will help us debug the installation issues you saw. Other people who aren't as technical as you will likely have the same issues and won't be able to get Allsky working.

Interesting with the quote PWD issue. That has been in the code for a while so I am not sure why it's failing now.

Eric

[ea1ii]

Will do. But before that, since I kept copies from everything, I'm re-installing both local and remote Web apps. Hopefully by next Tuesday

[ea1ii]

Reinstalling ig going a bit messy, but looks that it's progressing fine.

Regardind the quote issue. This is what I get:

But, if O omit the '|| exit 99'

[EricClaeys]

@ea1ii can you try pwd to see if it's supported?

[ea1ii]

Tried last week and I think to remember it is, but will confirm tomorrow

[EricClaeys]

@ea1ii Would you also please try cd . ?
The quote PWD is there to determine if we're connected to the remote server before we try to transfer a file. If not connected an understandable error message is printed.
I'm hoping cd . will work as well.

[ea1ii]

Will do.
By the way. I was trying to find out what difference makes 'quoting' the command, instead of sending just 'PWD' and could not find anything clear. Would you help and tell?

[ea1ii]

Eventually found this: https://www.ibm.com/docs/en/zos/2.3.0?topic=subcommands-quote-subcommandsend-uninterpreted-string-data
Now I understand why did you ask me to try cd .

[ea1ii]

same thing for cd .
but in both cases just removing the \\ exit 99 works

[EricClaeys]

The code is trying to execute a command on the remote server that doesn't do anything to check if the connection is up. quote PWD executes PWD on the remote. pwd by itself executes it on the Pi, which doesn't tell us if the remote connection is up.
I will probably just remove the line completely.

[ea1ii]

Additional issue

So the come in the remote Web is ok, but the local copy is not. I guess I need to debug postData.sh.....?
(CGallsky is the remote web folder)

[EricClaeys]

What is the come?

[EricClaeys]

Can you attach your ftp-settings.sh? Remove the password and user name first.

[ea1ii]

#!/bin/bash

# X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*XX*X*X*X*X*X*X

# For details on these settings, click on the "Allsky Documentation" link in the WebUI,
# then click on the "Settings -> Allsky" link,
# then, in the "Editor WebUI Page" section, open the "ftp-settings.sh" sub-section.

# X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*X*XX*X*X*X*X*X*X



	# How will files be uploaded?
PROTOCOL="sftp"

	# The directory where the current image should be copied to.
IMAGE_DIR="CGallsky"
WEB_IMAGE_DIR=""

	# The directory where the timelapse video should be uploaded to.
VIDEOS_DIR="CGallsky/videos"
VIDEOS_DESTINATION_NAME=""
WEB_VIDEOS_DIR="${ALLSKY_WEBSITE}/videos"

	# The directory where the keogram image should be copied to.
KEOGRAM_DIR="CGallsky/keograms"
KEOGRAM_DESTINATION_NAME=""
WEB_KEOGRAM_DIR="${ALLSKY_WEBSITE}/keograms"

	# The directory where the startrails image should be copied to.
STARTRAILS_DIR="CGallsky/startrails"
STARTRAILS_DESTINATION_NAME=""
WEB_STARTRAILS_DIR="${ALLSKY_WEBSITE}/startrails"


############### ftp, ftps, sftp, and scp PROTOCOLS only:
	# Name of the remote server.
REMOTE_HOST="_myHost_"


############### ftp, ftps, and sftp PROTOCOLS only:
	# The username of the login on the remote server.
REMOTE_USER="_myUser_"

	# The password of the login on your FTP server.  Does not apply to PROTOCOL=scp.
REMOTE_PASSWORD="_myPassword_"

	# Optionally enter the port required by your FTP server.
REMOTE_PORT="22"

	# If you need special commands executed when connecting to the FTP server enter them here.
LFTP_COMMANDS=""


############### scp PROTOCOL only:
	# The path to the SSH key.
SSH_KEY_FILE=""


############### S3 PROTOCOL only:
	# AWS CLI directory where the AWS CLI tools are installed.
AWS_CLI_DIR="/home/pi/.local/bin"

	# Name of S3 Bucket where the files will be uploaded.
S3_BUCKET="allskybucket"

	# S3 Access Control List (ACL).
S3_ACL="private"


############### GCS PROTOCOL only:
	# Name of the GCS bucket where the files are uploaded.
GCS_BUCKET="allskybucket"

	# GCS Access Control List (ACL).
GCS_ACL="private"

[ea1ii]

Also:

1. found a typo
   

2 ) remote viewSettings destination expected in postData.sh is outside the remote web folder
I guess that this

needs something similar to
VIEW_DIR="${ALLSKY_REMOTE_WEBSITE}viewSettings"

[EricClaeys]

@ea1ii thanks for finding the typo.
The viewSettings directory is always in the root directory; for your remote Website that's CGallsky so it should upload to CGallsky/viewSettings not to viewSerrings, so that's a bug.
For the data.json file the upload_file line should not have ${IMAGE_DIR} on it since that only applies to remote Websites. That's another bug.
I will fix.

The directory bugs didn’t show up on my systems since my IMAGE_DIR is "".

[EricClaeys]

@ea1ii I just posted an update to scripts/postData.sh that (I believe) fixes the problem. It works on my server where IMAGE_DIR="", and also when IMAGE_DIR="allsky". Let me know how it goes.

[ea1ii]

This one works. Cheers

[EricClaeys]

@ea1ii Try the attached scripts/upload.sh file to see if it fixes you "quote PWD" issue.
You'll need to rename the file to "upload.sh" and may need to "chmod 775 scripts/upload.sh".
Please let me know how it goes - if it works, I'll put it in the release.

upload.txt

[ea1ii]

I think this, too. Almost. I mean. Need to recheck but:
removed the echo (and double quotes of course)
And then it works. I tried manually (need to get some sleep now :) )
I believe the quote PWD fails but opens the connection and hence does not exit. Then it tries the cd ., that also succeeds and does not exit as well.

Looks brilliant. Tomorrow will check the full script. (got some other issues :D )

[EricClaeys]

The echo is needed on the quote PWD ... line, otherwise that line is executed on the Pi and not the web server.
The modified line runs quote PWD and ignores its output. If that fails (||) it runs cd . and if that also fails it exits. If either command succeeds it immediately goes to the next line.

[EricClaeys]

Carlos, If you’re running lftp in interactive mode, you are correct that the “echo” and quotes should NOT be there. The upload.sh script creates a file (tmp/lftp_cmds/SaveImage.txt) using “echo” to output to the file. It then has lftp read that file: ~~~ lftp -f /home/pi/allsky/tmp/lftp_cmds/SaveImage.txt ~~~ If you look at the file you’ll see exactly what lftp tried to do. Eric

…

-------------------------- From: ea1ii ***@***.***> Sent: Wednesday, January 18, 2023 5:12 AM To: thomasjacquin/allsky ***@***.***> Cc: EricClaeys ***@***.***>; Comment ***@***.***> Subject: Re: [thomasjacquin/allsky] Sun (and Moon) add-on (Discussion #2112) True. That works. But unless I'm doing something wrong the open... must be not 'echoed'. <https://user-images.githubusercontent.com/6370469/213156969-9b17871f-69fa-44d8-9c56-3f258701e8c1.png> vs <https://user-images.githubusercontent.com/6370469/213156664-244394c1-513e-4faf-a2ba-45b58c99eb1f.png>

[ea1ii]

Hi Alex,

I do have a v0.1 running version of a module with the light graph. Check it out in my cam. Still struggling with github to create a repository (visual code in desktop , editing via ssh in the Pi.
I can email you the code but I rather go via git (lots to lear here... )

https://cgastrophoto.co.uk/CG_allsky/index.php

Kind regards,

[ea1ii]

https://github.com/ea1ii/lightgraph

[Alex-developer]

https://github.com/ea1ii/lightgraph

Sorry missed this - Will take a look

[Alex-developer]

https://github.com/ea1ii/lightgraph

Its really good :-) Are you on Discord? Could do with getting you into the AllSky server so we can discuss a few little things and also getting it into the main modules repo

[ea1ii]

Hi Alex,
Happy to contibute. I do have discord, though not using it a lot, so another newbie thing for me.

I work on night shifts, 4on-4off, and I'm starting a block just tonight. Next weekend I'll be available almost any time. Just let me know.

Apologies in advance if I ask for too much help on some topics.

[Alex-developer]

Hi Alex, Happy to contibute. I do have discord, though not using it a lot, so another newbie thing for me.

I work on night shifts, 4on-4off, and I'm starting a block just tonight. Next weekend I'll be available almost any time. Just let me know.

Apologies in advance if I ask for too much help on some topics.

ea1ii

Drop me an email alex.greenland @ gmail.com and I will get you the discord details