Zigbee’s advantage is the mesh. Where a long-range network puts one sparse node at the end of a very long link, a Zigbee network puts many nodes close together and lets them relay for each other — so coverage comes from density rather than from transmit power.
Ambimat has used Zigbee to design and develop both smart-home solutions and security solutions for city-wide infrastructure. The engineering is the same in both: get the radio and the power budget right on a node that has to be cheap and small, then make a network of them behave predictably when devices are added, moved, replaced or lost.
Where a mesh fits
- Buildings and homes, where nodes are many, close together and mains-adjacent
- Lighting and control networks that must keep working when one node drops
- Distributed sensing inside a site, rather than across a city
- Deployments that grow over time, where new nodes join an existing network
- Products where a phone or hub is the user’s way in, but the devices talk to each other
The distinction from Ambimat’s LoRa and Sigfox work is worth being explicit about: LPWAN is for sparse nodes at long range with small, infrequent messages; a mesh is for many nodes at short range that can relay. They are not alternatives to each other so much as answers to different questions, and some deployments carry both.
Ambimat engineering capability
On a mesh product the hardware work is module or SoC integration, antenna and layout, and a power design that reflects whether the node routes for its neighbours or only sleeps and reports — a router and an end device have very different budgets. The firmware work is the application on top of the stack, the behaviour during commissioning, and how the device recovers when it loses its parent or the coordinator restarts.
The parts that decide whether a deployment succeeds are usually not the radio at all: how a device is commissioned in the field by someone who is not an engineer, how a gateway bridges the mesh to whatever back-end the customer runs, and what happens on the hundredth install rather than the first. Ambimat’s scope typically runs from architecture through firmware to board bring-up and manufacture.
Mesh architecture considerations
A mesh trades a single point of failure for a set of harder questions. Route healing keeps the network alive when a node dies, but it also means traffic paths change under you, so latency is a distribution rather than a number. Battery-powered end devices cannot route, which makes the placement of mains-powered routers a design decision rather than an installation detail. And a network that any device can join is a network any device can join — which is why commissioning is where mesh security actually lives.
Security as part of product engineering
In a smart-city or building deployment with thousands of devices, the mesh is the backbone, and weaknesses in commissioning and key handling scale with it. Ambimat has published a framework for this in Mesh network security hardening for IoT (Zigbee & BLE), and applied the same thinking at system level in Holistic IoT security architecture for smart city street light controllers and Zero-trust IoT security for smart cities.
Where a deployment needs keys held in tamper-resistant hardware rather than in firmware, that is AmbiSecure‘s territory.
Related Ambimat experience
- Smart home development — where much of this mesh work has been applied
- Design by Technology — the wider connectivity range
- AmbiIoT — IoT and embedded product design and development