- First to get this out if the way: DTHs, all DTHs, are in the process of being shut down, so there’s no point in spending time on those. You can’t add a new one to your account now, anyway. So whatever you come up with, it will be an Edge Driver as that’s how zwave communication will work in the new architecture. All the details about Edge Drivers are in the following FAQ:
FAQ: I have no idea what Edge is. Is that a new developer tool? (2022)
-
Yes, a straightforward motion sensor should work fine with SmartThings once you get the correct fingerprint, but it looks like your pairing failed because it has zeroes in the manufacturer and model number. (Those two fields are the fingerprint, btw. So all zeroes means no fingerprint to match on.) I’m guessing the issue was a security problem related to it potentially being a series 700 device, but maybe not.)
-
anyway, first let’s see if we can identify the device another way, it appears that Boundary didn’t make its own hardware, so it may be relabeled. Can you show us a picture of any labels on the back or inside the battery compartment? There aren’t that many series 700 devices on the market yet (the smartthings/Aeotec hub, for example, is series 500), so I’d guess Popp, but let’s see if we can tell more.
-
we need to know the model number of your ST/Aeotec hub.
-
there is a possibility that your sensors in their existing locations will be out of range (series 700 devices have significantly better range than series 500, so the hub may not be able to reach them), but first let’s answer the previous questions, then we’ll look into that issue. Although if there does happen to be a sensor pretty close to the hub, say within 15 meters, try pairing that one and see if you get better results.
Well, that’s enough to start with. I do think that if they are indeed standard zwave sensors you should be able to get them working, although they may need some additional repeaters, so I am optimistic for the longterm. But one step at a time.