Add configurable plant identifiers
CSIGildea opened this issue · comments
Add ability to change device identifiers from config, to a user configured plant identifier value
e.g. "optiplex_790_MTea" over existing device id.
Finalized MQTT topic structure of relevance to this issue:
iotea/<plant_id>/triggers
Cloud -> Board
Trigger actions on the board, e.g: take a picture, rotate plant, water plant, send vitals to vitals topic
iotea/<plant_id>/vitals
Board -> Cloud
It will publish vitals when triggered in triggers (e.g. cron serverless function every 30 mins).
iotea/<plant_id>/camera
Camera Board -> Cloud
Send pictures to this queue when triggered in triggers.
Example use cases:
-
Telegram bot wants current vitals, sends trigger vitals request to iotea/<plant_id>/triggers, the board then publishes vitals to iotea/<plant_id>/vitals topic.
-
Cron Job Computer Vision wants to get picture for processing, sends picture request to iotea/<plant_id>/triggers, the board then publishes the picture to iotea/<plant_id>/camera topic. If the computer vision suggests the plant to then turn based on the image, it publishes a stepper turn request to iotea/<plant_id>/triggers, thus moving the plant for optimal light.
Update MQTT topics used "IoTea" instead