sfromis

Yes, the links above shows that such a code change was merged. I'd still recommend against using the syntax error of JSON data with unquoted hex numbers, as JSON is...

There is no direct support for OTA migration from one firmware project to another. It may work in "many" cases, but do test with a similar setup before assuming that...

Here's the log from a cold start of tdm: ``` 2020-02-25 14:09:46 [INFO] ### TDM START ### 2020-02-25 14:09:54 [DEBUG] MQTT: Subscribed to tele/#, stat/#, cmnd/#, +/tele/#, +/stat/#, +/cmnd/# 2020-02-25...

Thats about the only thing that looks healthy. Typical  Next start of the tool, the affected devices are not even on the screen, not saved in devices.cfg. The single...

Checking my MQTT log, I see these commands, for each device, with the expected responses: ``` nodemcu6/cmnd/FullTopic nodemcu6/cmnd/template nodemcu6/cmnd/gpio nodemcu6/cmnd/buttondebounce nodemcu6/cmnd/interlock nodemcu6/cmnd/blinkcount nodemcu6/cmnd/pulsetime1 nodemcu6/cmnd/pulsetime3 nodemcu6/cmnd/pulsetime5 nodemcu6/cmnd/pulsetime7 nodemcu6/cmnd/modules nodemcu6/cmnd/switchdebounce nodemcu6/cmnd/mqttlog nodemcu6/cmnd/pulsetime4...

A possibly interesting detail is that the opening screen, after discovery, has Module (as the only field) detected for 1/3 of the devices, but a different set if starting again...

What is valid is the spelling `WcAELevel` already mentioned in the first post.

I saw a clear difference with `WcAELevel` values 0/1/2. Test case was the camera pointed at a lamp, with significant difference in the captured glare around the lamp.

``` {"WC":{"Stream":1,"Resolution":8,"Mirror":0,"Flip":0,"Saturation":0,"Brightness":0,"Contrast":0,"SpecialEffect":0,"AWB":1,"WBMode":0,"AWBGain":1,"AEC":1,"AECValue":204,"AELevel":2,"AECDSP":1,"AGC":1,"AGCGain":5,"GainCeiling":0,"GammaCorrect":1,"LensCorrect":1,"WPC":1,"DCW":1,"BPC":0,"Colorbar":0,"Feature":0,"Auth":0,"Rtsp":0}} ``` Did you try my specific test case? More generally, you should not expect a difference from just setting a different auto exposure level, only in circumstances pushing...

Again, did you try my *specific* test case? And I disagree that you should always see the whole frame change.