Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short version:
This replaces the 'misc/sampleconfigs/gpio_settings.ini.sample' (untouched since 11 months) with the current 'components/gpio_control/example_configs/gpio_settings.ini', which contains the latest syntax
A few example buttons were enabled by default. I changed these to disabled too. Reason: I think it's no good idea to configure concrete GPIO ports (without knowing the user's hardware setup!), just because a user activated the GPIO control component at installation.
Longer version:
Background for bullet #1 was that, after Release 2.3, a user reported an issue with a shutdown button reacting too quickly on a fresh install ( #1509 ). This was quickly resolved after identifying a missing line in the GPIO sample config.
When we updated and extended the GPIO component few months ago, we also added an syntax-auto-update for old-style configs.
Maybe this was the reason we did not also update the sample config in the misc folder. At least for the postponed shutdown button (which didn't work before 2.3 either) these auto-fixes did not suffice completely. So it's safer to bring the sample config to the latest syntax.