Senseair S8 plugin

[sobolkz]

Checked in mega-20190928.
Then sensor was added in devices - new information was listed at the configuration page:

2019-09-28 17-36-53 ESP_Easy - Google Chrome.jpg (33.35 KiB) Viewed 5179 times

But first section looks like explanation of values of second section parameters.
Second section look's like some dummy settings with strange negative meaning (hmm, negative time? really? )
But, most interesting, is that now I can see sensor data then sensor wasn't connected:
INIT : Booting version: mega-20190928 (ESP82xx Core 2.6.0-dev, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support)
84 : INIT : Free RAM:30344
85 : INIT : Rebooted from deepsleep #29 Last Task: Const Interval timer, id: 1 - Restart Reason: Deep-Sleep Wake
87 : FS : Mounting...
111 : FS : Mount successful, used 76053 bytes of 957314
580 : CRC : program checksum ...OK
591 : CRC : SecuritySettings CRC ...OK
694 : INIT : Free RAM:27168
696 : INIT : I2C
696 : INIT : SPI not enabled
697 : EVENT: System#NoSleep=60
2966 : S/N: 0 - Type: 0 - - sensor wasn't detected, no it's S\N, perfect.
5344 : INFO : Plugins: 79 [Normal] [Testing] [Development] (ESP82xx Core 2.6.0-dev, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support)
5345 : EVENT: System#Wake
5517 : WIFI : Connecting access_point8 attempt #0
5532 : EVENT: System#Boot
6096 : Senseair:
6099 : EVENT: S8#CO2=3766.00 -What? CO2 level from undetected device?
6379 : ADC : Analog value: 0 = 0.000
6382 : EVENT: VBat#Vbat=0.00
7260 : Dummy: value 1: 755.25
7262 : EVENT: P_Hg#P_Hg=755.25
7298 : EVENT: P_Hg#=0.00
7307 : EVENT: P_Hg#=0.00
7316 : EVENT: P_Hg#=0.00
7936 : BMx280 : Detected BME280
8064 : WD : Uptime 0 ConnectFailures 0 FreeMem 19728 WiFiStatus 6

Same sensor (same as before) was used in this test environment. Look's like this new plugin changes was affecting to Senseair S8 data corruption.

[TD-er]

Hmm, is it me, or do you now have several issues about this issue?
What topic should we continue in?
Maybe even best to open an issue on GitHub, if it is still an issue after you've removed the task and added it again (and save the settings at least once)

[sobolkz]

Maybe even best to open an issue on GitHub, if it is still an issue after you've removed the task and added it again (and save the settings at least once)

Done, issue #2636 was added.
It's look like different issue from deep sleep (which was successfully fixed). I think we should close old discussion and, if it's important go to github. Or, for any other forum members I can post new updates here.