b2b.iot — IoT Developer Portal

Platform Hierarchy

WHERE b2b.iot SITS

b2b.iot is a vertical within the 2nth ecosystem — the AI-native engineering platform. It inherits the same authentication, design system, and partner principles, but operates at a dedicated tier for IoT build partners.

2nth.ai

Platform & Auth Provider

OAuth, identity, billing, token economy

b2b.iot

IoT Developer Portal

Architecture, firmware, hardware — partner tier

Same principles, own tier. You sign in with a 2nth account. Your email must be on the partner whitelist. Technical docs require a signed NDA. No investor access, no platform admin — just the IoT blueprints.

The Problem

IoT IS A MESS OF REINVENTION

Every integrator starts from scratch. Every project re-solves the same problems — sensor wiring, firmware, MQTT schemas, dashboard layout, OTA updates. The result is fragile, inconsistent, and expensive.

60+

Hours reinvented per project

Custom firmware, manual HA config, bespoke wiring. Every time.

0

Standardised reference designs

No off-the-shelf blueprints for HA + ESP32 that an integrator can just adapt and deploy.

C++

Skill barrier too high

Custom firmware demands embedded C expertise. Most integrators don't have it — and don't need it.

The Model

BLUEPRINTS, NOT PRODUCTS

We design the system once. Partners deploy it many times. Each deployment is customised to the client — but built on a shared, tested foundation.

2nth Designs

Architecture Documentation

System design, MQTT conventions, HA auto-discovery specs, concept explainers for your technical team

ESPHome Firmware Templates

YAML configs per node type — climate, presence, control, combo. OTA & auto-discovery built in

Hardware BOMs & Schematics

Tested component lists, wiring diagrams, GPIO mappings, enclosure recommendations

Home Assistant Templates

Dashboard layouts, automation blueprints, MQTT broker config, multi-room presets

Deployment Playbooks

Step-by-step checklists for site survey, install, handover, and ongoing support

Partner Builds

1

Site Survey

Walk the property, test Wi-Fi coverage, identify zones, count nodes, scope client needs

2

Source & Assemble

Procure components from BOM, wire sensors to ESP32 per schematics, test on bench

3

Flash & Configure

Adapt ESPHome YAML templates, flash firmware via USB, set up Home Assistant with Mosquitto

4

Customise Automations

Build client-specific rules: motion triggers lights, temp controls HVAC, door alerts at night

5

Install & Handover

Mount nodes, connect power, verify auto-discovery, train client, hand over documentation

6

Support & Expand

OTA firmware updates, add new rooms, troubleshoot connectivity, grow the install over time

The Stack

FOUR LAYERS, ZERO CLOUD DEPENDENCY

Everything runs on the local network. No subscriptions, no vendor lock-in, no data leaving the building. Each layer is independent — change one without touching the others.

All open-source. ESP32 hardware is commodity. Home Assistant has 2,000+ integrations. MQTT is the industry standard for IoT messaging.

4

UI

HOME ASSISTANT DASHBOARD

Lovelace dashboards + HA Companion app (iOS & Android). Per-room views, real-time sensor data, tap-to-control switches.

Partner customises layout, themes, and card types per client.

3

Logic

AUTOMATION ENGINE

Home Assistant automations, scenes, scripts, and schedules. "If motion detected AND after sunset, turn on hallway lights at 40%."

No code. Visual editor or YAML. Runs on the HA server, not on the ESP32.

2

Bus

MQTT MESSAGE BUS

Mosquitto MQTT broker. All devices publish sensor data and subscribe to commands. Lightweight publish/subscribe — runs on kilobytes of RAM.

HA auto-discovery: nodes announce themselves, HA creates entities automatically.

1

Edge

ESP32 EDGE DEVICES

ESP32-WROOM microcontrollers with sensors and actuators. One node per room or zone. Wi-Fi connected, ESPHome firmware.

Nodes: climate (DHT22), presence (PIR/mmWave), control (relay), combo (all-in-one).

Why ESPHome Over Custom Firmware

Time to first node

Hours, not days

Partner skill bar

YAML, not embedded C++

HA integration

Auto-discovery built in

OTA updates

One click from HA dashboard

Maintenance

Community-maintained drivers

Customisation

Lambdas for edge cases

Reference Install

TYPICAL RESIDENTIAL DEPLOYMENT

Five zones, five ESP32 nodes, one Raspberry Pi running Home Assistant. All on the local network. Full-page detail available to signed partners.

Zone	Node Type	Sensors	Actuators
Living Room	Combo	Temp/humidity, presence (mmWave)	2-channel relay (lights, fan)
Kitchen	Climate + Safety	Temp/humidity, gas/smoke	1-channel relay (extractor)
Bedroom	Comfort	Temp/humidity, motion (PIR)	LED strip (MOSFET PWM)
Entrance	Security	Motion (PIR), door (reed switch)	Relay (porch light), buzzer
Garage	Utility	Temp/humidity, car (ultrasonic)	2-channel relay (door, light)

5

ESP32 Nodes

One per zone

1

Raspberry Pi

HA + Mosquitto

0

Cloud Dependencies

100% local network

Access Model

THREE LAYERS OF ACCESS

Public overview (this page). Authenticated partner portal. NDA-signed technical documentation. Each layer requires the one before it.

Public

THIS PAGE

Overview, stack explanation, partner model, reference install. No sign-in required.

Requirement: None

Authenticated

PARTNER PORTAL

Dashboard, getting started checklist, quick links to all documentation sections.

Requirement: 2nth account + partner whitelist

NDA Required

TECHNICAL DOCS

Architecture deep-dives, firmware YAML templates, hardware BOMs, wiring schematics, deployment guides.

Requirement: Signed + partner + account

Partner Skill Requirements

Basic electronics

Soldering, multimeter, reading schematics

YAML

ESPHome and Home Assistant configs

Networking

Wi-Fi, DHCP, basic troubleshooting

Linux basics

Helpful for HA server management

Not required: Embedded C/C++, custom PCB design, mobile app development

Partner Sign In →

Not a partner yet? Get in touch

BUILD IoT.DON'T REINVENT IT.