# I don't understand this message I see in the debug output

**URL:** <https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847>\
**Category:** General\
**Created:** [16 November 2021 19:57 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847 "2021-11-16T19:57:26Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [16 November 2021 19:57 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/1 "2021-11-16T19:57:26Z")

</div>

This could be a `tasmota` problem, but I have to start somewhere.

I recently got a device back into the system and since then I am getting these funny messages.

 ![Screenshot from 2021-11-17 06-52-33](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/b/2bee5260b1d6494c17711b5f5035716f2b03d6de.png)

Which is kind of fine, but when I click on the node name I am given this screen:

 ![Screenshot from 2021-11-17 06-52-50](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/7/37373eaf16721eff5d8f4c43a53322c39c422194.png)

Which again is ok, but I can't find that to which the previous one is referring.

---

<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:** [16 November 2021 20:10 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/2 "2021-11-16T20:10:14Z")

</div>

It isn't clear to me which message you're highlighting in the first screenshot.

Is it the `ECONNRESET` or the `Online` message?

I assume it's the `ECONNRESET` message as that does look like it has come from a Config node - which is why it has opened the config node sidebar. I would expect it to have scrolled to reveal the node in the list, but no matter.

If you copy the node id - `b8f39b....` - then open the search dialog (`ctrl-f`) and search for that id, that should help you identify it.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [16 November 2021 20:20 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/3 "2021-11-16T20:20:09Z")

</div>

Sorry. I got ambitious circling the error. It is the ECONNRESET message.

OK, I'll try what you suggested. It would be helpful if _you_ could copy the node-id as well.

When I go to that line, it only offers me the option to find that node.

Ok, found it.

Seems it is the/a `tasmota` node.

I'll go to them and see what happens.

Weird thing though:

That node is `disabled`.

Screen shot

 ![Screenshot from 2021-11-17 07-23-05](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/1/c1ec48622db664456be7987f9f403f72ec1c85f0.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [16 November 2021 22:12 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/4 "2021-11-16T22:12:48Z")

</div>

Is that the config node that is disabled, or one of the nodes using that config?

---

<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:** [16 November 2021 22:41 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/5 "2021-11-16T22:41:25Z")

</div>

The node that is logging the error is the first one in the search results - the config node.

The other node shows up in the search results because it uses that config node (so the id you're searching for appears in its configuration).

So you have a tasmota node that is unable to connect to the IP address it is configured with.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [17 November 2021 00:21 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/6 "2021-11-17T00:21:20Z")

</div>

Thanks.

I'll have to look into that a bit more then.

I got it (installed) because it looked interesting and may be useful.

I never got to use it (I put it there with the idea of replacing the other nodes with it but never got around to it - if I remember correctly.

Ok, maybe not.

I deleted it and the "then vacated MQTT node" and I couldn't talk to the Tasmota device.

Hmmm..

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [17 November 2021 04:42 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/7 "2021-11-17T04:42:43Z")

</div>

Hmm... Further investigation and observation indicates the new(er) device is causing the problem.

Until now I had a different device for the job. I replaced it with a different `Tasmota` device.  
Then the problems began.  
To test this assertion I have put things back to how they were.

If interested: stay tuned.

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [17 November 2021 07:13 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/8 "2021-11-17T07:13:16Z")

</div>

Hi Andrew,  
I had a similar error message a couple of years ago. I suspect your broker is not accepting 2 connections with the same Username and/or same ClientID, so the MQTT broker refuses the connection.  
From memory, I think my problem was I had two Sonoff S20 switches that had the same MQTT client reference, so it might be worth checking the MQTT parameters in your system especially as you say...  
_"I recently got a device back into the system and since then I am getting these funny messages"_  
You could take a look at the 'mosquitto' logs as that might give you a clue as to what is happening.  
Might also be worth doing an OTA update of Tasmota to the latest version which is 10.0.0

 ![Screen Shot 11-17-21 at 07.06 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/c/4c5d83a78952dda24357ac18b02b1fc4c821c6d3.gif)

Here's a link to a 'posting' that sounds very similar to your problem.

> <https://github.com/DaveMDS/node-red-contrib-tasmota/issues/27>
>
> Hi there, 
> Today I had upgraded to the latest version of node red (1.3.3 from m…aybe 1.3.1 or so). I had 38 instances of tasmota working which included sensors, buttons, etc. 
> However, when updating to the latest tasmota node version, all hell broke lose on my mqtt server (mosquito). It took me about 2 hours to pinpoint the problem to tasmota. Only once I pointed the tasmota mqtt settings to a non existing mqtt server, the rest of my home automation went back to normal. Every couple of seconds I had "burst" of over 200 mqtt msg/ sec, completely parallising my entire home automation system. 
> Experimenting with a single tasmota node and the correct mqtt settings did not yield any working results any longer either while all other nodes using mqtt work fine. 
> Not sure what exactly happend but all of my 38 node-red-contrib-tasmota nodes are down (while e.g. node-red-contrib-sonoff-tasmota-enhanced or mqtt receive work perfectly fine). 
> As my tasmota node configurations are partially complex, deleting and replacing them all would be a very bad option for me. 
> 
> Here a screenshot showing the debug output when I "freshly" create a new node-red-contrib-tasmota node and new MQTT settings, while node-red-contrib-sonoff-tasmota-enhanced works perfectly fine. 
> !\[image\](https://user-images.githubusercontent.com/5363948/115974452-bbb57780-a554-11eb-9447-1c7098f03958.png)
> 
> Not sure what it is but something seems "incompatible" with MQTT now! 
> 
> Is there anything I can do to provide additional information for further troubleshooting or any other (manual) tricks to restore normal operation? So far I was really happy with this tasmota node and it would be a shame if I had to replace it all. 
> 
> THANKS
> Robert

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [17 November 2021 19:44 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/9 "2021-11-17T19:44:45Z")

</div>

Slight/small update:

To test/prove it was that device causing the problem I unplugged it and put things back to what they were.

That was about 10 hours ago. But then I got curious and plugged in that unit again and scanned for WiFi (don't exactly know why, but anyway) and I saw a WAP appead `Tasmota......`.

Hhhmmmm... Seems it has been _reset_ back to being a WAP.

Anyway, that is that. Something else now.  
Yes: Putting back things to how they were has kind of helped.  
The power point isn't being turned on at random times.

For better or worse I forgot to change the logging and this is what I have in a log:

Starting with tings being good.  
11:55:xx Turn on power point.  
12:05:xx Turn off power point. (BAUHN-1)

Sept 16, things were a bit weird. (History)

Dunno what happened but then a jump to November.

17 November is about when I replaced/swapped the power point.  
Alas stupid me for got a lot of things and well, let's move on.

I will delete some lines only because they may confuse things.  
I also have a bulb and it was getting used a bit and it isn't part of the problem.

`BAUHN-1` is **not** in the picture from then on.  
It still gets commands sent because I goofed and hadn't modified the flow to dynamically accept changed of that device.

But you can see all the `ARLEC-1` commands.

The last line is about when I swapped them back and removed `ARLEC-1`

So I don't have much new stuff, as that was only yesterday afternoon about 17:00 and it is now 06:40 (local)

## Another thing:

Yes, I need to tidy up the command/s to turn the devices on/off. Sending `Y` and `N` as well as `0` and `1` isn't good programming.

I shall have to get to that soon. I know it is confusing, but I don't think it is/was contributing to the problem.

`BAUHN-1` is a 3 point device. `ARLEC-1` is a single one. Better suited to what is needed.  
I only used `BAUHN-1` because of clearances. I built a short _extension cord_ for the power and plugged it in, the I could plug in/use `ARLEC-1`. Or though I could.

A few months ago I also posted about weird things happening. `BAUHN-1 would be turned on randomly a lot of the time. Alas I wasn't always here and .... anyway. I replaced 3 power supplies with official ones and that problem stopped. `BAUHN-1` would stay off until commanded to turn on. Then turn off at the given time.

```auto
BAUHN-1/cmnd/power3 OFF 2021-09-11 12:05:55
BAUHN-1/cmnd/power3 ON 2021-09-12 11:55:22
BAUHN-1/cmnd/power3 OFF 2021-09-12 12:05:20
BAUHN-1/cmnd/power3 ON 2021-09-13 11:55:45
BAUHN-1/cmnd/power3 OFF 2021-09-13 12:05:43
BAUHN-1/cmnd/power3 ON 2021-09-14 11:55:52
BAUHN-1/cmnd/power3 OFF 2021-09-14 12:05:50
BAUHN-1/cmnd/power3 ON 2021-09-15 11:55:06
BAUHN-1/cmnd/power3 OFF 2021-09-15 12:05:04
BAUHN-1/cmnd/POWER 2021-09-16 05:01:36
BAUHN-1/cmnd/power1 Y 2021-09-16 05:01:37
BAUHN-1/cmnd/power2 Y 2021-09-16 05:01:37
BAUHN-1/cmnd/power3 Y 2021-09-16 05:01:37
BAUHN-1/cmnd/power0 Y 2021-09-16 05:01:37
BAUHN-1/cmnd/power3 ON 2021-09-16 11:55:07
BAUHN-1/cmnd/power3 OFF 2021-09-16 12:05:05
BAUHN-1/cmnd/power0 ON 2021-09-16 14:26:07
BAUHN-1/cmnd/power0 OFF 2021-09-16 14:26:08
BAUHN-1/cmnd/power3 ON 2021-09-17 11:55:32
BAUHN-1/cmnd/power2 ON 2021-11-13 08:07:11
BAUHN-1/cmnd/power2 ON 2021-11-13 08:11:35
BAUHN-1/cmnd/power2 OFF 2021-11-13 08:11:46
ARLEC-1/cmnd/power1 170 2021-11-17 07:30:33
BULB_2/cmnd/dimmer 170 2021-11-17 07:30:33
BULB_2/cmnd/ct 170 2021-11-17 07:30:33
BAUHN-1/cmnd/power1 170 2021-11-17 07:30:33
BULB_2/cmnd/dimmer 170 2021-11-17 07:30:33
BULB_2/cmnd/ct 170 2021-11-17 07:30:33
ARLEC-1/cmnd/power1 ON 2021-11-17 07:30:34
ARLEC-1/cmnd/power1 OFF 2021-11-17 07:30:36
ARLEC-1/cmnd/power1 A1 2021-11-17 07:32:26
ARLEC-1/cmnd/POWER 2021-11-17 07:58:24
ARLEC-1/cmnd/power1 170 2021-11-17 09:02:53
BULB_2/cmnd/ct 170 2021-11-17 09:02:53
BAUHN-1/cmnd/power1 170 2021-11-17 09:02:53
ARLEC-1/cmnd/power1 170 2021-11-17 09:07:59
BAUHN-1/cmnd/power1 170 2021-11-17 09:07:59
ARLEC-1/cmnd/POWER 2021-11-17 09:08:02
ARLEC-1/cmnd/power1 2021-11-17 09:09:42
ARLEC-1/cmnd/POWER 2021-11-17 09:09:42
ARLEC-1/cmnd/power1 ON 2021-11-17 09:16:08
ARLEC-1/cmnd/power1 OFF 2021-11-17 09:16:10
ARLEC-1/cmnd/POWER 2021-11-17 10:39:04
ARLEC-1/cmnd/power1 170 2021-11-17 10:48:56
BAUHN-1/cmnd/power1 170 2021-11-17 10:48:56
ARLEC-1/cmnd/POWER 2021-11-17 10:56:45
ARLEC-1/cmnd/power1 ON 2021-11-17 11:12:05
ARLEC-1/cmnd/power1 OFF 2021-11-17 11:18:09
>> -- Mark -- 2021-11-17 11:18:46 ------------
>> -- Mark -- 2021-11-17 11:18:47 ------------
ARLEC-1/cmnd/POWER 2021-11-17 11:22:36
ARLEC-1/cmnd/power1 ON 2021-11-17 11:23:02
ARLEC-1/cmnd/power1 OFF 2021-11-17 11:23:03
ARLEC-1/cmnd/POWER 2021-11-17 11:24:13
ARLEC-1/cmnd/power1 ON 2021-11-17 11:26:44
ARLEC-1/cmnd/power1 OFF 2021-11-17 11:26:45
ARLEC-1/cmnd/FullTopic 2021-11-17 11:40:05
ARLEC-1/cmnd/status 2021-11-17 11:40:05
ARLEC-1/cmnd/modules 2021-11-17 11:40:05
ARLEC-1/cmnd/gpios 2021-11-17 11:40:05
ARLEC-1/cmnd/switchdebounce 2021-11-17 11:40:05
ARLEC-1/cmnd/power1 ON 2021-11-17 11:45:21
ARLEC-1/cmnd/power1 OFF 2021-11-17 11:45:34
ARLEC-1/cmnd/power1 ON 2021-11-17 11:45:53
ARLEC-1/cmnd/power1 OFF 2021-11-17 11:46:03
ARLEC-1/cmnd/power1 ON 2021-11-17 12:07:11
ARLEC-1/cmnd/power1 OFF 2021-11-17 12:13:11
ARLEC-1/cmnd/power1 ON 2021-11-17 12:58:40
ARLEC-1/cmnd/POWER 2021-11-17 13:00:04
ARLEC-1/cmnd/power1 ON 2021-11-17 13:03:31
ARLEC-1/cmnd/POWER 2021-11-17 13:04:54
ARLEC-1/cmnd/power1 OFF 2021-11-17 13:05:05
ARLEC-1/cmnd/POWER 2021-11-17 13:07:59
ARLEC-1/cmnd/power1 ON 2021-11-17 13:08:34
ARLEC-1/cmnd/power1 OFF 2021-11-17 13:08:37
ARLEC-1/cmnd/POWER 2021-11-17 14:22:39
ARLEC-1/cmnd/power1 ON 2021-11-17 14:25:10
ARLEC-1/cmnd/POWER 2021-11-17 14:35:44
ARLEC-1/cmnd/power1 ON 2021-11-17 14:45:40
ARLEC-1/cmnd/power1 OFF 2021-11-17 14:58:31
>> -- Mark -- 2021-11-17 14:59:30 ------------
ARLEC-1/cmnd/POWER 2021-11-17 15:18:18
ARLEC-1/cmnd/power1 ON 2021-11-17 15:21:25

```

---

<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:** [16 January 2022 19:45 UTC](https://discourse.nodered.org/t/i-dont-understand-this-message-i-see-in-the-debug-output/53847/10 "2022-01-16T19:45:05Z")

</div>

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