Fall back from Beta now Fornt-end loading nonstop reboot no help #24208
Comments
|
Sounds like a caching issue. Have you tried a different browser, tried private mode? |
|
I tried different browsers, computers, and my app. I think my only solution
is to connect to the host computer and attemp to reload HA.
…On Fri, Feb 14, 2025 at 11:36 AM Simon Lamon ***@***.***> wrote:
Sounds like a caching issue. Have you tried a different browser, tried
private mode?
Also please consider safe mode, to rule out any issues with custom
components.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZGW2UP67EPSUMRIAG32PYLPHAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJZG44DONBRGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: silamon]*silamon* left a comment (home-assistant/frontend#24208)
<#24208 (comment)>
Sounds like a caching issue. Have you tried a different browser, tried
private mode?
Also please consider safe mode, to rule out any issues with custom
components.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZGW2UP67EPSUMRIAG32PYLPHAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJZG44DONBRGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
If you're getting notifications, it seems like it's working and it's just the frontend misbehaving. What I can further suggest is to open the developer tools to see what network requests are not loading. |
|
My biggest problem is my mini pc is in another state, so I have no access
to the developer tools. I should have never joined the Beta knowing I'm
away from the house.
…On Fri, Feb 14, 2025 at 12:00 PM Simon Lamon ***@***.***> wrote:
If you're getting notifications, it seems like it's working and it's just
the frontend misbehaving. What I can further suggest is to open the
developer tools to see what network requests are not loading.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZBIKX3UPBJ3EOP3HMT2PYOL3AVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJZHAZTOMRRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: silamon]*silamon* left a comment (home-assistant/frontend#24208)
<#24208 (comment)>
If you're getting notifications, it seems like it's working and it's just
the frontend misbehaving. What I can further suggest is to open the
developer tools to see what network requests are not loading.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZBIKX3UPBJ3EOP3HMT2PYOL3AVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJZHAZTOMRRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I mean, you can open the network developer tools of your browser. Not the developer tools of the system. |
|
How do you do that? I use DuckDns to access my system.
…On Fri, Feb 14, 2025 at 1:39 PM Simon Lamon ***@***.***> wrote:
I mean, you can open the network developer tools of your browser. Not the
developer tools of the system.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: silamon]*silamon* left a comment (home-assistant/frontend#24208)
<#24208 (comment)>
I mean, you can open the network developer tools of your browser. Not the
developer tools of the system.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I found the developer tools but have no idea how to access it? Can I send a
command to place back into Beta mode?
…On Fri, Feb 14, 2025 at 1:39 PM Simon Lamon ***@***.***> wrote:
I mean, you can open the network developer tools of your browser. Not the
developer tools of the system.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: silamon]*silamon* left a comment (home-assistant/frontend#24208)
<#24208 (comment)>
I mean, you can open the network developer tools of your browser. Not the
developer tools of the system.
—
Reply to this email directly, view it on GitHub
<#24208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I'm in the console but need to figure out what command to send to update
the system.
…On Sat, Feb 15, 2025 at 7:34 PM Roy Aguilera ***@***.***> wrote:
I found the developer tools but have no idea how to access it? Can I send
a command to place back into Beta mode?
On Fri, Feb 14, 2025 at 1:39 PM Simon Lamon ***@***.***>
wrote:
> I mean, you can open the network developer tools of your browser. Not the
> developer tools of the system.
>
> —
> Reply to this email directly, view it on GitHub
> <#24208 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
> [image: silamon]*silamon* left a comment (home-assistant/frontend#24208)
> <#24208 (comment)>
>
> I mean, you can open the network developer tools of your browser. Not the
> developer tools of the system.
>
> —
> Reply to this email directly, view it on GitHub
> <#24208 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVQMYZCWITNUHWAWYKJNEAL2PYZ4RAVCNFSM6AAAAABXA6TEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGAZDEOBUGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Describe the issue you are experiencing
Just before the February Update I loaded the Beta version to get my TC Alarm issue resolved. Once the February standard release came out I unclick Beta to fall back to the normal Software. My front end now is continuously loading. I use DuckDNS and my minicomputer is in another state. I had them power it down but it's stuck on loading. It's working as all my lights come on based on Node Red coding and other alerts I get on my watch.
Describe the behavior you expected
Fall back from Beta without any issues. I used the first Beta version available in February.
Steps to reproduce the issue
...
What version of Home Assistant Core has the issue?
Beta New February edition
What was the last working version of Home Assistant Core?
Beta New February edition
In which browser are you experiencing the issue?
Chrome , Ipome HA app,
Which operating system are you using to run this browser?
Win 11 , iphone
State of relevant entities
Problem-relevant frontend configuration
Javascript errors shown in your browser console/inspector
Additional information
No response
The text was updated successfully, but these errors were encountered: