Store a list of arrays at each location so duplicates aren't lost #1844
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.
Summary
Some Nanoleaf LEDs are in a strip
The Nanoleaf code calculates a position for each LED and stores each LED ID in a map, keying of X,Y.
With the layouts provided, LEDs have "overlapping" positions in X,Y in the corners.
This means that multiple LEDs land in the same map entry, overwriting existing IDs in the map.
At the end of the Nanoleaf init function is code to check the size of the map matches the number of LEDs.
In my setup, this was failing because of the 'overwritten' IDs aren't counted.
To fix this I've changed the value of the Map to be a vector of IDs, which allows for duplicates to be tracked correctly.
I've also improved the logging slightly to show that duplicates have been found.
This change is expected to have zero impact on any previously working configuration, as all the vectors will have size 1
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: