Zigbee 8 Button Wall Controller Advice needed

Evening all,

I am probably being stupid but I have just brought 2x 8 button controllers Vesternet Zigbee Wall Controller - 8 Button and I have paired them to Home Assistant through Sky Connect but when I try to create automations using Device as Trigger the only options I get for them are “Device Offline” / “battery level changes” and “identify has been pressed”.

With the other type of controller I had it lists all the different actions/buttons so not sure why I am missing.

When I go into the device page and I press a button I can see events fired:

Bed Switch On event was fired

19:19:32 - Now

Bed Switch Off event was fired

19:19:11 - 21 seconds ago

Bed Switch Move With On Off event was fired with parameters: {'move_mode': 1, 'rate': 50}

19:13:58 - 6 minutes ago

Is anyone able to advice please? Thanks.

Perhaps you need a blueprint:-

Hi I have the same controller. Can you help me please get it working? I’m new to all this. I have ZHA running but should I be using Z2M instead? I have got the short press buttons working using the blueprint linked here. I had to change the device name in the blueprint using the file editor. I can’t work out how to get long presses working. Thank you

I have imported both the 8 and the 4 button versions. Neither of them I can get to work. The vesternet switch I am trying to use as the input device has been paired on Zigbee and shows up as a device. However, I cannot enter it in this blueprint.

Its not guaranteed to work, it all depends on the device signature and how the blueprint detects it, and whether you are using ZHA or Z2M.

I’d start by seeing it its even sending events. Assuming you are using ZHA for your zigbee devices, go to the developer tools and click on the events tab.

On the right hand side, choose zha_events, then in the listen to events box put

state_changed

Then click start listening.

Then click some buttons on your device, does anything show up ? (Note that other things might also send events, so you need to be sure its your problem device thats showing up).