Yes, it seems that fingerprint is not added to the Z-Wave Siren driver yet and the Z-Wave switch driver has a generic fingerprint that takes on the device. However, there are two things you can do:
Copy the stock DTH and paste it into your IDE account. Custom DTHs come before drivers when you join the device.
Download the “Z-wave Siren” driver and add the missing fingerprint, then, even if it’s joined to “Z-Wave switch”, you can use the tool in the app to change the driver of the device.
The difference between them is that #1 will make the device run in the Cloud. These alternatives are so you can continue using your devices, in the meantime, I will ask the team why the fingerprint is missing.
Option 1 is very easy to do. I should have thought of that one myself. In addition after installing and pairing with the custom DTH, I should be able to switch back to the stock DTH for local control.
Option 2 looks very interesting, but is currently beyond my skills. I have been using Edge Drivers and the CLI for months, but have never modified a driver. When I go to GitHub I see there are a number of files for each Edge Driver including one called fingerprints.yml. I could download load it and add the fingerprint, but I have no idea what to do after that. Is there some sort of “Dummies” guide for adding fingerprints to Edge Drivers?
Thanks again for your reply, and option one will work at least temporarily.
It’s not much more than that. Make sure you download the entire zwave-siren folder and preserve the folder structure. After adding your fingerprint, you would follow the steps in the tutorial below in the “Uploading Your Driver to SmartThings” section.
I also have this siren and am attempting to switch it to the new architecture. It appears as though the fingerprint is now in the “production z-wave siren” edge driver.
I have removed the device but when I re-pair it, I think it is re-pairing with the legacy DTH (doesn’t show “placeholder” in the legacy API UI and doesn’t have a “Driver” choice in the Android app).
I may be operating on an incorrect assumption but I thought that all production edge drivers were automatically installed to my hub and that re-pairing a device fingerprinted in production would correctly choose the edge driver over the legacy driver? Is that right or do I need to manually install the production z-wave driver to my hub before repairing. Thanks!!