BUG: Camera API not accessible when it is used as an addon within homeassistant

[rabbitholelabsinc]

Describe the bug

no clear documentation about how to access the rest api when it is installed as an addon within home assistant and not running in a separate container. Home assistant usually runs from port 8123 and there is no port 5000. For example documentation says to use http://:5000/api/<cam_name>/<command_topic>/ but it is an addon and not a separate docker instance so this api is not reachable. Also tried with home assistant running port but that also does not work.

even the actual documentation within the addon documentation states the following,

Stream and API Authentication
Note that all streams and the REST API will necessitate authentication when WebUI Auth WB_AUTH is enabled.

REST API will require an api query parameter.
Example: http://homeassistant.local:5000/api//state?api=
Streams will also require authentication.
username: wb
password: your unique wb api key

but there is no port 5000 and it does not even work if I use the actual home assistants ip, port and proper api key.
I get a http 404 error but the stream works: rtsp://wb:apikey@homeassistant.local:8554/ works. So not sure how I am suppose to make api calls to the bridge when it is an addon

Affected Bridge Version

2.10.3

Bridge type

Home Assistant

Affected Camera(s)

all

Affected Camera Firmware

all

docker-compose or config (if applicable)

[AaronMcGuirk007]

Hi there, we have an on-going thread of the same issue here if you would like to add to it #1432

[Truepix]

Hi there, we have an on-going thread of the same issue here if you would like to add to it #1432

Yes but it doesn't seem to include the home assistant add-on...

[jdeath]

I made a PR to fix home assistant. My fix is in: #1432 (comment)