Hi Rainer,[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 5:04 pmI had the same issue on Sunday and could change the camera resultion by using a direct command: http://module_ip/cam_setpar?framesize=value[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 2:53 pmRight ... it should initialize with camera.setup(x) ... but it returns a "1" and doesn't wake up the camera nor set the resolution[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 2:18 pm Hi bugs
Not very sure ... but camera setup(7) should initialize with 800*600
I have an other issue with camera.picture("filename") as this seems to save always a picture with 320*240
As I don´t want to change it by software, this was a sufficient solution for me.
Rainer
Thanks ... came to the same point right now and found some issues that might be interesting for ciccioCB
I found the following issues in conjunction with version 1.48.22 and an ESP32Cam
# wlog camera.setup(x) returns 1 but does not do anything with the resolution. I used camera.params("framesize", x) instead.
Am I right to expect camera.stop to remove the driver from memory which can not be reverted by camera.setup(x)
# WLOG camera.params("framesize", 0) sets resolution to 96x96 but returns 0 instead of 1; the same with other resolutions
# There seem to be 3 new resolutions/framesizes which are currently not in the table in the help file . This may create some irritating results with old annex-code that relies on the old table and now runs in the version 1.48.22 environment.
Code: [Local Link Removed for Guests]
0 96x96 <-new
1 160x120
2 176x144
3 240x176
4 240x240 <-new
5 320x240
6 400x296
7 480x320 <-new
8 640x480
9 800x600
10 1024x768
11 1280x720
12 1280x1024
13 1600x1200
The browser cache is sometimes a cause for that kind of problems - I tried to avoid this.
Perhaps someone can test that as well - before I make alerts without need
TNX
Peter