Energy & IoT monitoring
Energy monitoring and IoT telemetry software
Every inverter manufacturer ships a portal, and none of them shows you your whole site. The moment you have two brands, a meter and a battery, monitoring becomes an integration problem rather than a hardware one. We ingest from whatever is installed, store it properly as time series, and put the number that drives a decision on the screen.
Where it usually breaks
Inverters, batteries and meters each produce data in their own format, and nobody can see load, generation and state of charge on one screen in time to act on it.
What we build instead
Telemetry ingestion from inverters and sensors, time-series storage, live dashboards and threshold alerting - including off-grid and time-of-use logic.
- Inverter and battery telemetry ingestion
- Live load, solar and grid dashboards
- Time-of-use and off-grid charging control
- Threshold alerting and historical trends
Load, generation and state of charge on one screen
Getting there means handling what generic software skips. These are the four that cost the most in this sector.
Every device speaks its own dialect
Modbus registers, vendor APIs, MQTT topics and CSV dumps all describing the same physical quantity in different units. Normalising at ingestion is what makes one dashboard possible at all.
Data that arrives late, twice, or not at all
Site connectivity drops. Ingestion has to tolerate gaps, out-of-order samples and duplicates without corrupting a daily total, because a total that is quietly wrong is worse than a gap.
Storage that gets expensive quietly
A reading every few seconds from every device is a lot of rows within a year. Downsampling and retention policies decided up front keep both the query times and the hosting bill sane.
Alerts nobody trusts any more
An alert that fires on every transient gets muted within a week, and then the real one is missed too. Thresholds need hysteresis and sensible grouping to stay worth reading.
What you end up with
- One live view across every inverter, meter and battery on site
- Normalised, downsampled history you can query quickly
- Alerting tuned to be worth reading rather than muted
- Time-of-use and off-grid logic applied automatically
- Reporting on consumption, generation and cost avoided
The disciplines this draws on
What this has changed in practice
A real outcome from this sector. We do not publish client names.
Inverters, solar and batteries reporting to one place
Home automation and IoT integration work across inverter systems, tracking solar generation and battery consumption. The hard part is rarely the dashboard; it is normalising what each device reports so that a single screen can be trusted.
Energy & IoT monitoring: common questions
Will this work with the equipment we already have installed?
In most cases. If a device exposes Modbus, an API, MQTT or even a scheduled file export, it can be ingested. We confirm exactly what your hardware exposes during discovery rather than promising support in advance.
Can it control equipment, or only monitor it?
Both are possible, but they are different risk categories and we treat them that way. Control paths get explicit authorisation, bounded ranges and a manual override, because software that can move a real contactor deserves more caution than a dashboard.
Tell us how your operation runs
Including the parts held together by a spreadsheet. You will get a straight answer on what is worth building and what is not.
A reply from a developer. Not a sales pipeline. The person who reads your message is the person who would do the work.
An honest answer on fit. If an off-the-shelf product solves your problem better than a custom build, we will tell you which one.
No obligation. A first conversation costs nothing and commits you to nothing. Discovery output is yours either way.