Home

Awesome

Raspberry Pi Remote

About

Control your remote power sockets with a raspberry pi. This project includes a web interface.

There's also a powerswitch branch, if you want to imitate a ConnAir remote station on the raspberry and use the nice android app from http://power-switch.eu

And in case your Raspberry is running Windows10, check https://github.com/Panzenbaby/Raspberry-Remote-for-Windows-10-IoT-Core

Credits

Required Hardware

Setup

Usage

Try if all is working with the send program

Options

Binary Mode

Most sockets available for purchase use the following numbering scheme:

no.address
A10000
B01000
C00100
D00010
E00001

Of course, this doesn't make much sense, because it limits the maximum of supported sockets to 5 (or 6, if 00000 is included), and is less intuitive. Using real binary numbering would increase the limit of supported sockets per system to 31, and be more intutive. In binary mode, the sockets need to be numbered as below:

no.address
100001
200010
300011
400100
500101
801000
1610000
3111111

Note that you need to configure your sockets to this kind of numbering to use this feature. This often includes that the dedicated remote that gets shipped with the sockets often is rendered useless, since it only supports the former way of numbering.

User Mode

Use this mode if you want to use send without root permission. The pin must be exported with the gpio utility beforehand because it will be used via the /sys/class/gpio interface. The command for the default pin is gpio export 17 out. The user must be a member of the gpio group to access exported gpio pins!.
Important Note: pin numbering is different in this mode! While wiringPi uses its own numbering scheme in default mode, this mode requires the native Broadcom GPIO numbers (the default port 0 is 17 in this mode). See the wiringPi documentation for further details.

Daemon

Use the daemon in combination with the webinterface