Thank you. I will check this out.
Aeon is no longer making the MiniMote. You may find them on ebay, or such. The ZStick is still being produced.
I was able to get these connected! I booted up smartthings and put it into general exclusion mode. Once excluded they connected just fine to the Hubitat. Thanks all for the help.
I had the same issue after bought a used GE Zwave from an auction. Frustrated and pretty much give up on trying to get it to factory reset since it was previously paired. I did the 3 times up and 3 times down with the paddle and noting, i tried various pressing sequences ( fast, slow etc) and it worked.
Keep trying the 3 up and 3 down it has to be a cretin speed. Oh, i have the z wave plus version. Good luck.
What driver did you end up using for your GE Direct-Wire device? I have mine as a generic switch, but I don't get monitoring (KW/Watt usage).
I am using Generic Z-Wave Switch. I also don;t have that information.
I also had the dandiest time to join several devices when migrating from Iris. Luckily, I had access to a z-wave sniffer from suphammer that helped shed some light on the process and helped me to understand.
I thought when releasing the items from iris they should be ready for inclusion on hubitat. That did not always happen especially when the device was connected via a mesh node. I ended up removing the switches and bring them close to the hub.
The sniffer allowed me to see the events going on. If I pressed the switch and it had a number other then '0' as it's address it was not excluded. So I turned on the hubitat exclude mode, pressed the removed switch 'on' button, sometimes several times, and I could see the traffic as the switch was "unpaired" even from a different manufacture's hub. Then, going back to discovery, the switch joined in just a few seconds.
Previously, there was a guessing game if the switch was really excluded/reset or not. Worked like a charm with my thermostat, and door locks as well. Once the traffic showed the exclusion process, the pairing process was no problem.
Why this did not work when the devices were a hop away is not clear to me. Someone recommended the GE remote to use as a portable exclusion device (short of moving the device or hub closer). Will try that and see if this helps at those distances.
I can imagine if a device thinks it is linked, it would not communicate over the mesh for the exclusion to work. Perhaps this may also be the reason for the inclusion not to work if distance is an issue. I would expect inclusion operations to work over the mesh routing, however.
As a general rule, it probably is best practice to bind a device before installing it in a distant location. Label it at the time so things don't get confused. Meshing will then figure out how to best connect to the device.
Oddly, this seemed to work fine with my iris network. Perhaps the iris outlets and their repeater capability had something to do with it. I just did not have to bind the devices near the hub. Just installed in distant location and binding worked as expected.
Only if you do a zwave repair after you get things in their final location...
Remember, zwave devices do not update their neighbor table on a schedule. They do it at pairing time, and during a zwave repair. So if you move things around and don't do a repair, you can actually make your mesh/individual device communication much worse.
Some hubs (Vera used to, might still - don't know) do repairs on a scheduled basis, but Hubitat does not. And it really should not be necessary to do on a schedule anyway, unless you move things around a lot and don't do a manual repair, I guess.