Great to hear that things are working! I think one important detail that was not clear in my earlier answer is the “Learn” button wake-up method from the manual.
I think one should press and hold “Learn” button certain number of seconds to wake up the minimote, it may not be enough just to click Learn button.
It is also great to hear about Zensys tool!
Ok - got it group mode - but in the yaml above - how did you come by the entity id? It’s not in the xml file for the zwcfg_xxxx.xml.
Still a no go for me - but working on it.
OK - found the id…by watching the HASS console via putty when I hit the switch. Got it working 
YEAH!
Now…after having to reset the z-wave usb stick through all of this, lost all of my switches/bulbs…and now the stick won’t go into include/learn mods…NOOO. So working on that now.
YEAH!!! All back up and running -with everything the way it should be - w00t!
How did you get the entity ID? What do you mean by the HASS Console? I think I have everything in scene mode, but I’m having trouble figuring out what the entity_id is.
@raccoonz - the HASS console I’m referring to is the putty session I had going to the raspberry pi - if you start HASS from there, you’ll see the output in real time from HASS. So if you click the button, you’ll see the button press occur. The entity_id will be listed as you press the button. That’s exactly how I got the entity_id - I did a copy/paste of the putty session and pasted it into notepad on my laptop, then copied the entity_id from there into my yaml file(s).
Hope this helps!
@vexter0944 I don’t get any output from HASS from a button push when I start HASS from the command line. I do get output from tail on the OZW_log file. Would you mind sharing what your entity_id looks like. This is what I get from the openzwave logs and I just don’t know what to use as the entity_ID.
2016-09-06 13:05:04.694 Detail, Node008, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x08, 0x04, 0x2b, 0x01, 0x01, 0x00, 0xd6
2016-09-06 13:05:04.695 Detail,
2016-09-06 13:05:04.695 Info, Node008, Received Scene Activation set from node 8: scene id=1 now. Sending event notification.
2016-09-06 13:05:04.696 Detail, Node008, Notification: SceneEvent
2016-09-06 13:05:04.696 Info, Notification: Scene Event Home d58eea90 Node 8 Genre basic Class NO OPERATION Instance 0 Index 0 Type bool Scene Id 1@zarthan - Here’s the exact automation from my .yaml for this remote - I can try and see if I see stuff in the console when I get home, but I’m almost 99.9% sure that’s where I got it from…
> alias: Minimote Button 1 Pressed
> trigger:
> platform: event
> event_type: zwave.scene_activated
> event_data:
> entity_id: aeotec_dsa03202_minimote_4
> scene_id: 1
> condition:
> - condition: state
> entity_id: switch.ge_unknown_type5052_id3031_switch_2
> state: 'off'
> action:
> service: switch.turn_on
> entity_id: switch.ge_unknown_type5052_id3031_switch_2@vexter0944 thanks for the reply. I think I understand the “aeotec_dsa03202_minimote” part. It is what shows up in the open zwave control panel minus the underscores in place of spaces. If the 4 in your configuration corresponds to the 8 in my node008 then I would need to use "aeotec_dsa03202_minimote_8 " in my test yaml file. Unfortunately that doesn’t work. I sure would appreciate the check on your end. Thanks
I can check - but what I ‘think’ may be going on (and I’m NO expert by any means…) is that the remote may not paired correctly. I think I added mine by clicking zwave/add device under the developers options. - I’m trying to remember but can’t this minute. But if not added correctly, I noticed it didn’t register as the “aeotec_dsa03202_minimote” but some generic kind of zwave device or something like that. I’ll try to remember to check the console when I get home.
I can try un pairing and re pairing to see if that helps. Thanks
@vexter0944 after I reset the minimote and re paired it works. I paired it through the OZW control panel. The entity_ID does use the nodeid that shows up in the control panel. So after pairing my entity ID became aeotec_dsa03202_minimote_28
Many thanks for your help!!
I was able to add my MiniMote via OZW, but couldn’t see it in HA. Are y’all seeing the remote on the states page?
I’m running the all-in-one installation of HA, so I’m not sure where to look for the console.
But I was able to trigger automations with it based on @vexter0944 's example above. When looking at the OZW output, I could see that the MiniMote was node 4, so I used: aeotec_dsa03202_minimote_4
But if I didn’t have that example with the entity_id, how would I know what to use?
If you have it working with scenes, you should see a HA log entry every time you hit a button. If you look at the entity id in the log info, that is its name
When you say “log”, do you mean the /logbook service? I don’t see an entry there, Nor in /home/hass/.homeassistant/home-assistant.log
@ih8gates - the log @aimc should be referring to (I believe) - is the console log for HASS (putty and start HASS is how I did it…) and you should see the remote presses in there IIRC.
Ok. I guess my confusion is stemming from the fact that I did the all-in-one install, so HA is running as a service in its own virtual environment. I was hoping the log would show up somewhere “easier to reach”.
If you used the all in one you should be able to see the log with:
sudo journalctl -u home-assistant@hass
If you add -f it will sit there and print out updates as they are written to the log.
I wonder, for the people that have a working remote: if you reboot your PI do you have to re-pair your remotes?