feat: support learn mode #7135
feat: support learn mode #7135
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
AlCalzone
force-pushed
the
learn-mode
branch
from
29e983b to
96ef717
Compare
|
@zwave-js-bot automerge |
### Features * Add support for EU Long Range (#6751) * Support learn mode to become a secondary controller (#7135) * Add method to query supported RF regions and their info (#7118) * Support `Firmware Update Meta Data CC` v8 (#7079) * Implement 32-bit addressed NVM operations (#7114) * Add methods to reset SPAN of one or all nodes (#7105) ### Bugfixes * Fix missing values in endpoint dump (#7101) ### Config file changes * Add new fingerprint for TZ45 thermostat (#7127) * Add alarm mapping for Schlage lock CKPD FE599 (#7122) * Add fingerprint for Climax Technology SDCO-1 (#7102) * Add Shelly Wave Pro 3 and Wave Pro Shutter (#7103) * Remove endpoint workaround for Zooz ZEN30, FW 3.20+ (#7115) ### Changes under the hood * Document soft-reset issue in VMs (#7119) * Update documentation for troubleshooting and Zniffer, clean up migration guides (#7107) * Update `FunctionType` definitions (#7106) * CI now checks that all device config files have a `.json` extension (#7099)
|
Should FAQ be also updated now? https://github.com/zwave-js/node-zwave-js/blob/master/docs/getting-started/faq.md or is it still considered "Not supported"? |
|
It's not fully supported yet - the other half of the Inclusion Controller CC implementation is missing. But I guess it's good enough to update the FAQ. |
|
Does this mean I can run a second instance of zwave-js-ui elsewhere in my environment, with another stick. and join it to the network as a range extender? It's not clear from the docs how to get it to join an existing network on startup. |
|
No, a secondary controller does not have the same functionality as the primary. For example with some devices you can not have them report to more than one controller. What you may be thinking of (multiple instances cooperating) would require some backend work. It may come one day, but no guarantees. |
|
Right but even if I didn't want to have it report to the secondary controller, or do any management from that node, could I at least get it as far as joining the network to extend the range of the mesh? I'm confused as to what the current limited support actually allows for. |
|
I don't think there's support for this in Z-Wave JS UI yet.
Mainly in preparation for #7096 /cc @robertsLando |
|
No support in UI yet but you could still try using it with driver function |
|
Do you have any pointers on how to do that? I'm assuming I'd need to run the driver headless and pass it the keys and such? |
|
@brandond Never tried those new APIs so I have no clue but if you want to understand how to work with custom driver functions you can look at docs here: https://zwave-js.github.io/zwave-js-ui/#/usage/driver_function |
|
I'm interested in experimenting with this as well. I'm using the Node-RED Z-Wave JS package. I don't expect to be able to do it from there but can I use learn mode via code in the driver used by Node-RED and then use the UI after it's included? |
|
@37Rb what do you expect to do when Z-Wave JS is a secondary controller? |
|
I'm trying to discover what's possible to do. I want to add a z-stick (Zooz ZST39 LR) to an existing network and use Node-RED to do as much as possible with it. The goal is to enhance the existing network to do automations that aren't possible due to limitations on the primary controller. I want to add Z-Wave to this tool and see how much mileage I can get. |
|
if you’re willing to todo some testing - I can start the ground work in the NR module? It can then be done in the UI |
|
I'm happy to do testing on it. That would be easier than trying to modify the driver instance myself! |
|
I'll ping you when something is ready to test. |
This PR adds support for joining another network using S2 and S0 and being a secondary controller
fixes: #6428
enables #7096
enables #1070