Current version shows no networks after verifying by email

[RuneMason1]

[rolandflores]

Having the same issue here.

[yarafie]

Same here it happened after subscribing to eero plus for me

[dennyreiter]

Same here I just noticed. My network was there but none of the sensors were available. I deleted it and tried to re-add, but no networks were available.

[PacoCT]

The same issue here. My config:

• HA on virtuaalbox (Host: Windows 11)
• USB WiFi Dongle passed to VirtualBox through USB Filter
• Second (non-Amazon) account as an admin of eero app/network, even though I am logged in the app using the amazon account

A dumb question: In order eero custom integration to work, HA has to have access to eero network using WiFi, or it can manage the eero network though a hard-wired connection?

[schmittx]

@PacoCT Home Assistant doesn't need direct access to the configured network (Wi-Fi or ethernet). The integration works by communicating with eero's API only. Eero's API handles the communication between the actual network(s).

Besides @PacoCT is everyone else using a non-Amazon account to login to this integration?

[yarafie]

@schmittx I'm using a non-amazon account (Set up another admin account), but as I mentioned It was working before I subscribed to eero plus (Google Play Subscription) For another reason I cancelled my eero plus subscription and it started working again.

[schmittx]

@yarafie Understood. From this issue and others it seems that eero API returns multiple values to indicate if a subscription is present/valid, it's hard to capture and test them all.

[RuneMason1]

Secondary admin invited. No eero plus sub. Eero is ISP provided, if that changes anything.

Sent from my T-Mobile 5G Device Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Matt Schmitt @.> Sent: Friday, March 1, 2024 9:59:58 AM To: schmittx/home-assistant-eero @.> Cc: RuneMason1 @.>; Author @.> Subject: Re: [schmittx/home-assistant-eero] Current version shows no networks after verifying by email (Issue #75)

@yarafiehttps://github.com/yarafie Understood. From this issue and others it seems that eero API returns multiple values to indicate if a subscription is present/valid, it's hard to capture and test them all.

— Reply to this email directly, view it on GitHubhttps://github.com/schmittx/home-assistant-eero/issues/75#issuecomment-1973347763, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASZJ6XAZ5ADBU645NB5B43LYWCJW5AVCNFSM6AAAAABBJQTB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGM2DONZWGM. You are receiving this because you authored the thread.Message ID: @.***>

[PacoCT]

@schmittx I'm now logged in to the Eero app as the second administrator (non-amazon account). I do have an Eero Plus subscription (original/first administrator). My Eero wifi network is set to bridge mode I am not able to see any network in the pop-up

[schmittx]

@RuneMason1 I don't have any experience with ISP-provided eero devices. I'd assume they're no different but can't be sure...

@PacoCT You should be able to proceed through the setup even though no networks are available. Then, ensure you have advanced mode enabled for your profile in Home Assistant. After that, go back to the Eero integration and click "Configure" and proceed through the flow again but this time you'll get an additional screen with debugging options. Enable the option to save responses and then find _2_2_account.json after clicking "Finish" (and letting Home Assistant re-initialize the integration"). Share the contents of that file here please, being sure to redact any personal information.

[dennyreiter]

Here is the json account file from my integration

On the setup flow, there is a second checkbox, under save server responses, but no description of what it should be?

I hope this helps, and thanks!

dennyreiter_2_2_account_redacted.json

[dennyreiter]

Also, here is the log file: eero20240301.log

[schmittx]

@dennyreiter Thanks, this helps a lot. Can you check one more thing for me please? Look for _2_2_networks_8796037.json, within that file should be a key and dict pair like the following:

        "premium": {
            "capable": true,
            "requirements": {
                "has_allowed_country_code": true,
                "has_allowed_group": true,
                "has_min_mobile_version": true,
                "has_min_version": true,
                "has_proper_connection_mode": true,
                "has_proper_org_configs": true,
                "has_proper_owned_network_count": true,
                "has_proper_owner_role": true
            }
        },

Can copy and paste here? I want to confirm my theory.

[dennyreiter]

            "capable": false,
            "requirements": {
                "has_allowed_country_code": true,
                "has_allowed_group": true,
                "has_min_mobile_version": true,
                "has_min_version": true,
                "has_proper_connection_mode": false,
                "has_proper_org_configs": true,
                "has_proper_owned_network_count": true,
                "has_proper_owner_role": true
            }
        },

[schmittx]

@dennyreiter Perfect, thanks. The "capable": false bit is causing the problem I believe. Not sure what necessarily makes this true or false but the false is triggering the error in your logs. I'll push a beta version shortly for you to try.

