Just to make sure we are referring to the same thing: I’m referring to the case where a device only supports low-power inclusion mode (like the Intermatic CA600, CA3000, and CA5100 devices). The devices can only be paired when the controller is within a few inches of the device.
You’re saying that even though the hub could be on the opposite side of my house, I could walk up to a low-power inclusion device like the CA600 and perform an include using the minimote and (perhaps with some steps in-between or not) have that device get included on the ST Hub?
This has worked great for me for an on/off switch and 2 dimmers, but when I tried to use it for a contact (door/window) sensor, the device was added, but didn’t seem to pair correctly. It might have been the specific contact sensor I was using it with (monoprice with custom/specific device type) or something else.
When I paired directly using the mobile app, it worked fine.
you probably can’t include door locks with the Minimote, you’ll have to pair those directly to the hub. But you should be able to exclude them. (You may run into the same issue with a few other “secure” devices which exchange an encryption key at time of pairing.)
if you want to use the “instant status update” feature of a light switch that supports it like some Cooper and Leviton models, you generally must pair the switch directly to the hub, not via the Minimote.
Other than that, you should be able to exclude/include most zwave devices with a Minimote.
Seems like many have found the Minimote to be useful in the V1->V2 migration. Any opinions over whether the version 2 Minimote is worth the extra cost, especially if it’s only use would be to assist in the exclusion/inclusion process?
Right, I have about 40 devices, 6 of which are zigbee. Not sure if it works with the Schlage zwave locks, I’ll find out. But hopefully it’ll help with the door/window contact sensors, motion sensors and water sensors.
Well, I was able to get my entire system moved over to the V2 Hub and all reconfigured and working well. The Minimote wasn’t much help, but I’m not sure I had it configured correctly. I joined it to the ST v2 hub as a device (Connect new device) and it’s not clear to me if that’s the same as adding it as a secondary z-wave controller. After including it as a device, pressing the + or the - results in a solid red light for 2 seconds, not the blinking red or blue lights as I’ve read about in the manual.
Hopefully I’ll get this working for future adds and removes. It turns out that simply using the V2 App (android) and removing the device to put the hub into exclude mode worked for me in most cases. A few devices required a second General Device Exclude to fully clear it in order for it to be added to the V2 hub.
I had to pair and unpair the Minimote 5+ times to get it to work properly with inclusion and exclusion on Hub v2. Someone else mentioned that the Minimote needs to be paired right by the hub… I don’t recall doing that with Hub v1, but I tried it anyway and I’m not sure if it helped or not since I still had to pair/unpair multiple times before it worked properly with all buttons and inclusion/exclusion working.
Edit: Also note that each time you pair/unpair the Minimote, it increments the Z-wave node ID available for the next device you add to the hub. This isn’t an issue for most people, but some GE secondary keypads/remotes have a 32 ID limit which could be an issue for some people.
Using V1 here. Reset it many times, included and excluded many times could not get inclusion and exclusion to work with V2 hub. Reset it one time, included it on my V1 hub and it works perfect. Made breaking down the V1 hub much easier but no help in setting up V2 hub.