Core: hassio sidebar issue on 1.3.1 release 0.72.0b2

[khemikel]

Home Assistant release with the issue:
hassio version 1.3.1 release 0.72.0b2

Last working Home Assistant release (if known):
hassio version 1.3.1 release 0.71

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
Hass.io sidebar link

Description of problem:
Clicking Hass.io sidebar link the following error pops up:
--Unable to load the panel source: /api/hassio/app/entrypoint.js.

Additional information:
All other sidebar links work. A reboot was done after patching completed.

[Bergasha]

Also having this issue..

[sveip]

Same issue here as well.

Problem seems to be auth related:

load_resource.js:29 GET https://petersv.duckdns.org:4356/api/hassio/app/entrypoint.js 401 (Unauthorized)

[agrieco]

Same issue. Was working fine, now not.

[Hackashaq666]

same issue here, how to update or roll back?
I am on 0.72.0b0

[Hackashaq666]

I am running hassio on pi3B+, is it specific to this dale3h HASSIO install script?

[RogerZx]

I also have this issue.

[sveip]

@balloob mentioned on the beta discord channel a fix is coming soon (tonight)

[RogerZx]

Wonder if it will be possible to get to a backup or a fix if you can't access the Hass.io tab???

[sveip]

It's possible, either with curl or from the console in chrome dev tools:
javascript:document.querySelector('home-assistant').hass.callApi('post', 'hassio/homeassistant/update', {version: '0.72.0b2'})

[Hackashaq666]

Thanks @sveip ! I was able to modify your script in chrome dev-tools to install 0.71.0
All is working as it should.
Will wait until 0.72 final is released until I update again.

[c727]

fixed in #15024

posts like "same issue" are not helpful btw. instead use the :+1: reaction on first post

[balloob]

Fixed in b3

[sveip]

To roll back to 71:
From the console in chrome dev tools (right click and select inspect, choose console tab) do: javascript:document.querySelector('home-assistant').hass.callApi('post', 'hassio/homeassistant/update', {version: '0.71.0'})

@c727, does liking the issue really mean that someone is experiencing the same problem? Does a few extra comments to attract attention hurt, isn't that exactly the point? Don't get me wrong, I don't know or have any strong opinion, that's why I'm asking.

Maybe some way to separate the issues that are beta related would help to avoid them drowning?

[RogerZx]

Thank you sveip! This worked for me.

On Mon, Jun 18, 2018 at 3:17 AM sveip [e-mail] wrote:

To roll back to 71:
From the console in chrome dev tools (right click and select inspect,
choose console tab) do: javascript:document.querySelector('home-assistant').hass.callApi('post',
'hassio/homeassistant/update', {version: '0.71.0'})

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15008#issuecomment-397962857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSfmptFsuz1Cy6zjtUdiRHKQtsz-O87ks5t91P9gaJpZM4UquT_
.

--
Roger Zilliox
1691 Parker St
Cortland, NY 13045

[phone]

[email protected]

[DatStorm]

Still having this problem :(