Closed shokwaav closed 2 years ago
Oh never mind, seems I use the example.yaml from the dev version.
It seems the main branch hasn't been updated yet?
It seems the main branch hasn't been updated yet?
The main branch was becoming a bit hard to maintain, because I often have new stable changes ready, while ESPHome has not yet moved forward. When I pushed new code to main, it would break things for users that use old ESPHome versions. So instead, the main branch is now "dev", on which I always work against ESPHome "dev", Once I get to a stable release, I branch to a release branch, for example "release/2021.10.0" for the current stable release.
So in fact, the "main" branch could be considered stale now. I won't remove it yet though, to not bother people that are still using it.
So in fact, the "main" branch could be considered stale now. I won't remove it yet though, to not bother people that are still using it.
I see - I think I got it confused because I clicked the example.yaml in the main branch instead of following the link int he readme.
Would it be possible to change the name of the "main" branch example.yaml name so it would be less confusing?
Not really, because "main" is what's referenced in the existing configs that make use of it.
What was changed however, is the default branch for the repository.
If you browse to https://github.com/mmakaay/esphome-xiaomi_bslamp2 , then you will see that dev
is selected as the default branch. So via that route you should get the most recent data.
In time, I certainly want to get rid of the main
branch completely, possibly by renaming it to legacy
or so, but at this point I think it's too soon for that.
Describe the bug A clear and concise description of what the bug is.
I'm getting an error with importing the component on validating the esphome firmware.
Here is my .yaml file:
I'm using ESPHome v2021.10.3