# Zigbee2mqtt command **URL:** \ **Category:** Bindings\ **Created:** [March 13, 2019, 12:47am UTC](https://community.openhab.org/t/zigbee2mqtt-command/70105 "2019-03-13T00:47:48Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![job](https://community.openhab.org/user_avatar/community.openhab.org/job/32/37738_2.png) [@job](https://community.openhab.org/u/job)\ **Post date:** [October 20, 2019, 9:32am UTC](https://community.openhab.org/t/zigbee2mqtt-command/70105/6 "2019-10-20T09:32:05Z")
If you use the mqtt1 binding, all the information has to be stored in the items file. With mqtt2 this is not possible because the topic structure is defined on thing level. The item level just references it. Here are plenty of examples to use zigbee2mqtt with the mqtt1 binding. You can use JSONPATH transformation directly, but I decided against because of the dynamic message structure and constant exception due to that. > [@Howto use zigbee2mqtt with openHAB, removing proprietary bridges / gateways](https://community.openhab.org/t/howto-use-zigbee2mqtt-with-openhab-removing-proprietary-bridges-gateways/48768): > > If you want to use zigbee2mqtt with openHAB, please advance to the next level. The following is a far nicer implementation of the same stuff, just with the mqtt2 binding and a new option of zigbee2mqtt The old stuff, if you prefer the mqtt1 binding and too many tranformations, please go ahead. Recently io discovered [zigbee2mqtt](https://github.com/Koenkk/zigbee2mqtt/blob/master/README.md), which made me think of getting rid of my hue bridge and being able to use a large number of cheap sensors. This works pretty well. I already joined 15 devices (inclu… --- _[View the full topic](https://community.openhab.org/t/zigbee2mqtt-command/70105)._