technische Details

unsere Lösung ist wie folgt aufgebaut (Informationen aktuell nur auf Englisch verfügbar).

Technical Overview

Sensor

sensor
The sensor collects the following information from the environment:
  • temperature
  • humidity
  • motion

Senses

Occupancy (Infrared Sensor)

Temperature (C°)

Humidity (ppm)

Dimensions

Diameter: 64 mm

Depth: 44 mm

Weight: 90 g

Power

1 replaceable CR123 Lithium Battery

Wireless

LoRa (868 Mhz)

Installation

sticker, magnets or screws

Durability

Indoor use only

Communication between Sensor and Gateway

The sensor transmits the following information:
  • current temperature
  • current humidity
  • how much motion has been seen
  • battery state
  • uptime of the sensor
Due to the way LoRa works, the following information could be gathered as well:
  • Approximate distance to the gateway (signal attenuation)
The data is encrypted using a key which only the LoRa provider and thingdust knows. The gateway or someone listening to the communcation on air would not be able to know what exactly the sensor sent.

Gateway

The gateway:
  • receives messages from all LoRa devices in range. That may be devices not from thingdust
  • may be provided by thingdust or it may already be installed for different purposes.
  • forward all received messages that are destined for thingdust to the LoRa provider

Communication between gateway and LoRaWAN provider

The gateway forwards the exact message as it has been received from the sensor. This usually happens over the mobile network.

LoRaWAN Provider

We support different mobile providers that you can chose on if you wish:The provider simply forwards the messages to the thingdust brain without doing anything further with it. If you already have a LoRa based installation in your company, we are happy to reuse that.

Communication between LoRaWAN Provider and the thingdust brain

The transmission from the provider to thingdust contains the following information:
  • The exact message from the sensor (as described above)
  • which gateway(s) received the message
  • Approximate distance to the gateway (signal attenuation)

thingdust brain

The thingdust brain receives all messages from all sensors and processes them using the information given by the facility manager. To fulfill the purpose of the product, it may store and process:
  • all messages exactly as they were sent
  • which sensors are in which space
  • the structural information of the spaces
  • various other configuration parts given by the facility manager (e.g. authentication)
We monitor the system for early problem management, because of that the system may also store and process:
  • logs of different nature (e.g. login, api usage ...)
By technical nature of the system, the following information may also be stored for system management purposes:
  • client ip address

Communication between the thingdust brain and the dashboard

The communication between the dashboard and the thingdust brain happens in an encrypted matter (TLS).

Dashboard

The dashboard is the client visible part of the whole system. Only authorized clients can access information from the system.

Communication between Dashboard and the employee

The employee can access the following information:
  • live state (temperature, humidity, occupancy)
  • limited historical data
The employee may provide the following information to the system:
  • his email address (for the authentication)
  • feedback to thingdust

Communication between Dashboard and the facility manager

The facility manager can access the following information (when part of the bought package):
  • live state (temperature, humidity, occupancy)
  • historical data and analytics
  • space configuration
  • authentication configuration
The facility manager may provide the following information to the system:
  • his email address (for the authentication)
  • configuration changes
  • feedback to thingdust

Communication between Dashboard and the api

An application that is using the api can access:
  • the live state (temperature, humidity, occupancy)
This may happen on a request basis (over ReST), or on a push-notification basis (over Websocket).

last update: 2018-12-03