Fix for frontend app trying to load /config.json from the root path #116
Conversation
|
Seems like a GitHub token issue in the PR build. |
Yeh, I didn't get around to fixing it yet as there hasn't been many PRs that aren't from myself.
Definitely not ideal. Though I am not sure if the proposed changes here will work all the time? For instance, loading directly into different client side paths like I'm finding it difficult to find a reliable way to find the path. Though given what
The commits don't follow the conventions. Please do follow them, as the release logic depends on the conventions to understand what kind of version bump is required. |
|
I've added a new commit, |
Will do.
Thanks for this. Could you tell me what Docker build command you use locally to build? I couldn't figure it out exactly from looking at the various workflow files. |
I don't really bother with Docker. For this, I just ran the Web UI with For testing these changess, I did a Now the PR is open here and built/published, you can also test the changes with the image |
|
Thanks for the tips. Im using that image now: https://github.com/fbradyirl/streammaster-addon/actions/runs/14810883099/job/41585402632#step:6:389 
but still see the config 404 from root: 
|
|
Not sure if it helps but here is the log: |
|
From testing my original commit, it did load the config OK but hit a problem further onwards as you suspected. 
404 for
|
It's web client side, so the logs should appear in the console output within the browser. However by default, only |
|
Huh im not seeing those new logs at all in the console (even when I directly navigate to the app outside of the HA UI)... 
Inside HA: Sorry Im a backend service dev and never ventured to frontend or any .Net stuff before so im a bit clueless on this. |
carlreid
force-pushed
the
main
branch
2 times, most recently
from
d6b8247 to
6fbe620
Compare
No problem, appreciate the effort 👍 I've modified the last commit to just force the You may also wish to use "Persist Logs" option in the Dev Console -> Console settings, in case a redirect happens where the logs wouldn't be then seen from the Edit: |
|
Thanks for this. Im still not seeing them im afraid. I think HA is doing something funky to intercept them maybe?
|
|
Even running in Docker on my Mac I dont see the logs. 
Using compose: |
|
Ok I have it working with the latest commit now. Also I can see those Console logs: 
There still are some 404's but im not sure what the impact is from these:
and a bunch more at the end: 
|
Great 👍
They look like attempts to load logos and things. My guess is that the handling of calls to |
|
Yes I got the images and /api endpoints working now in the latest commit. The Axios file upload is the latest thing that is broken. Painful stuff! |
Ah, nice 👍 Had a very quick read through already and seems alright.
I feel that way about making most changes on this project 😅 If you struggle with it then I can also try take a look when I get a bit more time again. |
|
Thank you. Copilot is doing most of the donkey work for me, so I might keep at it. |
|
Closing as there are too many major things to change to make this work. Instead, I have the addon cross launch out of HA into the browser (like the Plex addon does) so no changes are needed to this project to make that work. |
|
Thanks for trying @fbradyirl, and sounds like a fair approach given the complexity 👍 |
Description
The core issue now here that the frontend app in StreamMaster is trying to load /config.json from the root path, which does not work under Home Assistant’s Ingress, where paths are prefixed (like /api/ingress/slug/).
🧠 Root Problem:
This code in settings.ts is not ingress-aware:
request.open("GET", "/config.json", false); // hardcoded pathSo in Ingress, it tries to request:
https://<ha-host>/config.json → ❌ 404Whereas it needs:
https://<ha-host>/api/ingress/slug/editor/config.json → ✅ if served thereIssues (Fixed or Closed)
Type of Change
Dependencies
Checklist
mainbranch (rebased)