Closed TheDeein closed 2 years ago
I had an old instance of Homebridge, I completely reset the RPI and started fresh. the same problem is happening even with a fully updated version.
I fixed my own problem. I removed the association with the bridge and reconnected it. now its working fine.
the difference in connecting this time around was this -
[22/08/2022, 22:00:46] [Homebridge UI] [homebridge-lutron-caseta-leap] Incoming Request: /associate [22/08/2022, 22:00:46] [Homebridge UI] [homebridge-lutron-caseta-leap] Got request to associate with (DEVICEID) at 192.168.1.8 [22/08/2022, 22:00:46] [Homebridge UI] [homebridge-lutron-caseta-leap] association phase connected (DEVICEID) 192.168.1.8 [22/08/2022, 22:00:52] [Homebridge UI] [homebridge-lutron-caseta-leap] got message { Header: { StatusCode: '200 OK', ContentType: 'status;plurality=single' }, Body: { Status: { Permissions: [Array] } } } [22/08/2022, 22:00:52] [Homebridge UI] [homebridge-lutron-caseta-leap] Physical access confirmed
Glad you got this sorted. I suspect the issue was in HomeKit, and re-associating kicked it hard enough to stick. Once the button press is recognized, the plugin updates HomeKit and it's out of the plugin's control. The association message you've pasted is a normal part of bridge setup, and would have appeared for any successful connection to the bridge, which you demonstrated. If it recurs, please feel free to re-open this ticket, and thank you for the report.
Describe The Bug: I enrolled the devices and they show up on homekit no propblem. When I assign an action to the button it saves it no problem. Upon clicking the button the press shows. However nothing happens afterwards. The actual automation of turning on the light or off doesnt work.
Expected behavior: When I hit the on the PJ2-3BRL I wanted to turn on a light
Logs:
More Logs
Screenshots: https://www.youtube.com/shorts/QavB03Q82gI
Environment: