Node-Red Integration

Farewell Dweet.io

This section used to rely on the dweet.io service provided by Bug Labs, which has unfortunately been suspended. The work around is in some ways an improvement - as it uses eChook's own server, your telemetry data is no longer publicly exposed, and as a result the apps will allow location to be sent. The only downside being you do need to create an account on data.echook.uk.

Connecting Node Red to eChook Live Data

This section assumes that node-red is already installed and running.

  1. Create an account for your car at data.echook.uk, then bring up the developer tools in your browser (normally F12, or Ctrl+Shift+i) and select the 'Console' tab. After a fresh login to the website, near the top of the console should be a printed web address, along the lines of https://data.echook.uk/api/get/-----Long-Unique-Key------. This address is unique to your car. Copy it for later.

  1. In the Omni app, select upload to eChook Private Live Data enter your login details.

  2. For node-red setup, download the json file below and import it to your node red dashboard by right clicking on the background > insert > import, and selecting the downloaded file.

You should now have a dashboard that looks like this:

Double click the http request block, and enter the URL you copied in step 1, then deploy the changes.

How it works

Every 2 seconds the inject block on the left triggers the HTTP request. This asks the server for the latest data from the car, which is formatted into a JSON object by the JSON block, and then split out into separate flows in the 'eChook Data Split' block. Mouse over the output connectors to see what data each provides. The output data is in the format of '{name:xyz, value:123}, so is accessible in later blocks using msg.payload.value and msg.payload.name.

Last updated

Was this helpful?