@keiflab Glad to hear it’s working after the update, thanks for letting us know!

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

@Hacker182 Hi, We’ve released an improvement along with a new debug tool in Zircon3D v2.0.6 (2026-01-11). Please upgrade the Zircon3D Proxy add-on to this version, it should be more stable, as we’ve enhanced the WebSocket connection handling. What’s new in v2.0.6: Improved WebSocket stability for unreliable or high-latency network environments Added a built-in log viewer to both the Designer and Viewer for easier debugging If the connect/disconnect issue happens again, please do the following: When you see the Wi-Fi / connection icon toggling between connected and disconnected Click the icon to open the connection panel Click the Debug Info icon Export the log information and send it to us I’ll attach a screenshot to show exactly where to find this option. Thanks again for your patience and for helping us track this down, the new debug data will make it much easier for us to identify what’s happening if the issue persists. [image: 1768242317425-1efed2ef-78b1-4925-a9ef-15409ce15058-image.png]

Thanks for the question! Our controls on mobile and tablet still need improvement, and we’re planning to refine the touch interaction experience in future updates. For now, you can try creating a top-view camera angle, which is much easier to use on mobile/tablet and reduces accidental click-and-drag actions. Here’s how to create a custom view, please check the video at 5:03: https://youtu.be/tm3IbnAiQzA Feel free to share more feedback, it really helps us improve the mobile experience! [image: 1764603928731-0892d4d2-5e1d-4422-b614-eb9fe6437f8d-image.png]

Entities in Home assistant not appearing - General - Zircon3D Community.pdf

Home Assistant OS options - Feature Request - Zircon3D Community.pdf

How to add custom sensor data to Zircon - General - Zircon3D Community.pdf

Sensors from home assistant to Zircon3D - General - Zircon3D Community1.pdf