Sorry about that. Maybe wait for v1.0 and see if that works - I will be refactoring some of the JavaScript on the frontend so it may work (no guarantees though).
I know buying new hardware is not a “solution”, but in case anyone is curious, this is the 8" tablet that I run for HACC. It works well. You could even go down to a 7" tablet for even cheaper.
I have exactly the same problem, Base URL is set correctly to the external url for HA (in my case this is a reverse proxy), and it shows this in the /admin/technical page. Unfortunately HACC tries to source the image for entity_picture from:
url(“/local/me.jpg”)
and displays nothing, because it would need to use a different webserver.
If I change the entity_picture value to be fully qualified (ie https://myhome.com/local/me.jpg) then the picture loads, but only after I’m forced to authenticate past my reverse proxy. Its also not the ‘correct’ way of setting an entity_picture, so I wonder what else I might break
Hi @tseeley, as part of this PR, to be released in 1.0, I added support for an “Override Asset URL” which will allow you to override the base URL that is used for media and image assets. So in cases where it’s not able to resolve this correctly, you will be able to set “https://myhome.com” as the override asset URL and it should load your pictures properly.
I wanted to give everyone a brief update about Version 1.0. I know that many of you are eagerly awaiting it, however during testing, I discovered that the way I had set up communication between the app and Home Assistant would work for people generating their own long-lived access tokens, but would not work for people installing via the Supervisor Add-on interface due to the way tokens are handled. (This issue covers it in a bit more detail.)
So, I am currently working on updating the app to support installation as an add-on. Testing is difficult and slow because I have to fully compile the app and deploy it into an add-on container with every change I make. I am making progress though.
I will keep everyone posted as developments happen. Again, I know you are all eagerly awaiting 1.0 and I appreciate your patience!
@nickrout is correct - there are no special instructions for Raspbian specifically - you would just need to use Docker and match your system architecture (ARM32v7 or ARM64v8) - there are images for both.
I was having trouble with “too many redirect” messages in my original Docker installation of HASS. It was working fine until it wasn’t. Not sure what happened.
Just removed the container and image and started over from scratch and now I’m getting a 500 error when I try to access the service at port 8095.
Hey @fishertimj I just pushed out a preview version, 1.0.16, with new containers - can you update your container and try again? I think it should be fixed. If not, let me know!
Hello There,
I have installed the HACC add-on. When I launch either from the hassio dashboard or access HACC directly via the IP:PORT I get a gray screen. Nothing in the logs from what I can see. I have tried refreshing the page, as well as clearing cache and history just in case. Nothing. There is no error message of server not found just a gray background.
@holmiephoto The uninstall issue is a known bug in the current Supervisor version. It will be resolved with the next version.
The gray screen is the dashboard but you don’t have any tiles. Go to the URL /admin and you should see the interface. We also changed this in the next version so the admin area is the default page.