Beta v4 instructions need to be customized for MacOS

[BlackRockCity]

Description

I dont see the iframeRPC on a mac. A better tutorial is needed for macos users.

Device (optional)

No response

Additional information

No response

[BlackRockCity]

Update: I got it working. There were a few areas of struggle:

1. I had to manually download the beta 4.0v2 and install it manually by dragging it to the custom_components directory made visible because I had previously installed the 'Studio Code Server' Add-on. HACS installed the v3.0 release with no option to install the 4.0 beta as far as I could tell.

2. I tried incognito mode, but that didn't show the issueToken, so then I tried "clear browsing data". On a Mac, this is performed, not in the dev tools window but in the 3 ellipsis dots menu in Chrome>More Tools> Clear Browsing data. You only need to select the box that says clear "cached images and files".

3. the configuration form contains two methods with no explanation of which to use (sign in with google account and (field test)). When the first method didn't work I tried the 2nd method only to have to go back to the first.

4. the configuration form has no label... its not crystal clear that the issueToken goes in the first field and that the cookie goes in the second field. I assumed this correctly, but it would be nice if they were labeled.

Regarding Macos users:
For some reason filtering for IssueToken didn't show anything at all... then I open my macbook a day later after leaving the page open and it finally does show two iFramerpc entrities. Letting the page sit open seemed to make this data show up. Why did it take so long?

The instructions say to first filter for issueToken and then to filter for oauth2/iframe but on Macos Chrome these show the exact same data, so its a superfluous instruction that can be eliminated from the instructions. Coupled with no data showing at all initially for issueToken only to appear hours later, it added to the confusion.

[iMicknl]

Thanks @BlackRockCity. I hope to have some more time for this, so thanks for your clear feedback.

Regarding your first question; in HACS you can select "Show beta versions" in the dialog, to install the beta version. Hopefully this hassle with needing a beta version will be gone soon. The fields should be labeled now, but I have seen issues with no labels with other people that had an older version. If you install the latest beta version (manually) this should work.

[jnxxx]

I do not have a Mac, so I cannot try it out.

But in my experience (on Windows and ChromeOS), if a user is already logged in, then the two searches will find the exact same request in dev. tools.
With cleaned cookies or Incognito, it finds two different requests.
issueToken do have many (if not all) of the same cookies, but it updates one in response.

My experience when not properly cleaned, is that it led to reduced session lifetime.

If searching in dev. tools works differently, one possibility might be to search for "accounts.google.com" (hostname). It seems the second-last will be the issueToken, and last one the cookies.

[BlackRockCity]

I was able to enable the beta downloads by going to HACS and clicking the nest card then choosing redownload from the ... menu and then activating beta versions.

installed 4.0b4

restarted HA

clicked add integration > nest

In 4.0b4, the issuetoken and cookie fields were now labeled.

I had a better time doing this under Microsoft Edge Browser for MacOS.

Opened a New private browsing window.

loaded home.nest.com

logged in.

found the network tab and checked preserve log

signed out.

… > more tools > application > storage tab (on the left) > clear site data

logged in again.

followed these instructions to get the issueToken request url and oauth/iframe and request header cookie and the instructions worked:

https://community.home-assistant.io/t/integrating-nest-protect-smoke-alarms/603253

now i will see how long the cookie lasts

Update: 2 days later and the cookie is still working!