Aeotec wallmote quad zw130

I think I understand what you are doing here. You are listening on the event bus and its data rather than on the device itself. It is not transparent if you are creating the automation from the GUI, but it is a concept I appreciate very much :wink: Again, sorry for the dummy questions.

I tried the automation and it works really well. Thank you for helping!

Regards Matvey

Check this out - looks like you have to enable it in the OZW config and then it will start giving you additional parameters 9 and 10

For me is not woarking, I changed the values in the zwcfg_0xe4314a1f.xml filewith the inrmation in this page, but automatically when restart the RPI 4 the values are the old one,
When I test in the log show the folling values:

2020-08-26 21:11:06.803 Detail, Node007, Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x07, 0x05, 0x5b, 0x03, 0x10, 0x00, 0x01, 0xbb, 0x00, 0x06
2020-08-26 21:11:06.803 Detail,
2020-08-26 21:11:06.803 Info, Node007, Received Central Scene set from node 7: scene id=1 in 0 seconds. Sending event notification.
2020-08-26 21:11:06.803 Warning, Node007, No ValueID created for Scene 1
2020-08-26 21:14:39.186 Detail, Node007, Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x07, 0x05, 0x5b, 0x03, 0x11, 0x00, 0x02, 0xb9, 0x00, 0x06
2020-08-26 21:14:39.186 Detail,
2020-08-26 21:14:39.186 Info, Node007, Received Central Scene set from node 7: scene id=2 in 0 seconds. Sending event notification.
2020-08-26 21:14:39.186 Warning, Node007, No ValueID created for Scene 2

My zwcfg_0xe4314a1f.xml file by defaults have the followin configuration:

<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="5" innif="true" scenecount="0">
	<Instance index="1" />
	<Instance index="2" endpoint="1" />
	<Instance index="3" endpoint="2" />
	<Instance index="4" endpoint="3" />
	<Instance index="5" endpoint="4" />
		<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="2" 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="3" 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="4" 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="5" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
</CommandClass>

If I change the section above for the corrected one accoding with your instructions, when the systems restarts automatically change the section for the original one.

Thanks in advance,

Hi Kev,

Sorry but I’m a newbie in domotic and home assistant.
I bought a wallmote quad last week.
My goal is to pilot Tuya’s switch (integration already installed in my HA) with wallmote (I don’t want to pilot switch by swich but scenes already configured by Tuya application)
I prefer configure it through node red with mqtt but I don’t know how and what I have to configure in home assistant…
I saw and think you’re an expert in domotic.
So could you help me to configure it ?
Thanks to keep me informed.
Regards
Nikos

Anybody figured out how to turn off the sound and vibration function?

I’ve done it through Home Assistant Z-wave panel but it doesnt seem to stick, see screenshot.

Screenshot (1)

Yes via the admin panel of the qt openzwave addon I have disabled it.

Is there a certain process to getting this to stick?
Mine has Enabled by default, slightly greyed out.
I do the following:

  • Change to Disable
  • Set Configuration Parameter
  • Save Configuration
  • Restart Home Assistant

Doesnt seem to stick though.
The node comes up as Node:2 CacheLoad) whereas the Z-Wave adaptor says Node:1 Complete)

Sounds like you are running the wallmote with batteries? You need to wake it up.

  1. Change to Disable
  2. Set Configuration Parameter
  3. Wake Up Wallmote, manual says “Press and hold Action Button for 3 seconds and then release”
  4. Watch OZW_Log.txt to see if parameter was set, or test it
  5. Possibly “Press and hold Action Button for 3 seconds and then release” to disable wake up mode, or wait 10 minutes. It sounds like the action keeps it awake for 10 mins.
  6. Done
3 Likes

That seems to have done the trick, needed the hold action button piece for it to work.
Doesn’t appear to be keeping the device awake for 10 minutes though as according to the logs it is going straight back to sleep.
Any ideas how to increase the time?

You’d have to check the manual to see if it’s configurable. Usually you don’t want to keep it awake anyways. OpenZWave will also tell it to go back to sleep if there’s nothing to do.

1 Like

Not sure: but I think it stays awake with the usb charging cable attached.

1 Like

Hi Philip, thanks for the codes. I am now trying out your code to integrate with my script in HA for the swipe action. To do this I have already switched to OpenZwave.

Since I want to use your python script to manage non-zwave lights I need to change the last line to call my script instead. Unfortunately I can’t find any good documentation as how to call the script service from python. I now got the following:

hass.services.call('script', 'dimmer',  {
      'light_id': light_id,
      'swipe_action': swipe_action,
    }, False)

But too bad it doesn’t work. Syntax is correct because HA doesn’t complain about it. In the log I see:

2021-01-15 12:27:35 INFO (SyncWorker_6) [homeassistant.components.python_script] Executing wallmote_handler.py: {'node_id': 4, 'event': 'valueChanged', 'value': 33655783, 'index': 9}
2021-01-15 12:27:36 INFO (MainThread) [homeassistant.components.automation.wallmote_swipe_handling] Wallmote Swipe Handling: Running automation actions
2021-01-15 12:27:36 INFO (MainThread) [homeassistant.components.automation.wallmote_swipe_handling] Wallmote Swipe Handling: Executing step call service
2021-01-15 12:27:36 INFO (SyncWorker_18) [homeassistant.components.python_script] Executing wallmote_handler.py: {'node_id': 4, 'event': 'valueChanged', 'value': 33671400, 'index': 10}

I can see that the python script is being executed but the script never gets called. Do you know how to call the script service (script.dimmer) from within python along with variables? Thank you!

Hi Philip,

I just discovered a bug in your script:
index == '10'

index is actually not a string but integer. Just wanna point this out since I used your code for my solution. Thank you for sharing!

There seems to be a bug in his script:

index is not a string but an integer. So change it to:

if (index == 10) and event == 'valueChanged:

and you will be good to go.

And the slide function doesn’t generate any events in OZW as far as I know that’s why he is using a trigger to monitor the specific MQTT topic. His python script then fires off a Zwave event to control another Zwave device. You should adapt the last call routine to suit your needs:

to whatever you want to control. I used it to dim my Lifx bulbs for example.

Anyone know if on ZWave2JS if long press works?
Using that and single toggle presses in my automations for this and looking to make the switch away from OZW

Late reply here, I’m sure you already figured this out, but I just got one of these the other day and am using ZWaveJS. The long press and single press actions on each quadrant work just fine out of the box with ZWaveJS. You have to subscribe to the zwave_js_value_notification event in order to capture both single presses and long presses. In NodeRed the event is structured like below, the KeyPressed part will change depending on whether you single or long press. The options are KeyPressed, KeyHeldDown, and KeyReleased. The KeyReleased event is only fired after you release from a long press. The below event is for the 4th quadrant as indicated by a few of the event properties.

{
    "payload": {
        "event_type": "zwave_js_value_notification",
        "event": {
            "domain": "zwave_js",
            "node_id": 6,
            "home_id": xxxxxx,
            "endpoint": 0,
            "device_id": "xxxxxxx",
            "command_class": 91,
            "command_class_name": "Central Scene",
            "label": "Scene 004",
            "property": "scene",
            "property_name": "scene",
            "property_key": "004",
            "property_key_name": "004",
            "value": "KeyPressed",
            "value_raw": 0
        },
        "origin": "LOCAL",
        "time_fired": "xxxxx",
        "context": {
            "id": "xxxxx",
            "parent_id": null,
            "user_id": null
        }
    },
    "topic": "zwave_js_value_notification",
    "_msgid": "dea9a023.fdf67"
}

Thanks, I did make the swap a few weeks ago and used the blueprint available. Took all the work out of it.
I don’t use NodeRed, do everything in yaml or gui native to HA.
This will be helpful for someone though.

1 Like

Do you you have a link to the blueprint you used? Any chance you have found a way to get the slide up and down working?

Links to Blueprint I used.

About the sliding, nah haven’t got it working, but tbh I havent tried.

Tried to get the swipe working with zwavejs2mqtt but I couldn’t figure it out. Looking at zwave logs, I can’t see any of the data related to parameter #9 or #10.

I do see raw 16 byte hex strings from each key press. I can see the button number and press type (short vs long) encoded there, but nothing there which indicates anything related to swipe, or the raw data that I could scrape to make any kind of determination related to swipe events.

2022-07-24T01:29:51.371Z SERIAL .. 0x010e00a8000109055b03e6000100cd26                                  (16 bytes)
2022-07-24T01:29:51.372Z SERIAL .. [ACK]                                                                   (0x06)
2022-07-24T01:29:51.372Z DRIVER .. [Node 009] [REQ] [BridgeApplicationCommand]
                                  ... RSSI: -51 dBm                           
                                  ......[CentralSceneCCNotification]              
                                      sequence number: 230
                                      key attribute:   KeyPressed
                                      scene number:    1  
2022-07-24T01:29:51.373Z CNTRLR   [Node 009] [!] [Central Scene] scene[001]: 0
2022-07-24T01:29:51.374Z CNTRLR .. [Node 009] received CentralScene notification {
                                      "nodeId": 9,                                                               
                                      "ccId": "Central Scene",                                                   
                                      "ccCommand": "0x03",                    
                                      "payload": "0xe60001"
                                  }    

2022-07-24T01:29:52.487Z SERIAL .. 0x010e00a8000109055b03e7020100cd25                                  (16 bytes)
2022-07-24T01:29:52.488Z SERIAL .. [ACK]                                                                   (0x06)
2022-07-24T01:29:52.488Z DRIVER .. [Node 009] [REQ] [BridgeApplicationCommand]
                                  ... RSSI: -51 dBm                           
                                  ......[CentralSceneCCNotification]              
                                      sequence number: 231
                                      key attribute:   KeyHeldDown
                                      scene number:    1  
2022-07-24T01:29:52.489Z CNTRLR   [Node 009] [!] [Central Scene] scene[001]: 2
2022-07-24T01:29:52.490Z CNTRLR .. [Node 009] received CentralScene notification {
                                      "nodeId": 9,                                                               
                                      "ccId": "Central Scene",                                                   
                                      "ccCommand": "0x03",                    
                                      "payload": "0xe70201"
                                  }