You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I have set up the Fusion Add-on to run over a custom port. While the dashboard loads correctly, all sensor names and states are displayed as undefined. The browser console shows the following error:
DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
Details:
Home Assistant Setup: Running over SSL/HTTPS
Fusion Dashboard: Running over HTTP on a custom port
Due to the different protocols (HTTPS for Home Assistant and HTTP for Fusion Dashboard), the WebSocket connection fails to establish.
Observations:
The Fusion Add-on works perfectly when accessed via Ingress.
Request for Assistance:
Has anyone else encountered this issue and found a solution or workaround? Any suggestions on how to resolve the WebSocket connection issue in this mixed content setup would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
@fldc Yes, that looks like the same issue. If Fusion would add support to serve the same SSL certificate as homeassistant, the issue would be resolved.
Description:
I have set up the Fusion Add-on to run over a custom port. While the dashboard loads correctly, all sensor names and states are displayed as undefined. The browser console shows the following error:
DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
Details:
Home Assistant Setup: Running over SSL/HTTPS
Fusion Dashboard: Running over HTTP on a custom port
Due to the different protocols (HTTPS for Home Assistant and HTTP for Fusion Dashboard), the WebSocket connection fails to establish.
Observations:
The Fusion Add-on works perfectly when accessed via Ingress.
Request for Assistance:
Has anyone else encountered this issue and found a solution or workaround? Any suggestions on how to resolve the WebSocket connection issue in this mixed content setup would be greatly appreciated.
The text was updated successfully, but these errors were encountered: