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

REACHABLE_DEVICES only sent for one proxy device if multiple are present #147

Open
dominik-polic opened this issue Aug 29, 2024 · 1 comment

Comments

@dominik-polic
Copy link

I have a situation where I have multiple proxy devices, each of which has 1-7 endpoint devices connected to it. I'm trying to implement the local fulfilment and I've encountered a problem where after IDENTIFY-ing multiple devices as proxies, only one is actually working correctly, meaning that I only get REACHABLE_DEVICES request for one of them.

I receive and handle IDENTIFY request for all of them, and set the payload.device property of the response to:

{
 id: "[DEVICE_ID_HERE]"
 isLocalOnly: true|false
 isProxy: true
}

Some proxy devices also have OnOff functions of their own, so isLocalOnly is set accordingly if the specific proxy device is also available via cloud fulfilment and present in the SYNC response. I tried with all local only and all cloud-supported proxies and it made no difference.

It seems like the local fulfilment API only supports/recognizes one proxy/hub device and ignores the rest. The proxy device that gets the REACHABLE_DEVICES request is random and changes after each restart of the Google Nest device. EXECUTE intents work correctly for all actions that impact proxy devices directly and for the one proxy that has handled the REACHABLE_DEVICES, devices connected to that proxy handle the EXECUTE request correctly. Correct state is also reported to the Google Nest device and the Google Home app using local fulfilment. Devices connected via other hubs are never discovered locally and are actuated using cloud fulfilment.

@dominik-polic
Copy link
Author

This issue might be related: #94

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant