# Node-RED 4.0 warnings have taken over my debug window

**URL:** <https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556>\
**Category:** General\
**Created:** [25 September 2023 02:58 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556 "2023-09-25T02:58:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SteveMann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevemann/32/3810_2.png) [@SteveMann](https://discourse.nodered.org/u/SteveMann)\
**Post date:** [25 September 2023 02:58 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/1 "2023-09-25T02:58:55Z")

</div>

I am running Node Red V3.10 as an add-on in Home Assistant. Recently I have begun to receive this warning:  
`"Deprecated API warning: Calls to RED.util.evaluateJSONataExpression must include a callback. This will not be optional in Node-RED 4.0. Please identify the node ..."`

Every api-call-service (Home Assistant) triggers this warning, flooding my debug window, making it useless. I have no control over the Home Assistant implementation of Node-Red and the person who has control is aware of the issue. But, do I really need to see this warning _thousands_ of times? Is there no way to mute the warnings?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [25 September 2023 06:46 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/2 "2023-09-25T06:46:50Z")

</div>

> [@SteveMann](#):
>
> Is there no way to mute the warnings?

No there is not. Node-RED v4 is going to come along a lot quicker than the 3.1 release so it is important HA resolve this in their nodes sooner rather than later.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [25 September 2023 06:56 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/3 "2023-09-25T06:56:36Z")

</div>

> [@Steve-Mcl](#):
>
> No there is not.

Aren't warnings captured by a status node ?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [25 September 2023 06:58 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/4 "2023-09-25T06:58:45Z")

</div>

No they are not.

Actually, I said that before thinking. I thought for a second you said "a catch node"

I don't know if status node captures warning (I don't think they do - pretty sure they don't or didn't used to)

---

<div class="post-metadata">

**Author:** ![MyRandomThoughts](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/myrandomthoughts/32/41085_2.png) [@MyRandomThoughts](https://discourse.nodered.org/u/MyRandomThoughts)\
**Post date:** [26 September 2023 12:59 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/5 "2023-09-26T12:59:13Z")

</div>

> Aren't warnings captured by a status node ?

No they are not. I have catch nodes on all my flow tabs that forward to error logs.  
The API warnings still appear.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 November 2023 12:59 UTC](https://discourse.nodered.org/t/node-red-4-0-warnings-have-taken-over-my-debug-window/81556/6 "2023-11-25T12:59:31Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.