matterHub

(A)DSP: Lightweight matter Hub

Requirements

• PC with bluetooth hardware
• Wifi (which offers access to the internet)
• 2x ESP32
• At least 28GB of free storage space

Bonus:

• Breadboard, 330 Ohm resistor and an LED

Setup

Prepare the Operating System

Install Ubuntu 20.04 LTS. A minium install is enough, as all dependecies are specified. Before proceeding update all software (sudo apt update && sudo apt upgrade)

To install the required software run the following command:

sudo apt -y install git gcc g++ pkg-config libssl-dev libdbus-1-dev \
     libglib2.0-dev libavahi-client-dev ninja-build python3-venv python3-dev \
     python3-pip unzip libgirepository1.0-dev libcairo2-dev libreadline-dev expect

Choose a location and set the environment variable:

export MATTER_HUB_DIR="$HOME/matterHub/"

Clone this repository:

git clone https://github.com/OpenFogStack/matterHub.git ${MATTER_HUB_DIR}

Change into the repository:

cd ${MATTER_HUB_DIR}

Initialize the project and matter:

source ${MATTER_HUB_DIR}/scripts/activate.sh

This is expected to take some time.

Build the matter repo:

cd ${MATTER_HUB_DIR}/thirdparty/chip/repo/
gn gen out/host
ninja -C out/host

Configuration

Move to the demo directory: cd ${MATTER_HUB_DIR}/scripts/demo

Copy the example config file: cp config.example config

Edit the example config with your favorite text editor: vi config

Replace "YOUR MATTER HUB DIR" with the path to the matterHub dir. If you cloned into your home directory it should look like this:

set MATTER_HUB_DIR "~/matterHub"

Replace "YOUR CHIP-TOOL PATH" with the path to the chip tool. if you followed this guid so far your chip-tool should be here:

set CHIP_TOOL_PATH "~/matterHub/thirdparty/chip/repo/out/host/chip-tool"

Replace "SSID" and "YOUR PASSWORD" with your WiFi-SSID and your WiFi-password.

If you use the recommended setup (M5 Stack for the matterHub and an ESP32 for the lighting app) you can save and leave the file. Otherwise adjust the "M5_TTY" and "ESP32_TTY" entries accordingly.

Configure MQTT

Create HiveMQ Account and User

• Visit hiveMQ https://console.hivemq.cloud/
• Sign up for a new account
• Confirm your E-Mail
• Log in
• Enter further details
• Create a free cluster
• Choose a cloud
• Create a new user
  • Manage cluster
  • Access management
  • Enter username and password. For the rest of this demo we will assume the following:
    • Username: publicTest
    • Password: TODO:chooseABetterPassw0rd!
  • Click "add"

Download a mqtt client to send commands directly to the Matter Hub. We used the hiveMQ cli client But every other way to send mqtt messages to the topic should be fine.

Edit the matterHub configuration

Change into the source directory:

cd ${MATTER_HUB_DIR}/src/

Open menuconfig:

idf.py menuconfig

Select "MQTT Configuration"

Enter your HiveMQ credentials:

MQTT URI (you can find your under "overview"). It should look something like this:

mqtts://<some_prefix>.hivemq.cloud:8883 

Username and password are those you just chose.

Optional:

Consider setting you MatterHub ID Configuration, so you don't collide with other matterHubs under "MatterHUB ID Configuration".

Quit and save.

Build ESP32

Gain access to the serial ports:

sudo adduser $USER dialout

You probably need to reboot after this.

After the reboot run the activate script again (this might require setting the MATTER_HUB_DIR env variable again):

cd ${MATTER_HUB_DIR}
source scripts/activate.sh 

For the actual demo we provide a simple script:

cd ${MATTER_HUB_DIR}/scripts/demo/
./demo.sh

This should open three additional terminal windows:

• One used for commissioning the esp32 via the chip-tool
• One for flashing the lighting app on the esp32
• One for flashing the matterHub on the M5 stack

If everything works as designed you should see an MQTT_EVENT_CONNECTED on one of the shells and No erros in the chip-tool shell.

If not possible causes of error:

• The Wifi is not reachable (yes the wifi chip of the esp32 is quite bad and for reliable communication you need to be quite close)
• Wifi password/user name is not correct
• MQTT has not been configured successfully

If all of the previous steps failed you can try to debug the situation by manually commissioning the devices (however we highly discourage you from doing this. This is a way into insanity. Trust me.)

Manual Configuration (USE ONLY IF THE DEMO SCRIPT DID NOT WORK)

We strongly recommend against this! Please contact us instead so we can assist in debugging.

You again need three shells:

1. Setup:

     $matterhub:

   cd ${MATTER_HUB_DIR}/src

     $chip-tool:

   cd ${MATTER_HUB_DIR}/thirdparty/chip/repo/out/host

     $~/matterHub/thirdparty/chip/repo/examples/lighting-app/esp32

   cd ${MATTER_HUB_DIR}/thirdparty/chip/repo/examples/lighting-app/esp32

2. Cleanup:

   idf.py erase-flash -p "${PORT_TO_M5}"
   idf.py erase-flash -p "${PORT_TO_ESP32}"
   rm -rf /tmp/*.ini /tmp/chip_*

3. Setup hub

     $~/matterHub/src

   idf.py build
   idf.py flash monitor -p "${PORT_TO_M5}"

     $chip-tool:

   chip-tool pairing ble-wifi 111 "${SSID}" "${PASSWORD}" 20202021 3840

4. Setup end-device:

     $~/matterHub/thirdparty/chip/repo/examples/lighting-app/esp32

   idf.py build
   idf.py flash monitor -p "${PORT_TO_ESP32}"

     $chip-tool:

   chip-tool pairing ble-wifi 333 "${SSID}" "${PASSWORD}" 20202021 3840

5. Give hub permission to access the end-device:

   chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [111], "targets": null }]' 333 0

If you want to use multiple end-devices repeat steps 3 and 4, and replace 333 with a different number.

Sidenote: A lot of the configuration (Comissioning, WiFi credentials, etc is stored permanently. Should something go wrong consider erasing the flash of the esp32 (idf.py erase-flash) and cleanup the data stored by the chip-tool (rm -rf /tmp/.ini /tmp/chip_) The demo script will do this automatically.

Gratulations! You setup the ESP32 part.

Java Server

Requirements

• Java (jdk-17)

sudo apt install openjdk-17-jdk

• Maven (3.8.x)

Download the latest maven version from https://maven.apache.org/download.cgi

Extract the maven files:

sudo tar xf apache-maven-*.tar.gz -C /opt

Create a link:

sudo ln -s /opt/apache-maven-3.8.6 /opt/maven

Setup the environment variables in /etc/profile.d/maven.sh by adding the following:

export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64
export M2_HOME=/opt/maven
export MAVEN_HOME=/opt/maven
export PATH=${M2_HOME}/bin:${PATH} 

Make the script executable:

sudo chmod +x /etc/profile.d/maven.sh

Load the environment variables:

source /etc/profile.d/maven.sh

Verify the setup:

mvn -version

First steps

1. First of all, you need an active Subscription to the Bosch IoT Suite:

   • If requried register a new Bosch-ID
   • Click on "new Subscription" and select "Bosch IoT Device Management"
   • Choose the Plan you want (free plan is fine) and give your subscription an Instance Name
   • Click on "subscribe"

2. You have to configure a new OAuth2 Client:

   • Click on "New OAuth2 Client"
   • Write your Client Name
   • Select all Options on the Client Scopes
   • Select the "Owner" Option from the Organization Scopes
   • Click on "Create"

3. Update the application.properties. You will find the necessary credentials here:

   • On the OAuth2 Page click on Use and then on Spring.
   • Copy the application.properties Part from "Define the configuration properties in application.properties:"
   • Insert the copied application.properties in src/main/resources/application.properties (you can edit the file with VSCode).

4. Insert the HiveMQ Password in application.properties in src/main/resources/application.properties

   • Contact the HiveMQ Admin, if you need the password.

5. Create a Namespace.

   • Go to Subscriptions and choose "Go to Dashboard" and now choose "Things Dashboard".
   • Click on Namespace and "Create new namespace"
   • Choose a namespace name and click on "Comfort" and Create it.
   • Write the new created namespace in the "bosch-iot-suite.namespace"-field in application.properties in src/main/resources/application.properties

Start the server

Inside the server folder run mvn clean package and java -jar target/server-0.0.1-SNAPSHOT.jar

At this point you should have:

• Configured the ESP32 setup
• Been able to build the sources for the ESP32
• Start the demo
• Created and configured the hiveMQ Account
• Created and configured the Bosch IoT Account
• Been able to build and run the server

Congratulation, we can get started now.

Demo time

A simple Use-case

If not already happened: Build and start the server:

cd  ${MATTER_HUB_DIR}/server
mvn clean package
java -jar target/server-0.0.1-SNAPSHOT.jar

Start the demo:

cd ${MATTER_HUB_DIR}/scripts/demo/
./demo.sh

Discover commissioned device on the Matter Hub by typing the following into the shell: matter discover describe 1 333

Subscribe to an attribute (for example OnOff):

mqtt pub -s -h <prefix>.s1.eu.hivemq.cloud -p 8883 -u publicTest -pw TODO:chooseABetterPassw0rd! --topic spBv1.0/matterhub/DCMD/0/333 -m '{"timestamp": 1234,"metrics": [{"name": "1/6/subscribe/0","timestamp": 1234}],"seq": 0}'

Verify that the discover was successful via the IoT API:

Copy the Test Access Token

• Go to OAuth2 Clients
• Click on "Use" and copy the blue Test Access Token field.

Go to the Bosch IoT API and click on "Authorize" Now you can insert the Test Access Token and click on "Authorize".

Now you should be able to discover the newly created thing via get_things

• Click on "try it out"
• Enter the thingid: <namespace>:<matterhub id>_<node id>_<endpoint id> For example: namespace:0_333_1

It should look like this:

{
  "thingId": "namespace:0_333_1",
  "policyId": "namespace:0_333_1",
  "features": {
    "onoff": {
      "desiredProperties": {
        "OnOff": false,
        "GlobalSceneControl": false,
        "OnTime": 0,
        "StartUpOnOff": 0,
        "OffWaitTime": 0
      }
    }
  }
}

To change the thing you can send a put request

Reenter the thingid and a changed JSON representation of the thing:

{
  "thingId": "namespace:0_333_1",
  "policyId": "namespace:0_333_1",
  "features": {
    "onoff": {
      "desiredProperties": {
        "OnOff": true,
        "GlobalSceneControl": false,
        "OnTime": 0,
        "StartUpOnOff": 0,
        "OffWaitTime": 0
      }
    }
  }
}

Currently only "OnOff" is supported.

Now the light should be turned on!

To verify the other direction you can either use a button to turn on the LED (see advanced use-case below) or use the MQTT Client

Toggle the light via MQTT:

mqtt pub -s -h b9fbe0bc6f56486fab5642f0b79f127e.s1.eu.hivemq.cloud -p 8883 -u publicTest -pw TODO:chooseABetterPassw0rd! --topic spBv1.0/matterhub/DCMD/0/333 -m '{"timestamp": 1234,"metrics": [{"name": "1/6/cmd/2","timestamp": 1234}],"seq": 0}'

Turn the light off:

mqtt pub -s -h b9fbe0bc6f56486fab5642f0b79f127e.s1.eu.hivemq.cloud -p 8883 -u publicTest -pw TODO:chooseABetterPassw0rd! --topic spBv1.0/matterhub/DCMD/0/333 -m '{"timestamp": 1234,"metrics": [{"name": "1/6/cmd/0","timestamp": 1234}],"seq": 0}'

Turn the light on:

mqtt pub -s -h b9fbe0bc6f56486fab5642f0b79f127e.s1.eu.hivemq.cloud -p 8883 -u publicTest -pw TODO:chooseABetterPassw0rd! --topic spBv1.0/matterhub/DCMD/0/333 -m '{"timestamp": 1234,"metrics": [{"name": "1/6/cmd/1","timestamp": 1234}],"seq": 0}'

An advanced use-case

Bonus: Button and LED

For the hardware part follow this guide: https://medium.com/@madeadhika39/turn-on-led-on-esp32-with-push-button-8c8ee1b3652f

We used the default of GPIO 5 for the LED. We used GPIO 18 for the button so change the following line in:

$MATTER_HUB_DIR/thirdparty/chip/repo/examples/lighting-app/esp32/main/Button.cpp:
-#define GPIO_INPUT_IO_0 9
+#define GPIO_INPUT_IO_0 18

Follow the same steps as in the easy use-case.

Now you can add another device.

Open a new terminal and move to the lighting example dir:

cd ${MATTER_HUB_DIR}/thirdparty/chip/repo/examples/lighting-app/esp32

cleanup the ESP (the port is probably /dev/ttyUSB1):

idf.py erase-flash -p "${PORT_TO_ESP32_2}"

Setup end-device:

  $~/matterHub/thirdparty/chip/repo/examples/lighting-app/esp32

idf.py build
idf.py flash monitor -p "${PORT_TO_ESP32_2}"

Use the chip-tool (you can find one in the matter repository $MATTER_HUB_DIR/thirdparty/chip/repo/out/host/chip-tool) to commission the device

chip-tool pairing ble-wifi 444 "${SSID}" "${PASSWORD}" 20202021 3840

Give hub permission to access the end-device:

    chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [111], "targets": null }]' 444 0

Again discover commissioned device on the Matter Hub matter discover describe 1 444

Subscribe to an attribute (for example OnOff):

mqtt pub -s -h <prefix>.s1.eu.hivemq.cloud -p 8883 -u publicTest -pw TODO:chooseABetterPassw0rd! --topic spBv1.0/matterhub/DCMD/0/444 -m '{"timestamp": 1234,"metrics": [{"name": "1/6/subscribe/0","timestamp": 1234}],"seq": 0}'

Now you can interact with it in the same way as with 333!

FAQ

Connection timeout, Can not establish connection: In our experience the WiFi module in the ESP32 is quite bad. So you should test as close to the WiFi-Hotspot as possbile (using the PC as a hotspot worked quite well too)

idf.py: command not found

cd ${MATTER_HUB_DIR}
source scripts/activate.sh

If you want to repeat the demo, you have to remove the things and policies for the things you created!

You can leave the monitor with ctrl + altgr + 0 or ctrl + [.

Known bugs

There is a bug which throws an Exception every time a topic is published (org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)). It seems like this Exception has no impact on the correct server functionality. See eclipse-paho/paho.mqtt.android#209

Resources

https://phoenixnap.com/kb/install-maven-on-ubuntu

References

This tutorial on how to use idf.py