More data acquisition payload formats for Kotori

People are asking for more data formats on the ingress data acquisition path.

Support for Airrohr

Introduction

@clemens is already diverting output from a vanilla Airrohr device to weather.hiveeyes.org over HTTP transport. You can follow the stream by invoking

mosquitto_sub -h weather.hiveeyes.org -p 1883 -t 'umwelt/testdrive/luftdaten.info/#' -v

Data format

This device yields JSON data payloads like:

{
  "esp8266id": 12041741,
  "sensordatavalues": [
    {
      "value_type": "SDS_P1",
      "value": "35.67"
    },
    {
      "value_type": "SDS_P2",
      "value": "17.00"
    },
    {
      "value_type": "BME280_temperature",
      "value": "-2.83"
    },
    {
      "value_type": "BME280_humidity",
      "value": "66.73"
    },
    {
      "value_type": "BME280_pressure",
      "value": "100535.97"
    },
    {
      "value_type": "samples",
      "value": "3016882"
    },
    {
      "value_type": "min_micro",
      "value": "77"
    },
    {
      "value_type": "max_micro",
      "value": "26303"
    },
    {
      "value_type": "signal",
      "value": "-66"
    }
  ],
  "software_version": "NRZ-2018-123B"
}

Support for batch readings

Introduction

@wtf asked for submitting multiple readings in batches.

Data format

The proposed data format would simply encapsulate multiple readings into a list structure, so it would look like

[
  {"time": 0815, "temperature": 42.42, "humidity": 84.84},
  {"time": 4711, "temperature": 43.44, "humidity": 85.99}
]

See also: TTN-Daten an Kotori per HTTP/Post weiterleiten.

Support for TTN

Together with @Thias, we would like to unlock ingesting telemetry payloads from https://www.thethingsnetwork.org/.

See also

1 Like

Support for Tasmota

Together with @roh, we’ve unlocked decoding telemetry data originating from devices running the Tasmota Firmare the other day. Read all about it at https://getkotori.org/docs/handbook/decoders/tasmota.html.

See also

@valentinbarral also asked about this just recently and we have been able to finally implement it on behalf of Acquire bulk readings in JSON format by amotl · Pull Request #40 · daq-tools/kotori · GitHub. It will be part of one of the upcoming releases of Kotori.

Support für Appliances von Fine Offset

Im Rahmen des ClimArt Projekts werden wir ein paar weitere Geräte als Datenquellen für Kotori erschließen, oder andersherum.

Support für NDJSON

Mit [DRAFT] Add decoder for acquiring data in NDJSON format by amotl · Pull Request #129 · daq-tools/kotori · GitHub wird Kotori ein weiteres Datenformat annehmen können.

Es eignet sich besser für die Übertragung von mehrfachen Messereignissen, wenn man grundsätzlich noch im ASCII-Bereich und bei JSON bleiben will.

P.S.: Das gleiche gilt natürlich auch für den Export von Daten im JSON Format. Auch hier sollte es zukünftig die Möglichkeit geben, Meßereignisse im NDJSON Format zu exportieren.

µON [muon]

Volodymyr Shymanskyy, having conceived the Blynk library and platform the other day [1], revamped an interesting binary serialization format last year.

It is advertising itself as a compact and simple binary object notation format, and because this also fits the research around BERadio [2], we created a note about it at Look at µON [muon] · Issue #8 · hiveeyes/beradio · GitHub. For more details, Muon - Google Präsentationen has a presentation to convey the idea.

It would be sweet if Kotori could also decode that data format in the future. I like that the author, Volodymyr Shymanskyy, thought about assigning appropriate format properties like file extension, mime type, etc. from the very beginning.

File extension:     .mu
MIME type:          application/muon
Endianness:         little-endian
Signature/Magic:    optional, 8F B5 30 31 ["�µ01"] @ 0x0

  1. See also Search results for 'blynk' - Hiveeyes here. ↩︎

  2. Development of the BERadio RFM-to-MQTT gateway software ↩︎

1 Like