๐ Telemetry API
Why this is needed
We want our devices as well as customerโs own hack-projects to be able to stream data to us so that
- beekeepers can track their apiaries in web-app telemetry dashboards
- beekeepers can correlate data to get insights
- we can generate Alerts
Evaluation of the honey bee colonies weight gain during the intensive foraging period
Low volume metrics that Entrance Observer can send to Web-app
- temperature (min interval - 10 min)
- humidity (min interval - 10 min) - see Humidity monitoring
- weight (min interval - 10 min) โ [Beep.nl weight telemetry integration](https://www.notion.so/Beep-nl-weight-telemetry-integration-a72ed2ce25004a3c853bb41fa08abc48?pvs=21)
- bee counts at the hive entrance (min interval - 10 sec)
- how many worker bees have gone in and out
- how many of them had varroa mite
- how many of them had pollen
- how many guard bees are detected
- how many drone bees are detected
- how many queen bees are detected โ Detect queen mating from entrance video
- how many worker bees have gone in and out
- hornet count (min interval 10 sec) โ Hornet attack detection
- audio noise average volume (min interval - 1 sec)
- this should not be confused with actual audio stream that would be sent with 6-channel audio monitoring as part of Robotic Beehive, because Entrance Observer has limited amount of USB ports so we canโt have mics there
AC
- provide a flexible graphQL API in telemetry-api to store timeseries metrics
- store this data in telemetry-api time-series storage. MySQL is the current fallback when a dedicated time-series database is not justified.
- render time-series graphs directly in the web app by querying telemetry-api through
graphql-router