Aeon Labs Minimote with zwave js?

re: Were the buttons already Scene Mode, or other?
when I go to configuration there is nothing selected:

I selected scene and pressed the arrow for the 4 buttons but nothing changes.

You need to wake up the remote for the settings to be accepted.

i’m confused. I thought my screen shot showed that the remove is awake. I did that by pressing the join button.

From my experience, one you wake it up, zwave-js will not show it going back to sleep until you send a command. The minimote will never say it goes to sleep. So if you wake it it may have gone to sleep.

You may have to set the settings multiples times. The UI will also not show the value because a Get is never sent. You just have to set the values and hope it works.

  1. Set button 1 to Scene mode, click arrow
  2. Set button 2 to Scene mode, click arrow
  3. Set button 3 to Scene mode, click arrow
  4. Set button 4 to Scene mode, click arrow
  5. Hold the Join button for about 3 seconds, the settings should get applied.
  6. Go to HA, use the event viewer and see if it’s recognized now.

If it doesn’t work, try setting the buttons in multiple passes, e.g. set buttons 1 and 2, wake, wait for a bit, then set 3 and 4. It took me several tries in the past.

It’s easier if you watch the zwave_js.log file to see if it sent the Configuration commands (may depend on your logging level). The file is accessible from the zwavejs2mqtt UI.

no luck :frowning:

What setting do I need to change to get a ‘zwave_js.log’ file in ZWave2MQTT? I only have zwavejs_1.log. I think that log confirms that the change was applied:

20:47:26.433 CNTRLR   [Node 012] Interview stage completed: CommandClasses
20:47:26.433 CNTRLR   [Node 012] Interview stage completed: OverwriteConfig

There is a working blueprint at ZWave-JS - AEON Labs (Aeotec) Minimote

thanks eseelke. I think my problem is getting the minimote to work with zwave2mqtt. I tried multiple times to configure it as scene mode but i cannot see the events in home assistant when I push a button. I know the remote works because it was working fine with smartthings :frowning:.

I had similar problems and i was moving from smartthings to homeassistant as well.
So here is what I did, after pairing with zwave js using zwavejs2mqtt as a secondary controller

  1. Goto configuration window on zwavejs2mqtt for Aeon minimote

  2. Wake up minimote by pressing the join button for three seconds. Once the device is up
    Change the 4 buttons to scene mode and secondary controller to scene mode as well

  3. After changing the values from each dropdown click the arrow to send the command to the device. Also, keep the debug menu in a seperate window to see what is happening. After all 5 modes have been changed maybe restart zwavejs2mqtt. Do not worry about the scene mode not showing in configuration, as long as in the logs you can see command sucessfully sent its all good.

  4. Go back to debug mode and see if you can register button press, if you can then goto homeassistant developer menu and look for zwave-js-event and see if you can view events for minimote.

Once this is done there is a simple automation for each button and long presses

Edit: Make sure you change the secondary controller mode to scene mode as well.
Edit 2: Firmware should be 1.19 if I remember correctly.

4 Likes

Thanks @kan84 ! That did the trick.

Glad that worked. I added another minimote after changing the battery. Have one more, struggling to change the battery but not going to lie they have worked well as remote devices on smartthings and am glad it has been working well with HA zwavejs

i have read this solution for the Aeon Minimote and this get me on to the right track.
I’m using Aeon Wallmote Quad and i think the solution is the same for every device.

My final code is as followed:

- alias: Wallmote 1
  trigger:
    - platform: event
      event_type: zwave_js_event
      event_data:
        device_id: [OWN DEVICE ID HERE]
        label: [OWN LABEL HERE]
        value: KeyPressed (or KeyHeldDown or KeyReleased)
  action:
    - service: switch.toggle
      entity_id: light.wall

I came to this solution as follow:

  1. Add node to Zwave JS
  2. Wait untill is fully reconised
  3. Go to Developer Tools - Events
  4. Fill in zwave_js_event by Listen to events and press start listening
  5. Press, hold or release the button on your node
  6. Press stop listening
  7. Write down device_id, label and value
  8. Change previous code into your own

Good luck.

Hey I am sure I need to set up a remote I have as a scene controller. Is it possible currently with zwavejs or only with js2mqtt?
If only with js2mqtt how do I stop the zwavejs integration so I can setup js2mqtt to change the values on the remote?

Thank you so much! I can now make automations for all my Buttons!

I don’t have a scene mode I can select in the dropdown?


Any input to why the Quad button is shown like this now?

Under configurations I only have power:

Hello,

You must make an automation for the scenes to work. i have made an automation for dummies like me. let me find it.

blueprint:
  name: Aeotec ZWA003 NanoMote Quad
  description: Create automations for the Aeotec ZWA003 NanoMote Quad using the
    OZW integration.
  domain: automation
  input:
    aeotec_nanomote:
      name: Aeotec NanoMote Quad
      description: The NanoMote Quad to interact with.
      selector:
        device:
          integration: zwave_js
          manufacturer: Aeotec Ltd.
          model: Aeotec NanoMote Quad
    button_1:
      name: Press Button One
      description: Action to run on button press.
      default: []
      selector:
        action: {}
    button_2:
      name: Press Button Two
      description: Action to run on button press.
      default: []
      selector:
        action: {}
    button_3:
      name: Press Button Three
      description: Action to run on button press.
      default: []
      selector:
        action: {}
    button_4:
      name: Press Button Four
      description: Action to run on button press.
      default: []
      selector:
        action: {}

mode: single

max_exceeded: silent

trigger:
  platform: event
  event_type: zwave_js_event
  event_data:
    command_class_name: Central Scene
    device_id: !input aeotec_nanomote

action:
  - variables:
      scene_id: "{{ trigger.event.data.property_key_name }}"
  - choose:
      - conditions: "{{ scene_id == '001' }}"
        sequence: !input button_1
      - conditions: "{{ scene_id == '002' }}"
        sequence: !input button_2
      - conditions: "{{ scene_id == '003' }}"
        sequence: !input button_3
      - conditions: "{{ scene_id == '004' }}"
        sequence: !input button_4

this one is for the nanomote

Just reply to me so i see if you have any problems. im a total noob and I made them all work with the help of the Forum

What are the values available under Scene 001 and so on. Quad button cannot be used as a secondary controller I believe thats why there is no group or scene mode.

Look for Scene under all four buttons and set it one by one after you wake the device. Then use the above blueprint for creating automation

Hi @Soccs thanks for reaching out! trying to help

To anyone else who finds this and wants to use the new Z-wave integration.
I created a new yaml in blueprint folder using the code provided from Socs
path: \config\blueprints\automation\homeassistant

I added the Nanomote Quad using the zwavejs2mqtt UI:

I then used the template to create and select the NanoMote:

This is great! - Any way to get double press working having 2x4 buttons? :slight_smile:
One thing fixed and then you just want more :wink:

You want 2 separate controllers do the same thing ?