Community Hass.io Add-on: Home Assistant Control Panel

Installation Home Assistant OS
,
125

I am still having initial connection issues - despite reading all of the above and clearing cookies (hassio and duckdns ones -any others?), adding port forwarding for 7080, 8123, 3218 and having the following code in my config.yaml:

base_url: https://mydns.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
cors_allowed_origins:
- https://mydns.duckdns.org:7080
- http://mydns.duckdns.org:7080
- https://hassio.local:7080
- http://hassio.local:7080

I can access mydns.duckdns.org:8123 fine.
I can access hassio.local:8123 fine
I cannot access hassio.local:7080
I cannot access mydns.duckdns.org:7080 - it goes through manual setup and then I get the error popup window with my hassio url (irrespective of whether local or duckdns one - both of which I can bring up directly).

Any ideas?

126

I really like this frontend. It is simple and very easy to set up. The layout is great - and it is easy to do a configuration that is usable for non-tech users.
But there is one feature that I would really really like, and that is media player control.
I use Sonos devices all around my house, and it would be great to be able to see what is playing, starting/stopping music / turning volume up/down and skipping tracks :slight_smile:

127

Hi There,

Just a message to share experience. I was completly mad with this ! I had always the unable to connect error. This was because i had a “#” sign in my api_password… removed it and now works like a charm !

128

Hello all
how can i adding groups and entities in control panel ?

129

Deprecation warning

I’m sorry to say, that this add-on is no longer supported or maintained. This add-on required a lot of time to support since a lot of you had issues with getting (and keeping) the control panel in a working state.

This caused an awful lot of support questions, which take a lot of time. This add-on (not the control panel) does not actually do much, which makes it even more painful. Therefore I have decided to drop the add-on.

You can still install this control panel manually or use the hosted version
offered by the author. For more information see:

https://reformedreality.com/home-assistant-control-panel

Affected immediately, the add-on is removed from the add-ons store.

With kind regards,

…/Frenck

1 Like
130

Bad luck, I finally got it working again after disabling night mode on my google home devices.
Well, I hope it’ll continue working even without being supported, and that someone will pick this concept again to make a new supported module.

131

first of all, congratulations for the work done.

I have a big problem using your control panel.
I can not see the entities in any way, the psw API is correct, I can connect to the hassio server, but I do not see any entities.

if I try to go to http: // hassio.local: 8123 / api / states? api_password = YOUR_PASSWORD_HERE, I see only 2 square brackets, no entities are displayed.

I tried all the configurations.

thank you very much for your help, it would be wonderful for me to be able to use your addon!

132

if i enable the debug mode in the configuration of your control panel, the message “WebSocket Events Socket connection closed, reconnecting …” appears at the top right.

can the AppDaemon addon affect?

133

Hey montani, seems this is an upgrade bug in HA itself, see https://github.com/home-assistant/home-assistant/issues/18885

Fix is to edit the config/.storage/auth file and change:
"group_ids": [],
to:
"group_ids": [ "system-admin" ],

for the ‘Legacy API password user’ user.

134

I can not understand,
I in the file /config/.storage/authho the following text:

{
“data”: {
“credentials”: [
{
“auth_provider_id”: null,
“auth_provider_type”: “homeassistant”,
“data”: {
“username”: “ennio”
},
“id”: “66f7f89a8def437490baf770679c7c03”,
“user_id”: “051336e78cb648ca90225f6150f88dd3”
},
{
“auth_provider_id”: null,
“auth_provider_type”: “legacy_api_password”,
“data”: {},
“id”: “31f048a583d6491e9bbce3faedeae1f2”,
“user_id”: “8acc46d66cce4094b62fd7cb61f80961”
}
]
“groups”: [
{
“id”: “system-admin”,
“name”: “Administrators”
},
{
“id”: “system-read-only”,
“name”: “Read Only”
}

in the post you have reported to me they put a very different script:

        {
            "group_ids": [
                "System-admin"
            ]
            "id": "e1aba709becb4196a27574b0b7816103",
            "is_active": true,
            "is_owner": false,
            "name": "Legacy API password user",
            "system_generated": false
        }

should i add this?

the id must remain the same as the script (“id”: “e1aba709becb4196a27574b0b7816103”) or do I put id in my configuration file (“id”: 66f7f89a8def437490baf770679c7c03 ")?

135

ok, I solved by following the directions.

I had not seen the section in the quoted script at the end of the file.

everything works now.

thank you all
ennio

136

This add-on has been removed from the community add-ons repository.
Hence, I’ll close this topic, since there is nothing to support anymore.