|Description||Space empty? Power off!|
|No project picture! Fill in form Picture or Upload a jpeg here|
Read sensors and do some space automation using the Message Queuing Telemetry Transport protocol.
Currently, you can see the solder table powerstrip connected in the power graph.
The MQTT server can be found at 192.168.1.42, via the regular port (1883) as well as the TLS port (8883) and secure websockets at port 443 (subject to change). To connect securely, use the certificate authority chain
There is a sonoff Pow wifi switch in the space, (not yet) connected to a powerstrip near the soldering table (in a brown plastic case with a toggle switch on top of it).
The idea is to gradually add them to every power strip so we can:
- measure (over)current
- switch them off centrally if the space is closed (or notify the user that they are still on, for example, 3D printers).
It currently runs a modified version of the famous Tasmota firmware (the modification allows dangerous GPIO whist using the energy measurement).
NOTE: the switch is built in a box with an external toggle switch. This switch has potentially 240v on its contacts so don't open it and touch the contacts when it is plugged in! Also don't connect both serial and mains; things will break.
You can toggle it via wifi on h1r-2067.lan (subject to change), or by issuing a
mosquitto_pub -L 'mqtt://username:email@example.com/ackspace/hackspace/h1r/cmnd/POWER' -m 'TOGGLE'
Read it's status by subscribing to the sensor topics:
mosquitto_sub -L mqtt://ackspace:firstname.lastname@example.org/+/+/+/tele/SENSOR
mosquitto-clients to start experimenting.
If you run into problems or find something interesting/broken, let xopr know.
The proposed topic hierarchy is as followed:
Where both [prefix] and [type] come from Tasmota's topic definition (
Try to use all-lowercase names (with an exception of the last bit, often in CAPS),
services are supported as base. Services are a bit special; choose a category for room (i.e.
voip) and an identifiable name for device (i.e.
freeswitch); see the extra examples list of topics further below.
In the future, we can extend this to support something like
offsite and the names of participants.
Since ACKspace doesn't have rooms at different levels, the second hierarchy level consist of the room, like
device is the name of the device (similar as Tasmota's
At least the following topics will be implemented first:
ackspace/hackspace/spacestate/stat/RESULT(json power state)
ackspace/hackspace/spacestate/stat/POWER1(string power state)
ackspace/hackspace/spacestate/tele/STATE(json state at interval)
ackspace/hackspace/temperature/tele/SENSOR(json telemetry data)
outside/courtyard/barbecue/tele/SENSOR(json telemetry data)
services/voip/freeswitch/tele/STATE(FreeSWITCH specific data, like caller id)
services/network/bandwidth/tele/SENSOR(Current network bandwidth usage)
offsite/xopr/whatever/topic/he/pleases(details might be negotiated for ease of use)
allow_anonymous false password_file /etc/mosquitto/passwd acl_file /etc/mosquitto/acls listener 1883 protocol mqtt listener 8883 protocol mqtt cafile /etc/mosquitto/ca_certificates/ca.crt certfile /etc/mosquitto/certs/server.crt keyfile /etc/mosquitto/certs/server.key listener 443 protocol websockets cafile /etc/mosquitto/ca_certificates/ca.crt certfile /etc/mosquitto/certs/server.crt keyfile /etc/mosquitto/certs/server.key
user spacestate topic write ackspace/+/spacestate/# user temperature topic write ackspace/+/temperature/# topic write +/+/barbecue/# user hackspace topic write ackspace/hackspace/# topic deny ackspace/+/spacestate/# user slackspace topic write ackspace/slackspace/# topic deny ackspace/+/spacestate/# user stackspace topic write ackspace/stackspace/# topic deny ackspace/+/spacestate/# user myservice topic write services/category/myservice/# user ackspace topic read #
Passwords are generated with:
sudo mosquitto_passwd /etc/mosquitto/passwd [user]
- add MOAR sensors (upgrade the current temperature sensors)
- MOAR sonoffs