Sections on this page

Tasks and ideas

As this is our brainstorming area, lots of content is in german, sorry. You might want to try the Google translation of the “Hiveeyes system documentation” tasks.

2017

2017-08-05

2017-06-28

  • Add beehacker.com

2017-05-05

2017-05-03

2017-04-04

2017-04-02

2017-03-31

  • [o] open() “/usr/share/nginx/html/grafana/dashboard/db/hiveeyes-testdrive-cg-node-002-automatic” failed

2017-03-29

2017-03-28

2017-03-27

2017-03-17

2017-03-15

2017-02-21

2017-02-07

  • [o] Move content from “Agenda - finally!” to Forum

2017-02-05

2017-01-16

  • Maybe Transfer some content juwels like “Investigations into low-cost load cells” to community.hiveeyes.org

2017-01-12

2016

2016-12-30

  • archive.hiveeyes.org à la archive.luftdaten.info

2016-12-29

2016-12-20

2016-11-12

2016-11-12

2016-11-01

  • [o] Move PHP clients out of this repository. Put into Terkin.

2016-10-23

  • [o] Adapt Homie MQTT topic to Hiveeyes semantics

2016-10-11

2016-09-05

2016-06-08

2016-06-06

2016-06-05

  • Rangefinder Beacon with a Smartphone
    Buzzer, Beeper and GPS feedback for https://github.com/ksksue/Android-USB-Serial-Monitor-Lite

  • Build distribution packages of artefacts in hiveeyes/arduino

    • Source tarball and zip

    • Binary firmware, debug and stripped

    • Documentation about how to acquire and how to upload firmware from different operating systems

      • ino
      • avrdude
      • Windows and Mac OSX GUI

  • Refactor docs re. Handbook vs. Data acquisition vs. X

2016-06-04

2016-05-26

  • [o] Improve liability disclaimer: Explicitly mention all “hardware” having the notion of implicitly being part of an overall “system”.
  • [o] Replace all “get in touch” or “please email us” links through http links to community.hiveeyes.org
  • [o] Backlink with history.html#mqttwarn-xmpp
  • [o] Add proper content attributions to media elements from 3rd-party authors
  • [o] Display license in documentation
  • [o] Add more “bills of material” (Teileliste)

2016-05-25

2016-05-24

2016-05-23

  • [o] Schwarmalarm v1, HiveeyesDaily

2016-05-20 rpo, amo

  • [o] Use both raw and effective sensor values. Effective sensor values are modified by a specific delta.

2016-03-06 amo

  • [x] Get proper trusted certificates from Let’s Encrypt for hiveeyes.org

  • [o] Improve docs

    • foundation (more pointers)
    • hiveeyes-one (more pointers)

2016-02-27 amo

  • [o] Consider using the upcoming Raspberry Pi 3 as a flexible and universal gateway

2016-02-25 rgu, cgr, rpo, msw, amo

  • [o] BERadio Lua implementation for OpenWrt
  • [o] Get Vagrant going for Windows users
  • [o] Consider LoRaWAN
  • [o] Rephrase wording on splash screen
  • [o] How to do store-and-forward if Mosquitto doesn’t have it? Use DTN finally?

2016-02-23 jho, rpo, amo

  • [o] Get into Mosquitto store-and-forward mechanism. Does it actually have it?

  • [o] Check out improved “Annotations” feature of Grafana

    Annotations: Click links and select text from annotation popover

    Annotations: Click links and select text from annotation popover

  • [o] Setup Grafana HEAD from git repository at beta.hiveeyes.org for having a look at new features

2016-02-23 amo

  • [o] link to recent discussion about payload serialization formats

2016-02-22 rpo, amo

  • [o] Datenimport und -export über CSV
  • [o] Tabellarische Daten über datatables
  • Naming things: Will HiveFive be a proper name for the convenience kit?

2016-02-22 cgr, amo

