Hey there, guys! Can anyone tell me why I cannot press the timestamp button in any of my flows? The debug button also doesn’t work I have to keep reloading the page until it does. Homeassistant’s companion app and other browsers behave similarly. Uninstalling most of the pallets I installed in the past months hasn’t made any difference. Log seems to be clear, except for this : “[warn] Projects disabled : editorTheme.projects.enabled=false”
This was the only way to capture the cursor, so I apologize for not posting a printscreen.
Check that you are doing a full deploy (down arrow on the deploy button)
Check that you are using the right server node (Configuration Nodes - Gear in the upper right corner)
Not at all If I really need it to work, I just have to keep reopening the node-red, which can take up to an hour of my time.
Edit: since I commented I have not been able to make it work again…
Get Node Red started even if you have to wait hours.
Then check if nay palettes need to be updated and also check if any nodes are linked to wrong servers. One of the icon in the upper right menu should give you an overview of you elements with number of connections.
Aside from bad/extra configuration nodes and nodes that need updating, for home assistant addon users directly accessing NR could correct this. Use your HA IP with 1880 instead of 8123. Use your user name and password from home assistant to access the page.
So the next time I tried it failed. I had to go directly to the node red interface using the suggestion above (1880) and that failed too until I restarted the flows from there. I think it might be random at this point. Click on the deploy drop down and you will see it as the last option.
I don’t even know if anyone is looking into this since there hasn’t been any response along those lines. I think the problem is even deeper, as even when I can finally get NR deployed and hit a Timestamp button, scripts and functions do not seem to work at all, entities come up as “not found” and often the Switch nodes output every option no matter what. I would like to know if this is being looked into.
EDIT: Maybe it’s not the other nodes that aren’t working. When I attach a Debug Node directly to a Timestamp, nothing seems to be coming out of the Timestamp (nothing in the Debug at all). I asked about this in the NR forum and was basically told that it’s an HA problem, but I don’t know who’s supposed to be maintaining NR for HA.
There is a way with https to open an single port and then forward to different servers using a revrse proxy. Idk if that can be applied with nabu casa.
I assume this is because access through the HA sidebar nr link is not working. There are 2 other possibilities I can think of. Create a webpage dashboard with http://HA_ip:1880
There is also another access point @ http://HA_ip:8123/hassio/ingress/a0d7b954_nodered. You can try that in a web dash or click the link on the addon page “Open web ui”.
it keeps loading every ~1 second bottom lines with “red.min.js:16 (websocket)”
We’re experiencing continuous WebSocket reconnections (red.min.js:16) in the developer network tab when using Node-RED as an addon in Home Assistant OS. The issue likely stems from a misconfiguration or conflict with WebSocket handling, such as ingress proxy settings, authentication, SSL, or network timeouts. Direct access works fine, but the problem occurs via Home Assistant’s interface.
I have to keep reloading the page until it does. Homeassistant’s companion app and other browsers behave similarly. Uninstalling most of the pallets I installed in the past months hasn’t made any difference. Log seems to be clear, except for this : “[warn] Projects disabled : editorTheme.projects.enabled=false”
If I really need it to work, I just have to keep reopening the node-red, which can take up to an hour of my time.
