To integrate Aeotec WallMote / WallMote Quad a Home Assistant

6 minutes of reading
  • Software use and configuration
  • Home Assistant configured and working
  • A network Z-Wave already defined at Home Assistant (explained below)
GUIDE more indicated for:

All environments

Notes and disclaimer
  • qualsiasi modifica all'impianto elettrico dev'essere progettata ed effettuata da personale qualificato;
  • any changes implemented in probefore is a propersonal responsibility as well as a profirst risk and danger (the contents of the present page are purely educational);
  • any changes implemented in proprior to a device it voids the guarantee, quality approvals and certifications.
Driving review: 1.0


The adoption of wireless touch buttons in profirst personal domotics can be particularly convenient in order to control the different functions at the touch of a finger, without, among other things, the need to break walls, carry mains or other supplies.

Il WallMote's Aeotec è proone of these practices actuators: once the magnetic base has been fixed by a thin double-sided adhesive to the target wall, it is sufficient to bring the unit close to it so that it anchors itself to it and becomes in everything and for everything a tactile surface through which to control the domotics. Battery power - rechargeable - ensures the functionnamefor months.Aeotec WallMote - In hand

Now, being a device Z-Wave it is natural to imagine it integrated with Home Assistant in order to use it to control them entity defined therein; unlike other components based on this protocol - which is sufficient to add them as nodes to the network Z-Wave managed by Home Assistant to see them "arise" as autonomous entities immediately usable - theAeotec WallMote is different for a small perfectionnamein the configuration strictly necessary in order to be able to use its functions.

This guide illustrates this perfectionnameby assuming the presence of a network Z-Wave su Home Assistant; theHUB, in fact, integrates in itself the ability to manage the nodes of a network Z-Wave by the presence of a physical antenna connected to the computer on which it is running.

To define a network Z-Wave means Home Assistant exist various antennas (usually in format USB dongle); we recommend - for the simple fact of having successfully tested it - the adoption of the USB dongle antenna Aeotec Z-Stick.

It starts

Add the node to the network Z-Wave it's pretty simple, but often confusing. Let us immediately clarify that the inclusion of the node rappreturned by the Aoetec WallMote actuator must be carried out directly from Home Assistant and not in other ways: to do so, just go to the Z-Ware management panel of Home Assistant ("Settings">"Z-Wave") And select"Add Secure Node"Or"Add Node"Based on the methods of inclusion provided by the component to be added:

Home Assistant  -  Z-Wave - Add Node

Once selected the item of interest will be sufficient press the small button on the back WallMote unit to allow entry of the component on our network Z-Wave.

After a few moments at the voice "Nodes"In the list of nodes should appset the new node called "AEON Labs ZW130 WallMote"Or"AEON Labs ZW130 WallMote Quad”(Based on the model).

Home Assistant  -  Z-Wave  -  Aeotec WallMote Node

Make a note of the node number assigned to the component (in this case "2“).
We recommend then to restart Home Assistant.


The inclusion of the component in our network Z-Wave generates at Home Assistant a series of entities: four sensors and six switches:

  • zwave.aeon_labs_zw130_wallmote
  • sensor.aeon_labs_zw_wallmote_alarm_level
  • sensor.aeon_labs_zw_wallmote_alarm_type
  • sensor.aeon_labs_zw_wallmote_power_management
  • sensor.aeon_labs_zw_wallmote_sourcenodeid
  • switch.aeon_labs_zw_wallmote_switch
  • switch.aeon_labs_zw_wallmote_switch_2
  • switch.aeon_labs_zw_wallmote_switch_3
  • switch.aeon_labs_zw_wallmote_switch_4
  • switch.aeon_labs_zw_wallmote_switch_5

Unfortunately - and hence the need for this guide - none of these entities can be used directly How trigger of a'automation as the name would suggest (especially with regard to entities)Switch"). The first entity ("zwave.aeon_labs_zw130_wallmote_quad") Is that rappresident of the WallMote unit - it is important to recognize it in order to use it later in automation.

To make it possible trigger automatic actions in view of the pressure of one of the two / four buttons of the WallMote it is necessary to implement a small modification to the file containing the scenes and the configurations of the components Z-Wave.

Zwcfg file

After defining a network Z-Wave at Home Assistat and after adding one or more nodes, in the folder in which it is usually contained the configuration appnew files will be generated:

  • zwscene.xml
  • zwcfg _ *. xml

The second file varies by name based on probefore installation, but always contains the prefix “zwcfg", Which makes it always easily distinguishable. This file contains a series of information related to the nodes Z-Wave; in this case we will identify those relating to the WallMote node by adding some items that will enable us to use it in automation. This is a file written in XML marker language.

First of all to make these changes is need to stop running di Home Assistant.

With Home Assistant in stop, open the file with a text editor zwcfg _ *. xml and identify the block related to the WallMote actuator. Typically this blockage begins broadly so:

 <Node id="2" name="" location="" basic="4" generic="24" specific="1" roletype="4" devicetype="7172" nodetype="0" type="Basic Wall Controller" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">

where is it "Node id = "2""Corresponds to the number previously identified in the inclusion phase of the component in the profirst network Z-Wave. The block contains all the sub-blocks and the configuration keys related to all the nodes of the profirst network Z-Wave.

A further xml key onlumicontained in the block above is the following:

<Product type="2" id="82" name="ZW130 WallMote" />

At this point it is necessary to identify, within the block relating to the WallMote to configure the subblock “commandClass"With id number"91"

<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE">

which closes, like all type blocks "commandClass", With:


At this point it is necessary to replace in full the block and its contents (whatever) with the following:

<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="5" innif="true" scenecount="0">
	<Instance index="1" />
	<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="1" label="Button One" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="2" label="Button Two" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="3" label="Button Three" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="4" label="Button Four" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="5" label="Other" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />

at this point it is necessary save the file and start Home Assistant. When the startup is complete, check that the contents of the file zwcfg _ *. xml is actually the modified one.


At this point we have indirectly enabled the following "scenes Z-Wave"(Not to be confused with the"scenes"Of Home Assistant) usable through automation:

One press button10
One pressure holding button12
One release button11
Two single pressure button20
Two pressure holding button22
Button two release21
Three single pressure button *30
Button three maintaining pressure *32
Three release button *31
Four single pressure button *40
Button four maintaining pressure *42
Button four release *41

* if present.

Suppose, for example, of wanting to define an automation that triggers to press the 2 button. and turn on / off a "Light"Call"light.ingresso"

The code will be as follows:

- alias: Wallmote pressione pulsante 2
    platform: event
    event_type: zwave.scene_activated
      entity_id: zwave.aeon_labs_zw130_wallmote
      scene_data: 0
      scene_id: 2
  condition: []
  - service: light.toggle
    entity_id: light.ingresso

As easy to guess, it is necessary to indicate the correct entity (in this case "zwave.aeon_labs_zw130_wallmote“) Of which to intercept the scene Z-Wave (fields "scene_data" and "scene_id") In order to use it as trigger automation. Obviously the table above is necessary in consultation to define the correct pair "scene_data" and "scene_id”To be used in automation.

It is therefore possible / necessary to define as many automations as expected behaviors to be managed via WallMote (up to 6 in the case of the two-button model and 12 in the case of the four-button model).

Obviously in the block action, as always in the automations, it will be possible to indicate any service connected to one or more entities to be controlled by ours WallMote / WallMote Quad.

Home Assistant Official LogoATTENZIONE: remember that there is on our FORUM community an ad hoc section dedicated to Home Assistant, for any doubt, question, information on the specific merit of these components.


Stay up to date through ours Telegram channel!