Let's Control It

Hi i am using a battery powered temperature and pressure unit.
After i tried ESPMega 20180422 up to 20180426.
In all of this version i don't get the new values in my Broker.

OLD Version (which is working):

INIT : Booting version: (custom)
INIT : Rebooted from deepsleep #12
FS : Mounting...
FS : Mount successful, used 75802 bytes of 957314
CRC : No program memory checksum found. Check output of crc2.py
CRC : Settings CRC ...FAIL
CRC : SecuritySettings CRC ...OK
INIT : Free RAM:23632
INIT : I2C
INIT : SPI not enabled
EVENT: System#Wake
WIFI : AP Mode disabled
WIFI : AP Mode ssid will be ESP_TEMP_1-0 with address 192.168.4.1
IP : Static IP :2517280960
WIFI : Connecting XXXXXXXXXXXXXX attempt #0
EVENT: System#Boot
WD : Uptime 0 ConnectFailures 0 FreeMem 20896
ADC : Analog value: 776
EVENT: ESP_1_Volt#Volt=3.32
BMP : Temperature: 23.36
BMP : Barometric Pressure: 1016.23
EVENT: ESP_Temp_1#Temperature=23.36
EVENT: ESP_Temp_1#Pressure=1016.23
IP : Static IP :2517280960
ADC : Analog value: 776
EVENT: ESP_1_Volt#Volt=3.32
BMP : Temperature: 23.35
BMP : Barometric Pressure: 1016.24
EVENT: ESP_Temp_1#Temperature=23.35
EVENT: ESP_Temp_1#Pressure=1016.24
WIFI : Connected! AP: XXXXXXXXXXXXXX (E0:28:6D:87:DE:CA) Ch: 11 Duration: 3064 ms
EVENT: WiFi#ChangedAccesspoint
WIFI : Static IP: 192.168.10.150 (ESP-TEMP-1-0) GW: 192.168.10.254 SN: 255.255.255.0
EVENT: WiFi#Connected
MQTT : Intentional reconnect
MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:4E:72:1E
Subscribed to: /ESP_TEMP_1/#
EVENT: MQTT#Connected
WD : Uptime 1 ConnectFailures 0 FreeMem 20248
ADC : Analog value: 772
EVENT: ESP_1_Volt#Volt=3.30
BMP : Temperature: 23.33
BMP : Barometric Pressure: 1016.29
EVENT: ESP_Temp_1#Temperature=23.33
EVENT: ESP_Temp_1#Pressure=1016.29
EVENT: System#Sleep
EVENT: System#Sleep
SLEEP: Powering down to deepsleep...

New Versions:
INIT : Booting version: (custom) (ESP82xx Core 2_3_0)
294 : INIT : Rebooted from deepsleep #2
295 : FS : Mounting...
320 : FS : Mount successful, used 75802 bytes of 957314
330 : CRC : No program memory checksum found. Check output of crc2.py
360 : CRC : SecuritySettings CRC ...OK
463 : INIT : Free RAM:24184
463 : INIT : I2C
463 : INIT : SPI not enabled
476 : INFO : Plugins: 10 [Normal] (ESP82xx Core 2_3_0)
476 : EVENT: System#Wake
505 : WIFI : Switch on WiFi
505 : WIFI : Set WiFi to STA
517 : EVENT: System#Boot
550 : WD : Uptime 0 ConnectFailures 0 FreeMem 23376
567 : ADC : Analog value: 771
569 : EVENT: ESP_1_Volt#Volt=3.29
1154 : BMP : Temperature: 23.38
1155 : BMP : Barometric Pressure: 1016.08
1156 : EVENT: ESP_Temp_1#Temperature=23.38
1181 : EVENT: ESP_Temp_1#Pressure=1016.08
2204 : WIFI : Connecting XXXXXXXXXXXXXXXXX attempt #0
2204 : IP : Static IP : 192.168.10.150 GW: 192.168.10.254 SN: 255.255.255.0 DNS: 192.168.10.254
2219 : WIFI : Static IP: 192.168.10.150 (ESP-TEMP-1-0) GW: 192.168.10.254 SN: 255.255.255.0 duration: 2206 ms
2230 : EVENT: WiFi#Connected
2260 : Webserver: start
2262 : MQTT : Intentional reconnect
2288 : MQTT : Failed to connect to broker
2294 : WD : Uptime 1 ConnectFailures 0 FreeMem 21016
2294 : MQTT : Intentional reconnect
2315 : MQTT : Failed to connect to broker
2319 : ADC : Analog value: 772
2321 : EVENT: ESP_1_Volt#Volt=3.30
3271 : BMP : Temperature: 23.40
3271 : BMP : Barometric Pressure: 1015.96
3272 : EVENT: ESP_Temp_1#Temperature=23.40
3300 : EVENT: ESP_Temp_1#Pressure=1015.96
5398 : Current Time Zone: STD time start: 2018-10-28 03:00:00 offset: 60 min
5400 : EVENT: Time#Initialized
5427 : EVENT: Clock#Time=Fri,09:38
5458 : WIFI : Connected! AP: XXXXXXXXXXXXXXXXX (E0:28:6D:87:DE:CA) Ch: 11 Duration: 3066 ms
5459 : EVENT: WiFi#ChangedAccesspoint
5488 : WIFI : Static IP: 192.168.10.150 (ESP-TEMP-1-0) GW: 192.168.10.254 SN: 255.255.255.0 duration: 1 ms
5499 : EVENT: WiFi#Connected
5538 : ADC : Analog value: 776
5540 : EVENT: ESP_1_Volt#Volt=3.32
5636 : BMP : Temperature: 23.38
5636 : BMP : Barometric Pressure: 1015.95
5637 : EVENT: ESP_Temp_1#Temperature=23.38
5662 : EVENT: ESP_Temp_1#Pressure=1015.95
6636 : EVENT: Time#Set
6663 : MQTT : Intentional reconnect
6736 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:4E:72:1E
6749 : Subscribed to: /ESP_TEMP_1/#
6779 : EVENT: MQTT#Connected
6806 : EVENT: System#Sleep
6836 : EVENT: System#Sleep
6865 : SLEEP: Powering down to deepsleep...

