IoT device monitoring that notices when devices go quiet
A gateway loses power or a SIM runs out of data and devices simply stop reporting, and silence looks exactly like everything being fine. We build a workflow that checks each device and gateway against its expected reporting interval, separates a gateway or site outage from a single failed device, opens a ticket with the last readings and, if you want, tells the customer. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why offline IoT devices go unnoticed
Most IoT platforms alert on readings, not on missing readings. A device that stops sending data raises no threshold alarm, so it can be offline for days before a customer asks why their dashboard is blank.
When it is noticed, the next question is whether it is one sensor, one gateway or a whole site. Answering that by hand, across many customers and connectivity types, takes the time nobody has.
What we build
What our IoT device monitoring includes
Device inventory with intervals
Each device and gateway with its expected reporting interval, read from your platform or a maintained sheet.
Heartbeat checks
Scheduled checks that compare last-seen time with the expected interval plus a grace period.
Gateway and site grouping
Devices that go quiet together are grouped under their gateway or site as one incident.
Tickets with history
One ticket per incident with last readings, battery, signal and last-seen times.
Customer notices
Optional messages to the customer's contact when their site or devices go offline, in your wording.
Fleet health report
A weekly summary of offline incidents, repeat offenders and devices nearing end of battery.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Scheduled check
Every few minutes or hourly, last-seen times are read for every device and gateway.
-
02
Automated
Silence detected
Devices past their interval plus grace are flagged and grouped by gateway and site.
-
03
Automated
Ticket opened
A ticket opens with history, and the customer is notified if configured.
-
04
Ops team review
Support investigates
Support checks connectivity remotely, contacts the site or schedules a visit.
-
05
Engineer or ops lead decides
Site visits and credits
Truck rolls, replacements and service credits are decided by the ops lead.
How it behaves
How offline device monitoring behaves
What the customer sees
- A heads-up when their site goes offline, if you choose
- Faster fixes because support already knows
- Fewer blank dashboards
What support sees
- One ticket per gateway or site outage
- Last readings, battery and signal on each ticket
- A weekly fleet health report
What the automation does
- Checks last-seen times against expected intervals
- Groups silent devices by gateway and site
- Opens tickets and optional customer notices
Edge cases and fallbacks
- Device on a planned shutdown
- Marked as paused in the inventory and skipped.
- Reporting interval changed by firmware
- The inventory updates from the platform or the ticket asks a person to confirm.
- Platform API slow or down
- The check waits and retries rather than flagging every device offline.
- Device comes back before anyone acts
- The ticket closes with a log entry and the outage counts in the report.
Architecture
Offline device and gateway monitoring at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 The workflow reads last-seen times from the platform and expected intervals from the inventory.
- 2 Devices past their interval plus a grace period are flagged.
- 3 Silent devices are grouped under their gateway or site, and one ticket opens per incident.
- 4 Support investigates; customers are notified if you chose to, and the ops lead decides on visits.
Project planner
How the project runs, phase by phase.
Offline device & gateway monitoring project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Device types, intervals, gateways, platform data and how outages are found today.
-
02
Design
2 to 3 days
Grace periods, grouping rules, ticket format and customer wording.
-
03
Build
1 to 2 weeks
Inventory sync, heartbeat checks, grouping, tickets and the weekly report.
-
04
Shadow run
About 1 week
Incidents logged without tickets and compared with known outages.
-
05
Launch
1 to 2 days
Tickets switched on, customer notices once trusted.
-
06
Support
Ongoing
New device types, interval changes and report tweaks.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Intervals, grouping rules and wording.
$200 – $400
-
Build
Inventory sync, checks, grouping, tickets and report.
$500 – $1,300
-
Integrations
IoT platform, help desk and messaging.
$150 – $400
-
Testing and shadow run
Incidents compared with known outages.
$100 – $250
-
Launch and training
Switch-on and support team walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Assumes your platform exposes last-seen times through an API; building that layer first is scoped separately. Platform and n8n costs are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Help desk: Your help desk vendor's own plan.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: published security update period
The UK PSTI regime has required consumer connectable products, since 29 April 2024, to have no guessable default passwords, a way to report security issues and a published minimum security update period; the inventory tracks each model's end date.
Source: www.gov.ukEU: support period stated at purchase
Under the Cyber Resilience Act, manufacturers must determine a support period and state its end date at the time of purchase; main provisions apply from 11 December 2027.
Source: digital-strategy.ec.europa.euEU and UK: processors under contract
Device and site data tied to customers is processed under GDPR Article 28 contracts with the automation host.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Offline device & gateway monitoring questions, answered.
By comparing each device's last-seen time with its expected reporting interval plus a grace period, on a schedule. Devices that go quiet together are grouped under their gateway or site.
Yes. The Things Stack can forward uplinks to a webhook, so last-seen times are recorded as messages arrive, and the check runs against them.
Battery level, signal strength and error counts can be tracked alongside last-seen time, so the weekly report shows devices that are likely to fail soon.
Only if you want. Many companies start with internal tickets and add customer notices once the grace periods are tuned.
Yes, when the inventory knows which devices sit behind which gateway or at which site. Several devices going quiet together becomes one gateway or site incident.
Offline incidents, time from silence to ticket, incidents reported by customers first and repeat offenders.
Free 20-minute call
Want this for your iot & connected device?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for iot & connected devices
All servicesIoT CRM: trials, activations & fleet accounts
Link trial signups, device activations and fleet size to one CRM, flag accounts whose devices go live, automate follow-ups and keep every customer record tied to the devices they actually run.
From $1,000 · About 4 weeks Details
Sensor alerts to tickets & on-call SMS
Turn threshold breaches from your IoT platform or MQTT broker into one ticket per real problem, text the on-call technician from your rota, escalate if nobody acknowledges and log every step.
Scoped after a free call · About 6 to 9 weeks including a pilot Details
Cold-chain temperature excursion records
Detect temperature excursions from loggers and trailer sensors, alert the right people while there is still time to act, and assemble an excursion record with readings, actions and decisions for customers and auditors.
From $1,000 · About 4 to 5 weeks Details