Trying to make a weather station for my garden. I would like to be able to send OTA to my node when in deep sleep.
I have made the suggested implementation using Mqtt using an ON and an OFF message. These are controlled by a switch from the UI. I use Node Red and can send the required messages. However, when I want the esp to sleep it never wakes up again to send data, but strangely I can use the Mqtt ON to wake it. If I remove the Mqtt and just do plain deep sleep it works just fine. I am going nuts.
I am a total newbie in ESPHome, but here’s how I handle OTA and sleep in my garden. (NOT on ESPHome, but maybe it will give you an idea.)
To go into OTA, I publish a message to the garden ESP command topic with the message “OTA”. When the garden ESP wakes up, it gets the message to set the otaFlag. When the otaFlag is set, ESP.deepSleep is never executed, so the program finishes setup() and drops into loop() where the OTA is handled.
void setup(){
....
if (!otaFlag) { //If the otaFlag is set, then drop into loop to wait for the ota upload.
// ---------- Sleep ----------
pinMode(D0, WAKEUP_PULLUP);
ESP.deepSleep(sleepSeconds * 1000000);
}
}
void loop(void) {
// We only get here if the otaFlag is true, meaning the ESP never went to sleep.
ArduinoOTA.handle();
ArduinoOTA.onEnd([]() {
otaFlag = false;
});
}
Again, this is not done in ESPHome, but presented as an idea.
Hi, i have it like this (complete example below) and it works without any issues. I don’t subscribe to the “off” message within the ESP.
If you can “wake” your ESP with the “ON” message it’s not in deep sleep, the wifi is not active during deep sleep and the ESP can’t receive any messages in that state (that would defeat the purpose of saving battery).
I have a script that I trigger in Home Assistant when I want to update the sensors with something (I have the same for all of them). And when the ESP wakes up it sees the payload “ON” and prevents deep sleep. Then I send the update and when that is complete I send the “OFF” to the MQTT server and reboot the ESP, and everything is then back to normal. I could also monitor the “OFF” payload and reboot automatically I guess.
The only problem is that when you go to update the ESP it is almost always in the beginning of the deep sleep cycle so the wait time is always close to maximum (feels like that anyway ).
@veirum yes, like @stevemann says, the “esp-page” I was referring to is in HA and just has all of the esphome stuff including a quick way to just activate these scripts , that was what I meant.
No dashboard, just added everything on the same standard Lovelace page. I went to the integration page under Configuration → Integrations. Opened the ESP-boards and added everything were it says “Add to lovelace”.
On the page were everything is added (I mostly use Glance or just Entities-cards) I added a new card with buttons for the script that is in my post above. This way I can then activate the OTA-scripts on and off and see most of the ESP-boards in the same view.
When I need to change something in the ESP code or just update the little things I first go and edit that under the ESPHome dashboard. I then activate the script to send the persistent message for OTA ON. Then we just have to wait for the ESPs that are on battery to wake up, recieve the OTA on that pervent the deept sleep and stay on. From there we just issue the update over the air (OTA) through the ESPHome dashboard, when the compilation is done and the ESP has recied the update I usually check some of the logs, and then activate the other script for OTA Off. After that all the ESPs have to reboot in order to be able to go back to sleep again. I guess you could also active the OTA off script before doing the update through the ESPHome dashboard but I usually wan’t to see that ewverything runs as it should before I let the things go to sleep again. There is of course some battery drain when doing this since the ESP will stay on until you reboot the device again but it’s not that often a new firmware is required.
Ah, the scripts are just as it says scripts, not to be added directly on a lovelace card… that needs to be added under Scripts in Configuration, you need to add two scripts, one for on and one for off.
I am using two old 18650 from an old laptop battery I butchered a long time ago. Holds up quite well together with a small solar panel, I never recharge them. My design springs from this one (link) if we are talking about the temperature-station. But I built mine in a blocked off bird house with two 3D-printed Stevenson Screens (Thingiverse) on either side of it. On of the screens have a DS18B20 and the other one houses a BME280.
i use a voltage divider (680 and 300 ohm) as the ADC on 8266 only goes to 1V
when i messure with voltmeter i get 3.2 before the divider and about 0.95 after
2.266666666666667 is of course the theoretical value to multiply with,
my problem is that i only get 0.73V, i assume i do something to wrong but cant figure out what
for some reason mqtt do not work, i use the chrome app lens to check topics and nothing happens when i execute the scripts
my broker Mosquitto is setup to allow anonymous posting as its not exposed to the outside world anyway
EDIT EDIT:
so it do work, i guess the access from outside my raspberry pi (but STILL on local network) is not allowed, its also the first time my local devices need access to home assistant
This will depens on what kind of voltage divider you set up. If you have a Lolin (Wemos) board or something similar (and I believe the NodeMCU also has this) there is a voltage divider already built in so that the A0 accepts 3.3V input at max. Your setup needs to be configured to account for this and your resistors might need to change. You should be fine with having for example R1=300 and R2=1000 to get roughly 3.2V from a max 4.2V battery.
If you are using the VCC on a ESP8266 board you must first remove all connections to A0. There is some useful information here: Analog To Digital Sensor — ESPHome
).
, that was what I meant.
.
