Sunday, February 21, 2016

Raspberry Pi - Dedicated Speedtest Tracker

In the process of finding ways to automate my home, I stumbled upon a post on Make by Alasdair Allan entitled Use Raspberry Pi to Measure Broadband Speeds to Hold Your ISP Accountable. This project, as it sounds, will run speed tests with once an hour, and ultimately log the data to a Google Sheet on your Google Drive.

While following Alasdair's post, I ran into a few issues and felt that I should make a post that explains more of what needs to be completed as far as commands and setup as some are implied but not directly listed. This post uses mostly his post, so please make sure to give him thanks if you like it.
I will be running under the assumption that you already know how to SSH into your Raspberry Pi, but if you don't there is a nice YouTube video here on how to connect over PuTTY. I will also be using the assumption that you are logged in as the user pi, so adjust the user directory as needed if not logged in as pi.

Here is what will be needed to complete this project:
First things first, lets make sure that the Raspberry Pi is up to date. This can be done one of two ways:
  1. Scripted, using from Raspberry Pi - Update Raspberry Pi Script
  2. Manually run update and upgrade options:
sudo apt-get update
sudo apt-get upgrade 
Once you have made sure that your Raspberry Pi is up-to-date, lets get to setting it up for our speedtest tracking. First, we'll make sure that python-pip and speedtest-cli:
sudo apt-get install python-pip
sudo pip install speedtest-cli
 Now, make sure speedtest-cli works by running it:
 You should see a result similar to this (I have modfied some information for privacy)
Retrieving configuration...
Retrieving server list...
Testing from Acme ISP (
Selecting best server based on latency...
Hosted by Acme Server (Earth) [103.82 km]: 41.753 ms
Testing download speed........................................
Download: 45.68 Mbit/s
Testing upload speed..................................................
Upload: 5.65 Mbit/s
Next, we will get another script to help format the text for easy of transferring it to a spreadsheet. Lets install speedtest-cli-extras:
git clone
Now, we will test the new script to see its output:
cd speedtest-cli-extras/bin
Please note that there will be a period of time between when you execute speedtest-csv and when it provides an output similar to below as it is running the speedtest in the background.
2016-02-22 00:59:52;2016-02-22 01:01:51;Acme ISP;;Acme Server (Earth);103.82 km;43.183 ms;22.98 Mbit/s;2.26 Mbit/s;
We could stop here now that we have a delimited output, but that leaves a few issues:

  1. If you want to use the delimited log file, you will need to provide SSH access to the device from outside your local netwrok to check it on the go, OR
  2. You will need to setup a program to take the delimited file and provide other abilities like graphs
  3. Neither Alasdair nor I cover that.
So back to it. This next section will get IFTTT setup to allow our speedtest data to be put into a Google Sheet.
First, connect with the Google Drive IFTTT channel. Make sure that you allow the Google Drive channel to have access to the account that you want your results to be saved to. Now, follow the Maker IFTTT channel. With that complete, we will then need to add the Log Speedtest results to Spreadsheet recipe to our account. 
IFTTT Recipe: Log Speedtest results to Spreadsheet connects maker to google-drive
Make sure that you set the name the recipe "speedtest" before you click the Add button
IFTTT speedtest script name
Now that the online part is setup, lets finish with the local parts. We will now get an IFTTT version of the speedtest-csv script:
This will place a copy of in /home/pi/speedtest-cli-extras/bin.
We will need to modify to include your Maker Secret Key, and then make sure that the script can be be executed. Open in nano:
Scroll to the bottom of the file, and change the SECRET_KEY text to your key from the Maker IFTTT channel page SECRET_KEY location
Once complete, save (Ctrl+O) and exit (Ctrl+X). Now, we will make sure that the script is executable:
sudo chmod +x
Lets test this to make sure that it works:
Once complete, you should see the following message:
Congratulations! You've fired the speedtest event
Now check Google Drive, you should have a new Speedtest sheet.
When you open it, you should have a new row with the results:
February 21, 2016 at 02:16PM41.27845.475.72

Now that the are able to get our results saved, lets get a a cron script make and scheduled. For the sake of logging, we will create another script to run with some extra local outputs. First, create
Paste the following:

date >> /home/pi/speedtest.log
/home/pi/speedtest-cli-extras/bin/ >> /home/pi/speedtest.log
echo "" >> /home/pi/speedtest.log
This will create a quick access log that can be checked locally from first sign on with less speedtest.log, and will append it after each running. Before we test it, lets make sure that the script is executable:
sudo chmod +x
Ok, now let's test it out:
You should see a new line in your Speedtest Google Sheet, and when you run less speedtest.log, you should see a result like this:
Sun 21 Feb 21:29:16 UTC 2016
Congratulations! You've fired the speedtest event
We will need to schedule this to run at the top of the hour.  To do this, we must  open and modify the crontab file. To open it, type:
crontab -e
Scroll to the bottom of the file, then paste the following:
# Run Speedtest script ""
0 * * * * /home/pi/speedtest-cli-extras/bin/
Now you are set to keep metrics on your Internet connect, so you can make sure you are getting the speeds you pay for. Google Sheets also has some nice features such as conditional formatting and graphs that you can use to get on the fly views of the metrics you capture.

Google Sheets formatted example

Raspberry Pi - Update Raspberry Pi Script

While searching, I found a great little post on for quickly running your Raspberry Pi through all of its updates. The original post is here.

My only modification is I created the script in the logon user's /home directory instead of putting in a separate Code directory due to to single use of my Pis currently. While it may be ultimately a bad practice to not properly put all scripts into a dedicated directory, it provides the current ease of access that I desire.

Here is the process:
Create the shell script:
Copy/Paste(click) or manually type the following into the Nano screen:
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get dist-upgrade
sudo apt-get autoremove –y
sudo rpi-update
 Once complete, Save (Ctrl+X, then Enter) and exit (Ctrl+X).

Now, we need to make the script executable:
sudo chmod +x
 Lastly, lets run the script:
sudo ./
Depending on what updates are needed, you may be prompted to enter Y or N to continue the process. If a firmware update is installed, you may also require a reboot to make the change.
To restart immediately, run:
sudo reboot