IoT Device Management Server running on node.js.
The CircleCI build is limited and therefore returns mostly bad results. Closer look may show better numbers.
- Update IoT device by pushing a code to a Git repository. We'll build it.
- Swap operating system for another over-the-air.
- Migrate multiple devices at once between WiFi networks.
- THiNX provides complete IoT infrastructure for your device (where the data storage and visualisation can be fully up to you).
- automatic updates for headless devices, or semi-automatic (with user consent after build and tests succeed)
As a user I have already many IoT new and/or legacy devices at home and new platforms are coming every day.
Sometimes we need to change WiFi credentials on a wireless switch mounted on a ceiling. The other day I we want to swap whole firmware for new one, but not always to rewrite working legacy Lua or Micropython code to PlatformIO.
That's why we have decided to create the über-platform: THiNX.
Remote Things Management console for monitoring devices, attaching source code, pushing data, managing incoming payloads and firmware updates.
Continuous Integration practices to update device apps/configurations from a GitHub repository using commit hooks
Building secure MQTTS infrastructure as an optional side-chain transport layer.
Device registration endpoint while storing device data using CouchDB server and Redis session-store.
API is a back-end data provider (security agent) for RTM Admin Console Application.
Provides control to a dockerized build servers and pushes new firmware versions to client applications (FCM push) and devices (MQTT).
Provides HTTP-to-HTTPS proxy to secure legacy IoT devices that are not capable of TLS and/or AES-level encryption.
Allows transfer of device ownership (e.g. for pre-configured devices).
Custom firmware builder for MongooseOS, NodeMCU and Micropython (allow module selection, add THiNX as an OS-level library)
Transfer device to another owner along with sources/firmware.
Supports OAuth login with Google and GitHub.
Supports InfluxDB/Grafana data storage and visualisation.
Supports LoRaWan server integration.
Supported IoT Platforms
PlatformIO and Arduino IDE (ESP8266P/ESP32)
Tested on Wemos D1 Mini, Wemos D1 Mini Pro, RobotDyn D1, RobotDyn D1 Mini, RobotDyn MEGA WiFi and various NodeMCU (Lolin, AI-THINKER) boards with Mongoose, Arduino Core, ESP-IDF, Lua and Micropython-based core firmwares...
Expected: Arduino and BigClown with networking support
Base THiNXLib Platform Library in C++:
THiNX Platform Library repositories for various IDEs and firmwares:
With built-in THiNX Client Library:
Arduino, Plaform.io and MongooseOS are firmwares by nature.
Dockerized Firmware Builders
Prerequisites for running own THiNX Server
- Linux Server (min. 2 GB RAM, 32GB SSD, Ubuntu)
- API runs on HTTP port 7442 (HTTPS 7443) and 7447 (web socket)
- MQTTS runs on port 8883
- Admin runs on HTTP/HTTPS port (80/443)
- GitHub commit hooks are listened to on port 9000, 9001
- Grafana (3003), InfluxDB (3004)
- Status Transformers (localhost only, 7445)
- Optional monitoring services (Keymetrics, TrueSight) may run on other ports as well...
Experimental Docker installation can be found at Docker Hub.
First of all, set a valid FQDN (THINX_HOSTNAME) for your new THiNX instance on your DNS server. Use this FQDN to parametrise the Docker image by following example:
docker pull suculent/thinx-docker docker build --build-arg THINX_HOSTNAME=staging.thinx.cloud -t suculent/thinx-docker . docker run -ti -e THINX_HOSTNAME='staging.thinx.cloud' -e THINX_OWNERemail@example.com' suculent/thinx-docker
Installing Platform Builders
Attach to the running container with bash:
docker run -ti -e THINX_HOSTNAME='staging.thinx.cloud' -e THINX_OWNERfirstname.lastname@example.org' suculent/thinx-docker /bin/bash
Fetch required builder images from Docker Hub:
Run after boot
We're currently using /etc/rc.local to kick THiNX up after a failure:
# MQTT service mosquitto > /root/thinx-device-api/mosquitto.log & # Redis service redis-server > /root/thinx-device-api/redis.log & # CouchDB service /etc/init.d/couchdb start # NodeJS Sandbox docker run -d suculent/thinx-node-tranformer # Grafana/InfluxDB docker run -d \ -p 3003:3003 \ -p 3004:8083 \ -p 8086:8086 \ -v /root/docker-influxdb-grafana/influxdb:/var/lib/influxdb \ -v /root/docker-influxdb-grafana/grafana:/var/lib/grafana \ suculent/docker-influxdb-grafana:latest # THiNX itself cd /root/thinx-device-api/ && pm2 start index
GitHub Webhook support
You can direct your GitHub web-hooks to https://thinx.cloud:9001/ after adding a valid deploy key from GitHub to THiNX RTM.
See 03-test.sh. There is no point of maintaining documentation for this at current stage of development and user base zero.
Platforms State of Union
Platform libraries are now stabilised on the basic level, approaching first release version 1.0 with default HTTPS with optional fallback to HTTP for development.
- Docker builder works.
- Deployment update can be tested now.
- Docker builder has been recently updated.
- Deployment update can be tested now.
- File-based update has been pre-tested. Docker builder works fine but needs tighter integration with sources (
- Deployment is not verified, therefore update cannot be tested.
- Docker builder works fine but needs tighter integration with sources.
- Deployment is not verified, therefore update cannot be tested now.
- PlatformIO: end-to-end update
- Arduino: end-to-end update