Yes it is part of Astroberry, and you keep both INdI and Kstars updated with the usual terminal commands..

sudo apt update && sudo apt upgrade

Booting and running from HDD/SSD is not astroberry specific. If you configure your system to boot/run from external drive astroberry will be fine.
However raspberry does not boot directly from external drive. It always uses SD for it. So you need to keep at least SD card with boot partition and configure root parameter in /boot/cmdline.txt to point to your external drive partition e.g. /dev/sda1 (it must be ext4 formated and it should contain all the files from root partition). Also you would need to change the configuration of /etc/fstab to change / point to new partition (e.g. /dev/sda1).

The update has been released. So please run regular: sudo apt update && sudo apt upgrade

From now on GPS Panel and Astro Panel use only GPS readings as source of location. For users that do not have GPS, the system provides Virtual GPS (sudo apt install virtualgps), which can be configured by editing /etc/location.conf file or using Preferences/Geographic Location menu. Virtual GPS provides system-wide location information to each end every system component and application, so it can be used also in KStars, indi-gps and even indi_gpsd or indi_gpsnmea (any anything that uses gpsd service).

If you use GPS don't install virtualgps or disable it after installation (sudo systemctl stop virtualgps.service && sudo systemctl disable virtualgps.service).

The /etc/astropanel.conf file has been abandoned and is not used anymore. The same for binding to Weather Plugin location - it's not used anymore.

Will this work on Tinkerboard (armbian os) & Nvidia Jetson Nano( ubuntu ) ?

If you mean whether virtual gps will work on others hardware, the answer is yes, it should work. Regarding whole Astroberry Server the answer is no, it is designed to work on raspberry only.

Would it be possible to have the astro panels available somehow, on the desktop, so they can be viewed while using VNC viewer, instead of web based noVNC, the reason being is that it is much faster over VNC than we based noVNC...so would prefer to use that way, but do love the useful info in the panels...?. Cheers..

They are actually available on the desktop. Just point your browser to:
- http://localhost/gpspanel/
- http://localhost/astropanel/
- http://localhost/indiwebmanager/

UPDATE: I have just added a page with all the panels in one place. Update and point your browser to http://localhost/panels.html

Hello,

I was excited to see the process stating how to get updates. However, requesting updates has a few hang ups. After running upgrade, I have a message saying 2 apps not upgraded.

Also, PHD2 cannot see my QHYCCD QHY5LII. I select QHY5 driver In PHD2. I get lsusb cannot find the QHY5. This looks to be a case of looking for text explicitly. It will find the ZWO. The INDI driver is running and operations. Are there any updates?

If any of apps is not upgraded with standard apt upgrade, you should run apt dist-upgrade. Seeing 1 app not upgraded in astroberry is normal because 1 package is locked i.e. pixflat-icons. If you want to unlock it remove /etc/apt/preferences.d/astroberry-server file. This will probably change start menu icon when pixflat-icons get upgraded.

Regarding QHY I leave it to other users. I do not own one. Is QHY5LII supported on linux at all?

Indeed. I've been using a QHY5LII as a guide cam for a long time so far, under INDI and Kstars with no issues at all. Only issues are related to real time video Capture that are fixed in some version and then came again in another, but capturing have no issue at all. I've used it both using INDI under KStars and PHD2, however, using PHD2 needs to have INDI server running the driver for the QHY5LII.
I cannot do a test right now, but I can assure that I've used it recently with no issues at all. I'll do some tests with latest Astroberry version to be sure, however.

Hello,

I tried cruising the QHY forum for “drivers”. I found a 2016 driver and used it in AB 1.1. But, the QHY5. HEX file has QHY5LII in it. Under AB 1.1, logging clearly showed QHY5LII is in the stock driver.

The LSUSB finding seems to look beyond INDI and the HEX file. LSUSB shows the device is loaded and operational. I seemed to have this problem when I had a dead QHY5LII. This one works. INDI does not have a problem with the device.

Does it mean it used to work in the past and now it doesn't?
The current libqhy package uses QHY libraries v6.0.4 and it includes QHY5.HEX (see content of /lib/firmware/qhy)