I wanted to give you a status update before the holidays arrive!
First, thank you @fishertimj for your support! I have been meaning to e-mail you but with the holidays things are a little crazy! I promise I will though!
Second, I wanted to outline some goals for what would essentially be “HACC v1.0”.
Technical Goals
Upgrade project and Docker images to use .NET Core 3.1 (the latest LTS release of the platform)
Convert the Docker images to have multi-arch support so that we can release a single “HACC” image that works on amd64, armv7, armv8, etc.
Convert HACC from a polling-based architecture to instead utilize HA’s WebSocket API to receive real-time state updates (don’t ask why it wasn’t like this from the start )
Finish up some of the other requested tiles and features in the Version 1.0 Milestone (Currently at 4/14 completed)
Not all of these will likely make it into v1.0 - due to the significant architecture changes that have to happen between upgrading the framework version, changing to websockets, and redoing the Docker images, we may have to push some of these back to v1.1 or later.
For this reason, you should thumbs up enhancements on GitHub that you want to see - I will use the votes to determine priority!
Set up a Themes page on GitHub to offer up some OOTB themes / community themes for download
Set up a website! (I own http://hacc.dev/ but it just redirects to GitHub right now.)
I am hoping to get some of this work done during the holidays and around the new year, and I will try and post some status updates in this thread as things are completed. I know that back-end architecture updates are not exactly exciting, but trust me when I say that HACC will be a lot better and a lot faster when v1.0 is released.
Seems like WebView 30 is super out of date. Can you update your device to use WebView 36 or somehow install a newer version of Chrome/Chromium?
I use a tablet at home that has Android Go installed on it and that works really well - I’m not super familiar with the whole Android ecosystem but perhaps you could update your OS to that as another option?
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.