mirror of
https://github.com/USA-RedDragon/badnest.git
synced 2025-01-18 19:20:44 +00:00
Update Info.md
Added SID= to the notes as the cookie seems to have changed (left the old example as well) and created a installation section so people who have not before added a custom component can do so.
This commit is contained in:
parent
7ab48d968e
commit
1f11cfb1dc
5
info.md
5
info.md
@ -22,6 +22,9 @@ This isn't an advertised or public API, it's still better than web scraping, but
|
|||||||
- Nest Protect integration is untested by me
|
- Nest Protect integration is untested by me
|
||||||
- Nest could change their webapp api at any time, making this defunct (this has happened before, see <https://github.com/USA-RedDragon/badnest/issues/67>)
|
- Nest could change their webapp api at any time, making this defunct (this has happened before, see <https://github.com/USA-RedDragon/badnest/issues/67>)
|
||||||
|
|
||||||
|
## Installation
|
||||||
|
You must take the "custom_components" folder from this repo and drop it at the root folder that contains your configuration.yaml. So you will have configuration.yaml AND a "custom_components" folder that has a "badnest" folder inside of that, which in turn has a bunch of py files inside of that.
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
The camera's region is one of `us` or `eu` depending on your region.
|
The camera's region is one of `us` or `eu` depending on your region.
|
||||||
@ -86,7 +89,7 @@ The values of `"issue_token"` and `"cookie"` are specific to your Google Account
|
|||||||
7. In the Headers tab, under General, copy the entire `Request URL` (beginning with `https://accounts.google.com`, ending with `nest.com`). This is your `"issue_token"` in `configuration.yaml`.
|
7. In the Headers tab, under General, copy the entire `Request URL` (beginning with `https://accounts.google.com`, ending with `nest.com`). This is your `"issue_token"` in `configuration.yaml`.
|
||||||
8. In the 'Filter' box, enter `oauth2/iframe`
|
8. In the 'Filter' box, enter `oauth2/iframe`
|
||||||
9. Several network calls will appear in the Dev Tools window. Click on the last `iframe` call.
|
9. Several network calls will appear in the Dev Tools window. Click on the last `iframe` call.
|
||||||
10. In the Headers tab, under Request Headers, copy the entire `cookie` (beginning `OCAK=...` - **include the whole string which is several lines long and has many field/value pairs** - do not include the `cookie:` name). This is your `"cookie"` in `configuration.yaml`.
|
10. In the Headers tab, under Request Headers, copy the entire `cookie` (beginning `OCAK=...` or `SID=...` - **include the whole string which is several lines long and has many field/value pairs** - do not include the `cookie:` name). This is your `"cookie"` in `configuration.yaml`.
|
||||||
|
|
||||||
## Notes
|
## Notes
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user