🌡️  Monitor legacy analog systems with TinyML, Edge Impulse, and Blues Wireless. Learn more in our webinar on May 26th!

Search
Documentation Results
End of results
Community Results
End of results
Support
Blues.io
Notehub.io
Shop
Sign In
Search
Documentation Results
End of results
Community Results
End of results
Support
Blues.io
Notehub.io
Shop
×
HomeGuides & Tutorials
Welcome
Collecting Sensor Data
Routing Data to Cloud
Fleet Admin GuideDevice InformationEvent InformationSession InformationData HandlingFirmware ManagementOrganizational ToolingHardware Specific QR Codes
Notecard Guides
Guide Listing
Asset Tracking
Attention Pin Guide
Connecting to a Wi-Fi Access Point
Debugging with the FTDI Debug Cable
Encrypting Data With the Notecard
Minimizing Latency
Serial-Over-I2C Protocol
Understanding Environment Variables
Understanding Notecard Penalty Boxes
Updating ESP32 Host Firmware
Using External SIM Cards
Using JSONata to Transform JSON
Routing References
Twilio Route
MQTT Route
Azure Function Route
ThingWorx Route
Rate this page  
  • ★
    ★
  • ★
    ★
  • ★
    ★
  • ★
    ★
  • ★
    ★

Fleet Administrator's Guide

Notehub provides numerous features that allow you to inspect data transferred from the Notecard, manage fleets of devices, provision access to projects, and perform cloud-based OTA DFU.

Device Information

Notehub is built around a data set comprising of Notecard, Event, and Session data. The raw data collected from these sources is described in the JSON format. Notehub makes the data accessible through a graphical user-interface, which provides valuable insights and interactions with this data.

Raw Device JSON

The information contained in the JSON object is outlined in the following table:

KeyData TypeDescription
contactobjectContact information object
devicestringDevice UID
fleetstringFleet UID
latestobject
productstringProduct UID
provisionednumberProvisioning date (UNIX epoch timestamp)
session_activitynumber
session_begannumber(UNIX epoch timestamp)
session_towerobjectTower information object
session_tower.cstringTower location country
session_tower.cidnumberCell Identification
session_tower.lstring
session_tower.lacnumberLocation Area Code
session_tower.latnumberGeographic latitude
session_tower.lonnumberGeographic longitue
session_tower.mccnumberMobile Country Code
session_tower.mncnumberMobile Network Code
session_tower.nstringTower location city and state
session_tower.trinumber
session_tower.zonestringTimezone information
settingsobject
settings.modifiednumberModified date (UNIX epoch timestamp)
snstringProduct serial number
tempnumberAmbient temperature
voltagenumberVoltage on V+ pin

Navigating to Device Data

The device data JSON object can be found using the following steps:

  1. Select Devices from the left navigation bar and select a device from the list provided.

    Device selected from list

  2. Select View from the available options.

    Details option

  3. Select the JSON tab.

    JSON tab selected

Event Information

Notehub is built around a data set comprising of Notecard, Event, and Session data. The raw data collected from these sources is described in the JSON format. Notehub makes the data accessible through a graphical user-interface, which provides valuable insights and interactions with this data.

Raw Event JSON

The information contained in the JSON object is outlined in the following table:

KeyData TypeDescription
eventstringEvent UID
sessionstringSession UID
tlsbooleanTLS encrytped
devicestringDevice UID
snstringProduct serial number
productstringProduct UID
receivednumber
routednumberWhen the Note was transmitted to Notehub (UNIX epoch timestamp)
reqstringNotecard request API
whennumberWhen the Note was queued on the Notecard (UNIX epoch timestamp)
filestringNotefile name to which the Note was queued
notestring
updatesnumber
bodyobjectUser-defined Note payload
tower_whennumber
tower_latnumberCellular tower latitude
tower_lonnumberCellular tower longitude
tower_countrystringCellular tower country code
tower_locationstringCellular tower location (City/State)
tower_timezonestringCellular tower time-zone
tower_idstringCell Global Identity
movednumberlast epoch time that the device moved
orientationstringdescription of physical orientation (e.g. "face-up")
rssinumberReceived Signal Strength Indication
sinrnumberSignal-to-Interference-plus-Noise Ratio
rsrpnumberReference Signals Received Power
rsrqnumberReference Signals Received Quality
ratstringRadio Access Technology
barsnumberNumber of bars of cellular service
voltagenumberVoltage measured from power supply
tempnumberTemperature measured on chip
towersnumberConnected tower count
logattnbooleanEvent requires attention
logobjectRoute Log (list)
log.[rid*]objectRoute object
log.[rid*].attnbooleanRoute requires attention
log.[rid*].statusnumberError status code
log.[rid*].textstringError message
replystring

