Ah. Never mind. Apparently the zha_event log is not quite complete, and within the automation it looks slightly different. Some logging shows that actually {{args}} renders as [<MoveMode.Up: 0>, 50] in this case, and indeed then args[11] == 'U'.
You are right the zha_event indeed renders a bit strange. It took me a while to figure out that “[<MoveMode.Up: 0>, 50]” is a string and not a struct or object.
Hi all!
I’m quite new to HA.
Great work creating this automation!
My Robb-shop-8-button remote has a similar problem as stated in this thread before:
It seems logical that the cause is my button advertising in HA as ROB_200-025-0.
I opened an issue on github (8-knops-remote advertises as ROB_200-025-0 · Issue #2 · Bekkie/ha-blueprints · GitHub): I hope I didn’t annoy anyone with that…
I tried, but I couldn’t get the blueprint working as an automation: I’m just not that good at coding.
Could someone please help out? Adding the device in the restriction or an explanation on how to rebuild the blueprint to an automation would be a great help!
Champs74 I removed the model restriction and changed it to this model. Now itś working fine.
blueprint:
name: Robb smarrt 8-button switch
description:
"This blueprint is for the Robb smarrt 8-button switch panel (ROBB
ROB_200-007-0) when used with zha.
It is for general use so all buttons can be connected to any action of your choice.
This remote supports short button clicks and long button presses (over 4 seconds)
Make sure to select the correct sensor for the remote.
"
domain: automation
source_url: ha-blueprints/automation/robb-smarrt-8-switch-ROB_200-007-0.yaml at caf9109fe262dfb3bd80a68965824a1ffafbfae5 · Bekkie/ha-blueprints · GitHub
input:
remote:
name: Remote
description: Switch remote to use
selector:
device:
integration: zha
# model: ROB_200-007-0
model: ROB_200-025-0
multiple: false
on_button_1_short:
name: On button 1 - short
default:
etc.
Thanks!
I already had it working creating a blueprint based on Bekkie’s, with different device restrictions.
Great work responding to my ‘urgent’ issue!
hi, how can i get the vesternet switch to work? thanks
Hi. I have the vesternet 8 button version. I modified the device name in order to be able to select the switch. The short presses work but the long presses don’t. Could you help me work out how to get it working? Thanks
Hi where can i find that blueprint?
@gooseodyssey @jackbauer538
have you managed it to work in the meantime?
Thanks!
Sorry which blueprint are you referring to?
I never got the long presses to work with this blueprint, only short presses. I switched to Zigbee2MQTT and made my own automation and it seems to work well.
the 8 button one linked in the first post. is z2m really a good option? i have so many zha devices already set up
Hello, it is me again. The newbie trying to make use of a set of 4 Vesternet 4 button zigbee switches I got for a good price. Maybe there was a reason for that…
I have managed to factory reset one device for testing and I have also joined it to HA using ZHA.
I have found this thread discussing the Robb 4 button switch which apparently is the same device. Hence I have imported the 4 button version of the blueprint above.
So far so good, this is according to the description found here.
When I try to create an automation using the Robb blueprint, I am unable to select an input device.
This throws me off for a while until I realise that the code that was graciously shared in this thread locks the blueprint to devices with the manufacturer entity set to “ROBB smarrt”. Thinking I am a clever sod and an ex-developer I expect to be able to create a new instance of the blueprint into which I can modify the manufacturer entity.
That is basically what is described under “Editing an imported blueprint” here.
Unfortunately, when I try and take control, it doesn;t happen as described. I am unable to get an editable copy of the YAML of the blueprint. I can’t get access to the YAML at all.
Any top tips? What is it I am misunderstanding or forgetting?
Yes, I have tried copy and paste of the YAML. I just don’t seem to be able to create my own instance of the blueprint, hence no editable YAML.