How to Restore HamClock - Inovato Quadra HamClock migration to the new backend server -

 

HamClock is alive on a new server. If you are on the old server, then your hamclock will be deprecated. You need to move it to the new backend. First, go to hamclock.com and follow the instructions for the "one line switch". Follow the instructions here only if the hamclock instructions don't work for you. In my case, the information/instructions on the hamclock.com website for migrating didn't work.  Every reboot resulted in the new backend server address being overwritten. This is apparently because a script called "runner" was restoring the old parameters. I had to modify that program to boot to the new server. 

Here is the process I used to modify the script for the new backend server: 

If Hamclock is running, click on the lock icon to the right of the date and exit the HamClock program. 

The Hamclock package comes with a bunch of othe programs, one of which is a terminal program that you will use to modify the script. Open the terminal program by clicking on the terminal icon. After the $ sign, type: sudo nano /usr/local/bin/hamclock-runner. This will open the runner script and allow it to be edited. Note that the terminal program uses up down arrow keys to move the cursor for editing, not a mouse.

Locate this line: exec=$(hamclock -f on). Change it to exactly this:

exec=$(hamclock -b hamclock.com:80 -f on)

Scroll down and locate the Launch Command "exec=$(hamclock-4k -f on). Change it to exactly this:

exec=$(hamclock-4k -b hamclock.com:80 -f on) 

Press Ctrl + O to save the file

Hit Enter to confirm the file name

Press Ctrl + X to exit the nano editor

Fire up HamClock and Watch for the Settings Screen for BE:hamclock.com:80

-Once you close the editor, you can test it immediately by clicking the HamClock icon. When the splash screen with the MAC address in the upper left pops up, confirm that this line is exactly as follows - BE:hamclock.com:80. If it is, it's definitive verification that your pointer took effect and that the new backend is live. 

I want to acknowledge WB0OEW (SK) for developing the program and Bruce W4BAE and team for migrating it to a new server. This is a GREAT app!

Creating Google Gmail App Password for Less Secure Apps - Solved

On September 30, 2024, Google pulled the plug on "less secure apps"—and just like that, one of the email accounts connected to my main inbox stopped working. Same thing happened to my co-workers. Frustrating? Absolutely. And to make things worse, Google’s help docs on this issue have been... let’s just say, not very helpful.

If you're in the same boat and have been tearing your hair out trying to fix it (been there), I’m sharing what finally worked for me—hopefully it helps you too.

Here is the process for adding a "less secure" email account to gmail:

Log into a gmail (or google workplace) account you want to add to your primary. ie zsmith@workplace.com

Go to manage account and click on security.

Add two factor verification.  NOTE: 2F must be turned on for app pw option to appear!

Once added, return to two factor and select app passwords.

Name the app password, i.e. "NGO email" and click create.

Save the 16 digit app password. The spaces must be removed.

Log into your primary gmail account i.e. jsmith@gmail.com

Click on settings (gear icon).

Select accounts> send mail as> add another email address

In the pop up window enter smtp.gmail.com; your NGO email address, port 587, and TLS security. Enter the 16 digit app password (no spaces) instead of your NGO gmail password. "Enter" should provide an email sent notice.

Respond "confirm" to the confirmation email sent to your NGO email.

You should now be able to respond to incoming NGO emails with your @NGO email address automatically (assuming that you have set your NGO account to forward incoming mail to your primary account). 

I suspect there are others who would like to implement this process as it obviates the need to bounce between two accounts.