Skip to content

Instantly share code, notes, and snippets.

@ragingcomputer
Last active January 12, 2017 22:54
Show Gist options
  • Save ragingcomputer/147c445f48da021ed61e706f07ab3eb8 to your computer and use it in GitHub Desktop.
Save ragingcomputer/147c445f48da021ed61e706f07ab3eb8 to your computer and use it in GitHub Desktop.
Aeon Labs Minimote in OpenHAB 1.8.3

The video https://www.youtube.com/watch?v=z0Dmdwt8gNE Is just a repetition of the directions on this post https://community.openhab.org/t/aeon-minimote-configuration-oh-1-8-2/9585/9

Quoting TheKorn from Apr '16

I'm going to write this up in stupid levels of detail, not because I think you're an idiot but for people who search and run across this thread. (Plus when it inevitably comes up in the future, I can link back here and say "do that". 😉 )

There are at least four variants of this remote, possibly more. They all seem to have identical hardware and report identically via zwave as far as device IDs go, and react the same way when you push the buttons despite them being labeled very differently. Version one has the buttons labeled 1,2,3,4. Version two has each button labeled with a square. (Very helpful, Aeon. /s) White/black versions of both exist, etc.

We need a common nomenclature for the buttons. I'm going to go with the original white remote's button numbering, since writing "hit the lower left square button" is a lot more ugly than saying hit button 3. With the door closed, upper-left is button 1, upper-right button 2, lower left button 3, lower right button 4. If you then open the door, the numbering pattern continues; 5-6, then lower left is 7 and lower right is button 8.

You will need a version of the z-wave binding later than what shipped with 1.8.2. (Any of the 1.9 snapshots after late March 2016 should be fine.)

A complete reset of the device back to factory (and forget any zwave pairing) is done by holding down buttons 7 and 8. The blue and red lights will start blinking faster and faster indicating the safety countdown timer. Once they both go on at the same time, it'll reset itself to factory.

To pair, throw the controller in pairing mode in habmin. Tap button 8 once. The blue light should be blinking, then once pairing starts blue and red go nutso for a while. (If you just get the red light blinking once, then again a few seconds later, try again.)

Once it's paired in habmin, you need to wake the device up so that it completes initialization. Hold button 8. The red light will briefly flash, then the blue light will come on. Keep holding button 8 until the blue light is extinguished. If you have the zwave binding in debug mode, you should see NIFs go by and that the node number for your remote has woken up.

Now go into habmin, open up the minimote, and change configuration parameter 250. You want to set it to scene mode instead of blank or group mode.

Finally you need to wake the remote up one more time, so that it fetches the new config.

Congratulations! Now if you tap buttons 1-4, you should see scene info going into the zwave log if you have debugging on. (Or possibly warning messages complaining about unbound events if you don't. 😉 )

Switch REMOTE_DN_S1 "Remote Short Button 1" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=1, state=1"}
Switch REMOTE_DN_S2 "Remote Short Button 2" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=3, state=1"}
Switch REMOTE_DN_S3 "Remote Short Button 3" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=5, state=1"}
Switch REMOTE_DN_S4 "Remote Short Button 4" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=7, state=1"}
Switch REMOTE_DN_S5 "Remote Long Button 1" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=2, state=1"}
Switch REMOTE_DN_S6 "Remote Long Button 2" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=4, state=1"}
Switch REMOTE_DN_S7 "Remote Long Button 3" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=6, state=1"}
Switch REMOTE_DN_S8 "Remote Long Button 4" (Group_Remotes) { zwave="33:command=SCENE_ACTIVATION,scene=8, state=1"}
import org.openhab.core.library.types.*
import org.openhab.core.persistence.*
import org.openhab.model.script.actions.*
rule "turn off any bedroom remote scene button"
when
Item REMOTE_DN_S1 changed to ON or
Item REMOTE_DN_S2 changed to ON or
Item REMOTE_DN_S3 changed to ON or
Item REMOTE_DN_S4 changed to ON or
Item REMOTE_DN_S5 changed to ON or
Item REMOTE_DN_S6 changed to ON or
Item REMOTE_DN_S7 changed to ON or
Item REMOTE_DN_S8 changed to ON
then
{
postUpdate (REMOTE_DN_S1,OFF)
postUpdate (REMOTE_DN_S2,OFF)
postUpdate (REMOTE_DN_S3,OFF)
postUpdate (REMOTE_DN_S4,OFF)
postUpdate (REMOTE_DN_S5,OFF)
postUpdate (REMOTE_DN_S6,OFF)
postUpdate (REMOTE_DN_S7,OFF)
postUpdate (REMOTE_DN_S8,OFF)
}
end
rule "Remote Downstairs Button1 Activated"
when
Item REMOTE_DN_S1 changed to ON
then
if(Light_DN_Den.state>20) {
sendCommand(Light_DN_Den, OFF)
} else {
sendCommand(Light_DN_Den, ON)
}
end
rule "Remote Downstairs Button2 Activated"
when
Item REMOTE_DN_S2 changed to ON
then
if(Fan_DN_Den.state>66) {
sendCommand(Fan_DN_Den, 66)
} else if ((Fan_DN_Den.state<=66)&&(Fan_DN_Den.state>15)) {
sendCommand(Fan_DN_Den, 15)
} else if ((Fan_DN_Den.state<=15)&&(Fan_DN_Den.state>0)) {
sendCommand(Fan_DN_Den, OFF)
} else {
sendCommand(Fan_DN_Den, 100)
}
end
rule "Remote Downstairs Button3 Activated"
when
Item REMOTE_DN_S3 changed to ON
then
if(Temporary_DN_xmasTree.state == ON) {
sendCommand(Temporary_DN_xmasTree, OFF)
} else {
sendCommand(Temporary_DN_xmasTree, ON)
}
end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment