# EmonHub Development

**URL:** <https://community.openenergymonitor.org/t/emonhub-development/6432>\
**Category:** emonHub\
**Tags:** development\
**Created:** [31 January 2018 22:25 UTC](https://community.openenergymonitor.org/t/emonhub-development/6432 "2018-01-31T22:25:20Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![pb66](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/pb66/32/27_2.png) [@pb66](https://community.openenergymonitor.org/u/pb66)\
**Post date:** [1 March 2018 15:02 UTC](https://community.openenergymonitor.org/t/emonhub-development/6432/49 "2018-03-01T15:02:26Z")

</div>

Note this thread about emonLCD and mqtt.

> [@Emonpi display info bug](https://community.openenergymonitor.org/t/emonpi-display-info-bug/6668/7):
>
> Thanks @glyn.hudson, I understand a bit more now. Am I right in thinking the “legacy” format was specifically for the now retired Nodes module? So the emonLCD might be the only thing using the “legacy” format now? @TrystanLea and I have been discussing MQTT in emonHub and currently agree that there should be 2 main implementations, one that publishes local “status” QoS1 “topic per key” data and the other that publishes a “bulk” type input to deliver data to emoncms in a quick, concise and pre…

We will also need to think about a “Nodes legacy mode” mqtt by frame in the QoS1 mqtt interfacer.

---

_[View the full topic](https://community.openenergymonitor.org/t/emonhub-development/6432)._