MQTT Message Bus

Hostname: mqtt.hacklab
Port: 1883

• Do not use the MQTT network for evil.
• Do not annoy other lab users (especially with sound or lighting).
• Do not be the reason for new rules.

mosquitto_sub -h mqtt.hacklab -t '#' -v                      # listen to all messages
mosquitto_sub -h mqtt.hacklab -t 'sensor/g1/temperature' -v  # listen to a single topic
mosquitto_pub -h mqtt.hacklab -t 'display/g1/leds' -m red    # send a message
mosquitto_pub -h mqtt.hacklab -t 'dali/g1/preset/harmony' -n # send an empty message

MQTT Smart devices login/Documentation

This sets the labs public open/closed status. Changing the value will cause an IRC notification and changes on SpaceAPI and the website. A notification will also appear on https://twitter.com/edinhacklabopen.

When updating, the message should be sent with retain=True.

Access-controlled tools (read-only values):

The ceiling lights in the main (G1) room are connected via a DALI bus. They can be controlled by selecting a preset, setting individual light levels or by passing a script.

[["set", 5,0], ["delay",2000], ["set_all",254]]

The Ferrograph Rhapsody LED Display is configured to display a list of message chunks on it's main scrolling area. Use the submessage topic below to add a message to the scroller. Messages time out after 10 minutes, so resend the message every 1-5 minutes using the same id.

The wooden box by the door in G1, with two buttons and a 16×2 LCD:

• rainbow
• zap
• chase
• test
• pixelpicker
• redalert
• emergency
• xmas
• cyber

• lessbeans / lesbinyan
• nyanbinary
• pan
• trains / trams

The LEDs can also be addressed in real time via a UDP network protocol. See this example.

The strip is controlled by ledpi.hacklab, a pi 2 in the corner of the ceiling of G1. All code is in /opt/leds/. See README there for more info.

The one that goes across the ceiling in the middle of the room.

These are running the WLED firmware, which is ridiculously comprehensive and can talk to basically everything. However, MQTT seems to have been disabled.

There is a web interface at http://wled-ceiling-string.hacklab.

Full MQTT docs at https://github.com/Aircoookie/WLED/wiki/MQTT ^ Topic ^ Payload ^ Notes ^ | display/g1/wled/$STRIP_NAME | 0-255, “ON”, “OFF”, or “T” | “T” means toggle | | display/g1/wled/$STRIP_NAME/col | #RRGGBB | | |||STRIP_NAME can be replaced with “dangle” for the strip dangling in G1 or “all” for every strip running this firmware in G1|

The blinky chart of the West of Scotland in G1.

Note: Lighting mode may be overriden by hardware nya nya switch.

Code for this can be found on ehl-vm-things:/srv/docker/py3scripts/entrance-handler

The door is opened by a small ESP8266 and a relay connected to the intercom phone under the IRC terminal in G1

Replace [room] with one of g1, g2, g8, g11, or all. Room names can also be combined. e.g. “g1-g2-g8”

Sound effects get annoying fast. Don't say we didn't warn you.

Cazagen recently add a toy wiimote to G1 that allows for MQTT → IR.

It has the following commands.

On-Off keying for remote controlled mains sockets.

Space API is a standard for publishing data about Hackerspaces. Our data is generated at http://spaceapi.edinburghhacklab.com/spaceapi.json. The sensors section of the data can be extended by sending messages:

e.g. a temperature reading - type=temperature

{
  "_ttl": 300,
  "location": "In a deep dark hole",
  "value": 3.14,
  "unit": "\u00b0C"
}

_ttl=300 will cause the entry to expire after 5 minutes (change this to be 2-3x your update interval).

These are beacons that can be used as time-based callbacks. This allows simple scripts to be written, driven only by incoming MQTT events.

* Network devices
* Door and window status
* Shorekarn scrolling LED sign
* IRC bot