Store product key in config entry #170
Merged
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
ultratoto14
approved these changes
Nov 19, 2020
rospogrigio
approved these changes
Nov 19, 2020
PaulCavill
pushed a commit
to PaulCavill/localtuya
that referenced
this pull request
May 10, 2024
* Attempt to fix max header length. * Refactor main config
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.
Store the device product key when creating a config entry. It will be automatically updated by the discovery in case it's missing in an existing config entry (e.g. prior to this PR or for YAML config). When available, it be presented as the device model in the device registry.
I'm preparing a bit for the future "device database"-thing I've been talking about. It's a bit in the future, but I might as well do small tidbits when I get a feeling.