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
After upgrading to 0.57.4, I started encountering the following error:
24 Oct 11:31:37 - [error] TypeError: Cannot read properties of null (reading 'last_changed')
at WaitUntil._WaitUntil_onEntityChange (/data/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/wait-until/WaitUntilController.js:151:47)
at runNextTicks (node:internal/process/task_queues:61:5)
at processImmediate (node:internal/timers:437:9)
To Reproduce
Unsure. I'm currently narrowing down what nodes specifically (if any) are causing the error. So far, if I disable all my wait-until nodes, NodeRED starts up fine.
I've narrowed it down to one particular node (or set of nodes). I have a state node for a device tracker that is set to output on connect which is wired to a wait-until node.
Whenever the WIFI_DEVICE_TRACKER entity's state becomes not_home (either on startup or due to an actual state change), the crash happens. If I manually update the entity's state to home (in the developer tools), and restart the flow, the crash does not happen. If I change the state from home -> not_home (with the flow running), the crash happens.
Please not that it appears to only be the wait-until node receiving the message which causes the crash. Having the wait-until node disabled during these state changes/startup does not cause the crash to happen.
Describe the bug
After upgrading to 0.57.4, I started encountering the following error:
To Reproduce
Unsure. I'm currently narrowing down what nodes specifically (if any) are causing the error. So far, if I disable all mywait-until
nodes, NodeRED starts up fine.I've narrowed it down to one particular node (or set of nodes). I have a state node for a device tracker that is set to output on connect which is wired to a wait-until node.
Whenever the
WIFI_DEVICE_TRACKER
entity's state becomesnot_home
(either on startup or due to an actual state change), the crash happens. If I manually update the entity's state tohome
(in the developer tools), and restart the flow, the crash does not happen. If I change the state fromhome
->not_home
(with the flow running), the crash happens.Please not that it appears to only be the
wait-until
node receiving the message which causes the crash. Having thewait-until
node disabled during these state changes/startup does not cause the crash to happen.Expected behavior
No response
Screenshots
No response
Example Flow
Environment Information
Version: 0.57.4
Home Assistant version: 2023.10.5
Companion version: 3.0.1
Node-RED version: 3.1.0
Docker: yes
Add-on: no
Node.js version: 16.20.2
OS: Linux 6.1.34-1-lts x64 LE
Additional context
These are the messages that are going into the
wait-until
node during each state change (as captured by a debug node):not_home
->home
home
->not_home
The text was updated successfully, but these errors were encountered: