Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't seem to get the plugin to detect my lutron hub #158

Open
hmangnx opened this issue May 28, 2024 · 5 comments
Open

Can't seem to get the plugin to detect my lutron hub #158

hmangnx opened this issue May 28, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@hmangnx
Copy link

hmangnx commented May 28, 2024

Running the latest version of the plugin, I cannot setup the plugin because it doesn't detect the hub. Is there anyway to point the ip directly to the hub? Or some other way to get around this?

@hmangnx hmangnx added the bug Something isn't working label May 28, 2024
@Auirsblade
Copy link

Same issue here. I have a completely fresh homebridge install, and both the homebridge and lutron hub are correctly detected by homekit, but homebridge can't reach the lutron hub.

@thenewwazoo
Copy link
Collaborator

Are you using docker?

@Auirsblade
Copy link

Yep, so I had to jump though some hoops to get Homebridge itself communicating on the right interface, and advertising properly over mDNS. For what it's worth, overnight I got some logs where it seemed like it found the bridge, or at least the IP+BridgeID, but the plugin setup screen still stalls.

2024-08-30T07:40:55.397Z leap:protocol:discovery got useful ipaddr 10.0.0.164 2024-08-30T07:40:55.397Z leap:protocol:discovery extracted bridge ID: 0512CD4B [8/30/2024, 2:40:55 AM] [LutronCasetaLeap] no credentials from bridge ID 0512CD4B 2024-08-30T09:11:23.216Z leap:protocol:discovery checking HostAndPort { host: '10.0.0.164', port: 22 } 2024-08-30T09:11:23.218Z leap:protocol:discovery was not ipv6: Error [AddressError]: Incorrect number of groups found at new AddressError (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/ip-address/lib/address-error.ts:5:5) at Address6.parse (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/ip-address/lib/ipv6.ts:713:13) at new Address6 (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/ip-address/lib/ipv6.ts:153:31) at BridgeFinder.extractIp (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/lutron-leap/src/BridgeFinder.ts:95:30) at BridgeFinder.handleDiscovery (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/lutron-leap/src/BridgeFinder.ts:60:29) at MDNSServiceDiscovery.<anonymous> (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/lutron-leap/src/BridgeFinder.ts:43:18) at Event.emit (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/atvik/src/sync.ts:65:29) at MDNSServiceDiscovery.BasicServiceDiscovery.updateService (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/tinkerhub-discovery/src/discovery/basic-service-discovery.ts:67:24) at MDNSServiceDiscovery.refreshService (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/tinkerhub-mdns/src/discovery/mdns-discovery.ts:346:8) at Timeout._onTimeout (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/tinkerhub-mdns/src/discovery/mdns-discovery.ts:206:27) { parseMessage: undefined }

These logs started after the scheduled backup, and then have popped up every ~hour and a half since.

@Auirsblade
Copy link

Oh additionally, to get the plugin to run at all (before it wasn't initializing or logging) I had to add the secrets section to the json config with some null values, and that got it at least running and logging:
{ "platform": "LutronCasetaLeap", "name": "LutronCasetaLeap", "secrets": [ { "bridgeid": "", "ca": "", "key": "", "cert": "" } ] }

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants