Is there any speed or performance differences when setting up a button using Machine Rule vs the Button Controller app? I've added my first buttons today and it seems there is a several second delay from pushing the button until the action taking place using a Basic Rule.
I don't think there'd be a perceptable difference under most conditions. I'm guessing the issue may be between the button device itself and HE... but you should be able to verify this by looking at the device page or the page's events tab when you actually press the button.
What kind of button controller is it?
1 Like
Its a ZOOZ ZEN34
How's your zwave mesh look? I'm wondering if that's the source of the delay.
1 Like
Funny you should mention that. I can run a repair on individual devices, but when I select "Repair ZWave" at the top it just hangs with the status screen showing forever. Also, there are no ghost devices in the list.
Doing a general zwave repair isn't recommended anyway... at least not on a C7. I assume the button is there for backward compatibility with earlier models.
What does your zwave details page show for response time (RTT) on your Zooz?
3 Likes
Actually, I got it work by switching browsers. It reported 2 failed nodes. I then ran a device level repair on both of them and the node failure shows up there too. What does this mean and is there a way to fix it?
Note that of those devices seem to work fine in all my Machine Rules and button programming.
Post a screen shot of the failed nodes.
Actually both are brand new and installing today when I had the problem. I'm going to return them and replace with different brand. Thanks for help.
To help others who may try to use these buttons, you could post what brand/model you tried. Good luck w/your button future. 
1 Like
