It looks as though a few folks have been having trouble getting their Aeon Labs Minimotes working under Z-Wave JS after migrating to it from the deprecated Z-Wave integration. We certainly were, and I finally had some time to look into this today. As it turns out, what needs to change in an automation’s configuration for Z-Wave JS to work with minimotes is actually pretty simple.
Caveats and assumptions:
- Your minimote was previously working under the deprecated Z-Wave integration and has been re-included successfully under Z-Wave JS.
- Your minimote is in scene, not group, mode.
- You know the minimote’s node number.
- This is not a guide to making your new or unconfigured minimote work with Z-Wave JS. There are a number of threads that can help you to make that happen; please search for them.
With that out of the way:
Let’s say you want to call a scene that turns on the bedroom light when button 1 is pressed. Configure the appropriate automation’s trigger thusly:
In the above example, the minimote’s node ID is 74 and we want to watch it for event value 1. Just change the node ID to the one that your minimote is assigned, and the ‘value’ field to the button press you’d like to have perform the action.
These values are equivalent to short or long button presses. Short button presses are 1, 3, 5, or 7; long button presses are 2, 4, 6, and 8. Each button has a short and a long press value assigned to it. As an example, the top-left button can generate either value 1 or 2 depending on the length of the presses.
Hope this is helpful - not having the minimotes available isn’t necessarily the end of the world, but having to dig out a phone or tablet in order to turn a light on or off gets old really fast.