FeatureRequest.md
There are a lot of ideas for further improvements, but only limited capacity on side of the developer. Therefore I have created this page as a collection of ideas.
Whoever has a new idea can put it here, so that it is not forgotten.
Whoever has the time, capacity and passion to support the project can take any of the ideas and implement them. I will provide support and help wherever I can!
Demo mode requires a working camera (if not, one receives a 'Cam bad' error). Would be nice to demo or play around on other ESP32 boards (or on ESP32-CAM boards when you broke the camera cable...).
as reading the Electricity or Water meter every few minutes only delivers apparent accuracy (DE: "Scheingenauigkeit") you could just as well take a picture with your Smartphone every so often (e.g. once a week when you are in the Basement anyway), then with some "semi clever" tricks pass this image to the model developed here, and the values than on to whoever needs them e.g. via MQTT. IMO: It is not needed to have that many readings (datapoints) as our behaviour (Use of electricity or water) doesn't vary that much, say, over a weeks time. The interpolation between weekly readings will give sufficient information on the power and/or water usage.
for example see Roi in the next picture.. in case of position change between the measurements set this state to true, if there is no change set it back to false. In a defined time window this movement can lead into an alarm state / water leak.. having this state in the mqtt broker can trigger functions like closing the water pipe valve and so on...
Let the device be normally in deep sleep state, and wake it up periodically to collect data and push it via MQTT or HTTP post.
Support ESP-NOW to reduce the overhead of connecting to wifi and mqtt
the above should enable battery powered applications
An other way to set deep sleep would be to enable it in a specific period (at night).
Implement a zip file compression for store and restore
Update the html to handle it
Implement a look up table for non linear analog meters
Implementation of an authentication mechanism.
Make the readout intervall configurable via MQTT.
Check different types of error (e.g. tflite not availabe) and generate an error on the html page.
To do:
Check during configuration, that ROI names are unique.
To do:
Decimal separator configurable for different systems
To do:
Implementation of a shifting additional to the initial rotation of the raw camera input
To do:
Implementation of two different independent readouts in one setup
To do:
Extend the MQTT client to also enable callbacks for configuration setting
To do:
implement callback for receiving information and override config.ini settings
change configuration management to handle online updates (currently changes need a restart)
think about the startup, as there the default config is loaded
Implementation of an an extrnal flash / lightning through GPIOs.
To do: