In case of using the Terkin Datalogger firmware with the Hiveeyes.org
environment please follow this scheme for the TTN
and replace upper case strings with your individual lower case namings
without additional dashes.
hiveeyes-USER will become your InfluxDB
client data base and
LOCATION-NAMEOFHIVE_sensors will be your InfluxDB
settings.py networking section enter your TTN device credentials
(copy and paste from TTN console) and deactivate all telemetry targets
CayenneLPP over TTN-LoRa.
datarate defines the
bandwidth and spreading factor
for the joining process while
'adr' = True enables the
Adaptive Data Rate
for subsequent data packages depending on the LoRa signal quality.
CayenneLPP is our sensor data encoding standard of choice in conjunction with LoRaWAN transmissions. It ensures small data packages and consequently little air times for actually sending the data.
The upstream CayenneLPP Python library
has been extended to also encode
In order to forward those variables into your TTN payload you would need to insert
the given decoder.js code into your TTN App. In TTN console under Payload Formats
The decoder function is backwards compatible to the built-in CayenneLPP decoder.
PutsReq HTTP Endpoint¶
It’s a free service for inspecting and rewriting HTTP POST requests to a response that our data acquisition service (DAQ) at swarm.hiveeyes.org will be able to understand and process.
A Telegram bot for interacting with the device via LoRaWAN downlinks is available from the telegram_terkin_ttn_bot.py file.
Currently these two capabilities are implemented:
/unpausefor pausing and continuing the inclusion of sensor data into the payload, e.g for times when you are working on the bees hives.
/sleep MINfor remotely setting the Deep Sleep interval in
/sleep 0to return to the interval defined in your device configuration.
Please see Telegram bot documentation for how to get started with a bot at first. An always-on server under your control will be needed to run the bot. Remember that downlink messages to the device are not being sent immediately but shortly after an uplink message has been successfully received by the network.