tonesto7
commented
4 years ago Buttons are weird under home ridge. They won't trigger button press events back to ST. They only allow you to link automations to each button
Open shaunreinson opened 4 years ago
tonesto7
commented
4 years ago Buttons are weird under home ridge. They won't trigger button press events back to ST. They only allow you to link automations to each button
shaunreinson
commented
4 years ago I set up an automation on Homekit (via the Button device setting, not the Automation option - as per Home instructions), so that when Button 2 is pressed it changes the temp of the Honeywell Evohome Office Thermostat plugin that I'm also running on Homebridge.
This is not via ST.
I can see the button being pressed on the Homebridge status page.
But it still doesn't trigger an automation on Homekit, event though its not via ST.
Do Buttons work at all on Homebridge, as its not linking automations ?
zburk
commented
4 years ago @tonesto7 I'm also having an issue with the SmartThings button where if the same signal is sent twice (press -- press) nothing is triggered. If I send different signals (press -- double press), HomeKit registers the signal.
In the video, you can see Homebridge always registers the click in the logs but HomeKit only recognizes it when it's different back to back. https://streamable.com/n8uy78
shaunreinson
commented
4 years ago I have similar - example being the ZWave Aeon Minimote, which has 4 buttons and registers 4 child devices as accessories, this is good. When you press a button, the status window displays 'Button Number: 1 Button Value: Pushed' but repeats it 4 times. Homekit won't recognise this - neither will Node-Red, although it does get the occasional one - typically Press, then Hold - will show the Hold then Press again will show that - so you're basically alternating between states on the one button.
Fairly sure it shouldn't work like this.
I've tried using a few buttons on ST now - Fibaro fob, Popp Keypad (with my device driver which emulates a 23-button device), Nodon 4-button etc... - they all work fine in ST but I can't get them to trigger any automation on Homebridge.
I've tried all sorts of combinations, including with and without child devices.
I've inspected the log/console on Homebridge and its receiving the button being - although it will repeat it according to the number of buttons on the device - so Fibaro has 30 possible key sequences and when you press '+' on the pad it says 'Button 6 pressed' but says it 30 times. Same for Popp keypad which has a device driver with 23 'virtual' buttons - so says 'Button 1 pressed' 23 times. I think you get it...
When I edit the setting on Homekit on the button device, it has each button in there to be edited and I've used a light bulb as the test - with simple on/off - either as the device itself, or as a scene.
Both 'test' okay in Homekit, but the automation is refusing to run.
Has anyone actually got buttons (think they're also referred to as stateless devices) to work with this at all, and if so, what tweaks were needed ???
Either that, or its a bug....
All my Homebridge software and plugins are on OSX (Catalina) and I've running the latest everything, with no updates needed anywhere.