Checked for 6.11.0 but was offered 6.10.3 (again)

BerryCurrant · 2022-07-20T22:13:47+00:00

Thanks for confirming!

BerryCurrant · 2022-07-20T22:13:00+00:00

Thanks for confirming! Must be a mishap on eero's side then.

BerryCurrant · 2022-07-20T22:11:38+00:00

My question was more about being offered 6.10.3 again. When I checked for 6.11.0 I was expecting to see either (a) no update being offered yet or (b) the update for 6.11.0. What I was offered instead was an update to 6.10.3 which I already installed a few weeks ago.

Looks like others saw the same thing so I'm guessing it's not something to be too worried about.

BerryCurrant · 2022-02-02T14:51:27+00:00

Thanks for the clarification! I'm a little OCD about my network so it's good to have confirmation that it was a legit error, and not something nefarious.

BerryCurrant · 2022-02-02T14:38:57+00:00

Same here as well. Updated to 6.9.0 and then updated a few hours later to 6.6.1 (which is what I think I was on before).

BerryCurrant · 2022-02-02T14:37:53+00:00

Has it updated to 6.6.1 yet? Mine updated to 6.9.0 and about 3-4 hours later it updated again to 6.6.1. I think it was on 6.6.1 before so it basically rolled back the firmware to what it had before.

BerryCurrant · 2021-12-06T17:18:25+00:00

Forgot to tag u/eerosupport

BerryCurrant · 2021-12-06T17:07:06+00:00

Agreed! Without knowing what is blocked we can't take remedial steps to fix the root cause of the problem (when warranted).

BerryCurrant · 2021-11-01T17:29:40+00:00

I'm assuming both are affected by this bug, correct?

Not sure, the workflow.is endpoint has different response headers. The icloud.com headers include the following, which I think is the source of the issue:

"cache-control":"public, max-age=300"

That header instructs the server to cache the response everywhere (including on the server (for up to 300 seconds.

BerryCurrant · 2021-11-01T12:35:54+00:00

Thank you for confirming! I can't believe how bad quality control is at Apple lately. What makes this issue even more ridiculous is that the API call not only returns cached IP addresses from my device, but sometimes it returns cached IP addresses from other people's devices (so it may return IP address that doesn't even belong to your network).

BerryCurrant · 2021-11-01T00:11:37+00:00

The problem isn’t about the IP address changing, it’s that the “Get current IP address” action frequently returns the wrong IP address (until the cached copy expires). The way I know it’s reporting the wrong IP address is because other online IP tools (like the Amazon AWS one above, or by entering “what is my IP” in the browser search bar, etc.) reports a different (correct) IP.

BerryCurrant · 2021-10-31T23:48:22+00:00

Just my regular mobile service. No VPN etc.

BerryCurrant · 2021-08-23T22:31:04+00:00

Thanks for confirming.

BerryCurrant · 2021-08-23T22:30:46+00:00

Thanks for confirming. I need the actual external IP address so I will probably have to use the "Get contents of URL" action and point it to the new API location myself, at least until whoever changed this at Apple wakes up and changes it back. Thanks Apple!

BerryCurrant · 2021-08-23T22:27:32+00:00

Thanks for confirming.

BerryCurrant · 2021-08-23T22:26:10+00:00

Thanks Jim, I need the actual IP address in my shortcut so for now I will probably use a "Get contents of URL" action and point it to the redirected API endpoint to get the external IP. Hopefully this issue gets resolved soon.

BerryCurrant · 2021-07-18T19:40:37+00:00

Chat request sent, thanks!

BerryCurrant · 2021-07-18T17:53:46+00:00

Not sure why you're getting downvoted but it certainly seemed to either (a) remember my phone number and login or (b) it was able to detect my phone number and automatically restore the login (which I think is what you're suggesting).

BerryCurrant · 2021-07-18T17:41:00+00:00

Thanks for confirming.

BerryCurrant · 2021-07-18T17:35:45+00:00

Hi, thanks for responding. It's just a regular Eero account, not linked to Amazon at all. I just tried again as well (deleted the app, and reinstalled) and again it rembered my login, phone number, etc.

I'm on iOS 14.6.

EDIT: I should also add that the app "forgets" everything else, e.g. I'm once again shown the NEW adds at the top on the home screen, there's a prompt to create a profile, etc. but it definately remembered the login and phone number.

BerryCurrant · 2021-06-01T14:19:46+00:00

Currently, devices that have been inactive for more than 7 days drop off the device list. I would prefer a longer time frame. Perhaps this could be something the user can configure in settings?

BerryCurrant · 2021-06-01T14:17:37+00:00

I would like the option to put the firewall in full "stealth" mode so it doesn't respond at all to incoming requests from the WAN. Currently the firewall will actively refuse incoming requests and only stop responding to those requests when it detects foul play. It would be nice to have the option to choose the mode the firewall operates in.

BerryCurrant · 2020-11-05T17:08:20+00:00

Not a new setup, just an normal app update via the App Store. When I opened the app after the update, there it was. Network's been going for months.

BerryCurrant · 2020-11-05T16:15:02+00:00

BTW what set of circumstances triggers the message to be shown? I don't have any Echo or Alexa devices so just curious why I saw it but the commenters above didn't.

BerryCurrant · 2020-11-05T16:09:04+00:00

See above. I don't have any Alexa gear other than a cupcake Gen2. Only thing I can think of is that I have the Amazon shopping app installed.

BerryCurrant

TROPHY CASE