# DB2 - dropdown node sends unwanted \_session msg

**URL:** https://discourse.nodered.org/t/db2-dropdown-node-sends-unwanted-session-msg/96173
**Category:** Dashboard
**Tags:** dashboard-2
**Created:** [22 March 2025 13:18 UTC](https://discourse.nodered.org/t/db2-dropdown-node-sends-unwanted-session-msg/96173 "2025-03-22T13:18:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Switchblade2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/switchblade2/32/60655_2.png) [@Switchblade2](https://discourse.nodered.org/u/Switchblade2)
#### Post date: [22 March 2025 13:18 UTC](https://discourse.nodered.org/t/db2-dropdown-node-sends-unwanted-session-msg/96173/1 "2025-03-22T13:18:29Z")

</div>

I've found out that the DB2 dropdown node sends a \_session messagw as part of the full msg.  
The \_session message look like this

```auto
{"type":"websocket","id":"3e9d699ebed3fa04"}

```

and it blocks the payload to be received by my HeatPump via a websocket node.  
The msg from DB2 "number input" or "text input" nodes does not contain a \_session message

I've created a workarond to extract the payload and then delete the original msg before setting msg.payload again.

Is this \_session message normal and needed for anything?

---

<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: [21 April 2025 13:18 UTC](https://discourse.nodered.org/t/db2-dropdown-node-sends-unwanted-session-msg/96173/2 "2025-04-21T13:18:45Z")

</div>

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