I got tired of keeping all my Matter and HomeKit pairing codes in a spreadsheet that was difficult to keep together and so I went ahead and created a new HACS integration to add a database of devices and pairing codes in Home Assistant directly.
It subscribes to the Matter and HomeKit device events and creates a record for every device seen on the system. When a device is removed, it doesn’t delete the entry, but marks it as Removed, so you can look it up easily in the future (If you have to re-pair a device). You can remove a device you don’t want stored fully once it’s been removed from home assistant.
It uses the native Home Assistant config store, so it gets backed up and restored with the rest of the home assistant backups.
It’s pending being added to HACS directly, but if it sounds helpful to you, you can install it via HACS custom repository format now.
Would love to get feedback on if it’s useful or if there’s anything else that would make it more useful.
Yes! I’ve been intending to look into what it would take to support zwave devices. Mine are old style include/exclude nodes so I don’t have anything to test with, but I will take a look at the terms you gave this weekend. It should actually be pretty trivial to add into the core. The difficult code is already written to listen to the event bus and scan for devices in a domain.
V1.1.0 has support for zwave devices and I pull the DSK from zwave js when it’s available.
I also generate QR codes when we have enough data for a valid QR code. It won’t be a full smart start code unless you pull it off of the QR code sticker, but the DSK value is defined as valid to be a raw QR code, however, I can’t test it to verify.
Yes, I have indeed commissioned more than one ZWave device by typing in a DSK code instead of scanning a bar code. In fact, DSK code is all I’ve been keeping (or trying to keep) in my manual “device database” in a text document. That should be good. Thanks!
