DDF prevent load/store incomplete sensors with endpoint 0xFF #5757
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
Member
Author
|
@Smanar there were other devices we've seen this, I think this PR should fix them as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Auto generated DDF draft sensors — without a prior C++ implementation — have initially the ednpoint part set to FF in the uniqueid template.
This PR prevents loading and storing incomplete sensor of the database.
The problem was mostly even than the template was completed, two sensor resources existed with the FF one conflicting with the correct one.
One example is Wisers LK Switch: https://forum.phoscon.de/t/schneider-wiser-devices-not-working-in-dyna-version-2-14-00/1516