Configuring the Aeon Minimote (zwave)

[Ard van der Leeuw]

Hi, 

I wonder if anyone managed to get the Aeon minimote configured correctly through OpenHab / Habmin... 

I've been playing with it today, but the first thing I needed to do was patch the ZwaveSceneActivationCommandClass, as it's reading past the received messages buffer. 

But next I would like to set the scenes to operate from Habmin, instead of having to configure them through the minimote itself. 

any hints and tips appreciated. 

Ard

[jdw...@menelos.com]

I've been looking at this as well. They seem to be known to openHAB as they were added to the wave binding database many months ago (https://github.com/openhab/openhab/blob/master/bundles/binding/org.openhab.binding.zwave/database/aeon/minimote.xml). From reading on other forums there are two approaches to using the minimizes:

1) Add it to your network like any other zwave controller, program the buttons to interact directly with the device, and have openhab just listen in for these state changes and take action accordingly if needed.

2) Configure the buttons from the factory default mode to 'Scene mode'. This is mentioned in the minimize.xml file. At this point each button triggers a different scene and all actions would be controlled via openHAB. Presumably at this point the buttons would act like binary switches as seen by openHAB.

I'm trying to implement option 2.  What I don't know is:

1) How to configure the minimote buttons for scene mode.

2) How to pair the remote to my Zwave network.

I may have paired the remotes to my zwave network, but since the buttons aren't in scene mode its not doing my any good.

Any help would be appreciated.

Thanks,

-Jason

[Jason White]

I've successfully paired 6 minimotes to my network and was able to configure the buttons in scene mode.  I was not able to figure out how to do this within OpenHAB itself, so I used the Open ZWave Control Panel (https://code.google.com/p/openzwave-control-panel).  OZWCP knows about various configuration options, such as toggling scene mode on the minimote buttons or turning off the "night light" mode on my GE wall switches.

All of my minimotes are first generation (four switch buttons are numbered instead of having squares) so the buttom two buttons under the sliding cover are unlabelled and 'join'. For the v2 remotes the bottom two buttons are labelled (left to right) "associate" and "learn".  If you're trying this with v2 remotes I think you'll want to use the "learn" button in place of "join" in these instructions.

Using OZWCP I put the controller into "Add a new device" mode and then did a momentary press on the "join" button.  When the remote response you should see the blue and red LEDs on the remote blink quickly a few times and you will see the following in the terminal where you started ozwcp:

2014-11-07 16:33:23.728 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x3c, 0x02, 0x00, 0x00, 0x8c

2014-11-07 16:33:23.728 Detail,

2014-11-07 16:33:23.728 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:

2014-11-07 16:33:23.728 Info, ADD_NODE_STATUS_NODE_FOUND

2014-11-07 16:33:24.139 Detail,   Received: 0x01, 0x12, 0x00, 0x4a, 0x3c, 0x04, 0x29, 0x0b, 0x01, 0x01, 0x01, 0x86, 0x72, 0x70, 0x9b, 0xef, 0x85, 0x2b, 0x26, 0xc4

2014-11-07 16:33:24.139 Detail,

2014-11-07 16:33:24.139 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:

2014-11-07 16:33:24.139 Info, ADD_NODE_STATUS_ADDING_CONTROLLER

2014-11-07 16:33:24.139 Info, Adding controller ID 41

2014-11-07 16:33:24.139 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4

2014-11-07 16:33:24.139 Detail,

2014-11-07 16:33:24.139 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4

At this point the blue LED on the remote will blink for ~15 seconds.  Wait for it to stop blinking.  At this point the system still doesn't know enough about your remote to allow you to change any of the parameters.  Next we need to make the remote send a status update. Press and hold the 'join' button for a good 3 seconds or until you see a status update appear in the console log:

2014-11-07 16:34:04.141 Detail,

