Force associations in specific circumstances #1092
Merged
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.
This will prevent associations being removed if the system needs them, and the controller is configured as
master
. The PR searches to see if the database has an association configured, or if the association is the ZWave PlusLifeline
group. If so, it will set the association - thus preventing the user from removing it.This is to avoid the system becoming unusable due to either lack of knowledge by users, or, through UI problems causing associations to be removed.
It also transpired that somewhere in the system (either in the UI, or in ESH) the arrays/lists are not being parsed correctly and the array is being presented as a string (eg
[node_1, node_2]
). Code has now been added to handle this format!Signed-off-by: Chris Jackson [email protected]