Node not stating status #1626
Answered
by
zachowj
mtnbiker717
asked this question in
Q&A
-
Beta Was this translation helpful? Give feedback.
Answered by
zachowj
Oct 5, 2024
Replies: 1 comment 1 reply
-
WebSocket communication appears to be rejected when accessing Node-RED through an iframe in the Home Assistant UI rather than directly via port 1880. This issue affects inject nodes, the debug window, and the new issues feature, preventing proper communication between the Node-RED backend and UI. Until this is resolved or the root cause for the WebSocket issue is identified, I recommend accessing Node-RED directly on port 1880. Related issues for tracking: |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
mtnbiker717
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WebSocket communication appears to be rejected when accessing Node-RED through an iframe in the Home Assistant UI rather than directly via port 1880. This issue affects inject nodes, the debug window, and the new issues feature, preventing proper communication between the Node-RED backend and UI.
Until this is resolved or the root cause for the WebSocket issue is identified, I recommend accessing Node-RED directly on port 1880.
Related issues for tracking: