# Dashboard Socket ID bug?

**URL:** <https://discourse.nodered.org/t/dashboard-socket-id-bug/6229>\
**Category:** Dashboard\
**Created:** [30 December 2018 05:25 UTC](https://discourse.nodered.org/t/dashboard-socket-id-bug/6229 "2018-12-30T05:25:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [30 December 2018 19:07 UTC](https://discourse.nodered.org/t/dashboard-socket-id-bug/6229/2 "2018-12-30T19:07:09Z")

</div>

Hey @hugobox,

_ **I haven't much time** _, but you can debug the code in the [ui.js](https://github.com/node-red/node-red-dashboard/blob/master/ui.js#L268) file if you want to see it with your own eyes. In that code snippet, all messages arrive from your dashboard. However when you start in the dashboard with your own constructed message, there will be less original information available as explained below...

In line 269 another function is being called to do some processing before sending the message on the output of your Button node:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/e/e98f40627c17878859447337128f51672b06275b.png)

- For button A the original.msg will contain a lot of information.
- For button B the original.msg will contain only your payload (but **no socketId or \_msgid** ).

The result of this function is then used to determine the socketId of the toSend object (which is the message to be send on the output of your Button node):

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4ff31e684606d874c0555bd668fe487e4eb8bbf0.png)

So when you create a message by yourself, the code will behave differently. Don't know at the moment if that is correct or not.

Now I'm off ...  
Bart

---

_[View the full topic](https://discourse.nodered.org/t/dashboard-socket-id-bug/6229)._