| Organisation | Slug | Provider Code | Plan | Users | Properties | Sensors | Status | Actions |
|---|
| Name | Role | Tenant | Confirmed | Created | Actions |
|---|
| Organisation | Current Code | Requested By | Reason | Status | Date | Actions |
|---|
| Time | Action | User | Entity | Details | IP |
|---|
Sender Configuration
Set the "From" address for all outgoing emails. Must be a verified sender signature in your Postmark account.
Display Name <email@domain.com> — Leave empty to use the default Postmark sender address.
Notification Recipients
These email addresses receive new user registration alerts, email confirmations, and damp & mould reports.
Alert Recipients (High Risk)
These email addresses receive urgent alerts for high-risk mould readings from IoT sensors (Awaab's Law compliance).
Send Test Email
Verify your email configuration by sending a test message.
Email Templates
Manage the content and layout of all outgoing emails. Use {{mergeTag}} syntax for dynamic content.
Revenue by Client
| Client | Plan | Status | Monthly Rate | Total Paid | Last Payment | Next Payment |
|---|
Upcoming Payments
Recent Invoices
| Key | Label | Category | Has Value | Actions |
|---|
Configure the platform-level MQTT broker that all tenant gateways connect to. Tenant admins simply register gateways — they automatically use these settings.
IoT Sensor Monitoring System
Complete guide to the gateway, sensor, and MQTT architecture
System Overview
MyHome Passport uses a Zigbee-based sensor network to monitor environmental conditions in social housing properties. The system automatically tracks temperature, humidity, air quality, and mould risk — enabling early intervention and Awaab's Law compliance.
The architecture has three layers: sensors (battery-powered Zigbee devices in each room), gateways (SLZB-06M devices that bridge Zigbee to WiFi), and the platform MQTT broker (cloud service that receives all data). All configuration is centralised — you set up the MQTT broker once, and every gateway automatically connects to it.
System Architecture & Data Flow
┌─────────────────────────────────────────────────────────┐
│ PROPERTY (per home) │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Frient │ │ Frient │ │ Frient │ Zigbee 3.0 │
│ │ Sensor │ │ Sensor │ │ Sensor │ (battery) │
│ │ (Bedroom)│ │ (Living) │ │ (Kitchen)│ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │
│ └──────────────┼──────────────┘ │
│ │ Zigbee mesh │
│ ┌─────┴─────┐ │
│ │ SLZB-06M │ WiFi + Zigbee │
│ │ Gateway │ coordinator │
│ └─────┬─────┘ │
│ │ WiFi (property network) │
└──────────────────────┼──────────────────────────────────┘
│
│ MQTT protocol
▼
┌────────────────┐
│ MQTT Broker │ Cloud service
│ (HiveMQ / │ (configured in
│ Mosquitto) │ MQTT / IoT page)
└───────┬────────┘
│
▼
┌────────────────┐
│ MyHome │ This platform
│ Passport │ (auto-subscribes
│ Server │ to broker)
└───────┬────────┘
│
┌──────────┼──────────┐
▼ ▼ ▼
┌──────────┐ ┌────────┐ ┌───────────┐
│ Tenant │ │ Admin │ │ Compliance│
│ App │ │ Portal │ │ Alerts │
│ Dashboard│ │ Reports│ │ (Awaab's) │
└──────────┘ └────────┘ └───────────┘
Hardware Components
SLZB-06M Gateway
- SMLIGHT SLZB-06M (or P7 variant)
- Zigbee 3.0 coordinator + WiFi + Ethernet
- Runs Zigbee2MQTT firmware
- Powered by USB-C
- Built-in web interface at 192.168.1.1
- Creates WiFi hotspot for initial setup
- One gateway per property
- ~£28 per unit
Frient Sensors
- Frient Temperature & Humidity Sensor
- Frient Air Quality Sensor (VOC)
- Zigbee 3.0 — pairs directly to gateway
- Battery-powered (CR2032, ~2 year life)
- Compact, wall-mountable design
- High accuracy (±0.3°C, ±3% RH)
- Auto-discovered by the platform
- ~£25-35 per sensor
MQTT Broker Setup
MQTT is the messaging protocol that connects gateways to the platform. You need one MQTT broker for the entire platform — all tenant gateways connect to it. Think of it as the central postbox that all sensor data flows through.
Recommended MQTT Brokers
Free tier: 100 connections. Best for getting started. hivemq.com/mqtt-cloud-broker
Serverless option available. Good for scaling. emqx.com/en/cloud
Open source, full control. Requires a server. mosquitto.org
Configuration Steps
- Sign up for an MQTT broker service (or install Mosquitto on your own server)
- Create credentials (username & password) for the MyHome Passport platform
- Note the broker URL (e.g.,
mqtts://broker.hivemq.com:8883) - Go to MQTT / IoT in this admin panel
- Enter the broker URL, username, and password
- Set the default topic to
zigbee2mqtt/# - Click "Test Connection" to verify it works
- Click "Save Settings"
Gateway Provisioning (Installer Workflow)
Installers set up gateways using the tenant mobile app. The app includes a step-by-step wizard that guides them through the entire process. Here's what happens:
Power On
Plug in SLZB-06M via USB-C
Connect WiFi
Join "SLZB-06" hotspot
Configure
Set WiFi + MQTT at 192.168.1.1
Register
Name & link to property in app
Done
Gateway online, sensors auto-discover
Sensor Auto-Discovery
Once a gateway is online and connected to the MQTT broker, sensors are discovered automatically. Here's how it works:
- Pair the sensor — Put the Frient sensor in pairing mode (hold button 10s until LED flashes). The SLZB-06M will find it via Zigbee.
- Sensor sends data — The sensor starts reporting temperature, humidity, etc. to the gateway via Zigbee.
- Gateway publishes to MQTT — The SLZB-06M running Zigbee2MQTT publishes the data to the MQTT broker.
- Platform receives data — The MyHome Passport server is subscribed to the broker. It receives the MQTT messages automatically.
- Auto-creates sensor record — If the sensor is new (unknown device ID), the platform creates a new sensor record and assigns it to the property's default room.
- Data appears in dashboards — Temperature, humidity, and air quality readings immediately show in the tenant app and admin portal.
What Happens With the Data
Tenants see live readings (temp, humidity, air quality) grouped by room in their app.
High humidity or temperature triggers alerts. Dew point is calculated automatically.
Mould risk levels (LOW/MEDIUM/HIGH) set legal deadlines. HIGH risk triggers email alerts to admin.
All readings stored for trend analysis. Admin portal has property-level and room-level history views.
Admin Gateway Management
Client administrators (housing providers) can manage gateways from the Admin Portal → Sensors → Gateways page. They can:
- Register new gateways — Select a property from the dropdown, name the gateway. MQTT config is automatic.
- View gateway status — Online (green), Pending (orange), Offline (red), Error (red).
- See connected sensors — Each gateway shows how many sensors are paired to it.
- Regenerate API keys — For HTTP-mode gateways (not needed for MQTT gateways).
- Delete gateways — Removes the gateway record (sensors are preserved).
Troubleshooting FAQ
Check the gateway has WiFi connectivity (can you access 192.168.1.1 from its network?). Verify the MQTT broker URL and credentials in the gateway's web interface match what's configured in MQTT / IoT settings. Try "Test Connection" in the MQTT settings page.
Ensure the sensor is actually paired to the gateway (check the SLZB-06M's Zigbee2MQTT web interface for paired devices). Confirm the MQTT topic pattern matches (default: zigbee2mqtt/#). Wait up to 5 minutes for the first reading to arrive.
Double-check the broker URL format (should start with mqtt:// or mqtts://). Verify the username and password. Ensure the broker service is running and accessible from the internet. Check if the broker requires TLS (use mqtts:// for port 8883).
This means the gateway was registered in the platform but hasn't connected to the MQTT broker yet. The gateway needs to send its first message. Check that the SLZB-06M is configured with the correct MQTT broker settings and is connected to WiFi.
Auto-discovered sensors are assigned to the first room in the property by default. Administrators can reassign sensors to the correct room from the Admin Portal sensor management page.
No. One MQTT broker serves the entire platform. Each gateway is linked to a specific property, so data is automatically routed to the correct tenant and property. The platform handles multi-tenancy at the application level.
| Tenant | Plan | Users | Active (7d) | Active % | Logins | Avg/User | Reports | Tasks % |
|---|