A regression was added in commit 01154e949, which prepends
clutter to the status0 JSON status message.
Example:
```
$ curl 'http://webcam/cm?cmnd=Status0' -u admin:password ; echo
{s}Webcam Frame rate{m}0 FPS{e}{"Status":{"Module":0,"DeviceName":"...
```
The response is not properly formatted JSON and breaks client software.
The problem occurs because a new case statement was added for the
purpose of injecting webcam stats into the JSON status message, but
a break statement is missing and execution falls through to the
following case, which prepends garbage to the output buffer.
With this one-line fix in place, the output is properly formatted:
```
$ curl 'http://tahoe-front-door-cam/cm?cmnd=Status0' -u admin:password ; echo
{"Status":{"Module":0,"DeviceName":"
```
Note that the prior case for FUNC_EVERY_SECOND is also missing a break
statement. That looks wrong to me but it's unrelated to fixing this
issue and I'm inclined to punt that concern to others who are more
familiar with this code.
* Added "cam":1 in the discovery message, so that we can create a home assistant camera.
* Update tasmota/tasmota_xdrv_driver/xdrv_12_discovery.ino
Co-authored-by: Erik Kunze <eku@users.noreply.github.com>
* Rearrange the newly added field by size, for better packing.
---------
Co-authored-by: Erik Kunze <eku@users.noreply.github.com>
* Add new webcam driver over latest dev. To use the old one, define USE_WEBCAM_LAGACY
* enable build without RTSP.
check pin_pwdn before using it n 0x105!!!
* more fixes around pwdn. Make wcresolution -1 set the resoltuion setting to 'disbale cam' value (15).
* fix task stop - wait for debug to leave-> prevents guru. pin task to core 0.
* split motion from other code. Add USE_WEBCAM_MOTION to control inclusion of motion code (big hit). Change from using USE_WEBCAM_LEGACY to USE_WEBCAM_V2
* logging minimisation - behind WEBCAM_DEV_DEBUG
* Add mutex to many camera functions.
* Allow stream to continue after wcinit command (and other commands which reconfigure).
* Adust retries on camera init, specifically log success if it retried.
Shorten messages to save rom.
I have seen fail of 0x103 and 0x20002 succeed on second try.
