I have a solar-powered node that currently only reports the temperature from a DS18B20. But I am having trouble getting into OTA.
I am using mqtt persistent messages to enable or disable sleep, but I also have api enabled. I understand why I don’t want both api and mqtt, but without api, all of my entities are “unavailable”.
The only thing mqtt does here is to control the sleep mode.
I would like to stop using mqtt to control sleep, but I am curious if anyone has a suggestion to how I should proceed?
Seems bit too easy like your setting up nothing, but it works.
Once the helper switch is turned on the next time it comes out of deepsleep it goes into ota mode. Update the esp. Then turn ota helper off again and it returns to deepsleep.
Interesting- I hadn’t thought of doing it in an automation, but it looks like you are still using MQTT in the espHome node?
I tried creating a dummy switch that I could turn on and off from the front end, then in the espHome yaml file, I just need to test the entity. Here’s my latest test, but the yaml code is messed up:
# ###### Sleep #####
#Deep Sleep handler
deep_sleep:
id: deep_sleep_handler
run_duration: 15s
sleep_duration: 120s
binary_sensor:
- platform: homeassistant
id: ota_mode_test
entity_id: switch.solar_otamode
# This switch is controlled from the front end.
switch:
- platform: gpio
name: ${device_name} otamode
pin:
number: D4
mode: output
id: ${device_name}_d4
# Script to test if the otamode switch is on or off
script:
– id: test_sleep
mode: queued
then:
– delay: 10s
– if:
condition:
binary_sensor.is_on: ota_mode_test
then:
– logger.log: 'Skipping sleep, per ota_mode_test'
else:
– deep_sleep.enter: deep_sleep_handler
– script.execute: test_sleep
Is there no easy way to test an entity state (on or off)?
The error here is in the line: “mode: queued”
that “Mapping values are not allowed here”.
I stuck with mqtt to make it all as fast as possible to preserve battery in the dark months. I setup a mqtt to go into deepsleep early as soon as HA got temp and pressure readings. Shaves 8-9 seconds each time esp come out of deepsleep. I also set it up via mqtt to come out of deepsleep earlier to give readings more often if battery capacity is higher based on voltage of my 18650.
Update.
I created a virtual switch that I can control from the front-end (Lovelace).
But, I am having a heck of a time testing it in the yaml code. (Why isn’t there a simple if-then-else)?
Can someone point me in the right direction to at least not get format errors? Do I need a script or is there a better way to test the status of switch.solar_otamode?
My goal is to not need MQTT just to enable OTA.
(This script doesn’t work, but am I even on the right track)?
# Script to test if the otamode switch is on or off
script:
- id: test_sleep
then:
– if:
condition:
lambda: 'return id(switch.solar_otamode).state == "ON";'
then:
– logger.log: 'Skipping sleep, per ota_mode switch'
else:
– deep_sleep.enter: deep_sleep_handler
When the switch is on it won’t sleep. There is no ota mode. As long as the node is connected, you start the ota process by clicking update.
Setting that ha automation active will turn off sleep the next time the node wakes up. Then perform ota shut the switch off and it’s back to the sleep schedule.
Your esp is on a sleep rhythm based on the sleep duration, when it wakes up it checks if it is meant to remain awake, if yes then deep sleep is prevented, if no then it goes back to sleep. With deep sleep duration you can instruct the time until the next “awakening”
In HA / with the API method you essentially need 2 entities to achieve this, a boolean /switch and an input number. If you check my script above you will see the first as a binary sensor, the second as a sensor; both will need to be setup in HA as well (helper entities).
The script is run whenever the esp awakes.
My use case was that I wanted a device to sleep as long as we were asleep, saving maximum battery but not losing functionality during day time. As there is indeed no magic button I worked with dynamic sleep cycles moving from a longer cycle at midnight to shorter cycles early in the morning; once certain presence detectors were activated I disabled deep sleep.
Thanks for the assistance. Yes, I know how sleep works- I’ve been using it on Arduino projects for years. What confuses me is yaml.
Your code is one of the multitude of things I’ve tried, but when I try to toggle the entity: input_button.prevent_deep_sleep, the state becomes the date and time??