2014-11-07 16:34:04.141 Info, contrlr, Sending (Command) message (Attempt 2, Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4

2014-11-07 16:34:04.141 Info, Notification: Notification home 0185040c node 255 Timeout

2014-11-07 16:34:04.193 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x3c, 0x06, 0x29, 0x00, 0xa1

2014-11-07 16:34:04.193 Detail,

2014-11-07 16:34:04.193 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:

2014-11-07 16:34:04.193 Info, contrlr, ADD_NODE_STATUS_DONE

2014-11-07 16:34:04.193 Detail, Node041, AdvanceQueries queryPending=0 queryRetries=0 queryStage=ProtocolInfo live=1

2014-11-07 16:34:04.193 Detail, Node041, QueryStage_ProtocolInfo

2014-11-07 16:34:04.193 Detail, Node041, Queuing (Query) Get Node Protocol Info (Node=41): 0x01, 0x04, 0x00, 0x41, 0x29, 0x93

2014-11-07 16:34:04.193 Detail, Node041, Queuing (Query) Query Stage Complete (ProtocolInfo)

2014-11-07 16:34:04.193 Info, Initilizing Node. New Node: true (true)

2014-11-07 16:34:04.193 Detail, contrlr,   Expected reply was received

2014-11-07 16:34:04.193 Detail, contrlr,   Message transaction complete

2014-11-07 16:34:04.193 Detail,

2014-11-07 16:34:04.193 Detail, contrlr, Removing current message

2014-11-07 16:34:04.193 Info, Notification: Node Added Home XXXXXXXX Node 41 Genre basic Class NO OPERATION Instance 0 Index 0 Type bool

2014-11-07 16:34:04.193 Detail,

2014-11-07 16:34:04.206 Info, Node041, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=41): 0x01, 0x04, 0x00, 0x41, 0x29, 0x93

2014-11-07 16:34:04.209 Detail, Node041,   Received: 0x01, 0x09, 0x01, 0x41, 0x12, 0x96, 0x00, 0x01, 0x01, 0x01, 0x33

2014-11-07 16:34:04.209 Detail,

2014-11-07 16:34:04.209 Info, Node041, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO

2014-11-07 16:34:04.209 Info, Node041,   Protocol Info for Node 41:

2014-11-07 16:34:04.209 Info, Node041,     Listening     = false

2014-11-07 16:34:04.209 Info, Node041,     Frequent      = false

2014-11-07 16:34:04.209 Info, Node041,     Beaming       = true

2014-11-07 16:34:04.209 Info, Node041,     Routing       = false

2014-11-07 16:34:04.209 Info, Node041,     Max Baud Rate = 40000

2014-11-07 16:34:04.209 Info, Node041,     Version       = 3

2014-11-07 16:34:04.218 Info, Node041,     Security      = false

2014-11-07 16:34:04.218 Info, Node041,   Basic device class    (0x01) - Controller

2014-11-07 16:34:04.218 Info, Node041,   Generic device Class  (0x01) - Remote Controller

2014-11-07 16:34:04.218 Info, Node041,   Specific device class (0x01) - Portable Remote Controller

2014-11-07 16:34:04.218 Info, Node041,     COMMAND_CLASS_BASIC is not mapped

2014-11-07 16:34:04.218 Info, Node041,   Mandatory Command Classes for Node 41:

2014-11-07 16:34:04.218 Info, Node041,     COMMAND_CLASS_WAKE_UP

2014-11-07 16:34:04.218 Info, Node041,   Mandatory Command Classes controlled by Node 41:

2014-11-07 16:34:04.218 Info, Node041,     COMMAND_CLASS_BASIC

2014-11-07 16:34:04.218 Detail, Node041,   Expected reply was received

2014-11-07 16:34:04.231 Detail, Node041,   Message transaction complete

2014-11-07 16:34:04.231 Detail,

[...]

At this point you need to wait for OZWCP to properly see the remote. When it does it should look something like this:

41 B    Controller      Portable Remote Controller      Aeon Labs Minimote                              4:38:23 PM CST  Sleeping

At this point, click on entry for the controller and click the "Configuration" radio button.  At this point you'll need to perform a combination of pushing the 'join' button momentarily and holding it for 3 seconds so it sends a status update until you see the states of the four buttons appear ("Button #x Programmable: Default Mode"). Below that you will see an "All Button Scenes" option that will show as "Off".  Set it to yes.  This will queue a status update to your device.  Try pressing 'join' momentarily or push and hold for three seconds.  This is the part I could never repeat consistently.  The trick is that we need to wake the remote up so it can receive the status update from the primary controller telling it to put all the buttons in scene mode.  

If you're successful you should see something like:

