In case our router doesn’t have a DHCP server (unlikely) or it doesn’t support binding IP addresses to MAC addresses so we always get the same IP for our Pi (possible), we need to set a static IP on the Pi. That way we can make sure the Pi will be reachable on the same IP even across router reboots.
I needed to check the download speed on of an interface on my Raspberry Pi, so I have used a tool called speedometer to do so.
I have a set of SilverCrest IP20 remote controlled sockets purchased in LIDL.
Remote: SilverCrest 113854 RCT DS1 AAA-A 3726
4x Switches: SilverCrest 113854 RCR DS1 3711-A IP20 FR 3726
These work on 433Mhz radio frequency, so the switches can be controlled using my Raspberry Pi instead of the remote control which came with the set.
In one of the previous posts I have shown how to control the socket’s with pilight and an RF transmitter.
Since the pilight protocol which will be able to control my outlets (quigg_gt9000) is not finished yet, I wrote a simple command which sniffs out the raw codes (with pilight-debug) and a bash script to use send these raw codes to control the outlets (with pilight-send).
At the time of writing this post, the newest device in the Raspberry Pi universe was Pi 3, released on 29th February 2016, boasting a 64bit CPU, an onboard Bluetooth chip, and last but not least: onboard WiFi.
We’ll focus on how to set up WiFi in this post.
Downloading (legal) content using torrents is very convenient, but if you plan to “seed” back the stuff, then you’ll need to keep your computer running 24/7 which won’t be good for your electricity bills. For this reason it’s a nice idea to use a Raspberry Pi as a “torrent server” a.k.a “seedbox” which will run day and night, as it’s power consumption is tiny compared to a laptop, let alone a desktop PC.
We’ll be using Transmission as a torrent client, which can be installed as a “daemon” running in the background all the time on the Raspberry Pi.