rules delay to post vcc on deepsleep

[rene9900]

i have a eps8266-01 running ESPEASY 120, red led cut off for lowest power consume possible, it wake up on reset, and i ordered some LIPO's on ebay, want to try see how long it runs on battery. problem i have now is to make it publish VCC waking up then going to sleep, it works perfect if deep sleep is disabled but not if it is on, then all it publish is the online message, i made rules for delaying the boot so it has time to read the vcc correct..this is my rule set, can any of you locate the "problem"?

[TD-er]

Perhaps %vcc% returns something with a space in it?

In my tests, I do not have had a prefix '/' in the topic:

Code: Select all

Publish %sysname%/status,blah

So please test also with a simple string instead of %vcc% to eliminate the problem.

[rene9900]

i dont know if there is a difference from the rules if deepsleep is enabled or not? it publish perfectly vcc to my mqtt broker if deepsleep is disabled?

[TD-er]

Maybe vcc is not yet present when recovering from deep sleep?
Then it is an empty message.

[rene9900]

might be, but is there some way around this? what do others do?

[TD-er]

Just by looking at the code, it seems the value for vcc is only updated every 30 seconds. (and right after initTime(), but before a call to process the rules with "System#Boot" as event)
So as a test, you can set the initial 8 seconds to 38 seconds?
Just to see if the value is then updated.

You could move the publish vcc rule to the first block?

[rene9900]

i try change to 38 sec and still no vcc, log from node red:
11/2/2018 00.25.18node: 5435f871.00fb68
/8266-2/status : msg.payload : string[13]
"8266-2_Online"
11/2/2018 00.25.40node: 5435f871.00fb68
/8266-2/status : msg.payload : string[15]
"Connection Lost"

seems like it wont wait 38sec untill sleep :S

if i set the online publish in the delay it also stop publishing, but if i delete delay it publish vcc -1.0

[Domosapiens]

what do others do?

Connect Vcc to the A0 analog port

If you use Wemos D1 (has an internal 220K/100K divider):
Connect Vcc to the A0 analog port via a 100KOhm resistor
By adding a 100k , total resistance is 100k+220k+100k=420k.
So if the Voltage of a fully loaded Cell would be 4.2 Volt, the ADC of the ESP8266 would get 4.2 * 100/420= 1 Volt,
will give a Raw reading of 1023.
The True voltage then can be calculated by: voltage = AnalogRead(A0) * 4.2/1023;
Calibrate for a more accurate reading.

Create a Analog input Task with delay of 1 sec.

Then a rule, something like
On Analog#value do
Publish ..
Sleep
EndOn

With a Soshine 3.7V 3400mAh 18650 battery, the Wemos D1 with battery shield can run for approx. 10hr

[rene9900]

i would connect A0 but it is a esp8266-01 i'm using, i only have a few pins

[Domosapiens]

Sorry, overlooked that

[TD-er]

Did you also try to move the 2nd Publish line right after the first Publish line?
Thus in the event of reboot, not the event triggered by a timer.

[rene9900]

im not sure i understand how you mean after the first publish? seperated by comma or

On System#Boot do
timerSet,1,12
endon
On Rules#Timer=1 do
Publish /%sysname%/status,%sysname%_Online , Publish /%sysname%/VCC/VCC,%vcc%
endon

[grovkillen]

im not sure i understand how you mean after the first publish? seperated by comma or

On System#Boot do
timerSet,1,12
endon
On Rules#Timer=1 do
Publish /%sysname%/status,%sysname%_Online , Publish /%sysname%/VCC/VCC,%vcc%
endon

That should be

Code: Select all

On System#Boot do
 timerSet,1,12
endon

On Rules#Timer=1 do
 Publish /%sysname%/status,%sysname%_Online
 Publish /%sysname%/VCC/VCC,%vcc%
 timerSet,1,12
endon

[TD-er]

No I meant:

Code: Select all

On System#Boot do
 Publish /%sysname%/status,%sysname%_Online
 Publish /%sysname%/VCC/VCC,%vcc%
endon