[dennyreiter]

Awesome. Yes it's very confusing. In some places it says Premium is yes, then others Capable, false.

[PacoCT]

@PacoCT You should be able to proceed through the setup even though no networks are available. Then, ensure you have advanced mode enabled for your profile in Home Assistant. After that, go back to the Eero integration and click "Configure" and proceed through the flow again but this time you'll get an additional screen with debugging options. Enable the option to save responses and then find _2_2_account.json after clicking "Finish" (and letting Home Assistant re-initialize the integration"). Share the contents of that file here please, being sure to redact any personal information.

@schmittx I see @dennyreiter already provided the data you needed. In any case, here it goes the info I've got _2_2_account_edited.json

    "premium": {
        "capable": false,
        "requirements": {
            "has_allowed_country_code": true,
            "has_allowed_group": true,
            "has_min_mobile_version": true,
            "has_min_version": true,
            "has_proper_connection_mode": false,
            "has_proper_org_configs": true,
            "has_proper_owned_network_count": true,
            "has_proper_owner_role": true
        }
    },

Regards,

[schmittx]

@dennyreiter @PacoCT I published a beta release with multiple bug fixes, give a try and let me know if it helps.

[PacoCT]

@dennyreiter @PacoCT I published a beta release with multiple bug fixes, give a try and let me know if it helps.

@schmittx thank you very much to try solving this issue. I really appreciate your work

I'd be glad to help you troubleshoot the eero integration issue in Home Assistant.

Steps I've followed:

1. Downloaded Beta Version and installed the beta version. Replaced the eero folder in the config/custom_components folder.
2. Removed Standard eero integration using Home Assistant.
3. Install eero again using Home Assitant
4. Logged In the eero app with Non-Amazon Account

Observed Issues:

1. No Network Detection in the eero configure option.

2. Missing text in Pop-up Windows: The pop-up windows that normally appear in Home Assistant are not displaying any text.

3. In the Error Logs there are two errors in the logs,

_log_Error1_1431h20240305.txt, and

_log_Error2_1431h20240305.txt

5. The files (edited) in the eero\api\responses are attached as well

I hope my report helps you in going deeper in the issues.

log_Error2_1431h_20240305.txt _2_2_account_edited.json _2_2_networks_7038562_Edited.json log_Error1_1431h_20240305.txt

Paco

[RuneMason1]

I haven't done logs or anything yet. But paco has exactly my issue. If you need information from another user, please let me know

Sent from my T-Mobile 5G Device Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Paco Calvino @.> Sent: Tuesday, March 5, 2024 9:49:34 AM To: schmittx/home-assistant-eero @.> Cc: RuneMason1 @.>; Mention @.> Subject: Re: [schmittx/home-assistant-eero] Current version shows no networks after verifying by email (Issue #75)

@dennyreiterhttps://github.com/dennyreiter @PacoCThttps://github.com/PacoCT I published a beta releasehttps://github.com/schmittx/home-assistant-eero/releases/tag/1.5.0b0 with multiple bug fixes, give a try and let me know if it helps.

@schmittxhttps://github.com/schmittx thank you very much to try solving this issue. I really appreciate your work

I'd be glad to help you troubleshoot the eero integration issue in Home Assistant.

Steps I've followed:

1. Downloaded Beta Version and installed the beta version. Replaced the eero folder in the config/custom_components folder.
2. Removed Standard eero integration using Home Assistant.
3. Install eero again using Home Assitant
4. Logged In the eero app with Non-Amazon Account

Observed Issues:

1. No Network Detection in the eero configure option.

2. Missing text in Pop-up Windows: The pop-up windows that normally appear in Home Assistant are not displaying any text. Screenshot.2024-03-05.143147.png (view on web)https://github.com/schmittx/home-assistant-eero/assets/12235299/c9b52149-76f4-48c6-b8a9-100b963bb66e Screenshot.2024-03-05.143223.png (view on web)https://github.com/schmittx/home-assistant-eero/assets/12235299/b287cda7-cbbd-494a-8757-23645d57eadb

3. In the Error Logs there are two errors in the logs, Screenshot.2024-03-05.152338.png (view on web)https://github.com/schmittx/home-assistant-eero/assets/12235299/82395bb2-56ed-4ecc-8309-8aa5bc08fb2e

log_Error1_1431h_20240305.txt, and

Screenshot.2024-03-05.152413.png (view on web)https://github.com/schmittx/home-assistant-eero/assets/12235299/c1ee9363-83fa-416d-8a63-99b5a77de893

log_Error2_1431h_20240305.txt

1. The files (edited) in the eero\api\responses are attached as well

I hope my report helps you in going deeper in the issues.

log_Error2_1431h_20240305.txthttps://github.com/schmittx/home-assistant-eero/files/14496991/log_Error2_1431h_20240305.txt _2_2_account_edited.jsonhttps://github.com/schmittx/home-assistant-eero/files/14496992/_2_2_account_edited.json _2_2_networks_7038562_Edited.jsonhttps://github.com/schmittx/home-assistant-eero/files/14496993/_2_2_networks_7038562_Edited.json log_Error1_1431h_20240305.txthttps://github.com/schmittx/home-assistant-eero/files/14496994/log_Error1_1431h_20240305.txt

Paco

— Reply to this email directly, view it on GitHubhttps://github.com/schmittx/home-assistant-eero/issues/75#issuecomment-1978944566, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASZJ6XESC6XE6SYK63GBK5TYWXLP5AVCNFSM6AAAAABBJQTB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZYHE2DINJWGY. You are receiving this because you were mentioned.Message ID: @.***>

[dennyreiter]

The beta solved my issue and everything seems to be back. Thank you!

[schmittx]

@PacoCT I'm not entirely sure what's causing your errors. I think it's because you're trying to run two versions of the same integration in parallel (it looks like you renamed some things to eero_standard)? The errors regarding error.network.premium.not.capable have been addressed in the beta, and I can tell from the formatting of the exception logs that they're coming from the (older) non-beta version. Please re-try with the latest beta.

@RuneMason1 The first beta had a minor error regarding getting release notes, I just pushed an update for the beta. Try it out and let me know if it resolves your issues.

[RuneMason1]

It appears that the beta has a fix! It worked! Everything detected. The only gripe is that the dialogs in the wired/wireless clients only show MAC addresses. Is it possible to make them show Device Names/IP addresses instead? Or both?

---

From: Matt Schmitt @.> Sent: Wednesday, March 6, 2024 11:33 AM To: schmittx/home-assistant-eero @.> Cc: RuneMason1 @.>; Mention @.> Subject: Re: [schmittx/home-assistant-eero] Current version shows no networks after verifying by email (Issue #75)

@PacoCThttps://github.com/PacoCT I'm not entirely sure what's causing your errors. I think it's because you're trying to run two versions of the same integration in parallel (it looks like you renamed some things to eero_standard)? The errors regarding error.network.premium.not.capable have been addressed in the beta, and I can tell from the formatting of the exception logs that they're coming from the (older) non-beta version. Please re-try with the latesthttps://github.com/schmittx/home-assistant-eero/releases/tag/1.5.0b1 beta.

@RuneMason1https://github.com/RuneMason1 The first beta had a minor error regarding getting release notes, I just pushed an updatehttps://github.com/schmittx/home-assistant-eero/releases/tag/1.5.0b1 for the beta. Try it out and let me know if it resolves your issues.

— Reply to this email directly, view it on GitHubhttps://github.com/schmittx/home-assistant-eero/issues/75#issuecomment-1981279348, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASZJ6XFZO25IVRLFJ3JIQHDYW5AMJAVCNFSM6AAAAABBJQTB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGI3TSMZUHA. You are receiving this because you were mentioned.Message ID: @.***>

[PacoCT]

@PacoCT I'm not entirely sure what's causing your errors. I think it's because you're trying to run two versions of the same integration in parallel (it looks like you renamed some things to eero_standard)? The errors regarding error.network.premium.not.capable have been addressed in the beta, and I can tell from the formatting of the exception logs that they're coming from the (older) non-beta version. Please re-try with the latest beta.

Great, @schmittx !

That was my fault. when I've installed the beta, I renamed the original eero folder to eero_standard instead of deleting it. Now, I've removed eero and eero_standard folders, copied the new one from the latest beta 1.5.0b1, restarted homeassitant, and went to Configure the eero integration.

My network was discovered, the four eero-routers were there, and all devices connected to the mesh network appeared in the configuration windows :-)))

Now I've to start playing to remove unwanted devices

Thank you very much!

[schmittx]

@RuneMason1 Glad to hear it's all good now. If you give the client/device a nickname via the Eero app, then the integration will use that to help identify. IP addresses are too unstable for identification and hostnames aren't guaranteed to be unique within a network.

@PacoCT Good stuff. Let me know if run into any further problems.

[schmittx]

Closing this as the beta updates have been reflected into newest release here.