IoT / Sensorik
From the sensor bolted to the wall to the dashboard open in the browser — LoRaWAN networks, MQTT pipelines, and cloud backends that turn raw field data into decisions.
From sensor to dashboard.
Six capabilities, one stack. From the gateway on the roof to the Grafana board your operations team opens every morning.
LoRaWAN Networks
End-to-end LoRaWAN deployments — gateway placement, frequency planning, and network server config on TTN or a self-hosted private instance. Long range, low power, real-world tested.
MQTT Messaging
Broker setup (Mosquitto, EMQX), topic taxonomy design, QoS tuning, and TLS auth. Bridge field devices to cloud consumers without losing a single measurement.
Data Platform
Time-series storage in InfluxDB, visual wiring in n8n, and Grafana dashboards that non-engineers can actually read. All on EU-resident infrastructure, all under your control.
Sensor Hardware
Sensor selection, mounting, and commissioning — temperature, humidity, CO₂, door contacts, fill levels, vibration. We spec hardware that survives the environment it's deployed in.
Alerting & Monitoring
Threshold alerts via email, webhook, or PagerDuty. Watchdog logic for stale sensors and gateway uptime. If something stops reporting, you know before it becomes a problem.
System Integration
REST and webhook bridges into your existing IT landscape — ERP, BMS, ticketing systems. Sensor data doesn't have to live in a silo.
# IoT / Sensorik — layer418 stack [radio] protocol = "LoRaWAN 1.0.x / 1.1" network = "TTN v3 · self-hosted ChirpStack" gateways = "Dragino · RAK Wireless · Kerlink" sensors = "Dragino · Milesight · Elsys · custom" [messaging] broker = "Mosquitto · EMQX" protocol = "MQTT 3.1.1 / 5.0" security = "TLS 1.3 · certificate auth" [data] store = "InfluxDB 2.x" pipeline = "Node-RED" dashboards = "Grafana OSS" alerting = "Grafana Alerting · PagerDuty webhook" [infra] hosting = "EU-resident VPS (Hetzner / OVH)" iac = "Terraform · Ansible" monitoring = "Prometheus · Grafana"
Things people ask.
Do you supply the sensors and gateways, or do we source them ourselves?
Either works. We can spec, order, and configure all hardware, or work with kit you already have or prefer. We'll tell you upfront if a specific sensor is going to cause pain.
We already use The Things Network — can you build on top of that?
Yes, TTN v3 is our baseline. We connect your existing application or migrate you to a cleaner setup — webhook integration, MQTT bridge, or full stack replacement. No lock-in either way.
What's the typical range for a LoRaWAN deployment?
In open terrain, a single gateway reaches 5–15 km. In urban or industrial environments with obstructions, expect 1–3 km per gateway. We do a site survey before committing to a gateway count.
Can sensor data integrate with our existing ERP or building management system?
Yes — via REST APIs, webhooks, or direct database writes depending on what your system exposes. We've bridged LoRaWAN data into SCADA, custom ERPs, and plain email-based workflows.
Do you do ongoing operation or just the initial deployment?
Both. We can hand off a fully documented system for your team to run, or stay on as operators — monitoring, firmware updates, gateway maintenance, and expanding coverage as you grow.
Got sensors to connect?
Tell us what you want to measure and where. We'll figure out the rest. hello@layer418.de