But GrovKillen is the one to rules them ESP's. So if my suggestion is bogus, please say so

[rene9900]

I noticed that in arduino IDE the VCC do get reported before sleep, but not as MQTT..
ill try change the rules to the ones you suggested thank you

INIT : Booting Build nr:120
IP : Static IP :192.168.1.13
WIFI : Connecting... 1
WIFI : Connected!
MQTT : Connected to broker
Subscribed to: /8266-3/#
INIT : Boot OK
INIT : Deep sleep enabled
INIT : Reboot from deepsleep
EVENT: System#Boot
ACT : timerSet,1,12
SYS : 3.45
EVENT: VCC#VCC=3.45
Enter deep sleep...

[Domosapiens]

VCC#VCC=3.45

IIRC
Rules don't like Taskname and Value name the same

[rene9900]

No I meant:

Code: Select all

On System#Boot do
 Publish /%sysname%/status,%sysname%_Online
 Publish /%sysname%/VCC/VCC,%vcc%
endon

But GrovKillen is the one to rules them ESP's. So if my suggestion is bogus, please say so

your rules made this come out in my IDE, SYS sees the vcc but mqtt payload still say -1.00

INIT : Reboot from deepsleep
EVENT: System#Boot
ACT : timerSet,1,12
ACT : Publish /8266-3/status,8266-3_Online
ACT : Publish /8266-3/VCC/VCC,-1.00
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
MQTT : Topic: /8266-3/VCC/VCC
MQTT : Payload: -1.00
SYS : 3.46
EVENT: VCC#VCC=3.46
Enter deep sleep...

[rene9900]

VCC#VCC=3.45

IIRC
Rules don't like Taskname and Value name the same

just changed it but the result is the same

EVENT: System#Boot
ACT : timerSet,1,12
ACT : Publish /8266-3/status,8266-3_Online
ACT : Publish /8266-3/bat/VCC,-1.00
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
MQTT : Topic: /8266-3/bat/VCC
MQTT : Payload: -1.00
SYS : 3.46
EVENT: bat#VCC=3.46
Enter deep sleep...

[Domosapiens]

Does this helps?

Code: Select all

On bat#VCC do
 Publish /%sysname%/status,%sysname%_Online
 Publish /%sysname%/bat/VCC,%vcc%
endon

[rene9900]

Does this helps?

Code: Select all

On bat#VCC do
 Publish /%sysname%/status,%sysname%_Online
 Publish /%sysname%/bat/VCC,%vcc%
endon

still no vc post after online publish it go back to deepsleep

[budman1758]

Does this apply here?

https://www.letscontrolit.com/wiki/inde ... _Variables

Note the part about a custom compiled firmware?

[rene9900]

Does this apply here?

https://www.letscontrolit.com/wiki/inde ... _Variables

Note the part about a custom compiled firmware?

i did enable vcc by "true" before uploading to my 8266, and it does post vcc in every boot, as long as it is not from deepsleep, then it go to sleep before reading vcc, so it post only value of -1.00

This is arduino IDE serial output on normal boot :

INIT : Booting Build nr:120
IP : Static IP :192.168.1.13
WIFI : Connecting... 1
WIFI : Connected!
MQTT : Connected to broker
Subscribed to: /8266-3/#
INIT : Boot OK
INIT : Normal boot
EVENT: System#Boot
ACT : Publish /8266-3/status,8266-3_Online
ACT : timerSet,1,8
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
EVENT: Clock#Time=Mon,07:45
EVENT: Rules#Timer=1
ACT : On bat#VCC do
ACT : Publish /8266-3/bat/VCC,3.46
MQTT : Topic: /8266-3/bat/VCC
MQTT : Payload: 3.46
WD : Uptime 0 ConnectFailures 0 FreeMem 25432

This is Arduino IDE serial output with deepsleep enabled:

INIT : Booting Build nr:120
IP : Static IP :192.168.1.13
WIFI : Connecting... 1
WIFI : Connected!
MQTT : Connected to broker
Subscribed to: /8266-3/#
INIT : Boot OK
INIT : Deep sleep enabled
INIT : Reboot from deepsleep
EVENT: System#Boot
ACT : Publish /8266-3/status,8266-3_Online
ACT : timerSet,1,12
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
SYS : 3.46
EVENT: bat#VCC=3.46
Enter deep sleep...


this is my enabled rules:

On System#Boot do
Publish /%sysname%/status,%sysname%_Online
timerSet,1,12
endon
On Rules#Timer=1 do
On bat#VCC do
Publish /%sysname%/bat/VCC,%vcc%
endon

as serial show, the vcc publish part is ignored for some reason?

[budman1758]

Just for the hell of it have you tried turning deepsleep off and wait to see if VCC publishes at all? On boot and wake from sleep are different I imagine. Maybe it needs at least 60 seconds or so.
I'm just throwing stuff against the wall to see if anything sticks...

[grovkillen]

Just for the hell of it have you tried turning deepsleep off and wait to see if VCC publishes at all? On boot and wake from sleep are different I imagine. Maybe it needs at least 60 seconds or so.
I'm just throwing stuff against the wall to see if anything sticks...

+1
Good thinking Bud!

[budman1758]

I am wondering now what (if any) difference there is between "systemboot" and "wake from deepsleep" I think you may need a rule that fires when "wake from sleep" happens.
I noticed when I was watching the serial monitor on level 4 when I was testing my keypad app that only "some" system variables were called out in the log on a minute by minute basis. For instance, the ONLY time I ever saw the IP of the unit was on boot. Never saw it at all after that. Matter of fact I believe I only saw "time" and "uptime" regularly. Perhaps "vcc" is like that, only at boot.
Maybe it would work better set up as a regular task. Then you can control the delay time directly.
Hope some of my musings are helpful.

[Alpensepp]

Hi

Same problem here...

I use a ESP8266-12 and a BME280 Sensor with ESPEasy_mega-20180209.

The 8266 ist put in deep sleep, awakes every 300s and sends the BME280 data - perfect.

Now I started to use the ADC input to monitor the battery voltage. It works fine when the 8266 is awake all the time, but no ADC data is sent when awakening from deep sleep. The data from the BME280 is sent.

Any ideas?

best regards

Martin

[rene9900]

Just for the hell of it have you tried turning deepsleep off and wait to see if VCC publishes at all? On boot and wake from sleep are different I imagine. Maybe it needs at least 60 seconds or so.
I'm just throwing stuff against the wall to see if anything sticks...

i try changing my delay to 60 in rules like this:
On System#Boot do
Publish /%sysname%/status,%sysname%_Online
timerSet,1,60
endon
On Rules#Timer=1 do
On bat#VCC do
Publish /%sysname%/bat/VCC,%vcc%
endon

the result is that it do not wait 60 sec from deepsleep wakeup, but go straight to sleep after the boot message ignoring vcc again..
on ordinary boot with no sleep it do wait 60 sec then post vcc....
im clueless by now :S

INIT : Booting Build nr:120
IP : Static IP :192.168.1.13
WIFI : Connecting... 1
WIFI : Connected!
MQTT : Connected to broker
Subscribed to: /8266-3/#
INIT : Boot OK
INIT : Deep sleep enabled
INIT : Reboot from deepsleep
EVENT: System#Boot
ACT : Publish /8266-3/status,8266-3_Online
ACT : timerSet,1,60
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
SYS : 3.45
EVENT: bat#VCC=3.45
Enter deep sleep...

[grovkillen]

Please post all your setup using (if you want) my webdumper?

[rene9900]

Please post all your setup using (if you want) my webdumper?

i would but how? my mac can not run exe files

i tried adding Publish /%sysname%/Time,%systime%
within the timer1,10 event
the systime also do not get reported with sleep enabled..

if i put them all in rules before the timer the Console output do get systime and vcc but without any usable values, i get that the ntp need some secs to grab the time, and guess it is the same issue
with vcc reading, but how do i make a timer that holds deepsleep untill the unit has posted a reading?

