Change Discoverability in Google Home
A documented Google Home operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Change Discoverability
- POSTChanges data · Bluetooth
example.com/bluetooth/discovery
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Home operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Google Home operations
- Reboot and Factory ResetPOST · changes data
- Scan for NetworksPOST · changes data
- Forget Wi-Fi NetworkPOST · changes data
- Connect to Wi-Fi NetworkPOST · changes data
- Set Eureka InfoPOST · changes data
- App Device IDPOST · changes data
- Test Internet Download SpeedPOST · changes data
- Forget paired devicePOST · changes data
Questions
- Can HumDay change discoverability in Google Home?
- Yes. This operation is published in Google Home's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Google Home data?
- Yes — this is a POST operation, so it changes something in Google Home. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Home account.
Where this came from
Read from a published API description for Google Home at raw.githubusercontent.com/rithvikvibhu/GHLocalApi/master/GoogleHome.openapi3.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.