v2024.12.06_06

• Fixed an issue where downloading the support log from the Getting Support page would hang the page.
• Fixed a couple issues with WebUI "System Messages":
  • Some messages were displayed hundreds or thousands of times rather than being displayed once with a number of occurrences greater than 1.
  • A message was truncated when unable to download the de421.bsp file.
• Fixed a rare situation where the Module Manager will fail to display any modules due to corruption in a module's metaData.

v2024.12.06_05

Fixes a problem where RPi cameras could time out.

If your Keogram Font Color contailed three numbers you'll need to switch the first and third numbers.

See the Change Log for a complete list of changes.

v2024.12.06_04

Merge pull request #4701 from AllskyTeam/v2024.12.06_04

V2024.12.06 04

v2024.12.06_03

• RPi cameras that report sensor temperature now support dark frames.

• Bug Fixes

  • MOON variables work in the Overlay Editor (the de421.bsp file downloads correctly).
  • All the "Click here to ..." messages in the WebUI now work.
  • Using the analyticsTracking.js in an Allsky Website now works.
  • An issue with adding images in overlays was fixed.
  • The remoteWebsiteInstall.sh command now works if the Image Directory setting is empty.
  • Duplicate System Messages now have the correct count of the number of times the problem occurred.

v2024.12.06_02

Enhancements / Changes

• The WebUI will now notify you when a new Allsky version is available.
• The remoteWebsiteInstall.sh command does a better job telling you why problems occur and how to fix them.
• Additions to the allsky-config command:
  • If you are seeing a Multiple consecutive bad images message in the WebUI, run allsky-config bad_image_info. It will suggest how to fix the problem.
  • If a local or remote Allsky Website has a problem reading the data.json file, you are now directed to run the new allsky-config check_post_data command. It tries to determine why the message occurred.
  • The allsky-config move_images command is more robust and allows you to move the images back to the ~/allsky/images folder if desired.
• When an Allsky Website is stuck on the "Loading ..." message because it can't find the current image, you'll get a message telling you how to fix it.
• Several Allsky Website files are now in subdirectories, e.g., all the "css" files are in a css directory. No user action is needed.
• You can now have custom "notification images" like "Allsky is starting up". To do so, create a ~/allsky/config/myFiles/notificationImages directory, then put your custom images there using the exact same names as the Allsky files in ~/allsky/notificationImages.

Bug Fixes

• The problem with de421.bsp is fixed.
• Timelapse thumbnails now have the correct name.
• A security issue was fixed.
• Installing or upgrading Allsky is less likely to hang when there's a problem with an RPi camera.
• Fixed a typo in the ssl:check-hostname command in testUpload.sh.
• removeBadImages.sh now works with mean values that have a comma in them.

v2024.12.06_01

• You can no longer enter Issues in GitHub (you can still enter Discussions). Instead, use the new Getting Support page in the WebUI to automatically collect the information needed to troubleshoot your problem. Simply following the instructions on that page.

• NO private information is sent; that information is kept in the ~/allsky/env.json file which should never be uploaded.

• The WebUI's Editor page now:

  • Tells you if there is a formatting error on the page, for example, if you are missing a comma. You will not be able to save the file until the error(s) are fixed.
  • Placeholder values that need updating before a Website will work are highlighted like XX_NEED_TO_UPDATE_XX.

• The WebUI now displays the status of Allsky (Running, Stopped, etc.). The status is determined every time a WebUI page is displayed, so if the status changes while you are on a page it won't be updated until the page is refreshed.

• You can now easily specify a location to store Allsky's image other than in ~/allsky/images. This is typically done to store images on an SSD or a similar larger, faster, and more reliable media than an SD card. See the allsky-config move_images command.

• If you are having problems getting startrails to show the trails, the new allsky-config get_brightness_info command helps by displaying information on image brightness determined during startrails generation. That information helps determine what to put in the Brightness Threshold setting. See Startrails settings for details.

• The new allsky-config compare_paths command helps determine where to upload your remote Website files and what URL to use. See the Mapping Server Locations to URLs page for details.

• The allsky-config command can do more, including lettings you change the size of the ~/allsky/tmp directory and the amount of swap space. Run allsky-config for a full list of what it can do.

• The new meteors directory in Allsky Websites is to upload images with meteors. A meteor icon can be displayed to the list of icons on the left side of a Website page by setting the "display" line to "true" in the "Archived Meteors" section of the associated configuration.json file.

• NOTE: Support for saving and uploading images with meteors will be added in a future Allsky release.

• The remoteWebsiteInstall.sh command now prompts to upload any local startrails, keograms, and timelapse files. It's also more "polished", doesn't fail as often, and provides better messages.

