I have been working on a project that adds a LoRa module to the small SEEED ESP32S3 Sense board which has an OV2640 camera and SD card.
The images taken by the camera can be saved to SD and the transferred via LoRa to a remote receiver, there would be wildlife or security monitoring applications.
A low deep sleep current is important for a battery powered application and the ESP32S3 and LoRa part has a deep sleep current of 12uA.
The camera has an advertised deep sleep current of 3mA, which is about right when the camera is first powered up. You could probably live with 3mA, solar panel on the battery etc.
However if you use the camera, there does not appear to be any way of getting it back into the initial power on state and the 'deep sleep' current is 90mA.
The OV2640 appears to be configured via I2C, but an I2C scanner does not detect it.
The ESP32CAM, which also uses the OV2640, has a GPIO turning off the regulators that power the camera and that board does then have a deep sleep current of circa 2.5mA.
Any ideas on how to reduce the 90mA the OV2640 consumes, you would think if it can be configured for use, you could also reverse the configuration by putting all the registers back to the power up state.
Sure I could do that or in my case I would prefer a more flexible approach and use a circuit based on a PCF8563 RTC. That circuit would connect to the host via I2C and you can then programatically set sleep times of seconds, minutes, hours or days. Deep sleep current is 2uA.
However it would be good for some applications if you did not need to power down the board all the time (to kill the 90mA) but perhaps just pause it in light sleep mode.
Storing images to SD then using LoRa to transmit them elsewhere seems to me a mismatch. As the name LoRa implies, it's long range, but it's relatively slow. If the distance isn't great, you might be better served by 2.4 GHz WiFi.