Closed TheNexter closed 1 year ago
I think is good, if i miss something, sorry and say me what i need to change 😅
You could use ESPHome native methods instead of lambdas. Did you use the lambdas on purpose?
You could use ESPHome native methods instead of lambdas. Did you use the lambdas on purpose?
This method allow the scooter / ebike disconnect from the ESP by going outside, comeback at what ever pourcentage you want and this method gonna work ;)
ESPhome do not understand the change between null (disconnected) and 62% (come back to home and connected) with the default automation method provide by ESPhome (on_value_range), you can trust me i try many time yesterday 😅
I have try at my office, this method work like a charm now ;) Stop at 80% and enable charge if under 80%
I will provide another solution tomorrow. We can decide afterwards which solution should be added to the docs. It's hard to explain what I mean. :-)
I will provide another solution tomorrow. We can decide afterwards which solution should be added to the docs. It's hard to explain what I mean. :-)
Oh ok ;)
What do you think about this approach: https://github.com/TheNexter/esphome-jbd-bms/blob/main/yaml-snippets/esp32-ble-deepsleep-limit-charging-automation.yaml
FYI I've added a reboot_timeout: 0s
to some components (wifi
, api
, mqtt
). Without this setting the ESPHome node will reboot every 15 minutes if there is no wifi
, api
or mqtt
connection.
Oh your approach looks better than mine, your experience with esphome is clearly here 😄
I am gonna try your approach tomorrow ;)
readme updated to include an explanation of automation to preserve battery life
Closes: #49