You are under no obligation to update your firmware just because a new version came out, especially it was just minutes to hours ago and you donāt see release notes posted yet and you donāt feel comfortable updating without knowing what was changed. If your current firmware is working well, you can even keep using it indefinitelyāunlike ST, the updates are not forced on you. You choose if and when to update. (That being said, Iāve always updated pretty fast because Iāve been generally pleased with the changes they made. Sounds like youād be happier if you waited a while and let others test the waters first. Youāre again free to do soāto say nothing of the TOS quoted above that provides a disclaimer for this exact type of situation. But even if you are a heavy RM user and updated right way, this probably only affected you for a few hours. Want to compare that to STās all-day outage earlier this week? )
Back to the Minimote: despite apparent Z-Wave issues in recent firmware versions with device discovery for these particular devices, I was still able to get mine to work. If this is the worst problem Iāve had (and so far it is), Iād still be pretty happy.
I was able to pair minimote, but had to make like 10 attempts. I am on 705. Couple times minimote was paired but would not register any button pressed. I had to exclude and start over. Was ready to gave up when minimote suddenly started to work.
Iām in the same boat with a v1 minimote but still havenāt paired after about 15 tries. The farthest I get Is a device that I can switch to the minimote driver, but it never recognizes button presses.
I have 2 v1 minimotes, 1 with upgraded firmware and 1 without. Neither pair to Hubitat since the last few Hubitat firmware versions. I upgraded to the latest and tried again with no success. I have a support ticket opened in this issue as well.
@mike.maxwell have you been able to determine the issues pairing v1 minimotes? I saw posts that you were reworking a bunch of drivers and wasnāt sure if this was included. Iād really like to get my remote paired again and working on Hubitat. As mentioned above and via support, I am having challenges with original firmware and upgraded firmware remotes.
OK, I have some tips on how to do this until such time as this is no longer required.
If these work (as they do for me), awesome, if they donāt youāll have to wait for us to sort it out in the discovery processā¦
Thereās several possible states that a minimote can be in in the pairing process.
1-never paired, so how do I do it.
2-itās in the zwave info page with a āDiscoverā button where the device name usually is
3-in the zwave info page with the name Aeon Minimote, but pressing itās buttons does nothing.
There may be other states, and I wonāt be covering them
Pick your starting point from the above, then follow all the steps below from your starting point.
1a-If your mote has numbers on the buttons, upgrade the firmware if this has never been done
1b-Factory reset it, open the cover, press the bottom two buttons at the same time, hold while and until the red and blue LEDs stop flashing, if they never start flashing, repeat 1b until they do.
2a-Open a browser tab to the zwave info page, open a separate tab and begin device discovery.
2b-As soon as discovery starts, tap the bottom right button under the cover.
2c-Refresh the zwave info page until the minimote shows up as a new entry in the list, stop device discovery.
2d-Click the āDiscoverā button on the zwave info page, the discover button should go away, and be replaced by āAeon Minimoteā
2e-Open the live logging page, see if buttons 1 through 4 do anything, if not continue with step 3.
3a-Open live logging and in a separate tab, the mote device details page.
3b-Wake up the mote by pressing the bottom right button until the blue light goes out, then hit configure in the driver details. at this point the mote should work.
Iāve had three Minimotes pair perfectly with these instructions, but a day later, one shows āInitialize= Falseā and āRe-initializeā (white on red banner). What does this mean?
I managed to (finally) pair my two v1 minimotes thanks to some posts here and a little trial and error and with help from mike.maxwell above. Just outlining my steps/observations in case itās helpful. This worked for the first minimote, so I replicated and immediately worked for the second. I think these both have the firmware from 2016. I previously had these on Smartthings, so I used STās exclude mode because itās a little more clear when a device is successfully excluded. This is all about 100 feet from either hub with plenty of other zwave devices in the middle.
Exclude device (I used ST) by putting hub in exclusion mode then hit the āJoinā button on the remote once
Reset minimotes by holding ā+ā and ā-ā at the same time until the lights stop flashing
Once all lights are off, I went to device discovery in Hubitat and hit the āJoinā button on one minimote. The red and blue lights flickered indicating something happened, but nothing appeared on the device discovery page
In a separate tab, I went to Settings -> Z-wave information and looked for the device with āin: 0x86, 0x72, 0x70, 0x9B, out: 0x85ā under āClustersā which had a Discover button. Click the discover button.
Now the Minimote appears in Devices. On the Minimote configuration page, clicking/holding buttons did nothing. Click the āConfigureā button. The lights on the minimote flashed, and now button presses should appear on the device page.
I repeated this for the second minimote which was also successful.
I recently bought a couple Aeotec Key Fob Gen 5ās (ZW088). Whew, confusing user manual! But using the instructions here for the minimote and an Aeotec support page, I got one to work using the Aeon Minimote device driver. The key fob was added as a Device so I had to manually change to Aeon Minimote.
Take the Pin that comes with the Key Fob Gen5, then press and hold the "Mode" button for 20 seconds. The LEDs will alternate colors between red and green faster and faster until the green LED becomes solid.
Now release the "Mode" Button.
Key fob is now in Setup Mode.
Pairing Key Fob Gen5 to your Gateway
Tap the "Learn" Button on your Key Fob Gen5 with the Pin, the green LED should now be blinking.
Put your gateway into inclusion mode, or device pair mode. You will notice that the Key Fob Gen5 will blink rapidly to indicate that it is communicating. When it becomes solid Green for 2 seconds, this indicates a successful inclusion process. If it stays solid Red for 2 seconds, then the inclusion process failed. For this case, go back to the Factory reset steps above, and start again.
At this point the Hubitat Minimote instructions are applied (Hubitat never shows that the device was discovered on the discovery pop-up)
Go to Settings, then click Z-Wave Information, key fob will show up in the list with a Discover button in the device column
Click Discover and the key fob will be detected as a Device
Go to Devices, click on Device
Fill in Device Name, Device Label, select Aeon Minimote for type, Save. Leave page up.
Configure Key Fob as scene mode controller
Press and hold the "Learn" pin button for 3 seconds, then release.
Press Configure button on the device page, buttons should now work.
To determine what mode your Key Fob Gen5 is in, tap Button 3 (Bottom Left Button) and view the LED activity of the Key Fob Gen5:
No LED Activity = Setup Mode
Red LED = Group Mode
Green LED = Scene Mode
@mike.maxwell every time I restart my hub or apply a firmware update, I have to wake all my minimotes and configure them again. Otherwise they won't work. I wanted to bring this issue to your attention as you are working through the issues.
)