Improvements

  • [o] Open Hive: Add Fritzing schema for ESP8266

  • [o] Add Stückliste (via Excel file)

  • [o] Improve documentation of Hiveeyes One

    • Foundation libraries
    • Text from Grafana reference dashboard
    • Pictures

Features

  • [o] Kotori should be able to talk FTP (e.g. for batch-mode transmission of CSV data)

    Todo

    Link to GPRS module capable of talking FTP

  • [o] There should be a PHP script which is API-compatible to a future CoAP interface of Kotori to smooth the learning curve and lower the bar.

    Todo

    Research whether there already is a convenient PHP library talking CoAP

  • [o] This PHP script could also be used as a generic WebHook receiver when Kotori is dispatching messages to different receivers. mqttwarn might help.

2016-02-22 amo

Documentation updates

2016-02-21 amo

Documentation updates

  • [x] Add stub “About Open Hive”

  • [x] Write text about Hiveeyes One

  • [x] Write text about Open Hive

  • [x] Auf Kotori 0.3.2 and BERadio 0.4.4 CHANGELOG verlinken

  • [x] rpos neue Bilder reintun

  • [x] This and that

  • [x] Tag swarm-hiveeyes-org @ 0.1.0

  • [x] Add bumpversion

  • [x] Improve Kotori and BERadio docs

    • [x] Migrate use-case scenarios from BERadio
    • [x] Migrate Hiveeyes wishlist from Kotori

2016-02-20 amo

MS 1

MS 2

Tip

Ab jetzt möglichst auch mit feature branches in den code repositories arbeiten.

  • Kotori 0.7.0

    • Reguläres refactoring

    • MQTT Topic

      • Implementierung der “Content Type” Signalisierung über pseudo-Dateiendungen wie geplant (Inspired by Nick O’Leary and Jan-Piet Mens; Acked by cgr and rpo):

        hiveeyes/testdrive/area-42/hive3/temperature vs. hiveeyes/testdrive/area-42/hive3.json

        Weitere Diskussion und Implementierung der “Direction” Signalisierung (Inspired by computourist, Pushed by rpo) Proposal:

        .../node3/{direction}/{sensor}.foo

      • Generalisierung der BERadioNetworkApplication / HiveeyesApplication vendor Architektur

      • Verbesserung der service-in-service Infrastruktur mit nativen Twisted service containern

      • Flexiblere Anwendungsfälle ähnlich dem von Hiveeyes ermöglichen: mqtt topic first-level segment “hiveeyes/” (the “realm”) per Konfigurationsdatei bestimmen (Wunsch von Dazz)

      • Einführung von Softwaretests

  • BERadio 0.6.0

    • Generalisierung der Funktionalität, Stichwort “mqttkit”
    • Verbesserung der Dokumentation

  • swarm.hiveeyes.org

    • Prototypische Einbindung von mqttwarn in unser Gesamtsystem :-)

Research

Mit ein paar Dingen müssen wir uns bei Gelegenheit stärker beschäftigen.

  • InfluxDB

    • Wie geht man am besten mit InfluxDB-nativen Tags in unserem Kontext um? Bemerkung: Vielleicht war die Trennung auf Datenbank/Tableebene die falsche Strategie bzw. es gibt noch weitere, die orthogonal davon zusätzlich oder alternativ sinnvoll sind.

  • Grafana

    • Wie kann man hier die Tags aus InfluxDB am besten verarbeiten und in den Dashboards praktisch nutzen?
    • Wie funktionieren Annotations mit InfluxDB?

  • Gesamtsystem

    • Auch hier wird im Zusammenspiel der Komponenten noch viel geschwummst werden müssen. Ausblick: mqttwarn besser mit Kotori integrieren (via API) und als universeller Nachrichtenvermittler auf swarm.hiveeyes.org betreiben.

2016-02-12 rpo, amo