*An auto-generated route identifier, comprising of the project's unique identifier along with the route's unique identifier.

Navigating to Event Data

The event data JSON object can be found using the following steps:

  1. Select Events from the left navigation bar.

    Events menu

  2. Select an event from the list of events.

    Event selected from list

  3. Select Details from the available options.

    Details option

  4. Select the JSON tab.

    JSON tab selected

Session Information

Notehub is built around a data set comprising of Notecard, Event, and Session data. The raw data collected from these sources is described in the JSON format. Notehub makes the data accessible through a graphical user-interface, which provides valuable insights and interactions with this data.

Raw Session JSON

The information contained in the JSON object is outlined in the following table:

KeyData TypeDescription
sessionstringSession UID
devicestringDevice UID
productstringProduct UID
fleetstringFleet UID
addrstringProtocol, socket, and IP address
cellstringCellular global identity
ScanResults
rssinumberReceived Signal Strength Indication
sinrnumberSignal-to-Interference-plus-Noise Ratio
rsrpnumberReference Signals Received Power
rsrqnumberReference Signals Received Quality
ratstringRadio Access Technology
towerobjectObject describing tower information
tower.nstringTower location city and state
tower.cstringTower location country
tower.lstring
tower.latnumberGeographic latitude
tower.lonnumberGeographic longitue
tower.zonestringTimezone information
tower.mccnumberMobile Country Code
tower.mncnumberMobile Network Code
tower.lacnumberLocation Area Code
tower.cidnumberCell Identification
tower.trinumber
session_log_keystring
thisobjectObject describing Session transaction details
this.sincenumberPOSIX timestamp
this.bytes_rcvdnumberBytes received during this session (Cellular Notecard only)
this.bytes_sentnumberBytes sent during this session (Cellular Notecard only)
this.sessions_tcpnumber
this.sessions_tlsnumber
this.notes_rcvdnumberNotes received during this session (Cellular Notecard only)
this.notes_sentnumberNotes sent during this session (Cellular Notecard only)
nextobject
periodobject
period.sincenumberPOSIX timestamp
period.durationnumber
period.bytes_rcvdnumberBytes received during this session
period.bytes_sentnumberBytes sent during this session
period.sessions_tcpnumber
period.sessions_tlsnumber
period.notes_rcvdnumberNotes received during this session
period.notes_sentnumberNotes sent during this session
voltagenumberVoltage supplied to Notecard
tempnumberAmbient temperature of Notecard
continuousbooleanDescribes if continuous mode is enabled
tlsbooleanDescribes encryption status of session
worknumber
eventsnumberNumber of events that occurred during session
movednumberlast epoch time that the device moved
orientationstringdescription of physical orientation (e.g. "face-up")
triggerstringconfiguration details and reason for session establishment
LastWorkDonenumberPOSIX timestamp

Navigating to Session Data

note

Session data usage (bytes and notes) is only available on Cellular Notecards.

The session data JSON object can be found using the following steps:

  1. Select Devices from the left navigation bar and select Sessions from the available options.

    Sessions option

  2. Double-click a session from the list of sessions.

    Select session

  3. View the JSON of the selected session.

    Session selected

Data Handling

Notehub provides data handling capabilities for both data that was captured, or generated, by Notecards as well as data being sent to Notecards from Notehub.

Data Routing (ingress/egress)

A Route is an external API, or server location, where Notes are to be forwarded. A Route is established at the Project level, and by default will map every single transaction over a route. However, a route can also be filtered down to specific Notefiles and/or Fleets, allowing you to customize the amount of data you wish to share. Beyond filtering, any single event is capable of being multicast over several Routes, which gives you the ability to customize data ingress/egress to suit your needs.

For examples, view the Routing Tutorials

Data Origination

Not only can Notehub respond to data created by the Notecard, but it can send data to the Notecard as well. This functionality introduces interactive behaviors, configurations, and control.

Inbound Queues

Inbound may sound like a misnomer, but it was named from the perspective of the Notecard device. Therefore, when you load a Note into an Inbound Queue (.qi Notefile), that Note will be delivered the next time the Notecard device synchronizes with Notehub.

Environment Variables

Environment variables provide a mechanism to propagate cloud-based key/value pairs to a device, fleet, or project.

