Skip to content

Conversation

@manup
Copy link
Member

@manup manup commented Apr 14, 2022

Related to PR #5903

  • Keep uniqueid of existing single sub-device ZHASwitch sensors if the one in DDF uniqueid template differs.
  • Proceed DDF search when first match expression fails: The EcoDim ED-10013 has two possible DDFs which need to be checked, but only the first one is.
  • Prevent adding double entries of lights and sensors.
  • Fix generation sensor id consider all ids from database.
  • Remove sensor duplicates with same uniqueid, keep the one with lowest id (assuming it's the oldest).
  • Case insensitive manufacturer name comparison when matching DDFs.
  • Merge separate DDF files for Sunricher based switches to not differentiate between 0006/1000 cluster id in uniqueid, the code automatically selects the right one if legacy joined switches exist with 1000 cluster id.

@manup manup added this to the v2.15.2-beta milestone Apr 14, 2022
manup added 3 commits April 15, 2022 21:03
…y DB

For single sub-device switches use just the existing uniqueid. The one in DDF
can differ from what the legacy code had once created.
@manup manup changed the title Fix DDF proceed search when first match expression fails DDF fix ZHASwitch issues when upgrading from legacy sensors Apr 15, 2022
@manup manup linked an issue Apr 19, 2022 that may be closed by this pull request
manup added 3 commits April 20, 2022 23:45
Relaxes goodies like NAMRON vs. Namron.
The code now detects this and automatically loads the right legacy one.
New paired switches all use -0006 cluster in uniqueid.
@manup manup merged commit f807c3e into dresden-elektronik:master Apr 21, 2022
@manup manup deleted the ddf_ext branch January 3, 2023 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sensors do not get loaded or assume a different ID than in the DB

1 participant