AEOTEC Quad WallMote ZW130 Homeseer Setup Procedure

[MNB]

Working WallMote ZW130 Procedure for Z-Wave device(s) Direct connection.

Note: You must Include your WallMote as a non-secure device mode (secure mode at this time doesn’t seem to work even though it generates all the proper devices).

Note: Make sure you have the device on USB power when attempting to add/remove or make change of any settings on it. When the device is on USB it will stay awake so you can work with it. When on batteries, it keeps going to sleep which causes HS to keep timing out on sends and if those buffer up, it will lock up the plugin.

1. Plug your WallMote to USB power source and allow the battery to charge the WallMote will be Orange to indicate charging and will change to Green to indicate fully charged. Note: keep the WallMote connect to the USB power source whilst performing this operation.
2. On the Homeseer screen select “PLUG-INS” which will display a drop-down list tab, select “Z-Wave” > “Controller Management”.
3. Under the Z-Wave Interfaces, select your “Name: Main Z-Wave Controller” via the Orange arrow, Under the “Actions” select the drop-down list and selected “Add/Include a Node Nonsecure”. Which will display a green panel with instructions, Select “START” and wait for “add Node started…” with “activate the ‘Add to Network” function on the device…” message.
4. On the WallMote device press the Action Button (white button located on the back of the WallMote) once to “Add/Include the Node Nonsecure”.
a. The green LED will be on for 2 seconds and then the orange LED will fast blink for 10 minutes (if the WallMote does not receive the Wake Up No More Info command from primary Controller) to indicate the inclusion is successful.
5. Once you have successfully included the new WallMote you will have 12 new devices (see below) under the new Node XX id, you will have to select it in order to view these devices.



6. On the Device List, locate the device named “AEOTEC WallMote” it will be on top as a “No Status” device. Select the WallMote device by double clicking the “AEOTEC WallMote” Name. locate and select the “Z-Wave tab.
7. Locate “Functions” and open “Associations” via the orange arrow, select “Update” to update your existing Associations. This will expand your Existing Associations from original 4 (Group 1 through 4) to 12 elements (Group 1 through 9).
8. Note: Remember that Groups 2, 4, 6, 8 are for Binary On/Off switches associated with Wallmote Buttons 1-4 and Group 3, 5, 7, 9 are for Dimmable switches (multi-function devices) again associated with Wall mote Buttons 1-4.

·Wallmote Button 1 (Upper Left) = Group 2 – On/Off Switch(es) and Group 3 – Dimmable Switch(es)
· Wallmote Button 2 (Upper Right) = Group 4 – On/Off Switch(es) and Group 5 – Dimmable Switch(es)
· Wallmote Button 3 (Lower Left) = Group 6 – On/Off Switch(es) and Group 7 – Dimmable Switch(es)
· Wallmote Button 4 (Lower Right) = Group 8 – On/Off Switch(es) and Group 9 – Dimmable Switch(es)

9. On the Association Group select the appropriate Group X, under the “Device to be Controlled” select the drop-down list and select the appropriate switch or Dimmer (make sure to pay attention to the appropriate WallMote switch number and associated group number. I added my working version that turns the specific light On/Off and updates the Homeseer devices to reflect the same, you will note that in once case I added three different lights to be either turned On or Off as a toggle function, Make sure to depress the “Update” button as it will update the WallMote and will reflect your changes in the “Existing Associations” I found that if I did not update not all “Add Association” were always included. Once you’re happy with your selections, take your now functioning WallMote for a test drive.


Update: In my original post I had my Stair Lights, which is a dimmable (Multi-function) light switch in Group 8 with the other three binary On/Off switches, last night after selecting Button #4 I would get a random error (didn't happen every time) denoted with a red led cross after depressing Button #4, I then moved the dimmable (Multi-function) switch to Group 9 since that group is suppose to be slated for Multi-functional devices and "wala" has been working like a charm!

Note: There is another method to get this Wallmote to work with Homeseer and that’s by setting up Button X On/OFF events that when triggered perform specified tasks. The issue with this method is that it suffers at times with delays as it requires HS3 to detect the mote action e.g. Button X short Pressed or Long Press then run the event which in turn executes the On/Off command to the device. The Direct Connect to Z-Wave device method eliminates the middle man and is nearly instantaneous (MTC) If other folks have corrections or other method by all means lets share! Thanxs Mike

[MNB]

Anyone out there been using these WallMotes? I noticed that although they work great via Direct Connect to specific Z-Wave device, I can physically verify that the specific light turns On or Off when selected but when I look at my HS3 Light device I do not see the specific Z-Wave Device changing its status regardless if it's On or Off, is there something I'm missing or overlooking? Mike

[akatar]

I use a wallmote, works perfectly without direct Association. chose: "has its value set to ….. don't use changed to!

[MNB]

akatar, thanxs for the come-back, what was the decision point that made you use Event Driven (ED) rather than Direct Association (DA) method? I really like the rapid response with DA but, if HomeSeer doesn't see the changes it kind of defeats other device associated Event Triggers capabilities. Mike

[logbuilder]

I have several aeotec wallmotes in use as well as a variety of other remote controls. For each button, I created an event that triggers whenever the value is set on the z-wave device associated with the button. In that event, I can do whatever actions are needed. In many cases, the press of the button will trigger an event that sets a virtual device that represents a scene (ie. watching TV) which then triggers the real event to handle the scene actions. This allows the scene to be triggered in several different ways ranging from multiple wallmotes to a HSTouch app. All anyone needs to do is set the virtual device associated with the scene. All the logic for the scene are contained in one event.

Hope that makes sense.

[MNB]

Robert, thanxs for your suggestion, I guess "there are more than one way to skin a cat!" per chance could you provide a few examples of specifically what your actually doing? thanxs in advance.

In the absence of any forum discussion(s) re the ZW130, I thought by adding a procedure it would solicit comments/ recommendation based on others experiences. I agree with both of you that these devices seem to work well once one gets their head around how to include and set them up, In my case these ZW130 devices (5x) bridge/replace my old AEOTEC minimotes (getting old and grungy). With my MiniMotes I too used events, but I like the idea of using virtual devices. Mike

[akatar]

MNB I never tried da, this has Always worked flawless so no reason to try da.

[MNB]

akatar, I've just switched three of my Wallmotes to Event driven and they seem to work with HomeSeer showing proper status of each affected device.

[MNB]

Robert

logbuilder

I'm hoping you will provide some examples of your virtual device/event approach? I know PIA , Mike

[logbuilder]

Ok, here goes.

First, the notion of a scene is related to an activity such as . Watching TV, Eating, Waking Up.... There is an event for each of these scenes.

Here are a few of my scene events.



For each event, there is a virtual device. Here are some.



Here is an event. It is a simple one. Some scenes are much more complex.



So to activate a scene, any input device (wireless devices, a web based dashboard, or a HSTouch app) only needs to turn the virtual device to On. That triggers the event. Changes to the scene are easy since a single event contains all the actions.

Hope that helps.

[MNB]

Robert, many thanks for providing your examples, I find it interesting that you use the term scenes and events interchangeably, I hadn’t used term scenes since my VERA days, but I understand it in your context. So in regards to the Quad WallMote you would have one of your buttons set to turn the Virtue Switch to ON/OFF in you example for cooking which in turn triggers the “scene - cooking” to ON, what event turns the cooking devices OFF and what does the sleep event do? Mike

[logbuilder]

The sleeping scene sets all the lights to the appropriate levels, sets temperature, activates the perimeter security monitoring, sets Blue Iris to appropriate profile, turns off non light items that are not needed at night (ie, computer speakers, monitors), chirps a siren to let everyone know sleeping is set, turns all other scenes off, says 'Goodnight'.

On the distinction between scenes and events, the event infrastructure is provided by HS3. Scenes are a construct build on top of events. Scenes are more closely aligned with use cases. That's the way I view it.

[MNB]

On the distinction between scenes and events, the event infrastructure is provided by HS3. Scenes are a construct build on top of events. Scenes are more closely aligned with use cases. That's the way I view it.

Robert, thanxs for the comeback, I agree with your Scene vs Events, as to your sleep event, I have something similar whereas I will say to Alexa "Goodnight Alexa" and HS3 runs a script to check all my doors and locks and speak the current status and then turn off all non needed lights and also sez "Goodnight".

Back to your earlier posting in regards to the Quad WallMote you would have one of your buttons set to turn the "cooking" Virtue Switch to ON/OFF in you example for cooking which in turn triggers the “scene - cooking” to ON, what event turns the cooking devices OFF (I'm assuming that your have another event "Cooking Off"? MIke

[logbuilder]

Yep, there is an event to handle each button on the wallmote. The event turns on the scene virtual device.

Note: I have several types of remotes spread across two HS3 ilocations. I use 2 types of Aeotecs, the wallmote and the keyfob, some Insteon devices. This example is from an Insteon mini remote. By using this abstraction layer approach, as long as I can tell if a button has been pressed in an event, it can fit right in with all the others with no changes to or duplication of the actual commands associated with the scene. I've built simple arduinos with momentary buttons and they worked real well and required no changes other than an event to handle the press of the button and setting the scene device on.

Here is an example.

[logbuilder]

In regards to turning scenes off.... after pondering and studying how we actually behave... I decided upon allowing stacking rather than turning a scene off.

An example might help. Our house is very open and is two levels. Downstairs is the kitchen and living room. Upstairs is an open loft area where we watch TV and often eat dinner. As it begins to get dark, we active the 'Downstairs Leisure' scene that sets the light levels (almost all my lights are dimmable) for relaxing in the living room which is right next to the kitchen so the kitchen lights are set to 25%. When it is time to start cooking, we activate (stack) the 'Cooking' scene which effectively overrides the kitchen lights to a lighter dim level. When cooking is done and we move upstairs to each and watch TV, we stack a 'Watching TV While Eating' scene which sets the loft lights to a level that is low but you can still see to eat, sets kitchen to 25% dim, and turns off living room overhead can lights cause they are annoying when watching TV from the loft , and sets the cans over the stairs to a level to allow safe travel up and down but low enough to not impact watching TV. When we finish eating, we activate the 'Watching TV' scene which lowers the loft light levels even more.

Oh, there is a 'All Scenes Off' scene that turns all lights off and all scenes off. After bunches of scene stacking, sometimes I'll use it to return to a clean base scene.

Here is a capture of the HSTouch andriod app that we use for all local control and well as remote access and control. This is the Scenes Control Screen. It will give you a flavor of the types of scenes we use.