Platform

  • Zuordnung/Verdrahtung von Sensoren zu Hardware Ports zu measurement fields zu Grafana dashboard/panel [rpo]

    • Beschäftigung mit InfluxDB Tags und deren Benutzung in Grafana

  • Implement Grafana dashboard history - we already lost some… ;[

    22:33 die strategie mit dem git finde ich gut: https://wikitech.wikimedia.org/wiki/Grafana.wikimedia.org#No_history_of_dashboard_changes
    22:33 “One could run grafcli or something using the grafana HTTP API with git in a cron to have a better history.”

  • hiveeyes reference dashboard text

  • Check backup of elbanco

  • Issue PR2 of mqttwarn, write documentation (scenario window control)

  • Obfuscate email address at https://swarm.hiveeyes.org/

  • Improve splash page

  • Redesign topic namespace

  • Improve documentation

    • Interlink with documentation of foundation projects
    • Write about the integration of the components
    • Add Hardware Stückliste
    • Add more information fragments from distilled mailing list exchange

  • Package pinning for Grafana

  • Document how to upload pictures and screenshots, which should not go into a repository:

    # manual
scp ~/Backup/Desktop/2016-02-19/2016-02-12_hiveeyes-notification-xmpp.jpg root@ptrace.hiveeyes.org:/var/www/ptrace.hiveeyes.org/htdocs/

# automatic
make ptrace-hiveeyes source=/tmp/grafana-ber-prototype-1.jpeg

Kotori

  • Add more protocols

    • CoAP

    • CSV over UDP

    • HTTP/REST

      • CSV
      • Single values via x-www-form-urlencoded
      • Bunch of JSON

  • Add software tests

  • Log file rotation for /var/log/kotori/kotori.log

2016-02-15T10:13:50+0100 [kotori.daq.storage.influx        ] INFO: Storing measurement succeeded: {'fields': {u'RSSI1': -67.0, u'wght1': -631.0, u'time': 1.455527630507804e+18}, 'measurement': '3756782252718325761_1'}
2016-02-15T10:13:50+0100 [mqtt.client.subscriber           ] DEBUG: ==> PUBLISH (id=None qos=0 dup=False retain=False)
2016-02-15T10:13:50+0100 [kotori.daq.application.beradio   ] DEBUG: MQTT receive: topic=hiveeyes/25a0e5df-9517-405b-ab14-cb5b514ac9e8/3756782252718325761/1/message-beradio, payload=d1:_2:h11:#i1e1:wi-631e1:ri-67ee
2016-02-15T12:48:38+0100 [mqtt.client.factory.MQTTFactory  ] INFO: Stopping factory <mqtt.client.factory.MQTTFactory instance at 0x7f347c5b9a28>

2015 December

Platform

Prio 1

  • [x] Close sensitive ports
  • [x] Backupninja handler for InfluxDB
  • [x] Run with non-admin Grafana account
  • [x] Make system reboot-safe
  • [o] Run with non-admin InfluxDB account

Prio 2

  • [x] map domains

  • [x] change url in BERadio

  • [x] make application/index

  • [x] enhance 04-hiveeyes

  • [o] graph-screenshot for splash screen

  • [o] setup packages.hiveeyes.org

  • [o] Makefile deb: replace “build/virt” by variable

  • [o] Publish more user documentation

    • [o] Sending field names with underscore prefixes
    • [o] Sending timestamps

  • [x] Republish / link to more technical information from BERadio and Kotori

Software

2015 November

2015-11-06 rpo, amo

Wishlist

  • Aggregate measurements over time ranges (e.g. daily) and republish summary to MQTT

    • Provide reasonable “delta” values in relation to the point of last summary
    • Proposal for summary topics: hiveeyes/username/summary/foo/daily/bar
    • Schedule at: Morning, Noon, Evening

  • Threshold alerting

  • Weather information publishing

  • “Stockkarte” subsystem

  • Timeseries anomaly detection using machine learning

Todo

List of collected .. todo:: admonitions:

Todo

  • Add more convenience by adding appropriate Javascript widgets.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/acquisition/index.rst, line 166.)

Todo

Make distribution packages hiveeyes-php.zip and hiveeyes-php4.zip.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/acquisition/php.rst, line 33.)

Todo

  • Emphasize generation of custom “network”, “gateway” and “node” identifiers.
  • Add convenience by adding appropriate Javascript widgets.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/acquisition/php.rst, line 47.)

Todo

  • [o] After having export features, implement TelemetryClient->fetch(from, to) à la Grafana
  • [o] [docs] Link to Kotori: handbook/kotori, setup/getting-started and other appropriate sections

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/acquisition/php.rst, line 74.)

Todo

Describe how to order the parts, build your own sensor kit and finally operate it.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 75.)

Todo

Describe how to package the electronics and choose an appropriate power supply.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 76.)

Todo

Describe how to wire electronics with sensors.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 81.)

Todo

Describe how to get the parts and build one of the scale frames/sockets and how to connect it to the electronics.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 88.)

Todo

Describe how to start transmitting data from the new sensor node.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 98.)

Todo

Describe how to operate BERadio and forward telemetry data from the new sensor node to the backend.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 104.)

Todo

Describe how to receive and display telemetry data from different sensor nodes in Grafana.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 111.)

Todo

Describe how to start transmitting, receiving, publishing and visualizing telemetry data, all together now.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/do-it-yourself.rst, line 124.)

Todo

The constraints are somewhat harsh in all terms of efficiency, flexibility and robustness.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/goals.rst, line 69.)

Todo

There’s a another story about catching the colony from a nearby Robinia tree. More on that later from Richard.

(The original entry is located in ../HISTORY.rst, line 448.)

Todo

Get some pictures from the ESP8266 actually transmitting telemetry data here. Write some lines about the past and current setups at Open Hive.

(The original entry is located in ../HISTORY.rst, line 674.)

Todo

GraphViz flow graphs for giving insight into the communication paths between these components

(The original entry is located in ../HISTORY.rst, line 802.)

Todo

Add description about how to run an Nginx- or Apache-based reverse proxy in front of Kotori and Grafana.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/setup-backend.rst, line 162.)

Todo

Link to GPRS module capable of talking FTP

(The original entry is located in ../TODO.rst, line 713.)

Todo

Research whether there already is a convenient PHP library talking CoAP

(The original entry is located in ../TODO.rst, line 718.)

Todo

GraphViz flow graph

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/architecture.rst, line 38.)

Todo

GraphViz flow graph

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/architecture.rst, line 51.)

Todo

GraphViz flow graph

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/architecture.rst, line 101.)

Todo

TBD.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/architecture.rst, line 110.)

Todo

TBD.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/architecture.rst, line 115.)

Todo

Ask Richard for more links to sensor hardware and about how to assemble all stuff.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/index.rst, line 189.)

Todo

There is more software involved.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/index.rst, line 201.)

Todo

Ask Richard.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/index.rst, line 251.)

Todo

This section is just a stub. Please help writing some words about notifications with mqttwarn.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/notifications.rst, line 17.)

Todo

Write more text about this topic.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/topology.rst, line 16.)

Todo

GraphViz drawing

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/topology.rst, line 94.)

Todo

Use .. literalinclude in the future when projects are more interlinked:

.. literalinclude:: kotori/vendor/hiveeyes/application.py
   :lines: 1,3,5-10,20-

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/topology.rst, line 99.)

Todo

Discuss wording and describe use cases of network domain identifiers.

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/hiveeyes-one/topology.rst, line 174.)

Todo

Ask Clemens about code for Seeeduino Stalker

(The original entry is located in /srv/docs/organizations/hiveeyes/documentation/doc/source/vendor/open-hive/index.rst, line 151.)