Can anyone advise how to troubleshoot if it says “no matching devices found” under device when you try to use the blueprint?
I’m running core-2021.4.3, zwavejs2mqtt 0.11.0, and the wallmote shows up under the zwavejs2mqtt control panel as AEON Labs WallMote Quad ZW130
Does it show up under devices in home assistant like mine? The lines of code below are what is controlling the selector.
I would start with upgrading zwavejs2mqtt with something newer. I’m currently running as a standalone container, not running Home Assistant OS. Here’s the version info from the zwavejs2mqtt info box: zwavejs2mqtt: 3.2.1, zwave-js: 7.2.2
I was using the previous version of this blueprint but removed it so I could add the new one. Unfortunately, it seems I can’t do that. Should there be an Import Blueprint button on the top post?
If import doesn’t work for you, you can always just copy and paste the contents of the blueprint into a file you create yourself. The import button is just a convenience feature.
I did end up adding it that way. Was looking for the Import Blueprint button to take advantage of this functionality:
Updating Blueprints
When a user imports a blueprint, Home Assistant stores the URL from which it was imported. This will allow Home Assistant in the future to update blueprints by looking at updated blueprint code in the forum topic.
Anyway, thanks for the blueprint!
thx for your work, works perfect!!!
I know i’m still new to HASS, but I still can’t get it to work. When I try to create an automation from the Blueprint, it tells me there are no matching devices found… But the device is there and connected in Z-Wave JS…
If you look in the blueprint, you’ll notice this chunk:
zwavejs_device:
name: ZWaveJS Device
description: The Aeotec WallMote Quad controller to listen for events on.
selector:
device:
integration: zwave_js
manufacturer: AEON Labs
model: ZW130
You need to have a device that is using the zwave_js integration, from AEON Labs with the model number ZW130. If that doesn’t match, then you will not get anything in the input device selector. Are you absolutely sure that you have a ZW130 device, and not a clone or device from another vendor? There are three Z-Wave implementations for Home Assistant, and this blueprint is only compatible with ZWave-JS. If all of this matches, then I think you might have an issue in your Home Assistant to ZWave-JS integration and you’ll need to debug that.
If you go into the event listener and listen for the event zwave_js_value_notification and then try to tap the buttons on the wallmote, do you get any output? If you don’t, then you have a HA/ZWaveJS communication issue. If you get events, then you might have some other device, or some weird firmware issue.
Thanks Robin, turns out the issue was with my zwave js config. I fixed that and it showed 
Can you use this blueprint on multiple wallmotes?
Seems everytime I try to setup another automation using the blueprint, it errors until I remove all the actions.
I actually use it with two in my home, so my immediate answer would be yes. You’ll need to share more details from your setup to be able to debug it properly. Maybe a copy of the YAML automation using the blueprint would help, or possibly an automation trace file (although I don’t know how to use those yet).
I did finally get it to work, and onto a third so that’s good.
Not sure what HA was moaning about with it, but after I did the 2nd automation in the visual editor saved and copied into my yaml automation file it worked.
Some reason just didn’t like me typing it out, even tho I copied and pasted over the autogenerated one.
Must have been a weird line ending character somewhere.
Strong Work, Robin! I am trying to adapt for Wallmote Duo ZW129. Has anyone done this yet? What needs to change? I am scanning the ZWave log files for clues.
To my knowledge, they are exactly the same, except the Duo has two switches instead of four. I think you should only need to change the device selector to make it work. I’m guessing that two of the four switches will work, so it should be a matter of just renaming those to left/right or top/bottom (depending on the orientation) and just removing the two others.
I seem to recall that I have seen someone post here on the forum a blueprint for the Duo based on my blueprint already.
I recently installed Z-Wave integration, a handful of sensors, and most recently a WallMote Quad. The sensors are working perfectly, and I can see the WallMote communicate via Event Listener. However the blueprint does not recognize the AeoTec WallMote Quad (ZW130). I’m running core-2021.11.1, and see a number of power management sensors when looking at the Device WallMote. But that is about it. Any help would be appreciated. I’d like to get the switch operational.
If you don’t get the WallMote Quad in the dropdown list I’m guessing you’re not using ZWaveJS integration for Z-Wave support in Home Assistant. If you’re using either the zwave or the ozw integration (both deprecated), this blueprint won’t work for you. You’ll need to migrate to the zwavejs integration.
I’m using the latest build of ZWaveJS (Current version: 0.1.46) with an AeoTec ZWave stick (Firmware: 1.1) with Home Assistant 11.01 HASS. I’ve never used the deprecated ZWave integrations.
I just put the ZW130 in single quotes, so I now get two devices, the stick and the switch. Let me put an automation together and see if this is now working. Thanks
I got it working … thanks
I was having issues getting this to work. What I finally figured out was that there was an issue with the interview process and I had to re-interview the wallmote. Be sure that under the device overview it shows Device Ready: Yes (Goto Configuration>Devices & Services, Click the Devices tab, search for WallMote and click the entry to find this). If it’s not ready then click Re-Interview Device.
Before I reinterviewed i was seeing log entries when I would tap the buttons so I didn’t even think to look if the device was ready, but evidently the logging can still occur even if it’s not in a ready state.