• Allsky Websites now give a detailed message when they can't find the image, instead of just the "Loading..." picture forever.

v2024.12.06

Click to view changes

Changes that may require action (upgrades only)

The changes in this section may require settings changes; after upgrading, check that your settings and images look right.

• The config.sh and ftp-settings.sh files are gone - their settings are now in the WebUI.
  Possible action: The upgrade should migrate your prior settings to the WebUI unless you have a very old version of Allsky in which case you'll be notified during the upgrade on what to do.
• The CROP settings have been simplified to specifiy the number of pixels to crop from the top, right, bottom, and left of an image.
  Possible action: If you cropped your images the upgrade will notify you to re-enter the settings using the new fields.
• The Remove Bad Images Thresholds settings are now between 0.0 and 1.0 instead of 0 - 100.
  Possible action: The upgrade should adjust your threshold values to the new range, but check.
• Allsky now uses the mean brightness of an image to determine if it is too bright or too dark. This is the same way auto-exposure determines the exposure to use. Prior releases looked at the whole image including any dark borders.
  Possible action: You may need to adjust your Remove Bad Images Thresholds to take into account for this change.
• (ZWO only) The mean brightness of an images is now a number between 0.0 and 1.0; it used to be 0 - 255. This matches the Mean Target settings which have always been between 0.0 and 1.0 as well as the Remove Bad Images Thresholds. settings, making it easier to determine what values to use.
  Possible action: If the MEAN variable is on your overlay you may need to change the format it's displayed in. A two or three-digit number is best.
• The WebUI now hides the settings in each section unless there's an error in that section. To view a section's settings, click the symbol on the left side of a section heading.
  Possible action: This may take a little time to get used to. However, with the significant increase in WebUI settings it would be difficult to find what you want if the sections weren't hidden.
• check_allsky.sh is now called checkAllsky.sh to be consistant with other program names.
  Possible action: None.

Enhancements / Changes

• Added truetype fonts to the core repository
• Setting up an Allsky Website on the Pi is now trivial - just enable the the Use Local Website setting and optionally set the number of days' images to keep via the Days To Keep on Pi Website setting. No more trying to figure out how to set the variables!
• Setting up a Website on a remote server is easier since the only directory you have to specify is the top-level Image Directory in the WebUI.
• Installing a Website on a remote server is significantly easier as well. Use the new remote_website_install.sh command; it will upload the Allsky Website files for you and remove any old, unneeded files. If this is a new remote Website, remote_website_install.sh will ask you whether or not to also upload any startrails, keograms, and timelapse videos on your Pi.
• Images, timelapse, keograms, and startrails can now be written to a remote server in addition to, or instead of, a remote Website. This is useful if you want to include those images in a different website or want to archive them.
• The new allsky-config command is similar to the raspi-config command but for Allsky information and configuration. This command is mentioned in several documentation pages (as well as below) to easily describe how to do something.
• Execute allsky-config to see what it can do.
• Running allsky-config samba allows you to mount the ~/allsky directory on a PC or MAC. See Copy files to / from a Pi for more information.
• The new testUpload.sh command tries to upload a test file to either a remote Website or remote server. If the upload fails, the command attempts to tell you why it failed and what to do about it.
• When changing settings, Allsky only restarts if it needs to. Some settings, like the Owner don't impact taking images so there's no reason to restart Allsky. A few settings cause Allsky to stop after being changed. Hovering you mouse over a WebUI data field displays a popup that indicates what will happen after changing that field.
• The module Overlay Method is now the default for new installations. In the next major Allsky release the legacy method will be removed and the only way to add text will be using the Overlay Editor.
• You can now have more than one ZWO camera connected, and on the Pi 5, more than one RPi camera connected. The installation will show ALL attached cameras.
• If you change cameras without notifying Allsky (e.g., you shutdown the Pi, replace the camera with a different model, then restart the Pi), Allsky will not start and will put a message in the WebUI telling you how to properly change cameras. No message will be given if you replace a camera with the same model, e.g., an RPi HQ with another RPi HQ camera.
• If you try using an unsupported camera you'll receive a message stating that and telling you what to do and how to request support for the camera.
• All ZWO cameras as of September 7, 2024 are supported (library version 1.36).
• Support for some new third-party RPi cameras was added.

Run allsky-config show_supported_cameras to see the supported ZWO and RPi cameras.
The ZWO list is over 130 entries so if you want to check if a camera you're considering getting is supported, run:

allsky-config show_supported_cameras --zwo | grep -i "CAMERA_NAME"
replacing CAMERA_NAME with the name with OUT ASI, e.g., 178mc.
Checking for an RPi camera is easier:

