Showing posts with label remote control. Show all posts
Showing posts with label remote control. Show all posts

Monday, January 04, 2016

Control Home Devices via XMPP Chat with Raspberry Pi

Control your home devices from anywhere using a Raspberry Pi running the RBox Linux distribution. The RBox chat-bot connects to a public XMPP/Jabber server, so you can toggle GPIO pins from your phone's chat app — no port forwarding, no dynamic DNS, no paid cloud services.

How it works

Setup diagram — Raspberry Pi at home communicating with smartphone via XMPP

Setup diagram — Raspberry Pi at home and your phone both connect to a public Jabber server. Chat messages carry GPIO commands.

Both the Raspberry Pi (running RBox) and your Android phone (running Xabber or any XMPP client) log in to a public Jabber server with their own credentials. Once the two accounts have authorized each other, they can exchange chat messages through the server.

Advantages

  • No router configuration or port forwarding needed — all incoming firewall ports can stay blocked
  • No dependency on paid cloud services — hundreds of free Jabber servers are available
  • Works from any location as long as your phone has internet access (Wi-Fi or mobile data)

Controlling GPIO

To toggle a GPIO pin, send a chat message from your XMPP client:

Gpio 2 1    # set GPIO2 high
Gpio 2 0    # set GPIO2 low

For full setup instructions (SD card preparation, XMPP account creation, first boot), see the RBox installation guide.

SOURCE CODE

github.com/hackboxguy/brbox — RBox sources and build instructions

Sunday, January 03, 2016

RBox XMPP Command Reference for IoT Control

Complete command reference for RBox. Send Help to your RBox device and it will reply with the full list of available commands. For background on RBox, see the introductory post.

RBox Help command output on Xabber

Help command output shown in the Xabber Android app.

Commands are not case-sensitive — they are converted to lowercase internally before processing.

System commands

Version — returns the RBox version in the format MJ.Mn.BUILD (major, minor, 5-digit SVN revision). Run this before and after Sysupdate to confirm the upgrade.

Sysupdate — downloads and installs the latest RBox release from GitHub onto the non-active boot partition. A reboot is required for changes to take effect. Tip: send Sysupdate;reboot to update and reboot in one step.

Reboot — gracefully shuts down all services and restarts the device.

Poweroff — gracefully shuts down and halts the system. Always use this before cutting power — a hard power-off leaves the XMPP session stale (the server shows the device as online but it is unresponsive).

Uptime — returns the device uptime in hours.

Network commands

Publicip — returns the public IP address assigned to the router. Useful when dynamic DNS is unavailable or not updating correctly.

Localip — returns the local LAN IP address of the RBox device. Useful for SSH access on the same network.

Hostname commands

Hostname [name] — with an argument, sets a new persistent hostname (takes effect after reboot). Without an argument, prints the current hostname. Useful when SSH-ing into RBox on the local network.

Resethostname — resets the hostname to the default format brbox-1A2B3C4D5E6F (where the last 12 characters are the MAC address). Requires a reboot.

GPIO commands

Gpio <address> [value] — reads or writes a GPIO pin. Examples:

Gpio 2 1    # set GPIO2 high
Gpio 2 0    # set GPIO2 low
Gpio 2      # read current state of GPIO2

GPIO pin values are not retained across reboots — they revert to defaults.

SOURCE CODE

github.com/hackboxguy/brbox — RBox sources and build instructions

XMPP Account Setup Guide for IoT Remote Control

A step-by-step guide to creating XMPP master and slave accounts on a public server (tested with xabber.de, jabber.de, ubuntu-jabber.de) using the Psi desktop client. These accounts enable remote control of embedded Linux devices over the public internet via XMPP chat protocol.

Shortcut: If you have two Google accounts, you can skip this guide entirely — just authorize both accounts as contacts and use one as the master (your phone/PC) and the other as the slave (chat-bot). In the second account's Google security settings, set "Allow less secure apps: ON".

Why XMPP for IoT?

XMPP is widely used as a chat protocol between humans. The technique described here repurposes it for remotely accessing and controlling embedded devices over the public internet. XMPP was chosen for its wide adoption, built-in security, and ease of connectivity.

Typical client-server communication over the public internet requires exposing a server port through a firewall and registering a dynamic DNS name — a common challenge for home routers or 3G-connected devices with non-static IPs. Using existing public XMPP server infrastructure sidesteps these connectivity challenges entirely.

In this setup, the master account is for the person controlling the device (from a smartphone app like Xabber or a PC client like Psi), while the slave account runs on the remotely deployed Linux machine (Raspberry Pi, BeagleBone, etc.) as a chat bot. As long as both devices have internet access, they can communicate regardless of location.

Creating the master account

Step 1: Install Psi XMPP client on your Windows machine.

Step 2: Start Psi, go to General → Account Setup.

Psi Account Setup dialog

Step 3: Click on "Add".

Account list with Add button

Step 4: Follow the numbered fields as shown below.

New account dialog — follow fields 1 and 2

Step 5: Enter the public server as xabber.de and click "Next".

Server selection — entering xabber.de

Steps 6–10: After pressing "Next", wait for the registration form to load. Fill in the fields:

  • Field 1: Choose a username (e.g. "master")
  • Field 2: Enter your password
  • Field 3: Open the captcha link in a browser
  • Field 4: Enter the captcha number shown by the browser

Click "Next".

Registration form with username, password, and captcha fields

Step 11: If registration succeeds, click "Ok" on the confirmation dialog.

Registration success dialog

Step 12: Click "Save" on the account properties dialog.

Account properties — click Save

Step 13: Click "OK" on the next confirmation dialog.

Confirmation dialog — click OK

Step 14: Back in the Psi main window, right-click on the "Master" entry → Status → Online.

Setting master account status to Online

Step 15: Enter your full name and nickname, then click "Close".

Profile setup — enter name and nickname

Step 16: Master account creation is done. Log out by right-clicking on the "Master" entry → Status → Offline.

Setting master account status to Offline

Creating the slave account

Repeat steps 1–15 for the slave account. Pay attention to these differences:

  • Step 4: Use the string "Slave" instead of "Master"
  • Steps 7–8: Choose a different username and password
  • Step 15: Use "Slave" as the full name and nickname

Pairing master and slave accounts

Once both accounts are created, go to General → Account Setup. Enable both the Master and Slave account checkboxes, then click "Close".

Account Setup with both accounts enabled

Right-click on "Slave" → Status → Online (wait for the grey star to turn yellow). Repeat for "Master". When both stars are yellow, both accounts are online.

Both master and slave accounts online — yellow stars

The master and slave accounts now need to authorize each other — this is XMPP's standard mechanism to block unsolicited messages. Send a few test messages between the accounts to confirm bi-directional communication works.

Next step: Proceed to Rbox — A Lightweight Linux system for IoT to set up the slave device.