-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add Camera Devices (Doorbells, Hubs, Cameras, etc.) #62
Comments
Thanks! Would you know which values we need to expose (not supported in SDM only!) and which values we need to be able to change? (select or switch?). (and can you change these settings via https://home.nest.com? In that case, you could have a look at the XHR request as well and share them here). |
As far as things to try to expose to Home Assistant:
Yes, you can control those things from home.nest.com. Not sure if sensing the doorbell ring or motion-related sensing is visible there, though. Do you have any docs or a guide for how to look at the XHR request you mentioned? I'm not familiar with that, but I'm happy to try it out to get additional data. |
@ErikSGross are you sure that doorbell ring etc. are not implemented yet in the SDM API? Here you find an example of how an XHR request would look like: https://support.deskpro.com/en/kb/articles/how-to-inspect-ajax-requests-with-chrome-tools |
This is new to me, but poking around the XHR data, I see the following when I enabled a camera that was previously disabled: There's a POST request to And then there's a response of:
I tried disabling the camera and I got basically the same thing, except I'm not sure where the UUID comes from, but I'm assuming that's associated with the particular camera I toggled the enable for. Presumably, a call to that API would allow you to set/get any of those settings associated with the camera, right? Is that what you're working with to observe/manipulate the topaz/kryptonite devices? |
Opening up the settings page of a doorbell results in this XHR entry: GET request to: Response is similar to above, but much more data proivided - the above entries are all contained within |
Thanks @ErikSGross! It seems that cameras use another endpoint, which I didn't implement yet. I am quite busy the coming period, but let's keep these issues open to track this request. Perhaps someone else with cameras is willing to implement this and otherwise we need to wait. The HomeBridge repository uses these endpoints as well, thus could be a good example. |
I wanted to see what functiuonality homebridge currently exposes, so I spun up an instance and added the
The authentication method appears to be the same as what The homebridge plugin has a configurable polling interval, so it appears this is cloud polling, not cloud push. Setting the polling to the default of 10s seems to get notifications reasonably quickly. So it looks like it's definitely possible to get Google/Nest to cough up the data, and the method seems very similar to what's already present in |
They use the GRPC / protobuf API, however this works in another way and is hard to test and debug for me since I don't own any of these devices. When I have some more time in the future, I will perhaps give it another try, but for now this won't be implemented soon. |
Description
Though the Google SDM API allows access to the cameras integrated into the Nest Hello doorbell and Nest Hub Max products, it does not allow control of the devices. Additional control and information for these devices is located in the Nest mobile app, so perhaps these devices can be enhanced by this integration.
The doorbell and hub devices are available as
quartz
buckets like this:The
object_key
entry for a doorbell looks like this:The
object_key
for the Hub Max looks like this:Device (optional)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: