Replies: 1 comment 5 replies
-
Those options are created by Kauf's modified version of esphome components and you don't need them. There are ways to save values if you want to. If you want to know what those options you listed are for, you'll have to ask Kauf or look at the source code. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I have just seen a beautiful implementation of saving to flash for configuration items.
As per my understanding, some settings will be written to flash, so you can dynamically change values to the ESP without reflashing.
Unfortunately, there are certain things in the project I don't understand why they were used.
e.g.
force_adress, why specifying a special adress in flash?
globlal_force_adress: no idea for what it is used.
hash_forced: some sort of identification for "newest" implementation?
I think this is a very nice idea from @bkaufx!
Repo: https://github.com/KaufHA/PLF10/blob/main/kauf-plug.yaml
Is it worth / possible to have that in the main branch for ESPHome?
In my special case:
I would need such for my "pool manager" project.
So I can dynamically apply and save a new value for:
Warn_Min_Temperatur: e.g. 5°C
Warn_low_PH: e.g. 6
Cheers all!
Beta Was this translation helpful? Give feedback.
All reactions