IIRC, 20.49.0 is when they started requiring logins. Subsequent versions have included that security feature.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Gateway updated to 21.20.2
- Thread starter h2ofun
- Start date
It seems that some pages, but not all require a recent login. For example /api/meters/aggregates does, but /api/status does not.
that's certainly possible. i can try flushing caches etc.
edit: actually - i just reloaded the tab and the 'go off grid' button is gone. so indeed it must have been some kind of browser caching issue.
Pretty sure I can see why now, at least from my Gateway v2.
Take a look at the attached image, you can see that every 45 minutes or so the gateway is either losing its network connection and then rejoining or the gateway is restarting.
You can see the section where the software update/downgrade occurs and now all the lines are flat again. Looks like they've pulled it for some type of stability issue.
Take a look at the attached image, you can see that every 45 minutes or so the gateway is either losing its network connection and then rejoining or the gateway is restarting.
You can see the section where the software update/downgrade occurs and now all the lines are flat again. Looks like they've pulled it for some type of stability issue.
Attachments
I am still on new stuff. Now I have hardwired, no wifi, is this going to make a difference. Anyone who got pushed back hardwired?
I have Ethernet, wifi and cellular and am still on 21.20.2, so maybe it was due to wifi stability issues.
That seems to be one possible data point. I am also still on 21.20.2. Shall be interesting to see if anyone that got changed back has hardwire
Im still on 21.20.2 as well. I also have my gateway hard wired to my network. Interesting observation there, about wired vs wifi. I do have the gateway setup for all three, like @MorrisonHiker does, but it prioritizes wired when you have a wired connection.
10 points for me
If you'd like another point my Powerwall is on 21.20.2 and its connected via ethernet.
i'm on wifi but didn't experience any dropouts until the moment the powerwall rebooted. however, this is exactly the kind of bug that ships - works with some wifi protocols reliably but not all, so would not be surprised if that's what happened based others' experience with wifi.
honestly though, if they found a bug with wifi and then selectively reverted if the user happens to be on wifi, that's really asking for trouble too. it bifurcates the problem needlessly and what happens if for some reason a user switches to wifi? you have to have server-side code to keep looking for new wifi-connected 21.20.2 systems and downgrade them. more code == more opportunities for random bugs.
honestly though, if they found a bug with wifi and then selectively reverted if the user happens to be on wifi, that's really asking for trouble too. it bifurcates the problem needlessly and what happens if for some reason a user switches to wifi? you have to have server-side code to keep looking for new wifi-connected 21.20.2 systems and downgrade them. more code == more opportunities for random bugs.
My gateway is connected with WiFi. There is no ATT signal here, so that is the only connectivity. I have not been reverted. I am on 21.20.2.
I have cabled Ethernet, wifi and cellular here in Sydney and was just changed back from 21.20.2 to 20.49.0
My other thoughts is maybe it’s related to gateway version. I’m running a Gateway V2 and was reverted. Is everyone still running 21.20.2 using the Gateway V1?
My vote, I’m on a v2 gateway and was downgraded from 21.20.2 to 20.49.0
My vote, I’m on a v2 gateway and was downgraded from 21.20.2 to 20.49.0
