Tail your OZW_Log.txt file as you long press the button on the minimote. Which scene do you see being activated?
Please can someone help me, I have connected my miniote to OZWCP without any problems, I’m 99% sure I have managed to set it to scene mode, as its appearing the the OZWCP console. But when I restart HASS and press a button on the miniote there is no evidence of it anywhere in the HASS events console. I have tried so many times, and I feel like I’m going MAD.
I followed the video in BRUH’s youtube channel to the letter, apart from adding the config location for OZWCP in my yaml file, as this one doesn’t work, is the config path important? I just removed.
zwave:
usb_path: /dev/ttyACM0
config_path: /srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config
Here is the output from the OZWCO console,
00:01:47.749 Info, Node003, Received Scene Activation set from node 3: scene id=1 now. Sending event notification.
2017-02-09 00:01:47.749 Detail, Node003, Notification: SceneEvent
2017-02-09 00:01:47.749 Info, Notification: Scene Event Home e95bb835 Node 3 Genre basic Class NO OPERATION Instance 0 Index 0 Type bool Scene Id 1
It looks like you properly got the remote into scene mode, in console you should see a new entry every time you press a button (ie, you’ll get something like “Notification: Scene Event Home e95bb835 Node 3 Genre basic Class NO OPERATION Instance 0 Index 0 Type bool Scene Id 4” if you long press 2)
The config for yaml looks correct, you’ll want to double check that that location exists as that is how HA pulls in your zwave devices.
As for the entity id, I had to restart HA once after it first detected the remote to get it to complete the id (that could have just been what HA did at the time, maybe that’s been fixed). That said, it’ll be something simple like “aeotec_minimote_3” 3 being the node # you see in OZWCP. Just put that into the automation scripts provided by BRUH and your should be all set.
Good luck! You’re almost there!
I just added 3 of them to Hass.
One worked liked a charm and had no issues.
- Stopped Home Assistant
- Started up openzwave
- Chose Add Device
- Changed mode to scene
- Started hass manually to find the remote name
The other 2, I did the same thing and … nothing…
What finally worked was:
- I did the steps above for each device and made sure they worked in openzwave.
- Started Hass manually
- Then in Hass I went to the services tool and choose Domain “zwave”, Service “add_node” and then “CALL SERVICE”
- Pressed the “Join” button on the remote and viola! I can now see button (scene) presses in the Hass console
- Did this for the other remote
- Stopped Hass and restarted using the service
2 Likes
Thanks, I was also able to get the minimote to show up by doing what you suggested
Hi guys. If i wanted to use this just as a dimmer with on/off for my lifx bulbs would i leave it in group mode? And does HA support this remote in group? Thanks
Group mode is where you pair a single switch/dimmer with a single button, outside of HA. Is that what you want?
Actually you may be able to assign more than one light to a single button. There is a pairing process when I read the manual. But it has the ability to connect directly with a light switch without having a controller. I am not sure if you can have a switch connected to the Minimote and HA as I connect my 3 to HA using the scene mode. I would assume that you cannot connect the minimote to a light that is already connected to HA because z-wave requires you to only have 1 controller (Include/Exclude).
Definitely with HA so scene mode it is. Thanks for clarifying!
I realize this thread is old, but it was the first one that popped up when I searched for “minimote”.
At least in version 0.49.9 of Home Assistant, you can now use the z-wave control panel to directly set the “scene mode”. This is nice since I don’t need to stop Home Assistant, and fiddle with ozwcp to do this.
It took a few tries to bang the parameter change in there… first include the remote and it will show up as a new node. Zip over to the the HASS “Z-Wave Manager” pane. Select the new node from the “Z-Wave Node Management” pulldown list. Then scroll down to “Node config options”, and select the config parameter and config value like
Don’t press “SET CONFIG PARAMETER” yet.
Then press and hold the ‘Learn’ or ‘Join’ button (this is the bottom right button under the slider on my mimimotes) for a few seconds. The blue LED should come on… and now press “SET CONFIG PARAMETER” in Home Assistant.
I find it useful to have a tail -f OZW_Log.txt going in a shell window, and you can see the the COMMAND_CLASS_CONFIGURATION message being sent out. After this is successfully completed, you can bang on the scene keys, both short and long press, and you should see SceneEvent messages pop out as confirmation.
2017-07-16 17:14:16.944 Detail, Node016, Notification: Notification - Node Asleep
2017-07-16 17:14:28.455 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x01, 0x00, 0xce
2017-07-16 17:14:28.455 Info, Node016, Received Scene Activation set from node 16: scene id=1 now. Sending event notification.
2017-07-16 17:14:28.455 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:29.625 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x03, 0x00, 0xcc
2017-07-16 17:14:29.625 Info, Node016, Received Scene Activation set from node 16: scene id=3 now. Sending event notification.
2017-07-16 17:14:29.626 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:30.381 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x05, 0x00, 0xca
2017-07-16 17:14:30.381 Info, Node016, Received Scene Activation set from node 16: scene id=5 now. Sending event notification.
2017-07-16 17:14:30.381 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:30.818 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x07, 0x00, 0xc8
2017-07-16 17:14:30.818 Info, Node016, Received Scene Activation set from node 16: scene id=7 now. Sending event notification.
2017-07-16 17:14:30.818 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:30.912 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x07, 0x00, 0xc8
2017-07-16 17:14:30.912 Info, Node016, Received Scene Activation set from node 16: scene id=7 now. Sending event notification.
2017-07-16 17:14:30.912 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:33.305 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x02, 0x00, 0xcd
2017-07-16 17:14:33.305 Info, Node016, Received Scene Activation set from node 16: scene id=2 now. Sending event notification.
2017-07-16 17:14:33.305 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:34.835 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x04, 0x00, 0xcb
2017-07-16 17:14:34.835 Info, Node016, Received Scene Activation set from node 16: scene id=4 now. Sending event notification.
2017-07-16 17:14:34.835 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:35.906 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x06, 0x00, 0xc9
2017-07-16 17:14:35.906 Info, Node016, Received Scene Activation set from node 16: scene id=6 now. Sending event notification.
2017-07-16 17:14:35.906 Detail, Node016, Notification: SceneEvent
2017-07-16 17:14:37.025 Detail, Node016, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x2b, 0x01, 0x08, 0x00, 0xc7
2017-07-16 17:14:37.025 Info, Node016, Received Scene Activation set from node 16: scene id=8 now. Sending event notification.
2017-07-16 17:14:37.025 Detail, Node016, Notification: SceneEvent
6 Likes
How many tries did it take you to get this going? I’ve got the minimote added and when hold down the learn button and the blue led lights up, I try to set the parameter and it says its sends it in the log but the blue light keeps flashing like it never received a command. I’m using Hass.io or I would try the ozwcp path.
The flashing is just that it is awake after pushing the learn button.
Using tail -f on the OZW_Log.txt file will show you what is going on.
yeah I’ve been tailing, I get it added just fine and see that process, but when I go to do the second step of learning to change the config parameter, it says command sent, but the flashing doesn’t stop like it would after receiving the initial join command. And then the config option for mode goes back to group from scene and I can’t see any of the button presses coming in.
Got it working. Out of frustration I started to just hit the learn button randomly and that apparently woke it up to then received the queued config messages… now it works.
1 Like
Just got this working thanks to @lmamakos comment above.
A few key points from my experience…
- As long as the minimote is paired to home assistant and shows up in the Developer Tools States list, you can come back and set 250: Mode to Scene at a later time. You can even restart
hassif you want. Just know that you don’t have to quickly set the mode within some sort of short timeframe after pairing. The key is just to wake the remote back up with the Learn button. - To wake the remote up, you have to press and hold the learn button. If you simply touch it, it will go into a mode where the blue light is flashing. This will not properly wake it to receive the mode-change command. Pressing and holding Learn will make the blue light light up and then turn off. At that point, I was successful in updating the mode and could see my scene button presses being recieved in
OZW_Log.txt
3 Likes
thanks a lot - saw a bunch of confusing info when i searched just now for how to set this up - your info was short and sweet and worked. cheers.
in case anyone is interested, i created a blueprint for this here:
it seems to work 
tho if you press multiple buttons quickly in a row it doesn’t register all of the events
You should clarify that this blueprint only works with Zwave 1.4 (Deprecated)
Is there a more modern way of getting this to work? I recently dropped it from Vera hub and included it to HA, but I can’t seem to figure out how to get its buttons to trigger automations. The instructions above seem to revolve around an outdated version of HA where everything has since changed. Is the minimote that useless with HA? Is there a better rechargable remote solution out there? Because I hate coincell batteries.
Nevermind. Found a more current blueprint here: ZWave-JS - AEON Labs (Aeotec) Minimote
I then pulled up the device within Z-Wave integration, clicked configuration, scrolled down to button and enabled scene mode. Then I held the join button down until it awoke and updated. I created an automation with the Blueprint and everything is working. Shew…thought I was screwed there…
It should create event entities. If no, it’ll use zwave events