Nanomote Quad Help

Configuration
1

I followed the setup docs, walk through videos, anything that google would give me.

YES! I stopped the z-wave network. YES! I stopped the home assistant service.

I still have no “scene support configuration parameter.” option anywhere. This thing does nothing but “initializing” & has been that way for the last 2 hours. I would LOOOVVVEEEE to use the smartthings buttons as they are as easy to setup in hassio as it is to blink your eyes. But I bought this thing earlier in the year & really want to try to get this working.

Thanks for your help in advance. Please keep in mind that I’m not as familiar with Hassio as some of you might be, so a little extra guidance would be beneficial.

Some tidbits:
HassOS 4.17

This is what the device tells me:
Node ID 2
Node name Aeotec Limited ZWA003 NanoMote Quad
Manufacturer name: Aeotec Limited
Product name: ZWA003 NanoMote Quad
Query stage: Probe
Is awake: false
Is ready: false
Is failed: false
Is info received: false
Max baud rate: 40000
Is zwave plus: true
Capabilities: zwave_plus, beaming, routing
SentCnt: 1
SentFailed: 1
Retries: 0
ReceivedCnt: 2
ReceivedDups: 0
ReceivedUnsolicited: 2
SentTS: 2020-12-12 21:19:10:749
ReceivedTS: 2020-12-12 21:38:13:538
LastRequestRTT: 0
AverageRequestRTT: 0
LastResponseRTT: 0
AverageResponseRTT: 0
Battery level: 100
Wake up interval: 0
Application version: 1.02

1 Like
2

Does anyone have any thoughts on this?

3

After 2 weeks and zero help, I’m closing this thread.

4

I had similar challenges getting a NanoMote Quad connected. In fact I did assume that my actual device was broken and got a new one (which behaved the same).

In my case a device was added with the Z-Wave JS procedure but there were no buttons shown, just a “Nanomote: Ping”, “Battery level”, “Low battery level” and “Nanometer: Status”.

The way I nonetheless was able to use the buttons as triggers was this (not sure if that is the most efficient but it was the only one I got to work).

Go to “Configure device”. There is a parameter 41, central scene notification. It was switched of initially. I did switch it on. In order to sync I had to get the Nanomote quad into longer wake status (5 sec button press).

Then I went into automation and selected as trigger “device”. Selected under the device line the Nanomote and under trigger “Central Scene action Endpoint 0 Scene 001” (and similar for the others).
Selecting Key press variants did not work well, sometimes there was a “value: 1 automatically added”. I believe this determines if it is a keypress action (without the value line) or or keyhole action (value: 1).

This is how my trigger section looks now and it works on key press action for all 4 keys:

trigger:
  - platform: device
    device_id: 28c2f216191e2a433e983b8fc66666
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: '001'
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 001
    variables:
      trigger_key: 1
  - platform: device
    device_id: 28c2f216191e2a433e983b8fc66666
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: '002'
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 002
    variables:
      trigger_key: 2
  - platform: device
    device_id: 28c2f216191e2a433e983b8fc66666
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: '003'
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 003
    variables:
      trigger_key: 3
  - platform: device
    device_id: 28c2f216191e2a433e983b8fc66666
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: '004'
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 004
    variables:
      trigger_key: 4

Based on “trigger_key” I build the action section to, in my case, start a water pump for a defined time depending on the button pressed.

I hope it helps others to save some time.

5

Thanks. I found it easier to throw it away & switch to Aqara buttons.

6

@RoSche Any other tricks to get the NanoMote working? Like you, I had the basic stats info about the remote, but none of the scene commands came through. I was able to enable parameter 41, but that didn’t change the behavior. What am I missing?

7

On my NanoMote Quad it only shows these parameters
32: 20%
41: on
42: 255
43: off
Other than this and what I described above was not required in my case.

Can you describe your problem in more detail please? Maybe sharing your automation would shed some light?