Notehub events are pure JSON and can be filtered, transformed and routed to any third-party cloud application. Using one of our Route templates, or create fully customizable requests with common protocols.
Notecard has a mostly-offline data sync for low power and an always-online mode for low latency. The battery typically draws less than 8μA when idle.
Manage and monitor your fleets in real-time, configure shared settings at the device, project, and fleet levels, and flash Notecard and host firmware with over-the-air device firmware updates.
Once a Notecard is associated to a Notehub project, provisioning is automatic—no certificate management, user-association, or manual claiming required.
For early adopters and evaluation
For building early prototypes with collaborators
For deploying internal and customer pilots. Higher level support
For deploying commercial and production solution. Business level support
For large scaled deployments with enterprise level support. Private Notehub instance included
Data sent by your host into the Notecard flow through a Notehub on its way to your own cloud service. These data Events and other device activity & security Events are first logged in a cloud database so that you may assess the operational health of your devices and fleets. Events are then routed to any number of cloud services that you may configure. Finally, logged Events may also be accessed through a Notehub API. Charges are assessed as Events are routed out or accessed through the API.
The Notehub keeps its rolling log of Events in a cloud database referred to as an Event Log. The Event Retention Period – usually denominated as 24-hour UTC-aligned days, 7-day weeks, or 30-day months – defines the timeframe during which you’ll have access to the event log using the Notehub Web UI and APIs. The Notehub may permanently purge events from its event log storage once they fall outside the Retention Period.
Whenever the Notecard connects to the Notehub and establishes a new session, the Notehub opportunistically gathers information that may be useful to the project administrator, such as the current time and information about the cell tower and wireless signal strength. At the same time, the Notecard is capable of optionally gathering and uploading additional information about its surroundings, such as the list of all cell towers and WiFi access points whose antennas are “in view”. Each Notehub project is configurable such that it can anonymously use third party triangulation and multilateration services to determine an approximate geolocation, which is used to annotate the applicable session events. These specific session events, which are annotated with geolocation metadata, are referred to as Triangulation Events. The additional cost of these events is due to the inherent expense in gathering and keeping up-to-date a global database of cell towers and WiFi access points.