We have begun an initiative to simplify the management of i3's space and infrastructure. The first step is bringing as much of the shut down procedure into a single button as possible. As it evolves things like networked thermostats that behave how we want, building out the new half of the space without having to wire lightswitches everywhere, putting the EV charger on the network for logging, and implementing SpaceAPI or SpaceDirectory all become possible (maybe even a version of RFID entry system). This page is made up of content moved from the #home-automation channel in slack.

IoT kiosk screen w/ partial shutdown list

Firmware explanation

Most of the devices we have installed run a version of Tasmota that has been either had the settings tweaked before uploading or had a pin map added to the available options. Remember to bounce the power between flashing over serial and the first OTA attempt. Some of them are our own code creation using a template written by Mark Furland and mimic the MQTT format of the Tasmota devices for consistency. The repository is here: [1]

List of Equipment

to get the IP address of each device, run this command

sudo nmap -sP 10.13.0.0-255 | grep -v "Host" | tail -n +3 | tr '\n' ' ' | sed 's|Nmap|\nNmap|g' | grep "MAC Address" | perl -pe 's/.*report for (?:([^ ]*) \()?((?:[0-9]{1,3}\.?){4})\)? MAC Address: ([A-Z0-9:]*).*/$1 $2 $3/'

Has individual page

Needs page written

• laser cutters (POW)
• bumblebee status lights 10.13.107.90
• bumblebee timer 10.13.107.81
• bumblebee chiller 10.13.107.114
• wolverine status lights 10.13.107.246
• wolverine timer 10.13.107.85
• wolverine chiller 10.13.107.231
• laser blast gate monitor 10.13.107.203
• front door funnel 10.13.107.37
• hallway light switches 10.13.107.167, 10.13.107.174
• large bathroom vent fan 10.13.107.116
• weld zone tank sensors 10.13.107.57
• small bathroom light switch 10.13.107.79

Add Equipment Link

Equipment Page Form

MQTT Hierarchy

The hierarchy of our MQTT layout is mostly physical by design. It should be possible to publish/subscribe to more and more general sections of messages if you want to monitor different areas or control them. The <type> section came from Tasmota, previously we had wanted to put that at the end instead of the beginning which may have some MQTT benefits.

Right now the hierarchy we aspire to is:

   <infoType>/<location>/<course-zone>/
                                       <zone>/<item>/<modifier>
                                       <itemType>/<itemSubType>/<modifier>

• <infoType> can be "cmnd", "tele", or "stat".
• <location> is just "i3" for now but could encompass remote locations like people's houses or other hackerspaces.
• <course-zone> is the coarse delineation of location, outside, inside, openhab
• <zone> is the fine delineation of location, and could refer to areas that are physically important but not a zone as defined by i3's structure.
• <item> is the name of one device that is being controlled, this should not be the same across two different pieces of hardware to avoid collisions.
• <itemType> is type of item, like lights
• <itemSubType> is the subtype of a type, like for lighs, emergency-lights, or for fans, ceiling-fans.
• <modifier> is the command given, or the status being reported (examples include POWER, STATE, RESULT, display, delay).

MQTT Debugging Notes

• To view the MQTT log, use mosquitto_sub -v -t "#" on Mcclellan or mosquitto_sub -h 10.13.0.22 -v -t '#' remotely.
  • The lines of form "tele/i3/inside/lights/015/STATE {"Time":...." are regular status pulls against the MQTT members, not command records.
• MQTT log with timestamps: mosquitto_sub -v -t '#' | xargs -d$'\n' -L1 bash -c 'date "+%Y-%m-%d %T.%3N $0"'

Automation Software

HomeAssistant

Main Page:HomeAssistant

Home Assistant is a home automation hub for connecting many IoT devices together into one system controlled by a web GUI.

OpenHAB (out of date)

Main Page:OpenHab

We are no longer using OpenHAB, we have moved to HomeAssistant

OpenHab2 is a centralized method to manage multiple IoT devices from a Web GUI.

ToDo

Please contact Evan Allen or Mark Furland for details on any of these

All issues tracked here: https://github.com/i3detroit/custom-mqtt-programs/issues Moving to that in progress

Write up, not hardware

• clean up wiki articles on all the things

Network in general

• Expand iot subnet, need to decide on new IP scheme. 10.13.107.0/24 is current IOT, 10.13.0.0/24 is current user. 107 is vlan id.
• Static leases for IoT items so the IP addresses can be filled out in the wiki
• Configure the router so the map pi can talk to the main network from the iot network

Misc.

Dash buttons 24-28 are set up but don't have things attached yet.

HomeAsistant

https://github.com/i3detroit/homeassistant-config/issues