Sensors
A platform should support the device that fits.
HotDrop, VoltDrop, DIY hardware, standard LoRaWAN devices, and Bricksoft Scout can all have a place. We evaluate measurement, installation, radio, lifecycle, and data needs before choosing.
Mixed fleets are normal
Interoperability is an operating requirement.
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 |
|---|---|---|
| Bricksoft Scout | Purpose-built submetering with Bricksoft deployment features | Measurement, commissioning, radio plan, integration, lifecycle |
| 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 |
| DIY / custom | Special measurements or workflows not served by catalog hardware | Certification, enclosure, power, validation, maintainability |
| Other LoRaWAN | Open-market sensors suited to the physical and operational need | Payload contract, regional plan, provisioning, failure modes |
| Wi-Fi Scout | Lower-entry-cost sites with suitable Wi-Fi and no gateway need | Coverage, credentials, network policy, power, service path |
Custom when justified
30–60 day targets, after the problem is understood.
Scout’s common CPU foundation and an FCC pre-certified Wi-Fi module can shorten the path to custom sensing or features. The target is not a blanket promise: scope, enclosure, power, validation, certification, and supply constraints still have to be evaluated.
Coming-soon concept placeholder
Start here
Tell us the measurement and the field conditions.
The device recommendation comes after that.