There is no Event for Volt, Temperature and Pressure after MQTT connected.
Maybe there is only a little rule needed in the new versions now.

Hi,

since yersterday I was playing around with deep sleep, same effect. No data are received from my controller.

Wemos D1 mini, 4MB
Git-Version mega-20180413
Controller Domoticz

Last settings:
Deep Sleep setting: sleep awake time 90 sec, sleep delay 1800 sec
Device 1: INA219, delay 15 sec
Device 2: DS18B20, delay 15 sec

The protocol I can't see, because I have no access to the serial port of the Wemos, currently no other device available.

Wiki wrote: ↑28 Apr 2018, 13:13 Hi,

since yersterday I was playing around with deep sleep, same effect. No data are received from my controller.

Wemos D1 mini, 4MB
Git-Version mega-20180413
Controller Domoticz

Last settings:
Deep Sleep setting: sleep awake time 90 sec, sleep delay 1800 sec
Device 1: INA219, delay 15 sec
Device 2: DS18B20, delay 15 sec

The protocol I can't see, because I have no access to the serial port of the Wemos, currently no other device available.

I also have this problem

Wemos D1 mini Pro
ESP_Easy_mega-20180512_dev_ESP8266_4096.bin
Controller Domoticz
Sleep awake time:20
Sleep time:60 (for testing, normal 900)

Last working Release mega-20180403 (mega-20180405 not working)

Hi,

publishing from deep sleep works for me on a Wemos D1 with git-version mega-2018-05-06 pretty stable.

Only hints: power drain (might be a hardware issue with my step-up) and publishing after wakeup three times.

Hi.
OK i will try this version.
Thanks.

Hi,

after i updated my weather station from ESPEasy_mega-20180522 to ESPEasy_mega-20180826 i experienced the same issue:

System info data is sent after wake up (just for testing i added Voltage info in Devices). But the BME280 sensor data is not sent after wake up from deep sleep.
Sleep awake time: 15
Sleep time: 120
Wemos D1 mini
Is there a workaround? Or should i downgrade?

Cheeers
ED

EDsteve wrote: ↑06 Sep 2018, 20:10 [...]

I see a lot of reports about deepsleep and Core 2.4.x, not only at ESPeasy, but also on other projects.
Can you test this testbuild? https://github.com/letscontrolit/ESPEas ... -418520967
It introduces a queue to the controllers, which may help these issues. DeepSleep issues may still cause other issues though.

You are awesome. Thanks for the link.
I uploaded your test-build and it works without issues for now.

BTW: Is there a donate-button somewhere?

EDsteve wrote: ↑06 Sep 2018, 20:57 BTW: Is there a donate-button somewhere?

We're working on a Patreon page, stay tuned. It'll be announced very soon.

Thanks and very good to know it is working.
Like Grovkillen said, we are working on a Patreon page.

As a sneak-peek, you could look at these links. The texts are still beta, but the donation option should work
https://www.patreon.com/GrovkillenTDer

If you prefer to "just" give us a coffee you can add your support here: http://ko-fi.com/grovkillentder

TD-er wrote: ↑06 Sep 2018, 21:33 Thanks and very good to know it is working.
Like Grovkillen said, we are working on a Patreon page.

As a sneak-peek, you could look at these links. The texts are still beta, but the donation option should work
https://www.patreon.com/GrovkillenTDer

If you prefer to "just" give us a coffee you can add your support here: http://ko-fi.com/grovkillentder

You're that kid who told your friend what the gift was when you handed over the birthday present, right!?

Nope, I am the one to let people test the good stuff as soon as possible

Very cool options. Thx for the links. Click and pay is what i was looking for so Ko-fi it is

Coming back to topic:
After let it run for a while i realized that it only works 60% of the time.
I observe the MQTT broker and the MQTT messages from my deep-sleep-node are only send randomly. Couldn't find a logic behind it.
When i read the MQTT messages on my broker and the serial output from the sensor i get the impression that it sends data BEFORE it connects to the MQTT broker.

So when the sensor wakes up it should connect first to the MQTT broker and send data after. That's my understanding

A working example on my broker looks like this: And this is how it looks when no data is received on the MQTT broker: Here is the serial output after wake up (it connects to the broker AFTER it sends data?):
Not sure if the problem is on domoticz side. But maybe it's worth to play with the queue timings?
Cheers
ED

Thanks for the ko-fi! You got our first post as well (see ko-fi page).

Coool I didn't realize it's public though
But i like your thinking. Change to a open source job. First step to our new society
Between 10.000 and 100.000 people searching for ESPeasy every month. Should be just enough to make you quit your jobs. Well... depends on how high your status is

Well at this moment we are thinking about 1 - 2 days a week would be great.
I think it will still cost us money, but we'll see how far we can get.
Grovkillen just posted the announcement also on this forum.