This is an asset tracking dashboard to display the information captured from Blues Notecards in vehicles.
Screen.Recording.2021-12-13.at.11.48.01.AM.mp4
The Asset Tracking dashboard is a Next.js app which serves up a pre-configured dashboard complete with Leaflet.js map and Mapbox overlay to plot Notecard coordinates as they're relayed to Notehub, Recharts charts displaying Notecard's current voltage and temperature, and a react-table event list so a user can see the frequency with which tracking events are being recorded.
The Notecard records its current GPS location once every 10 minutes while the vehicle is in motion.
It is preconfigured to poll for new events from the Notehub project every 2 minutes, and re-render the latest data on the dashboard.
- Next.js Docs - Introduction to Next.js
- Notecard Asset Tracking Docs - Configuring a Blues Notecard to do asset tracking
- Recharts Docs - Introduction to Recharts composable chart library
- React Leaflet Docs - React Leaflet library introduction
- React Table Docs - React Table getting started and example documentation
- Mapbox Docs - How to generate Mapbox access token and select view
Below are steps from the Notecard all the way to the software to get your own instance of this dashboard up and running.
- Notecard from Blues Wireless
- Notecarrier A with LiPo battery connector from Blues
- LiPo battery
- (Optional) MicroUSB to USB converter cable (or other cable to connect vehicle's power source to Notecarrier when vehicle is powered on)
- Create an account with Blues Notehub site and make a new project that this Notecard will be associated with.
- Follow the "Quickstart Guide" on the Blues developer site to get connect your Notecard, Notecarrier A and Notehub project.
- Feed the following commands in, one at a time, to the Notecard while it's connected to your computer using the webREPL built in to the
dev.blues.iosite.
{"req":"card.restore","delete":true} # factory reset card
{"req":"hub.set","product":"com.blues.[PRODUCT_UID]","mode":"periodic","outbound":15,"inbound":15} # attach tracker to Notehub project, set it to periodic syncing outbound reqs every 15 mins and inbound reqs from Notehub every 15 mins
{"req":"card.motion.mode","sensitivity":2} # set card accelerometer to higher sensitivity level
{"req":"card.location.mode","mode":"periodic","seconds":360} # tell card how often to get GPS reading and only when motion is detected
{"req":"card.location.track","start":true,"heartbeat":true,"hours":12,"sync":true} # start tracking, issue heartbeat every 12 hours when no motion detected, sync data with Notehub as soon as a tracking event is acquired (this is an important one)- Clone this repo locally.
- Run
npm installat the root of the project. - Generate an access token for Notehub via the following curl command. For further info see this documentation
curl -X POST
-L 'https://api.notefile.net/auth/login'
-d '{"username":"[you@youremail.com]", "password": "[your_password]"}'- Open your
.envfile and replace the placeholder values with your own identifiers and tokens.
NOTEHUB_PROJECT_ID=app:12345-67890-12345-67890
NOTEHUB_TOKEN=abc123def456ghi789
MAPBOX_ACCESS_TOKEN=pk.abc123def456ghi789abc123def456ghi789- Run
npm run devin the terminal to start the server - Visit http://localhost:8080 in your browser.
- Watch the events begin to populate the new dashboard as the asset moves around.
If you do intend to use this as a potential vehicle tracker, keep the following things in mind:
- Hide the Notecard - Hide the Notecard somewhere in the vehicle where it's not easily discoverable. The Notecard A is equipped with an Ignion antenna, which is quite powerful, therefore, it's very possible that without a direct line of sight to the sky - say, inside the center console of a car, and it will still be able to get a triangulation lock for GPS purposes. Test this out by placing the Notecard where you might want to keep it stored and check if its location registers. Also, avoid putting it somewhere where it would either be exposed to extreme heat (like in the dashboard near the engine and windshield) or wet (like in the bumper of the car)
- Have multiple power supplies - In addition to a LiPo battery to power the Notecard when the vehicle is off, invest in some way to power the Notecard from the vehicle's power source when it's on. Although the Notecard is designed to be low power, it is still relatively power intensive to get a GPS coordinate lock and then send that data to Notehub. When SOS Mode is enabled, especially, this could be an issue. Nowadays, most vehicles come equipped with USB ports or adapters to plug in electronics, so wherever the Notecard is hidden, invest in a micro-USB to car connector so that when the car is powered on, the Notecard can run off of the car battery and charge its LiPo battery, which it will run off of when the vehicle is off.
- Invest in a cloud database to persist Notehub events - Notehub charges users after a certain amount of events are sent out of the application per month (5,000, I believe), so it's not the most cost effective to poll all events from Notehub every 2 - 5 minutes. For a larger product, I'd recommend investing in some sort of a cloud database that could both pull all the initial data from Notehub and then possibly also receive events routed from Notehub as they are recorded there to cut down on costs. Then the app can pull data from that database as often as it likes with no fear of extraordinary bills being incurred from Notehub.
This project accomplished what I originally set out to do, which was build a standalone dashboard that can connect to a Blues Notehub project, but in an internal hackathon at work, I took it one step further and made a similar dashboard that also has the capability of enabling high frequency tracking if, say, the vehicle being tracked is stolen (it happened to my parents while I was building this dashboard, in fact).
If you'd like to see the improvements in that dashboard, visit this repo for more info.