Postpone 'outside Zigbee spec' max value restriction #1615
Closed
+12
−9
Conversation
This file contains hidden or 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
Collaborator
|
This should be worked around/fixed in converters instead. e.g.: Koenkk/zigbee-herdsman-converters#11177 |
Author
|
I see! Thank you for the tip |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi! I went off-spec with one attribute in tuya-zigbee-switch firmware.
So we can't use it since Z2M 2.7.2. It's not critical, but I don't have a quick workaround without an OTA update.
@Nerivec's PR should have came with a warning 😅 I didn't look close enough..
Can we comment that error for the next Z2M release?
It should give me time to push a fix, and users time to update. Then we can add it back.
I also added "(outside Zigbee spec)" to the error messages, to give some context.