note

The Hierarchy of Environment Variables

Environment variables can be defined in a number of locations, from the Notecard, to Notehub device settings, the device's Fleet, and the Notehub project. Variables set at different levels of this hierarchy can override one another. When obtaining an environment variable, the Notecard uses the following priority order, where the fist matched result is returned:

  1. The value set on that Notecard with the env.set request.
  2. The value set in Notehub directly on Notehub's record for the Device.
  3. The value set in Notehub on a Fleet to which the Device belongs.
  4. The value set in Notehub on the Project to which the Device belongs.
  5. The value set on that Notecard with the env.default request.

Firmware Management

Notehub's ability to send and receive data has also been generalized to send firmware. Firmware can be uploaded to Notehub, then subsequently rolled out on a project, fleet or device scope. The firmware is not only limited to Notecards, it can also target the host MCU.

For more information regarding host DFU capabilities, please refer to the Notecard Walkthrough: Host Firmware Update Requests.

Organizational Tooling

Notehub.io provides tooling for organizing projects, team members, and Notecard devices. Team members can be granted role-based access to individual projects, and devices can be grouped into both projects and fleets.

Project Management

Projects are the highest form of organization in Notehub. Each project is comprised of one or more products identified by ProductUIDs which are globally unique identifiers in reverse-DNS format (e.g. com.acme.tools.drill_press).

This project > product relationship enables users to organize multiple products into coherent groups. For example, a company could have a project called "Refrigerators". Under this Refrigerators project, they might have multiple products such as "upright refrigerators", "chest refrigerators", and "side-by-side refrigerators".

As such, projects offer a logical grouping of products in an account, and act as the entry point for drilling into information regarding Notecard devices and their associated data.

Relevant Project Actions:

  • Product management
  • Fleet and device management
  • Route management
  • Team member management
  • OTA firmware deployment for Notecards and hosts
  • Environment variable management

Team Management

Notehub.io allows for the creation and management of team members who may be delegated varying levels of access to projects. With the provided role-based privileges, a single team member can have differing degrees of access to multiple projects under an account.

Team members can be granted one or more of three different roles on a single project:

  • Owner (Collaborator) has full administrative privileges.
  • Developer (Collaborator) has limited administrative privileges.
  • Viewer has read-only privileges.

Fleet Management

Fleets allow for the organization of Notecard devices into logical groupings. Fleets are managed at the project level.

Fleets can be named and used in any way that fits your individual project. However, if you are looking for guidance, we recommend the following:

  • Using a New fleet to view (and potentially triage) Notecard devices newly-added to a project.
  • Using one or more Operational fleets denoting active devices and organized by device type, region, or some scope of environment variables.
  • Using a Repair fleet for all devices that have been taken out of service but may be put back into service when functioning properly.
  • Using a Decommissioned fleet for all devices that are out of service and will not return to service.
  • Using custom-tagged fleets to identify devices that may need to be monitored for anomalies, associated with a geolocation, linked to a specific custodian, and so on.

Users concerned about the possibility of a "rogue" device polluting data in Notehub will find the usage of the New fleet useful. Newly-provisioned devices will appear in New, allowing for easy re-assignment or removal of unidentified devices. Likewise, using an Operational fleet allows users to designate specific devices as approved to route data to third-party cloud applications.

Hardware Specific QR Codes

Each Notecard comes with a sticker containing a QR code unique that device. By default, the QR code links to the Quickstart Guide.

Depending on the needs of your company, a different URL redirect can be specified, allowing you to forward the user to a company- or product-specific address.

  1. Navigate to Settings, and find the Device Dashboard URL section.

  2. Fill in the field with the URL you would like to use.

    URL example with variables

note

Pay special attention to any substitution variables specified in the URL above. You may use the substitution variables [device], [sn] (serial number), and [product]. These enable you to provide endpoints or URLs capable of being tailored to individual devices.

Can we improve this page? Send us feedbackRate this page
  • ★
    ★
  • ★
    ★
  • ★
    ★
  • ★
    ★
  • ★
    ★
© 2022 Blues Inc.Terms & ConditionsPrivacy
blues.ioTwitterLinkedInGitHubHackster.io
Disconnected
Disconnected
Having trouble connecting?

Try changing your Micro USB cable as some cables do not support transferring data. If that does not solve your problem, contact us at support@blues.com and we will get you set up with another tool to communicate with the Notecard.

Connect a NotecardClick 'Connect' and select a USB-connected Notecard to start issuing requests from the browser.