Wemos D1 Pro with Senseair S8 boot loops

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Wemos D1 Pro with Senseair S8 boot loops

#1 Post by sobolkz » 12 Sep 2019, 16:50

Hi all!
There is strange situation with Senseair S8 plugin support at least it past releases with Wemos D1 Pro board.
Now I'm using mega-20190830, problem was fully investigated - then S8 sensor was added and deep sleep was activated board could not be fully booted. Board was going sleep after about 16 sec from awaking, there is serial console log:
NIT : Booting version: mega-20190830 (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
70 : INIT : Free RAM:29824
72 : INIT : Rebooted from deepsleep #151 Last Task: Const Interval timer, id: 1 - Restart Reason: Deep-Sleep Wake
75 : FS : Mounting...
513 : FS : Mount successful, used 76053 bytes of 13904898
575 : FS : Success garbage collection
632 : FS : Success garbage collection
1328 : CRC : program checksum ...OK
1345 : CRC : SecuritySettings CRC ...OK
3120 : INIT : Free RAM:21640
3122 : INIT : I2C
3123 : INIT : SPI not enabled
3125 : EVENT: System#NoSleep=60
6378 : S/N: 72b56eb - Type: 10e -
10896 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
10898 : EVENT: System#Wake
11458 : WIFI : Set WiFi to STA
11491 : WIFI : Connecting access_point8 attempt #0
11508 : EVENT: System#Boot
11897 : ADC : Analog value: 873 = 873.000
11906 : EVENT: VBat#Vbat=3.58
13491 : Senseair: co2 = 2581
13495 : EVENT: S8#CO2=2581.00
16209 : EVENT: System#Sleep
16668 : SLEEP: Powering down to deepsleep...
It's look like old problem with WiFi connection issues, but if S8 device was disabled after adding (no booting with it's support) serial console looks like:
INIT : Booting version: mega-20190830 (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
70 : INIT : Free RAM:29824
71 : INIT : Rebooted from deepsleep #150 Last Task: Background Task - Restart Reason: Deep-Sleep Wake
74 : FS : Mounting...
512 : FS : Mount successful, used 76053 bytes of 13904898
1207 : CRC : program checksum ...OK
1225 : CRC : SecuritySettings CRC ...OK
2999 : INIT : Free RAM:21792
3002 : INIT : I2C
3002 : INIT : SPI not enabled
3005 : EVENT: System#NoSleep=60
3200 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
3203 : EVENT: System#Wake
3764 : WIFI : Set WiFi to STA
3797 : WIFI : Connecting access_point8 attempt #0
3814 : EVENT: System#Boot
4200 : ADC : Analog value: 874 = 874.000
4210 : EVENT: VBat#Vbat=3.58
5771 : Dummy: value 1: 763.86
5775 : EVENT: P_Hg#P_Hg=763.86
6238 : EVENT: P_Hg#=0.00
6254 : EVENT: P_Hg#=0.00
6271 : EVENT: P_Hg#=0.00
7802 : WIFI : Connected! AP: access_point8 (88:DC:96:26:7F:0A) Ch: 4 Duration: 3805 ms
7804 : EVENT: WiFi#ChangedAccesspoint
7819 : WIFI : DHCP IP: 192.168.3.3 (ESP-Easy-2) GW: 192.168.3.1 SN: 255.255.255.0 duration: 16 ms
7834 : NTP : NTP replied: delay 10 mSec Accuracy increased by 0.819 seconds
7836 : Time adjusted by -1568298238999.43 msec. Wander: -435638399.72 msec/second
7838 : Current Time Zone: STD time start: 2019-10-27 03:00:00 offset: 360 min
7842 : EVENT: Time#Initialized
7860 : EVENT: WiFi#Connected
7881 : Webserver: start
7883 : firstLoopConnectionsEstablished
7886 : EVENT: System#NoSleep=60
7909 : WD : Uptime 0 ConnectFailures 0 FreeMem 10632 WiFiStatus 3
7914 : EVENT: Clock#Time=Thu,20:24
7928 : BMx280 : Detected BME280
7950 : WD : Uptime 1 ConnectFailures 0 FreeMem 10432 WiFiStatus 3
10445 : BME280: dew point 12.30C
15085 : BME280 : Address: 0x76
15086 : BME280 : Temperature: 23.46
15087 : BME280 : Humidity: 49.65
15088 : BME280 : Barometric Pressure: 1018.50
15093 : EVENT: BME280#Temperature=23.46
15556 : EVENT: BME280#Humidity=49.65
15569 : EVENT: BME280#Pressure=1018.50
15585 : ACT : TaskValueSet,12,1,1018.50*0.75
15601 : Command: taskvalueset
16084 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
16099 : Command: publish
18505 : ADC : Analog value: 898 = 898.000
18512 : EVENT: VBat#Vbat=3.68
19012 : Dummy: value 1: 763.87
19017 : EVENT: P_Hg#P_Hg=763.87
19478 : EVENT: P_Hg#=0.00
19492 : EVENT: P_Hg#=0.00
19505 : EVENT: P_Hg#=0.00
23262 : SaveToFile: free stack: 3424
23299 : FILE : Saved config.dat
23301 : SaveToFile: free stack after: 3424
23784 : SaveToFile: free stack: 3360
23862 : FILE : Saved config.dat
23863 : SaveToFile: free stack after: 3360
28218 : BME280: dew point 12.69C
28238 : BME280 : Address: 0x76
28240 : BME280 : Temperature: 23.50
28241 : BME280 : Humidity: 50.81
28242 : BME280 : Barometric Pressure: 1018.50
28247 : EVENT: BME280#Temperature=23.50
28712 : EVENT: BME280#Humidity=50.81
28726 : EVENT: BME280#Pressure=1018.50
28742 : ACT : TaskValueSet,12,1,1018.50*0.75
28759 : Command: taskvalueset
29247 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
29262 : Command: publish
33520 : ADC : Analog value: 877 = 877.000
33527 : EVENT: VBat#Vbat=3.60
35101 : Dummy: value 1: 763.87
35106 : EVENT: P_Hg#P_Hg=763.87
35566 : EVENT: P_Hg#=0.00
35579 : EVENT: P_Hg#=0.00
35593 : EVENT: P_Hg#=0.00
35626 : WD : Uptime 1 ConnectFailures 0 FreeMem 9064 WiFiStatus 3
37747 : SaveToFile: free stack: 3152
37785 : FILE : Saved config.dat
37786 : SaveToFile: free stack after: 3152
38273 : SaveToFile: free stack: 3424
38308 : FILE : Saved config.dat
38310 : SaveToFile: free stack after: 3424
38792 : SaveToFile: free stack: 3360
38867 : FILE : Saved config.dat
38869 : SaveToFile: free stack after: 3360
41973 : S/N: 72b56eb - Type: 10e -
49402 : Senseair: co2 = 2757
49408 : EVENT: S8#CO2=2757.00
52557 : ADC : Analog value: 888 = 888.000
52564 : EVENT: VBat#Vbat=3.64
53047 : Dummy: value 1: 763.87
53052 : EVENT: P_Hg#P_Hg=763.87
53514 : EVENT: P_Hg#=0.00
53530 : EVENT: P_Hg#=0.00
53544 : EVENT: P_Hg#=0.00
53582 : BME280: dew point 12.31C
54688 : BME280 : Address: 0x76
54689 : BME280 : Temperature: 23.52
54690 : BME280 : Humidity: 49.50
54691 : BME280 : Barometric Pressure: 1018.51
54696 : EVENT: BME280#Temperature=23.52
55162 : EVENT: BME280#Humidity=49.50
55177 : EVENT: BME280#Pressure=1018.51
55194 : ACT : TaskValueSet,12,1,1018.51*0.75
55211 : Command: taskvalueset
55707 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
55723 : Command: publish
61587 : EVENT: Clock#Time=Thu,20:25
63063 : ADC : Analog value: 892 = 892.000
63070 : EVENT: VBat#Vbat=3.66
64714 : Dummy: value 1: 763.88
64719 : EVENT: P_Hg#P_Hg=763.88
65181 : EVENT: P_Hg#=0.00
65195 : EVENT: P_Hg#=0.00
65211 : EVENT: P_Hg#=0.00
65254 : WD : Uptime 2 ConnectFailures 0 FreeMem 7664 WiFiStatus 3
67885 : EVENT: System#Sleep
68346 : SLEEP: Powering down to deepsleep...
All look's good (60 sec awake and 60 sec. sleep cycles was tested).
Also another serial sensor was checked - PMS7003, no same boot loops at the same softserial pins. There is console out while PMS7003 was used:
INIT : Booting version: mega-20190830 (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
70 : INIT : Free RAM:29824
71 : INIT : Rebooted from deepsleep #138 Last Task: Background Task - Restart Reason: Deep-Sleep Wake
74 : FS : Mounting...
512 : FS : Mount successful, used 76053 bytes of 13904898
576 : FS : Success garbage collection
635 : FS : Success garbage collection
1332 : CRC : program checksum ...OK
1348 : CRC : SecuritySettings CRC ...OK
3123 : INIT : Free RAM:21640
3125 : INIT : I2C
3126 : INIT : SPI not enabled
3128 : EVENT: System#NoSleep=60
3305 : PMSx003: using software serial
3335 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
3337 : EVENT: System#Wake
3898 : WIFI : Set WiFi to STA
3931 : WIFI : Connecting access_point8 attempt #0
3948 : EVENT: System#Boot
4338 : ADC : Analog value: 857 = 857.000
4348 : EVENT: VBat#Vbat=3.52
6071 : Dummy: value 1: 763.69
6075 : EVENT: P_Hg#P_Hg=763.69
6569 : EVENT: P_Hg#=0.00
6586 : EVENT: P_Hg#=0.00
6602 : EVENT: P_Hg#=0.00
7959 : WIFI : Connected! AP: access_point8 (88:DC:96:26:7F:0A) Ch: 4 Duration: 3841 ms
7961 : EVENT: WiFi#ChangedAccesspoint
7976 : WIFI : DHCP IP: 192.168.3.3 (ESP-Easy-2) GW: 192.168.3.1 SN: 255.255.255.0 duration: 16 ms
7991 : NTP : NTP replied: delay 10 mSec Accuracy increased by 0.275 seconds
7993 : Time adjusted by -1568296420297.65 msec. Wander: -435637894.53 msec/second
7995 : Current Time Zone: STD time start: 2019-10-27 03:00:00 offset: 360 min
7999 : EVENT: Time#Initialized
8016 : EVENT: WiFi#Connected
8037 : Webserver: start
8040 : firstLoopConnectionsEstablished
8042 : EVENT: System#NoSleep=60
8071 : WD : Uptime 0 ConnectFailures 0 FreeMem 10152 WiFiStatus 3
8079 : EVENT: Clock#Time=Thu,19:53
8096 : BMx280 : Detected BME280
8132 : WD : Uptime 1 ConnectFailures 0 FreeMem 9912 WiFiStatus 3
10431 : BME280: dew point 11.43C
10451 : BME280 : Address: 0x76
10452 : BME280 : Temperature: 23.17
10453 : BME280 : Humidity: 47.70
10454 : BME280 : Barometric Pressure: 1018.26
10459 : EVENT: BME280#Temperature=23.17
10922 : EVENT: BME280#Humidity=47.70
10937 : EVENT: BME280#Pressure=1018.26
10954 : ACT : TaskValueSet,12,1,1018.26*0.75
10975 : Command: taskvalueset
11502 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
11518 : Command: publish
12951 : PMSx003 : invalid framelength - 142
15558 : HTTP : C004 connection failed (1/10)
18189 : ADC : Analog value: 881 = 881.000
18197 : EVENT: VBat#Vbat=3.61
18723 : Dummy: value 1: 763.70
18728 : EVENT: P_Hg#P_Hg=763.70
19187 : EVENT: P_Hg#=0.00
19201 : EVENT: P_Hg#=0.00
19215 : EVENT: P_Hg#=0.00
20130 : EVENT: Clock#Time=Thu,19:54
28431 : BME280: dew point 11.35C
28451 : BME280 : Address: 0x76
28452 : BME280 : Temperature: 23.19
28454 : BME280 : Humidity: 47.40
28455 : BME280 : Barometric Pressure: 1018.24
28459 : EVENT: BME280#Temperature=23.19
28924 : EVENT: BME280#Humidity=47.40
28938 : EVENT: BME280#Pressure=1018.24
28955 : ACT : TaskValueSet,12,1,1018.24*0.75
28971 : Command: taskvalueset
29505 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
29524 : Command: publish
33642 : ADC : Analog value: 890 = 890.000
33670 : EVENT: VBat#Vbat=3.65
35305 : Dummy: value 1: 763.68
35310 : EVENT: P_Hg#P_Hg=763.68
35801 : EVENT: P_Hg#=0.00
35815 : EVENT: P_Hg#=0.00
35829 : EVENT: P_Hg#=0.00
35865 : WD : Uptime 1 ConnectFailures 0 FreeMem 8616 WiFiStatus 3
39851 : PMSx003 : invalid framelength - 70
47435 : BME280: dew point 11.31C
47955 : BME280 : Address: 0x76
47956 : BME280 : Temperature: 23.21
47957 : BME280 : Humidity: 47.22
47958 : BME280 : Barometric Pressure: 1018.22
47963 : EVENT: BME280#Temperature=23.21
48427 : EVENT: BME280#Humidity=47.22
48441 : EVENT: BME280#Pressure=1018.22
48459 : ACT : TaskValueSet,12,1,1018.22*0.75
48475 : Command: taskvalueset
49002 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
49018 : Command: publish
49065 : ADC : Analog value: 850 = 850.000
49073 : EVENT: VBat#Vbat=3.49
49583 : Dummy: value 1: 763.66
49588 : EVENT: P_Hg#P_Hg=763.66
50049 : EVENT: P_Hg#=0.00
50063 : EVENT: P_Hg#=0.00
50077 : EVENT: P_Hg#=0.00
63640 : PMSx003 : invalid framelength - 32772
64122 : ADC : Analog value: 857 = 857.000
64129 : EVENT: VBat#Vbat=3.52
65837 : Dummy: value 1: 763.66
65842 : EVENT: P_Hg#P_Hg=763.66
66333 : EVENT: P_Hg#=0.00
66347 : EVENT: P_Hg#=0.00
66361 : EVENT: P_Hg#=0.00
66401 : BME280: dew point 11.34C
66409 : WD : Uptime 2 ConnectFailures 0 FreeMem 8496 WiFiStatus 3
66429 : BME280 : Address: 0x76
66431 : BME280 : Temperature: 23.22
66432 : BME280 : Humidity: 47.29
66433 : BME280 : Barometric Pressure: 1018.23
66438 : EVENT: BME280#Temperature=23.22
66901 : EVENT: BME280#Humidity=47.29
66915 : EVENT: BME280#Pressure=1018.23
66932 : ACT : TaskValueSet,12,1,1018.23*0.75
66948 : Command: taskvalueset
67476 : ACT : Publish ESP_Easy/P_Hg/P_Hg,
67492 : Command: publish
68041 : EVENT: System#Sleep
68501 : SLEEP: Powering down to deepsleep...
How it can be fixed?

User avatar
grovkillen
Core team member
Posts: 3197
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#2 Post by grovkillen » 12 Sep 2019, 16:57

If you're using hw serial you need to disable serial logging.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Re: Wemos D1 Pro with Senseair S8 boot loops

#3 Post by sobolkz » 12 Sep 2019, 17:05

Yes, sure. it was checked too.
Same problem with HW serial (with disabled serial logging) connection and SW serial connection (for example GPIO14&GPIO12). As you can see such boot loops can be reproduced only if S8 device was activated (you can find it's SN). Also this boot loops will going up if device was disconnected (no serial transmission from sensor). It's look like some ESPEasy FW trigger was abnormally changed then S8 was added in active state and some data was received.

TD-er
Core team member
Posts: 1456
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#4 Post by TD-er » 12 Sep 2019, 21:54

Is the reported value of 2700+ ppm realistic?

Apart from that, can you please summarize it a bit?
Also please give the following info:
- RX pin
- TX pin
- How is the sensor powered? (is the voltage dropping when the S8 starts a measurement and the ESP boots + starts the WiFi connection?)
- Was it working before like this (older firmware version)?
- What is the set sensor interval?
- How long does it take the ESP to stay awake?
- Is the S8 sensor powered down when the ESP is sleeping? (otherwise it would not really be a battery saver to sleep)

sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Re: Wemos D1 Pro with Senseair S8 boot loops

#5 Post by sobolkz » 13 Sep 2019, 12:05

TD-er wrote:
12 Sep 2019, 21:54
Is the reported value of 2700+ ppm realistic?

Apart from that, can you please summarize it a bit?
Also please give the following info:
- RX pin
- TX pin
- How is the sensor powered? (is the voltage dropping when the S8 starts a measurement and the ESP boots + starts the WiFi connection?)
- Was it working before like this (older firmware version)?
- What is the set sensor interval?
- How long does it take the ESP to stay awake?
- Is the S8 sensor powered down when the ESP is sleeping? (otherwise it would not really be a battery saver to sleep)
Hi, TD-er
OK, one by one:
- As I see it isn't important, which PIN's was used for this issue - last time S8 was connected to the GPIO14 and GPIO12 (D5&D6 pins of D1 mini Pro board). Same issue if it was connected for example to GPIO5 and GPIO4 (D1&D2).
- Sensor power, by default was connected to 5V PIN of my board. But separate power line (with GND interconnected) also checked - no luck. No power drops, PS was good with power budget at least 2 Amperes. As I see power at sensor not less about 4,7 V if it's powered from 5V board's PIN. And about 5V if it was commected directly to another PS.
- I'ts new installation and I can't answer about old firmware expirience. Also PMSX003 support was added only to the "test" and "dev" versions of ESP Easy firmware and I can't use "normal" for it.
- Sensor interval is about 15-20 sec (both was checked).
- Sleep time - as configured, 60 sec. Awake time as you can see in firsh log - about 16 sec, not as configured (60 sec).
- No, S8 was connected and powered all the time (also in sleeping). As you wrote - it isn't best way for battery power, but I'll change power scheme when issue with S8 will be fixed. I think it'll be MOSFET key.
Also - I have another board (same type). This board was checked too - same issue.
This boot loop can't be released if S8 was disconnected from RX\TX and power (no data transmission and power consumption).
Most weird that I can't check settings because board wasn't booting, I can see onle serial logs. After this issue this board can be loaded only after factory reset. It can't be loaded if there is no any PINS was connected too (only power connected).
And, strange for me is that S8 was was examined each time without it's connection state checking. Look here - S8 wasn't connected, but there is it's blank S/N and some timeout after it:
7615 : S/N: 0 - Type: 0 -
12133 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
Here it's connected, but same timeout:
6378 : S/N: 72b56eb - Type: 10e -
10896 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2.6.0-dev, NONOS SDK 3.0.0-dev(c0f7b44), LWIP: 2.1.2 PUYA support)
I will try to check full issue prerequisites and add new information ASAP.

TD-er
Core team member
Posts: 1456
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#6 Post by TD-er » 13 Sep 2019, 12:59

As I see it isn't important, which PIN's was used for this issue
With the pins you mention now, it is indeed not really important.
But if pin 0, 2 or 15 would have been used, then it is important.
These must have a very specific state at boot or else the node will not boot in the correct mode.
And, strange for me is that S8 was was examined each time without it's connection state checking. Look here - S8 wasn't connected, but there is it's blank S/N and some timeout after it:
As long as the plugin is active (enabled) it will try to do its stuff. One of the things is reading the connected device.
This could also be the key issue here.
What if the S8 is in some undefined state after the deep sleep, which causes the ESP to "hang" waiting for a timeout.
If it does just wait and not call the delay() function to process background tasks, then it will reboot due to watchdog timeouts.
Similar to when it is no longer connected (or never has been connected)

I will look into this issue.
Can you make an issue for it on GitHub?

TD-er
Core team member
Posts: 1456
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#7 Post by TD-er » 13 Sep 2019, 14:31

Just a quick update.
processCommand() (Modbus_RTU.ino) does call delay() while waiting for data, and it does take some timeout into account.
But it does not return something to indicate there was a timeout, nor if nothing was received.

So I can imagine this will cause some issues as it will hit timeouts over and over again.

sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Re: Wemos D1 Pro with Senseair S8 boot loops

#8 Post by sobolkz » 13 Sep 2019, 15:47

TD-er wrote:
13 Sep 2019, 12:59
I will look into this issue.
Can you make an issue for it on GitHub?
Perfect. Will wait you results.
I'm not registered at GitHub, but I'll register tomorrow morning and add this.

sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Re: Wemos D1 Pro with Senseair S8 boot loops

#9 Post by sobolkz » 14 Sep 2019, 05:48

TD-er wrote:
13 Sep 2019, 12:59
Can you make an issue for it on GitHub?
Done, issue #2616 was reported.

P.S. no any additional information. Problem can be reproduced at 100% if test scheme was created with Wemos D1 mini Pro, SH1106 framed plugin, I2C BME280 and active Senseair S8 plugin. If plugin wasn't enabled after task adding - no any problems with deep sleep.

User avatar
grovkillen
Core team member
Posts: 3197
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#10 Post by grovkillen » 14 Sep 2019, 09:29

Please observe that the S8 is not built for deepsleep. You would want to have the LP8 for that.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

sobolkz
Normal user
Posts: 6
Joined: 12 Sep 2019, 16:30

Re: Wemos D1 Pro with Senseair S8 boot loops

#11 Post by sobolkz » 14 Sep 2019, 10:18

grovkillen wrote:
14 Sep 2019, 09:29
Please observe that the S8 is not built for deepsleep. You would want to have the LP8 for that.
Yes, sure. Also, as I know - there is no sleep mode support in PMSX003 plugin. I'll add MOSFET key for it with free GPIO.

TD-er
Core team member
Posts: 1456
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#12 Post by TD-er » 14 Sep 2019, 11:35

grovkillen wrote:
14 Sep 2019, 09:29
Please observe that the S8 is not built for deepsleep. You would want to have the LP8 for that.
Not sure if that one is already implemented in the plugin code.

User avatar
grovkillen
Core team member
Posts: 3197
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Wemos D1 Pro with Senseair S8 boot loops

#13 Post by grovkillen » 14 Sep 2019, 11:40

No it's not. But as a heads up about trying to do deepsleep with the S8.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 17 guests