Looks like part of the script moves the security keys and device path into Home Assistant’s config and out of settings.json.
Will it be possible (instead) to just run the 1.0.0 app (add-on) and manually configure it, including keys and device, via the ZUI interface?
Not sure I understand this at the end. It’s been a long time, but I though the ‘Use the Z-Wave Supervisor app’ was what installs the app. What else does it do? Push the config to z-wave js?
[migrate] Migration complete!
[migrate] You can now reconfigure the Z-Wave integration as follows:
[migrate] If using a USB or TCP based controller:
[migrate] - CHECK 'Use the Z-Wave Supervisor app'
[migrate] Otherwise:
[migrate] - DO NOT check 'Use the Supervisor app'
[migrate] - URL: ws://core-zwave-js:3000
I updated it and it’s fine. One thing, why don’t they list ZUI what the name of the device is and what area it is in to correlate it back to the dashboard
It’s one-way to HA. When you include a device z-wave js tells HA the name and area, but if you change either of those in HA it doesn’t get sent back to z-wave js.
Again, this is why I like to use SmartStart (in ZUI) to keep track of the device names in one place. (And means excluding and including back they keep the same device and thus entity names.)
Here’s where people do different things. You need to scan the QR code and there’s different ways to do that. I have a Mac so I can just paste, so quite easy. But you could text or email it or whatever.
You can only scan from your computer if running with SSL (https://), so what I do is use my iPhone like this:
and click CONFIRM. You should see a new entry where it already knows the make and model of the device. Then you have to scroll all the way to the right to find the edit button:
That’s it. If you ever remove (exclude) that device the SmartStart data is still available and if enabled all you do is plug in the device again and it will connect.
The helpful point of SmartStart is you can provision a bunch of devices and then just plug them in or power up wall switches and they auto-include.
Yes, you can go into the “Control Panel” page of the ZUI where all your “already” included devices are at, and for a given device entry, click on it and it exposes a place where you can enter the name/location.
@Paddy707, yes, you can add SmartStart into already included devices. It’s only used WHEN including the device, so no effect to existing devices other than you have the device pre-configured if you ever want to exclude and re-include it.
update: And if you do, use the current HA device name so that entities would be recreated with the same names and your dashboards, scripts, automations, templates won’t need updating.
I did exactly this for all my devices (opened up wall plates and scanned the QRs) so that I had a kind of doomsday restore option. If a controller failed where I couldn’t exclude devices I could just reset a device and it would include itself again.
Interestingly, if you change the name and area on the Control Panel z-wave js does send the name/area change to HA, and HA logs it, but the device name doesn’t change in HA.
I had just gone off and deleted the integration and re-added it and saw that worked, too. Which is what you would hope. Makes sense that it would also do it on restart, unless the device has been renamed in HA, of course.
Just no live updates even though the update in ZUI is sent to HA over the websocket.
I think @Paddy707 was asking about adding devices already included into the provisioning list for a later re-include.
Handy to have all the devices in the provisioning list so if a controller failed or you somehow needed to re-include devices you wouldn’t have to go find QR codes.
Greetings @busman ,
Can you elaborate please? I have a bunch of z-wave added manually and I’d like to ensure I have all the DSK’s properly backed up (that’s a whole different story ).
You can scan the QRs and associate them without excluding/reincluding them? How?
Just for grins, I just scanned a few of the QR codes but now they are all showing as new devices in “not ready” state. How do they get associated with existing devices?
Yes, you can scan or enter the DSK w/o re-including. When you do that you will probably see it show the current node ID on the left of the provisioning page.
You can add devices either useing the DSK or QR, I think. I just always use the QR since it’s easy with my phone. And then I just plug in the device and that’s it.
Z-Wave JS can’t associate the provisioning entry with an existing node if the DSK does not have a match. You mentioned in your other post missing DSKs.
If you add the QR code in HA it will create the pending device until the node is added. Adding the QR code in Z-Wave JS UI will not create the pending device.
If you click on Z-Wave on that last image (device page) for each does it show differ node IDs?
Yes.
And dos ZUI show multiple or duplicates?
I do not see multiple/duplicates. Just the original.
If you add the QR code in HA it will create the pending device until the node is added. Adding the QR code in Z-Wave JS UI will not create the pending device.
Ah. Interesting. If I use the Z-Wave JS to scan the QR code :- it crashes the app. But if I use the “add device entry” I can scan the QR code. Let me try manually adding the QR code to the Z-Wave JS and see what happens.
Thanks!
Hrm. No different capturing the QR and adding it via text except for the toggle option between mesh and LR. It did not associate with the existing ID.
How you add the QR code won’t have any influence in how an included node is associated with the provisioning entry. Did you confirm the DSK is known for this particular device? See:
).
