Hi David,
This is unfortunately a known issue related to a Home Assistant API called ingress, which allows our add-on’s UI to communicate with its backend.
It appears that the ingress channel is only fully activated after the add-on UI has been opened at least once from Home Assistant. If the UI is accessed via a web card before that initial opening, Home Assistant may raise this error.
Workaround
As a workaround, our add-on also exposes port 11200, which bypasses Home Assistant’s ingress proxy entirely.
For example, instead of using this URL:
http://homeassistant.local:8123/api/hassio_ingress/ym-tlrzEEeGSTSNCz7up0Gf3uqHboBU5NGFvBfH7AMY/offline/viewer/?group=haEBrqFXAEIs&project=sLVclZKQrCvP#cam&p=0.00,0.00,0.00&h=40.11&v=39.56&z=400.00|dsp&fs=1.00&fd=tc&wc=1.00&wd=t&od=tc&thm=auto|viz&layer=rkqaX00R
You can replace:
:8123/api/hassio_ingress/ym-tlrzEEeGSTSNCz7up0Gf3uqHboBU5NGFvBfH7AMY
with:
:11200
So it becomes:
http://homeassistant.local:11200/offline/viewer/?group=haEBrqFXAEIs&project=sLVclZKQrCvP#cam&p=0.00,0.00,0.00&h=40.11&v=39.56&z=400.00|dsp&fs=1.00&fd=tc&wc=1.00&wd=t&od=tc&thm=auto|viz&layer=rkqaX00R
Additional notes
Home Assistant ingress has caused several issues beyond this one—some users have also reported unstable connections. Accessing Zircon3D directly through port 11200 is generally more stable and can help avoid these ingress-related problems.
It’s possible that the Home Assistant team will improve the ingress proxy in the future. Until then, this is currently the most reliable workaround.
Please give this a try and let us know if it works for you.
Thanks in advance,
Chris
D