allsky-config show_supported_cameras --rpi

• The LAN Dashboard and WLAN Dashboard WebUI pages now display all network adapters, regardless of their names.
• The endOfNight_additionalSteps.sh file is no longer supported. The few people that had that file should use the "night to day" module flow instead.
• When taking dark frames, any images that is too bright is deleted. This can happen if you start taking darks before covering the lens or if the lens cover lets in some light, e.g., a plastic lens cap.
• DHCP on the Pi can be configured via the WebUI's Configure DHCP page. This is an advanced option that is not used very often.
• Overlay changes:
• The overlay module debugging output is easier to read.

1. You can now create different overlays for daytime and nighttime. The new Overlay Manager is available from the main toolbar in the Overlay Editor. Several overlay templates for different cameras are provided which can be customised to your requirements. If you have customised the overlay then during the upgrade process a new custom overlay will be created for you and assigned to both daytime and nighttime captures. If you have not customised the overlay then Allsky will attempt to use the best overlay for your camera.
2. The Overlay Editor will display a warning if any of the fields on the overlay are outside the image area. The fields can be fixed which will move them into the bounds of the image. See [BUG] If a field is outside the image ...
3. If images are not being captured the Overlay Editor will not start and will display a message and wait until images are being captured. This prevents a (usually much smaller) notification image from being used as the Overlay Editor background.

• See Modules Documentation for details on Extra Module changes.
• New Modules:

1. Allsky AI - Detects cloud cover using AI
2. Allsky Fans - Controls a fan based upon cpu temperature
3. Allsky Border - Expands an image to include additional borders
4. Allsky HDD Temp - Retrives hard drive temperatures using SMART
5. Allsky ina3221 - Allows current and voltage measurements
6. Allsky influxdb - Allows data to be written to uinfluxdb
7. Allsky light - Determines light levels using a TSL2591
8. Allsky LightGraph - Displays a graph of day and night
9. Allsky ltr390 - Measures UV levels
10. Allsky mlx90640 - Captures an IR image of the sky (very experimental)
11. Allsky Publish Data - Publish Allsky data to Redis, MQTT, or REST
12. Allsky Temp - Reads up to three temperature sensors and controls a gpio pin based upon the temperature

New Settings

• Images Sort Order determines the sort order of the images on the WebUI's Images page.
• Show Updated Message allows hiding the Daytime images updated every... message on the WebUI's Live View page.
• Nighttime Capture and Nighttime Save are the same as the daytime settings but for nighttime.
• ZWO Exposure Type specifies how images should be taken. See the documentation for a description of the different types.
• Deleted Settings
• The Image Width and Height settings were deleted since they are no longer needed. Use the crop and/or resize settings instead.
• The Version 0.8 Exposure setting was deleted since it's functionality is incorporated into the ZWO Exposure Type setting.
• The New Exposure Algorithm setting was deleted because it produced better results so is now always used.
• The REMOVE_BAD_IMAGES setting was deleted to keep people from disabling the check. In addition to "too dark" and "too light" images, images that are empty and corrupt are also checked for, and those images kept timelapses from being created. If you don't want to run the brightness checks set their Remove Bad Images Thresholds to 0.
• The Brightness settings were deleted since there is no need for them. Changes to brightness should be done via the Target Mean settings.
• (ZWO only) The Offset setting was deleted. It brightened every pixel by the amount specified and is not needed with allsky cameras.

Bug Fixes

• ASI_ERROR_TIMEOUT messages are mostly gone. Yea!!!
• The ...

v2023.05.01_05

Point Release 5 for base release v2023.05.01 (Security update. Thanks to @heruan for reporting the issue.)

Click to view changes

What's Changed

• #3867 Remove module upload functions by @Alex-developer in #3868

v2023.05.01_04

Point Release 4 for base release v2023.05.01.

Click to view changes

See the Change Log in the documentation for an overview of the changes.

What's Changed

