Stating you made changes but detailing what you changed isn’t particularly helpful to folks. Also, you might consider just making a PR against the upstream so that you’re not forking the repo if it isn’t actually needed…
You’re right, sorry for the shortness earlier!
Here are the main changes I made:
- Redesigned the Admin UI to better match the Home Assistant aesthetic with a cleaner layout.
- Added a centralized interface for managing custom CSS and footer HTML directly from the admin panel.
- Introduced a password change feature, this was actually the functionality that first motivated me to modify the add-on. I use it for a vacation rental property and wanted to be able to update the password regularly without having to create a new link each time.
I’d like to test these changes for a few more days to make sure everything works reliably before opening a PR to the upstream repo.
Good day TekniskSupport
I was just wondering if this add-on still works with the latest release of HA 2026.1.2?
My reason for asking, is that I needed to restore a backup and the second I un-install this add-on and try re-installing it, I can never get it to start up again. I am currently just using a Pi 4 with the standard HAOS, so, no fancy containers etc.
I additionally attempted a wipe, onboarding, and then tried to install the add-on on a completely blank slate, just to verify I wasn’t trying to restore a backup that could maybe have an issue, and it did the exact same thing, which I found rather odd.
The log errors I see continually while trying to start the add-on are as follows:
/run.sh: line 15: php-fpm83: command not found s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped
I also just did a quick ChatGPT query and it came up with this remark:
Even though you reinstalled the add‑on from the Add‑on Store, the image available there still expects php‑fpm83 — which no longer exists in the latest OS base images for HA add‑ons (especially after OS updates).
Any help with this would be most appreciated.
Thank you.
Hi!
That sounds like something has changed upstream in the docker image the package is built upon; should not be directly connected to which home assistant version you are running, rather that it is a new install of the add on.
It should be a quick fix either to just update to latest version of the packages or lock the older ones, however as i have recently moved i cannot say for certain when i will find the spare time to fix it.
Thank you for the reply.
This isn’t a major crisis, I just thought I would ask and see if you maybe had any ideas about the kind of error I was getting.
After experiencing the weirdness with the add-on, I thought it was the backup that was faulty/corrupt in some way, so, as I mentioned, I decided to start from scratch with a blank slate, but when I saw the add-on still didn’t start up with a fresh copy of HA and nothing else on it, I decided the best course of action would be to do another restore, because at least then I still have a working version of the add-on, so all good for now.
Ps. Are “congratulations with the move” in order? 
Have an awesome one!
Thanks!
Good news, i have now updated the addon to work with the new base image.
Best
Iesus