Everything you need to deploy smart building applications
Connected device designed for building equipment networks
- Collect data and send commands.
- Universalize the various BMS field communication protocols into one embedded API.
- Connect automatically to Wattsense cloud platform through 4G or ethernet.
- A white-label product so you can promote your own brand.
- Host plug-ins, edge computing capability for low-latency and fail-safe features.
The building has a BMS?
The Box connects to the primary bus of the BMS as a third party.
There is no BMS?
A BMS network can be created from the Box.
Supported communication protocols
- LoRa (under development)
- We are at the very beginning... many more to come (KNX, M-Bus, WM-Bus, etc...)
- CPU: 528MHz ARM Cortex A7
- Memory: 256MB DDR3 SDRAM
- Storage: 256MB NAND Flash
- 9V-30V AC/DC power input
- Consumption: 5W
- Industrial-grade temperature range
- Size: 160 x 110 x 55 mm
- Weight: 300g
- 2 x Ethernet
- 2 x serial RS485
- 1 x serial RS232
- 2G/4G global coverage
- LoRa and WM-Bus gateway
- Bluetooth 4.0
- 2 x USB
- Pulse counter
- Secure Linux Yocto distribution
- Integrated drivers for all buses, protocols and building equipment
- Equipment discovery over BACnet and LonTalk
- Complete remote and automated configuration
- Secure server communication over WebSocket
- Secure automatic software updates
APIfication of building management systems. Abstracts away the chaotic BMS network technologies.
Web service to deploy smart building apps
- Connect and manage your fleet of Boxes.
- Configure field networks remotely. No need to call for an automation engineer.
- Collect data and control building equipment.
4G communication included in our cloud subscription.
A RESTful interface which connects your app
- Access your database.
- Send commands.
- Configure network and variables.
- Manage events (under development).
- Manage your Wattsense services.
- Get manual access to the API functionalities.
Wattsense cloud service is an abstraction layer which relieves smart building developers from a series of contingencies, boosting their productivity and streamlining the design of their apps.
Reaching the Boxes is abstracted away. The service is always on to receive the notifications from the Boxes, even if the app itself is not. It relieves the apps from timeouts and retries policies which are required when trying to establish a direct connection to a Box.
The Boxes will evolve (they have to), which will lead to multi-version support challenge. The cloud service abstracts away the diversity to present a unified vision of the Boxes, irrespective of their original version.
The cloud service monitors the health of the network of Boxes, and provides programmatic options to notify relevant parties. Those statistics are compiled and made available to a sysadmin audience on the side of the apps.
Event-driven data layer
The stream of events/notifications produced by the Boxes is typically not suitable to be consumed as such. The cloud service provides a consolidation of those data into an event store, which ensures reliable access to historical data, as well as querying capabilities (per Box, building, time interval, etc.).
Proactive maintenance of the IoT fleet driven by the cloud service to safeguard the Boxes from being turned into a botnet.