• Hotfix to remove colour error by @Alex-developer in #2962
• Fix for Python dependencies by @Alex-developer in #2999
• Bump grunt from 1.4.1 to 1.5.3 in /html/js/jquery-ui-1.13.1.custom by @dependabot in #3001
• Eliminate flicker in firefox brower by @minichate in #3024
• Update install.sh: Temp. check for Bookworm by @EricClaeys in #3026
• Point release 4 by @Alex-developer in #3027
• Merges from master by @EricClaeys in #3037
• Fixes by @Alex-developer in #3118
• Added support for ArduCam IMX462 by @will-rigby in #3123
• Update ASI SDK to 1.31 by @Varnius in #3138
• Update AllskyWebsite.html by @Dhovin in #3160
• Additional error handling by @Alex-developer in #3163
• Add missing modules by @Alex-developer in #3164
• Fixes for Bookworm and pi 5 by @Alex-developer in #3174
• Remove experimental display option by @Alex-developer in #3181
• Upgrade to ZWO SDK 1.32 by @EricClaeys in #3186
• Remove advanced options by @EricClaeys in #3188
• Remove unused python modules by @Alex-developer in #3192
• Update FAQ.html: Better explain how to focus by @EricClaeys in #3201
• Update startrails.html: minor improvements by @EricClaeys in #3204
• #3185 Fixes for locale dp separator by @Alex-developer in #3211
• Revert "#3185 Fixes for locale dp separator" by @Alex-developer in #3212
• #3185 Fix for locale by @Alex-developer in #3213
• Fix for missing module by @Alex-developer in #3214

Full Changelog: v2023.05.01_03...v2023.05.01_04

v2023.05.01_03

Point Release 3 for base release v2023.05.01.

Click to view changes

What's Changed

• Install.sh shorten "not restored" message by @EricClaeys in #2808
• Update changeLog.html: mention installation keeping track of what it's...
• Update install.sh: don't prompt to reboot if not needed
• display_msg(): allow newlines before initial "*" by @EricClaeys in #2811
• Update install.sh: skip whole Python dependency step if all packages...
• Update install.sh: shellcheck change
• Update generate_notification_images.sh: improve error messages
• Update install.sh: add set_what_can_be_skipped()
• Update documentation.css: add classes for overlays
• Update changeLog.html: mention RPi sensor temp
• Update FAQ.html: add missing ">"
• Update mode_mean.h: add argument to aegCalcMean()
• Update mode_mean.cpp: add "useMask" argument
• Update capture_RPi.cpp: call aegCalcMean() a 2nd time for a full mean
• Update mode_mean.cpp: Optionally create mean without mask
• Update mode_mean.cpp: add debug line
• Update mode_mean.cpp: get mask working
• Update saveImage.sh: rename AS_MEAN2 to AS_BAD_IMAGES_MEAN
• Update functions.sh: minor changes
• Update install.sh: check for failed command.
• Update options.json.repo: fix meanthreashold defaults
• Update install.sh: fix quotes
• Update options.json.repo: fix min and max for thresholds by @EricClaeys in #2819
• Update changeLog.html for _03
• Update README.md for _03
• Update allsky_common.cpp: fix consistent delays bug
• Update functions.sh: add --null argument
• Update allsky.sh: put "-cmd" at start of capture_* command line
• Update changeLog.html: add bug fix description
• Update version to _03
• Update install.sh: fix when installing remote website
• Update changeLog.html: add bug fix
• Update install.sh: Add message to restart installation
• Update install.sh: change the way IN_TESTING is checked for
• Update install.sh: more error checking
• Update AllskyWebsite.html: fix typo
• Update allsky.sh: remove message about ALLSKY_INSTALLATION_LOGS
• Update makeChanges.sh: only update map if we're using it
• Update changeLog.html: add map fix
• Update makeChanges.sh: fix SHOW_ON_MAP
• Update install.sh: check for raspistill on Bullseye
• Update allsky_common.cpp: better lat/long checking
• Update changeLog.html: add Latitude and Longitude fix
• Update install.sh: better log message when no prior version
• Update install.sh: fixed typo with directory name
• Update install.sh: Fix unnecessary reboot
• Update install.sh: update message to testers
• Update install.sh: display error message on flowupgrade.py failure
• Fix for flow upgrade not handling empty files by @Alex-developer in #2920
• Update ASI_functions.cpp: add ov5647 (version 1) camera
• Update changeLog.html: added support for RPi version 1 camera
• Update sidebar.html: Rename file and link to it
• Update exposureGainSaturation.html: remove Brightness, plus more
• Update allsky.html: removed Brightness
• Update allsky.html: fix mention of "module" mode.
• Update other.html: improve section on image brightness
• Update RPiCameras.html: use Contrast as example instead of Brightness
• Update functions.sh: fix determineCommandToUse()
• Update install.sh: add comment
• Update install.sh: remove reboot file if not needed
• Update install.sh: update tester message
• Update install.sh: bug fix with meanthreshold
• Update FAQ.html: Added Samba
• Update changeLog.html: Add Samba FAQ
• Update shell.js: Display decimal numbers in one color
• Update saveImage.sh: bug fix with IMAGE_TO_USE
• Update changeLog.html: added AUTO_STRETCH fix

Full Changelog: v2023.05.01_02...v2023.05.01_03