2014-11-07 16:36:37.982 Detail, Node041,   Received: 0x01, 0x11, 0x00, 0x49, 0x84, 0x29, 0x0b, 0x01, 0x01, 0x01, 0x86, 0x72, 0x70, 0x9b, 0xef, 0x85, 0x2b, 0x26, 0x78

2014-11-07 16:36:37.982 Detail,

2014-11-07 16:36:37.982 Info, Node041, UPDATE_STATE_NODE_INFO_RECEIVED from node 41

2014-11-07 16:36:37.982 Detail, Node041, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1

2014-11-07 16:36:37.982 Detail, Node041, QueryStage_Dynamic

2014-11-07 16:36:37.982 Detail, Node041, QueryStage_Configuration

2014-11-07 16:36:37.982 Detail, Node041, QueryStage_Complete

2014-11-07 16:36:37.982 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1

2014-11-07 16:36:37.982 Info, Node041,   Node 41 has been marked as awake

2014-11-07 16:36:37.982 Detail, Node041, Queuing (WakeUp) ConfigurationCmd_Set (Node=41): 0x01, 0x0c, 0x00, 0x13, 0x29, 0x05, 0x70, 0x04, 0xfa, 0x01, 0x01, 0x25, 0x47, 0x20

2014-11-07 16:36:37.982 Info, Notification: Node 41 Queries Complete

2014-11-07 16:36:37.982 Info, Notification: Notification home XXXXXXXX node 41 Awake

2014-11-07 16:36:37.982 Detail,

2014-11-07 16:36:37.982 Info, Node041, Sending (WakeUp) message (Callback ID=0x47, Expected Reply=0x13) - ConfigurationCmd_Set (Node=41): 0x01, 0x0c, 0x00, 0x13, 0x29, 0x05, 0x70, 0x04

, 0xfa, 0x01, 0x01, 0x25, 0x47, 0x20

2014-11-07 16:36:37.999 Detail, Node041,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2014-11-07 16:36:37.999 Detail, Node041,   ZW_SEND_DATA delivered to Z-Wave stack

2014-11-07 16:36:38.002 Detail, Node041,   Received: 0x01, 0x08, 0x00, 0x04, 0x04, 0x29, 0x02, 0x84, 0x07, 0x5f

2014-11-07 16:36:38.002 Detail,

2014-11-07 16:36:38.002 Info, Node041, Received Wakeup Notification from node 41

2014-11-07 16:36:38.002 Detail, Node041, Queuing (WakeUp) Wakeup - No More Information (send to sleep) (Node=41): 0x01, 0x09, 0x00, 0x13, 0x29, 0x02, 0x84, 0x08, 0x25, 0x48, 0x2f

2014-11-07 16:36:38.059 Detail, Node041,   Received: 0x01, 0x05, 0x00, 0x13, 0x47, 0x00, 0xae

2014-11-07 16:36:38.059 Detail, Node041,   ZW_SEND_DATA Request with callback ID 0x47 received (expected 0x47)

2014-11-07 16:36:38.059 Info, Node041, Request RTT 65 Average Request RTT 45

2014-11-07 16:36:38.059 Detail, Node041,   Expected reply was received

2014-11-07 16:36:38.059 Detail, Node041,   Message transaction complete

2014-11-07 16:36:38.059 Detail,

2014-11-07 16:36:38.059 Detail, Node041, Removing current message

2014-11-07 16:36:38.059 Detail,

2014-11-07 16:36:38.059 Info, Node041, Sending (WakeUp) message (Callback ID=0x48, Expected Reply=0x13) - Wakeup - No More Information (send to sleep) (Node=41): 0x01, 0x09, 0x00, 0x13

, 0x29, 0x02, 0x84, 0x08, 0x25, 0x48, 0x2f

2014-11-07 16:36:38.064 Detail, Node041,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2014-11-07 16:36:38.064 Detail, Node041,   ZW_SEND_DATA delivered to Z-Wave stack

2014-11-07 16:36:38.076 Detail, Node041,   Received: 0x01, 0x05, 0x00, 0x13, 0x48, 0x00, 0xa1

2014-11-07 16:36:38.076 Detail, Node041,   ZW_SEND_DATA Request with callback ID 0x48 received (expected 0x48)

2014-11-07 16:36:38.076 Info, Node041, Request RTT 16 Average Request RTT 30

2014-11-07 16:36:38.076 Info, Node041,   Node 41 has been marked as asleep

2014-11-07 16:36:38.076 Detail, Node041,   Expected reply was received

2014-11-07 16:36:38.076 Detail, Node041,   Message transaction complete

2014-11-07 16:36:38.076 Detail,

2014-11-07 16:36:38.076 Detail, Node041, Removing current message

2014-11-07 16:36:38.076 Info, Notification: Notification home XXXXXXXX node 41 Sleep

NOTE: ozwcp will report that buttons 1-4 are still in default mode and that "All Buttons Scenes" is still off, even once they are configured for scenes.

Now, pressing the 1 (upper left) button momentarily will trigger the event:

2014-11-07 16:36:42.045 Detail, Node041,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x29, 0x04, 0x2b, 0x01, 0x01, 0x00, 0xf7

2014-11-07 16:36:42.045 Detail,

2014-11-07 16:36:42.045 Info, Node041, Received Scene Activation set from node 41: scene id=1 now. Sending event notification.

2014-11-07 16:36:42.045 Info, Notification: Scene Event Home XXXXXX Node 41 Genre basic Class NO OPERATION Instance 0 Index 0 Type bool Scene Id 1

Now, a momentary press of 1, 2, 3, and 4 will trigger a scene id of 1, 3, 5, and 7, respectively.

Pushing and holding 1, 2, 3, and 4 will trigger a scene id of 2, 4, 6, and 8, respectively.

I have this in my items/minimotes.items file:

Switch Rem_A_b1m  "Remote A Button 1"      (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=1,state=1"}

Switch Rem_A_b1h  "Remote A Button 1 hold" (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=2,state=1"}

Switch Rem_A_b2m  "Remote A Button 2"      (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=3,state=1"}

Switch Rem_A_b2h  "Remote A Button 2 hold" (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=4,state=1"}

Switch Rem_A_b3m  "Remote A Button 3"      (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=5,state=1"}

Switch Rem_A_b3h  "Remote A Button 3 hold" (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=6,state=1"}

Switch Rem_A_b4m  "Remote A Button 4"      (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=7,state=1"}

Switch Rem_A_b4h  "Remote A Button 4 hold" (button)  {zwave="41:0:command=SCENE_ACTIVATION,scene=8,state=1"}

My next challenge is to determine if I can get these remotes to talk through the zwave mesh network instead of directly to the primary controller.

Hope this helps,

-Jason

[Jason White]

On Friday, November 7, 2014 8:17:33 PM UTC-6, Jason White wrote:

My next challenge is to determine if I can get these remotes to talk through the zwave mesh network instead of directly to the primary controller.

I contacted Aeon Labs tech support (who has been very good at answering my question on their products -- even on weekends) about making the minimotes use the mesh network in scene mode. Their response:

The problem with using the minimote to control scenes is that the Minimote is required to be near the Z-Stick or primary controller in order to control these scenes.

One way you can avoid this is to directly create scenes via the minimote. This will require you to configure the parameter setting of the minimote. First you will need to set parameter 250 [1 byte dec] to 0 or if your software has a option to turn of scene activation mode on the minimote.

Physically tying a slave device to a scene

-Hold down a scene button for a few seconds (keep holding), the blue LED will continue to blink while holding down a scene button until you let go. If you tap a switch device z-wave button, the blinking blue LED will go solid to indicate a successful add to the scene, then continue to start blinking

(while it is still blinking, you can still walk around holding the scene button down to add other devices to the scene button, i prefer to let go to save batteries)

Physically removing a slave device to a scene (Must be the same device on the same scene)

-Hold down a scene button for a few seconds (keep holding), the blue LED will continue to blink while holding down a scene button until you let go. If you tap a switch device z-wave button that is tied to the scene button, the blinking blue LED will alternate to a red LED for a second to indicate a successful removal, then continue to blink until you let go.

(Same effect as adding a slave device, you can still walk around to include other devices, or remove them, i prefer to let go to save batteries).

The methods above will only work when the minimote is not in scene activation mode (this is set by parameter 250).

Scene activation mode gives you much more customization depending on the scene you have set the buttons to control.

The general group mode will only allow you to dim, turn on or off. 

So now I'm moving my zstick to a more centralized location so all the remotes can reach it.  I really don't want to give up scene mode as it gives me 8 discrete events I can trigger.

-Jason