Configurator Add-on Install

I have watched 4 or 5 youtube videos of people installing this app and using this app. I just cant get it to work even following step by step with them.

My theory is the " Option: ssh_keys (required)" which I have left blank and don’t understand what to put in it, however none of the youtube videos did anything with this or talked about it.

When I install and start the addon, I only get the following screen. It does show up on the sidebar, but is not working from the sidebar or from the “open web ui” option inside the app.

Any help on this would be greatly appreciated.

This is a bran new install of Home Assistant, I have changed or added nothing. I could format and start fresh if I needed, but as I haven’t changed anything and only have added a few addons, I haven’t tried the reinstall because I didn’t think that was the problem. (installed addons: Configurator, Mosquitto Broker, SSH server, Samba Share)

Thanks

This is my working config:

{
  "dirsfirst": true,
  "enforce_basepath": false,
  "ignore_pattern": [
    "__pycache__",
    ".cloud",
    "deps"
  ],
  "ssh_keys": []
}

I think that’s pretty much the default

well then having the “ssh_keys”: [] as that is not the problem. I have no idea where to go from here.

It could be a browser problem? Or cache perhaps? Also try a different browser.

Chrome and edge both the same. cache cleared.

Looks like you are blocking the css from coming through. Check extensions in the browser

Well that was fun. Tons of googling about blocking CSS. Didn’t figure out anything, but you said blocking, so I disabled a lot of things (firewalls, virus protection, malware,…) to see what was blocking… turns out my PiHole was blocking it. The only thing it shows being blocked is clients1.google.com which I highly doubt is the right thing, however disabling the PiHole for 10 seconds lets configurator load and work properly until I close edge again. I will keep trying to figure out how the 2 are related, but at least for now, thanks for saying “blocking” in your reply!!

Strange. A lot of people here use Pihole, including me, and I never had this problem. Did you include a custom blocklist or something ?

I imported a ton of custom stuff from years of manually blocking via hosts file. they are all probably not necessary as they are probably on the PiHole lists already. But I am more surprised that PiHole blocks locally, I thought it was for WAN IPs.

Oh well, at least this issue is solved. And if anyone gets that screen I posted, they have a possible starting point as well.

It’s not blocking locally. It’s trying to download the css from Google. You were blocking that download.