# Trigger node and msg.payload in debug node

**URL:** https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778
**Category:** General
**Created:** [9 February 2019 21:37 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778 "2019-02-09T21:37:39Z")
**Posts on this page:** 5
**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: [9 February 2019 21:37 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778/1 "2019-02-09T21:37:40Z")

</div>

Could someone tell me if I am missing something.

The `debug` node has an option for output to be put at/on the node similar to the `node.warn()` command in the `function` node.

For the sake of _being able to check myself_ I added a `trigger` node and a `debug` node to the output of an `inject` node set to repeat.

Granted the `trigger` node would suffice with the nice blue dot, but I decided to stick a `debug` node there and tick the button to get the message below the node too.

This is the "flow" (cut down version)

```auto
[{"id":"9f5332ad.2d8c6","type":"inject","z":"cb1ffcc6.d23ba8","name":"WAP scan","topic":"","payload":"1","payloadType":"num","repeat":"60","crontab":"","once":true,"onceDelay":"300","x":160,"y":2150,"wires":[["650fb371.4a3b04"]]},{"id":"650fb371.4a3b04","type":"trigger","z":"cb1ffcc6.d23ba8","op1":"1","op2":"0","op1type":"str","op2type":"str","duration":"1","extend":false,"units":"s","reset":"","bytopic":"all","name":"","x":340,"y":2150,"wires":[["31ed7d8f.cd836a"]]},{"id":"31ed7d8f.cd836a","type":"debug","z":"cb1ffcc6.d23ba8","name":"WiFi Scan polling","active":false,"tosidebar":true,"console":false,"tostatus":true,"complete":"payload","x":560,"y":2150,"wires":[]}]

```

It isn't rocket science.

Problem:  
The `debug` node doesn't reflect the input.

The `trigger` node detects an input. Sends a `1` then after 1 second sends a `0`

As said: The `trigger` node is a good enough indication, but ...... I stuck a `debug` node there for the fun of it.

See attached.  
 ![Screenshot%20from%202019-02-10%2008-24-01](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/3/31ada4b9e632be85a409b777525c49d7a0243bec.png)

 ![Screenshot%20from%202019-02-10%2008-30-19](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/f/fa71b34d4b7b10f119d6bfbf0fdd2cc3d041e515.png)

So the debug node is set to display the message as `node status`.  
I press the `inject` node.  
the `trigger` node is _triggered_.  
Yet, the `debug` node isn't seeing the 1.

I am probably doing something wrong. But for the sake of _getting it out there_ and maybe stopping others falling for this mistake....

Am I doing anything wrong?  
Other things to note:  
Granted this was on my _overworked_ RPI.  
I copied it and put it on the NUC (massively powered) and it does the same.  
So it can't be blamed on the RPI not having time to do it.

---

<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: [9 February 2019 22:21 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778/2 "2019-02-09T22:21:01Z")

</div>

Hi @Trying_to_learn

you have the Debug node deactivated - its button on the right-hand edge is 'in'.

In 0.19.5 that stops all output from the node in the editor - both the debug sidebar _and_ status.

In 0.20.0 we have changed that behaviour so deactivating the node will only mute the debug sidebar - the status will continue to update as you expect.

---

<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: [9 February 2019 22:35 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778/3 "2019-02-09T22:35:57Z")

</div>

ARGH. I can't believe I missed that.

Extreme apologies.

I shall maybe have to get around to updating. But with all the other _monsters_ I am not sure it will be of benefit or just re-arrange the monsters to other positions.  
(No offence.)

---

<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: [9 February 2019 22:49 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778/4 "2019-02-09T22:49:38Z")

</div>

> [@Trying\_to\_learn](#):
>
> I shall maybe have to get around to updating.

Right now, 0.20 is still in beta. I'd suggest you hold off any thought of upgrading to it until we do the full release later this month.

---

<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: [9 February 2019 23:00 UTC](https://discourse.nodered.org/t/trigger-node-and-msg-payload-in-debug-node/7778/5 "2019-02-09T23:00:26Z")

</div>

Maybe I should.

I will probably find too many _problems_ with it that will be more my contusion than problems.  
And the last thing you need are false positives.
