Aeotec trisensor found but freezes at initializing

I have a new Aeotec Trisensor that I can't get to included. I've done a factory reset, put it in pairing mode and run z-Wave inclusion a couple times and HE sees the sensor. I get the "Found Z-Wave Device with id xx" message and below that it says "initializing" but that's as far as it gets. It does not show up in my device list or on the z-wave page.

My HE is a C7 and I'm on the latest HE build. I've attempted this with the sensor near where it will be mounted and also right next to the hub. Still no joy... Any ideas on how to deal with this would be greatly appreciated.

Thanks!
Tom G.

While the need for this has been lessened (maybe eliminated?) with recent hub firmware updates, it can't hurt: try shutting down the hub, removing power for about 30 seconds or more, then reconnecting power (to restart the hub). The goal is to leave the Z-Wave radio powered down for all of the residual power to dissipate, and a regular reboot won't do that. Be sure to initiate the shutdown from Settings, as always.

Before you try again, also check Settings > Z-Wave Details for any "ghost" devices. These would be failed pairings where you're likely to see just blank values for everything in the "in:, out:" column. Click "Remove" if it's available, or "Refresh" then (wait a few seconds and) "Remove" if it appears then. These have been reported to cause problems for some people. In the early days, if I did too many of these in a row, I again had to shut down the hub, but I again think this is better now. Mentioning just in case...

After that, see if it works if you try again. You will likely need to reset or exclude the sensor if it went through a previous failed pairing attempt, as you might be aware from trying this more than once already.

1 Like

I'll give that a try this evening after work. Thanks!

Also check z-wave logs. Eventho' the device is not visible in the z-wave page it could still display logs (with its old Id) which is a sign it's not yet fully dispatched.
Especially with a lot off near pairings it's a good idea to double check those logs before doing another attempt.

1 Like

That did the trick. Thanks!

1 Like