EVENT: System#Boot
ACT : Publish /8266-3/status,8266-3_Online
ACT : Publish /8266-3/VCC,-1.00
ACT : Publish /8266-3/Time, 0:00
ACT : timerSet,1,10
NTP : NTP sync requested
NTP : NTP send to 192.36.143.130
NTP : NTP replied!
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
MQTT : Topic: /8266-3/VCC
MQTT : Payload: -1.00
MQTT : Topic: /8266-3/Time
MQTT : Payload: ,0:00
SYS : 3.46
EVENT: #VCC=3.46
Enter deep sleep...
state: 5 -> 0 (0)
rm 0
del if0
usl

[grovkillen]

https://www.letscontrolit.com/wiki/index.php/SleepMode

Note that its recommended to set the Message Delay to 0 in the advanced settings page, since you want the unit to broadcast messages asap in order to save precious battery power.

Have you done this?

[rene9900]

https://www.letscontrolit.com/wiki/index.php/SleepMode

Note that its recommended to set the Message Delay to 0 in the advanced settings page, since you want the unit to broadcast messages asap in order to save precious battery power.

Have you done this?

yes the message delay in advanced and the delay in devices on the VCC is both on 0

but on the wiki it say :
It will send all the sensor-readings at once (delays are ignored, except for Message Delay at the advanced settings page)

[grovkillen]

https://www.letscontrolit.com/wiki/index.php/SleepMode

Note that its recommended to set the Message Delay to 0 in the advanced settings page, since you want the unit to broadcast messages asap in order to save precious battery power.

Have you done this?

yes the message delay in advanced and the delay in devices on the VCC is both on 0

but on the wiki it say :
It will send all the sensor-readings at once (delays are ignored, except for Message Delay at the advanced settings page)

You're right. Maybe open a issue on Github?

[rene9900]

You're right. Maybe open a issue on Github?

i know not how

only way it works is by shortcutting positive and negative to coldboot it then it works . besides the missing delay

WIFI : Connected!
MQTT : Connected to broker
Subscribed to: /8266-3/#
INIT : Boot OK
INIT : Deep sleep enabled
INIT : Cold Boot
EVENT: System#Boot
ACT : timerSet,1,10
NTP : NTP sync requested
NTP : NTP send to 194.239.123.230
NTP : NTP replied!
EVENT: Clock#Time=Mon,13:30
pm open,type:2 0
EVENT: Rules#Timer=1
ACT : Publish /8266-3/status,8266-3_Online
ACT : Publish /8266-3/VCC,3.45
ACT : Publish /8266-3/Time,13:30
MQTT : Topic: /8266-3/status
MQTT : Payload: 8266-3_Online
MQTT : Topic: /8266-3/VCC
MQTT : Payload: 3.45
MQTT : Topic: /8266-3/Time
MQTT : Payload: 13:30
EVENT: Clock#Time=Mon,13:31
WD : Uptime 0 ConnectFailures 0 FreeMem 25624
SYS : 3.45
EVENT: #VCC=3.45
Enter deep sleep...

[Alpensepp]

Hi

Same problem here...

I use a ESP8266-12 and a BME280 Sensor with ESPEasy_mega-20180209.

The 8266 ist put in deep sleep, awakes every 300s and sends the BME280 data - perfect.

Now I started to use the ADC input to monitor the battery voltage. It works fine when the 8266 is awake all the time, but no ADC data is sent when awakening from deep sleep. The data from the BME280 is sent.

Any ideas?

best regards

Martin

I am a step further now.

When I put the ADC/VCC device as the first device in ESPEasy, the data is sent when awakening from deep sleep. But now, the BME280 data is not sent any more.
It seems, like the 8266 is going to deep sleep too fast, and therefore the last (ore later) devices are not able to send their data.

[grovkillen]

Please raise this issue up Github, referring to this thread.

[rene9900]

Please raise this issue up Github, referring to this thread.

I made a ticket on github about it.
https://github.com/letscontrolit/ESPEasy/issues/870

[grovkillen]

Please raise this issue up Github, referring to this thread.

I made a ticket on github about it.
https://github.com/letscontrolit/ESPEasy/issues/870

Great