You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Together with @MKO1640, we are considering to use the ESP32-e-Paper-Weather-Display by @G6EJD (thanks, David!) in order to display beehive information on a Waveshare e-Paper module [1].
We outlined how to use Arduino to acquire beehive data from the HTTP data export interface of Kotori at [2].
Objective
Therefore, we would like to improve the telemetry field name mapping for MQTT and HTTP not to yield the technical sensor names like temperature.0x77.i2c:0, humidity.0x77.i2c:0 or temperature.28ff641d8fc3944f.onewire:0.
Introduction
Together with @MKO1640, we are considering to use the ESP32-e-Paper-Weather-Display by @G6EJD (thanks, David!) in order to display beehive information on a Waveshare e-Paper module [1].
We outlined how to use Arduino to acquire beehive data from the HTTP data export interface of Kotori at [2].
Objective
Therefore, we would like to improve the telemetry field name mapping for MQTT and HTTP not to yield the technical sensor names like
temperature.0x77.i2c:0
,humidity.0x77.i2c:0
ortemperature.28ff641d8fc3944f.onewire:0
.This has already been done for the field name mapping for the Bee Observer project, so we would like to generalize that to the other telemetry adapters.
[1] https://community.hiveeyes.org/t/anzeige-der-daten-auf-einem-e-paper-display/3229
[2] https://github.com/hiveeyes/hiveeyes-epaper-display/tree/master/lib/hiveeyes
The text was updated successfully, but these errors were encountered: