-
-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat] support for secondary controllers (and maybe transfer etc?) #127
Labels
enhancement
New feature or request
Comments
I think this is something that needs to be implemented on zwavejd and I think there is already an open issue. @AlCalzone |
Yup zwave-js/node-zwave-js#1070 |
Closing this, comment on that issue so :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I want to add an ISY 994i as a secondary controller (i already have it as my current home automation engine)
Describe the solution you'd like
I would like the same option as in zwave2mqtt on the controller node - where there were options for multiple controller management (i would have to respin the docker to get the exact names, can do that if needed).
Describe alternatives you've considered
switching back to zwave2mqtt
Additional context
I am using a RaZberry zwave module with this project (the previous test done on zwave2mqtt used a different controller, just incase that matters?
The text was updated successfully, but these errors were encountered: