You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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?):
Any thoughts on the issue?
The text was updated successfully, but these errors were encountered:
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.
Things I've confirmed and tried:
It looks like the cloud fallback is happening according to the logs:
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?):
Any thoughts on the issue?
The text was updated successfully, but these errors were encountered: