# Mqtt In node shows other payload than mqtt Bridge Node

**URL:** <https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187>\
**Category:** General\
**Tags:** debugging, mqtt\
**Created:** [25 January 2022 07:08 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187 "2022-01-25T07:08:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![pi1234](https://avatars.discourse-cdn.com/v4/letter/p/d9b06d/32.png) [@pi1234](https://discourse.nodered.org/u/pi1234)\
**Post date:** [25 January 2022 07:08 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/1 "2022-01-25T07:08:00Z")

</div>

Hello,

I have a problem with the payload I got from an In node (zigbee2mqtt).

I have a Philips Hue Dimmer Switch (V1) and I can see at the bridge node that all keystrokes of the dimmer switch will be shown correctly. This means On\_press, On\_Hold, On\_press\_release and the same for Off and the dimmer keys.

But if I connect the dimmer switch with an In node I only got "On\_Press" for every action. This means I press the On button and got **two** times "On\_press" instead of 1x On\_press and 1x On\_press\_Release. The same for any other button.

Any idea how to fix this?

Kind Regards,  
Philipp

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [25 January 2022 10:48 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/2 "2022-01-25T10:48:00Z")

</div>

What are you using as the `topic` in the `mqtt-in` node?  
Put a `debug` node on the output of the `mqtt-in` node and show us the different data.

---

<div class="post-metadata">

**Author:** ![pi1234](https://avatars.discourse-cdn.com/v4/letter/p/d9b06d/32.png) [@pi1234](https://discourse.nodered.org/u/pi1234)\
**Post date:** [25 January 2022 11:53 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/3 "2022-01-25T11:53:06Z")

</div>

I do not use "mqtt in" node. I use the "In" node from contrib-zigbee2mqtt.

What do I have to use for a topic at "mqtt in" node to get msg.payload.action? deviceID/action ?

---

<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:** [25 January 2022 12:30 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/4 "2022-01-25T12:30:24Z")

</div>

Is the bridge node part of contrib-zigbee2mqtt too?

---

<div class="post-metadata">

**Author:** ![pi1234](https://avatars.discourse-cdn.com/v4/letter/p/d9b06d/32.png) [@pi1234](https://discourse.nodered.org/u/pi1234)\
**Post date:** [25 January 2022 14:57 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/5 "2022-01-25T14:57:47Z")

</div>

Hey,

Yes it is:  
 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/c/dcd2d436356ad10d3e3be0226c4bbda0a1d59f3f.png)

I have further information. The payload will be shown correctly at the moment (I did not do anything) but after I have changed the payload output of the IN node the payload is crap again. After waiting a few minutes the payload is correct again.

Looks like some kind of temporary output bug ....

---

<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:** [25 January 2022 15:11 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/6 "2022-01-25T15:11:19Z")

</div>

I am not sure whether anyone here uses the zigbee node. Most use the standard MQTT nodes to achieve the same thing. I know that some have had problems with the zigbee node and have moved away from it. You can do anything with the standard nodes that can be done with that node. Some find it useful to set, in the zigbee2mqtt configurartion file, `outptut: attribute_and_json` which makes the measured values available individually as well as combined in a javascript object. This is described in [MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/configuration/mqtt.html#mqtt-payload-format)

A useful tool to install is MQTTExplorer which will show you all the topics your device publishes to, and the values received.

---

<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:** [26 March 2022 15:12 UTC](https://discourse.nodered.org/t/mqtt-in-node-shows-other-payload-than-mqtt-bridge-node/57187/7 "2022-03-26T15:12:00Z")

</div>

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