CaCO3

So if I understand you right, there is not an easy solution for this issue. How should we proceed? Should we revert the changes I did to the html file...

Since there is no clear solution for this I will revert https://github.com/jomjol/AI-on-the-edge-device/commit/ec00e943dababa18b9b471b142003283df3dade8 and remove this issue from the `16.0.0` release

I am closing this request, because it is not feasable with the way the project works. We would have to implement video recording and realtime analyzation. The ESP for sure...

According to https://github.com/jomjol/AI-on-the-edge-device/issues/2625#issuecomment-1773154210 it should work. How ever there seems to be a restriction: https://github.com/jomjol/AI-on-the-edge-device/discussions/3054#discussioncomment-9271256 Can you test if it works with TLS 1.2?

@LordGuilly Can you provide some documentation how you generated your certificate? This seems not to be clear. I looked at https://tasmota.github.io/docs/TLS/#implementation-notes but there is a lot of information and not...

I agree that it is not good practice. How ever @jomjol (the core dev) once decided he does not want to have the responsibility to protect the device (see eg....

> files containing credentials write only Yes, I think that is the only feasable way unless we restrict the access to the UI.

There is now basic authentication available for the Web UI which can be used (although it is not a good solution it is better than nothing).

Did you try if you could use [Gray Scale](https://jomjol.github.io/AI-on-the-edge-device-docs/Parameters/#parameter-grayscale) mode to work around this?

Not sure what [CamSpecialEffect](https://jomjol.github.io/AI-on-the-edge-device-docs/Parameters/#parameter-camspecialeffect) actually does, but maybe give it a try. @SybexX FYI