Button maps enhancements #3781
Merged
Button maps enhancements #3781
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Get rid of some magic numbers; - Make Multi State Input attribute general, as the button maps already provide a filter.
Albeit the button map works a ZHASwitch is never created.
For debugging unknown values.
0 here means the parser automatically does the right thing for "123", "0xff", etc. Note that hex values in the button maps must be expressed as string with 0x prefix, aka "0x0012" not "0012" or 12.
The commit replaces a few magic values with constants.
To run the validation `ajv` is needed (should work with other validators as well.
ajv -s button_maps.schema.json -d button_maps.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
lumi.ctrl_ln1.aq1andlumi.ctrl_ln2.aq1;lumi.sensor_switch.aq3,lumi.remote.b1acn01andlumi.remote.b186acn01in favor of button maps;