You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.
Is your feature request related to a problem? Please describe.
When working with multi-endpoint or multi-instance devices, where each instance is a replica of other instances (f.ex. buttons on a multiple-button device), it becomes cumbersome in Z2M to keep track of which value belongs to which instance.
Zensys Z-Wave PC Controller, the view is presented in a tree view to help distinguish multiple instances.
Z-Wave PC Controller view for Node 20.1 - note the fewer CC's, as 20.1 doesn't expose the same features as 20 does (which exists as a backwards compatible thing)
Is your feature request related to a problem? Please describe.
When working with multi-endpoint or multi-instance devices, where each instance is a replica of other instances (f.ex. buttons on a multiple-button device), it becomes cumbersome in Z2M to keep track of which value belongs to which instance.
Zensys Z-Wave PC Controller, the view is presented in a tree view to help distinguish multiple instances.
20.1
doesn't expose the same features as20
does (which exists as a backwards compatible thing)Describe the solution you'd like
A view in Z2M that conveys the tree-like structure of the devices setup.
Describe alternatives you've considered
N/A
Additional context
I've run
Zensys Z-Wave PC Controller 5.38
.Original issue: #405
I've copied out the INIT nodes object from my Z2M to aid in the visualization of this. z2m-nodes.json.txt
The text was updated successfully, but these errors were encountered: