Closed Baael closed 2 years ago
What version of HA are you running?
for me the node-red Web UI is not reachable and seems to be stuck in an endless loop. If I disable node-red companion everything works fine.
companion v5.4 Hassio core-2021.11.5
+1 for the crashing of Node-Red after this update. Error stated in the Node-Red addon log:
"[error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#
If I remove the Node-Red Companion integration, Node-Red addon will start.
@Cafun what version of the NR nodes are you running?
Current version: 10.2.0 is the version I'm running
Current version: 10.2.0 is the version I'm running
That's the add-on version. What's the version of the node-red-contrib-home-assiatant-websocker package?
@Cafun what version of the NR nodes are you running?
Hi! I've updated all pallets and now everything is working again.
Current version: 10.2.0 is the version I'm running
That's the add-on version. What's the version of the node-red-contrib-home-assiatant-websocker package?
0.5.4
I have also looked at all the sensors ... I had wrong device classes in two of them. After deleting those, everything worked fine.
What version of HA are you running?
Home Assistant 2021.11.0
I've noticed lots of sensor even after downgrade randomly stuck with values, it almost destroyed my heater. For some reason many of them have NaN state, I tracked it down that it was because HA wanted to parse "unavailable" as float. It happens whenever I am trying to upgrade version to 0.5.3+, on 0.5.2 everything is handled properly.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
0.5.3+
Describe the bug
Since I updated to version 0.5.3 or 0.5.4 all the poll state and change state nodes are returning
unavailable
on all sensors. Downgrading to 0.5.2 solved a problem.Debug log
Nothing in logs.