Click any image to see a full-screen preview.

Hamclock for Raspberry Pi ... the easy way!
Simple install instructions for Hamclock and how to keep your Hamclock running past the June 2026 closure of CSI.
*** Have an existing Hamclock and want a quick answer to how to keep it running past the CSI closure? Look no further, don't even read below. Right-click your Hamclock Desktop icon, select Properties and the Desktop Entry Tab: amend the Command to this.. /usr/local/bin/hamclock -b ohb.hamclock.app:80 *** Do see below if you want HC to autostart.
*************************************************
In January 2026, Elwood Downey WB0OEW sadly passed away. As the developer, this signalled an impending end to his beloved ClearSkyInstitute HamClock project that had run for many years. Not wishing to lose such a valuable resource in the ham community, Dave N9DK has developed open-hamclock-backend. Your pre-installed Hamclock, or new installation, will seamlessly continue as before.
There are now several Hamclock variations. If you want accuracy of data, only OHB fits the bill. Same Hamclock frontend, the ultimate backend. Being Linux, the tendency for programmers is to be ambiguous in their explanations. Even OHB suffers from this with not just the OHB GitHub page but also two associated websites proffering complex scripts and commands when actually there exists the easy way.
If you need a new or fresh install, use Raspberry Pi Imager from https://www.raspberrypi.com/software/ and because I recommend that you have Hamclock start automatically on the Pi at boot, avoid selecting the latest Trixie. In this distribution some important functions have been removed or are handled differently. Select instead Bookworm 64-bit with Desktop. After installing the OS, bring it up to date by opening Terminal and using the command sudo apt update && sudo apt upgrade. Now reboot your Pi.
Some HC websites mention amending the hosts file at /etc/hosts but I recommend that you do not do that. SSL certification will get broken and updates will fail. Use only the -b option as described below.
Download Hamclock from here: https://www.dropbox.com/scl/fi/qt270dddqyo5kcjtxaldi/hamclock-main.zip?rlkey=mplgegz413yebfiwso6unui4s&st=wqfdfci6&dl=0
This is currently HamClock version 4.26 which will self update according to your settings.
If you open this site hamclockeasy.com in a web browser on your Pi, you can click the above link to start the download. You do not need to login, instead click ‘continue with download’ and the zip file will transfer to your Downloads folder. Extract it and open a Terminal window at the ESPHamClock folder. Enter each of these commands in turn:
make help
make hamclock-1600x960
or whatever your preferred size is from the presented list
sudo make install
Hamclock will be installed - try in Terminal the command /usr/local/bin/hamclock &
If you are not familiar with HamClock configuration, see the User Guide button at the top of this page.
HamClock will need to know where to get its data. It must therefore be pointed at open-hamclock-backend. A desktop icon will provide a means of manually starting HamClock. An autostart entry will set HamClock to automatically start when your Pi boots up.
To get a desktop icon, open the ESPHamClock folder in the Pi file manager and copy the HamClock file to the desktop (copy & paste). You can set the server in the icon by right clicking and opening properties. Go to the Desktop Entry tab. In the command box, change the command to /usr/local/bin/hamclock -b ohb.hamclock.app:80 and press OK.
For autostart, if you want Hamclock to start on Pi launch, open a Terminal window then
mkdir -p ~/.config/autostart (if it does not already exist, otherwise go to it: cd /home/<user>/.config/autostart )
nano ~/.config/autostart/hamclock.desktop
[Desktop Entry]
Name=HamClock
Exec=/usr/local/bin/hamclock -b ohb.hamclock.app:80
Icon=/home/pi/.hamclock/hamclock.png
Terminal=false
Type=Application
Save and exit with Ctrl+O, Enter, Ctrl+X .
Hamclock will prompt you when there are frontend image updates. The version number will turn red. Double-click to update. Version 4.22 Hamclocks, for example, will update to version 4.23 in a similar process to the original Hamclock.
With Hamclock directed to OHB, using the external server, reboot your Pi.
All done. You have done it the easy way!
============================================
Accuracy of the Kp solar index value.
The Space Weather Prediction Center updates the estimated Kp value every 3 hours starting at midnight UTC. The exact timing can vary from 1 minute past the hour to as much as 8 minutes past. OHB therefore pulls data at 10 minutes past the hour to ensure the update is grabbed. The Hamclock application refreshes from its server, originally CSI but now OHB, every 45 minutes. Conceivably it could have taken up to 45 minutes for Hamclock to show the latest value. But if you downloaded from my DropBox, the KP_INTERVAL has been edited from 2500 seconds to 600 seconds. When OHB pulls the new Kp value from SWPC, your Hamclock will update between 1 and 10 minutes later. Therefore, at the latest, Kp will be up to date within 20 minutes of SWPC posting the new value.
To edit KP_Interval yourself, changes must be made before the make compile. Use the Pi file manager and open the ESPHamClock folder. Right-click the HamClock.h file and use Search to find KP_INTERVAL. Its default setting is 2500 (seconds), change this to 600 (but not less than). Save the file. If there is a permissions issue, merely save with another name, delete the original HamClock.h file and rename the saved file to HamClock.h
With this amendment, open-hamclock-backend is the most accurate of all the Hamclock variants with not just Kp being up to date but also the other solar data indices having precision presentation. OHB is actually a step forward from the original CSI Hamclock.
================================================
Want to run your own local open-hamclock-backend server?
OHB can be deployed on a host OS. But there are many distributions out there and potentially the OHB dependencies can cause issues with your system, especially when updating. The generally accepted method of managing this is to run the service in a Docker container.
Docker is easily installed. Follow the short instructions at: https://pimylifeup.com/raspberry-pi-docker/#installing-docker-to-the-raspberry-pi
Next, install OHB using these commands, after first checking for the latest version number at https://github.com/komacke/open-hamclock-backend/releases
sudo apt update
sudo apt install jq
curl -sLO https://github.com/komacke/open-hamclock-backend/releases/download/v2.0.3/manage-ohb-docker-v2.0.3.sh (assuming version 2.0.3 is the latest)
mv manage-ohb-docker-v2.0.3.sh manage-ohb-docker.sh (plug in the latest version, same as above)
chmod +x manage-ohb-docker.sh
./manage-ohb-docker.sh install -t <insert version here> so for example your command might be
./manage-ohb-docker.sh install -t v2.0.3
Open the properties of the Hamclock desktop icon and go to the Desktop Entry tab. In the command box, change the command to /usr/local/bin/hamclock -b localhost:80 and press OK. Amend your autostart entry with nano ~/.config/autostart/hamclock.desktop as before and change the Exec= line to the same as above for the icon, pointing at localhost:80 Your Hamclock will, on the next reboot, connect to your own OHB server. There is no real advantage to having a local OHB server but anyway the possibility is there and the above sets it up for you.
When there are OHB updates, seen on the releases page as above, open Terminal and execute the three commands listed under the section “versions starting with v0.24” except that the final command should include the update version like this: ./manage-ohb-docker.sh upgrade -t v1.0.11 or whatever the version currently happens to be.
With Hamclock directed to your own OHB server, reboot your Pi.
All done. You have done it the easy way!
About
The creators of this website are long time Hamclock users who, faced with needing to find a method of keeping our displays from going dark in June '26, looked for alternative sources but were bamboozled by Linux commands, scripts and other unnecessary complications. We decided to find out how to do it the easy way.