# Debugging and Notification issues

**URL:** <https://discourse.nodered.org/t/debugging-and-notification-issues/46652>\
**Category:** General\
**Created:** [3 June 2021 12:20 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652 "2021-06-03T12:20:09Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![alamapstieks](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@alamapstieks](https://discourse.nodered.org/u/alamapstieks)\
**Post date:** [3 June 2021 12:20 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/1 "2021-06-03T12:20:09Z")

</div>

Hi chaps,

I have Node Red running in HA, it installed version 1.3.5 in the add-on 9.1.3. I've been using NR for a few years and love it. Since this update my debugging stopped working as well as the notifications under the nodes that tells you what is going on. I checked and I have the option enabled:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/a/9ae366adaadac31c721831347bd110fd3987b275.png)

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/1/113f95abda850de83e8ab0d34bebc517d6e5ec14.png)

I am not sure if there is an easy way to downgrade or if anyone has any ideas on how I can get debug to work again?

Many thanks

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 June 2021 12:26 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/2 "2021-06-03T12:26:00Z")

</div>

Hi @alamapstieks

Whilst I can't claim any knowledge of how NR is embedded in HA, the symptoms you describe indicate an issue with the websocket connection from the editor back to the NR runtime.

We've not had any reports of issues, in HA or otherwise.

Can you try a different browser just to rule out anything on that side?

---

<div class="post-metadata">

**Author:** ![alamapstieks](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@alamapstieks](https://discourse.nodered.org/u/alamapstieks)\
**Post date:** [3 June 2021 12:40 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/3 "2021-06-03T12:40:36Z")

</div>

Thanks for that, to my knowledge you just need the node-red-contrib-home-assistant-websocket. I am on the latest.

I just tried it in both Chrome and Firefox... no joy. Same issue with no debugging or status.

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/6/16fc6aaabad1a4dbd8c93422c7db2cd00ca3cd68.png)

---

<div class="post-metadata">

**Author:** ![alamapstieks](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@alamapstieks](https://discourse.nodered.org/u/alamapstieks)\
**Post date:** [3 June 2021 13:12 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/4 "2021-06-03T13:12:37Z")

</div>

Actually I am not sure it could be a websocket issue as Node Red works, all the scripts run just fine. The only issue is that they don't provide a status any more, nor does the debugging function run

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 June 2021 13:18 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/5 "2021-06-03T13:18:42Z")

</div>

The debug messages and status updates get to the editor via a websocket connection. This has nothing to do with the ha websocket nodes you've mentioned - it is entirely internal to how the editor/runtime communicate with each other.

The fact you're not getting either debug or status tells us something is wrong with that websocket connection.

Have you tried a different browser? Checked the browser console for any errors?

---

<div class="post-metadata">

**Author:** ![alamapstieks](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@alamapstieks](https://discourse.nodered.org/u/alamapstieks)\
**Post date:** [3 June 2021 13:23 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/6 "2021-06-03T13:23:57Z")

</div>

> [@alamapstieks](#):
>
> I just tried it in both Chrome and Firefox... no joy. Same issue with no debugging or status.

Yes, no luck in getting errors or getting it to work in other browsers. For now I will try to downgrade and see if I can get it working at least for now.

Thanks again, I really appreciate you trying to help!

---

<div class="post-metadata">

**Author:** ![alamapstieks](https://avatars.discourse-cdn.com/v4/letter/a/82dd89/32.png) [@alamapstieks](https://discourse.nodered.org/u/alamapstieks)\
**Post date:** [3 June 2021 14:08 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/7 "2021-06-03T14:08:12Z")

</div>

I downgraded to 1.3.3 and it is working again 😃

I guess I will just wait a few months before I risk upgrading...

---

<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:** [2 August 2021 14:08 UTC](https://discourse.nodered.org/t/debugging-and-notification-issues/46652/8 "2021-08-02T14:08:21Z")

</div>

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