Sensors
HotDrop, VoltDrop, DIY hardware, standard LoRaWAN devices, and custom sensors can all have a place. We evaluate measurement, installation, radio, lifecycle, and data needs before choosing.
Mixed fleets are normal
The data model, device identity, decoder lifecycle, health signals, and replacement plan matter as much as the radio logo on the box.
| Device path | Where it may fit | What we verify |
|---|---|---|
| HotDrop | Existing or new non-invasive electrical monitoring deployments | Availability, data path, installation, platform contract |
| VoltDrop | Electrical monitoring where the device meets the deployment requirements | Measurement fit, decoder, radio behavior, security, supportability |
| Custom development | Measurements or workflows not served by suitable catalog hardware | Feasibility, electronics, firmware, enclosure, power, certification, validation, maintainability |
| Other LoRaWAN | Open-market sensors suited to the physical and operational need | Payload contract, regional plan, provisioning, failure modes |
Custom when justified
Bricksoft can design new sensor hardware, adapt an existing design, develop embedded firmware, define payloads, and integrate devices with Spark or another accessible customer system.
We begin with a bounded feasibility and requirements pass. Measurement accuracy, enclosure, power, radio behavior, security, certification, components, manufacturing, installation, updates, and long-term service all affect the right path.
A practical development path
Start with the measurement, field conditions, and integration contract. Then use a prototype or pilot to validate the hardware and firmware before planning production.
Discuss a sensor needStart here
The device recommendation comes after that.