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

Local Home app IDENTIFY requests not showing up #52

Open
mchiang-goo opened this issue Dec 30, 2020 · 1 comment
Open

Local Home app IDENTIFY requests not showing up #52

mchiang-goo opened this issue Dec 30, 2020 · 1 comment

Comments

@mchiang-goo
Copy link

I'm going through the README and got to the last section of trying to test that the local home SDK works with the virtual device.

When going into the Chrome inspector however, I'm not receiving any IDENTIFY requests at all per the attached image.

Screen Shot 2020-12-30 at 6 36 20 AM

Things I've confirmed and tried:

  • I've got the UDP scan config configured on the AOG console, the virtual device running with the discovery protocol as UDP, and the cloud fulfillment control protocol and virtual device control protocol matching one another (currently HTTP for the hub example).
  • Unlinking/linking the virtual device in my Google Home App (though every time I tap on them, it says they're offline)
  • Rebooting my Nest Mini (by plugging/unplugging)

It looks like the cloud fallback is happening according to the logs:

Screen Shot 2020-12-30 at 6 49 18 AM

It seems like local discovery isn't happening...not sure if the SYNC request is being sent (I'm assuming that the SYNC request happens in the cloud functions in the sample code), or my virtual device is configured incorrectly when I run it (is the address supposed to be 0.0.0.0?):

Screen Shot 2020-12-30 at 6 57 34 AM

Any thoughts on the issue?

@proppy
Copy link
Collaborator

proppy commented Jan 21, 2021

I believe the README might have errouenous value for Broadcast and Listen port.

  • Broadcast port should match the UDP port the virtual device is listening on 3311
  • Listen port should match the UDP port the Home device will wait for a response on 3312.

Can you confirm if updating those fixes the issue for you?

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

2 participants