@glyn.hudson and @TrystanLea are insistent on everything using the same topics and so that you can target one specific device they must therefore be broken out to individual topics and it is then emoncms that suffers for it. IMO there is no good reason why emonHub couldn’t breakout all the values to non-time sensitive topics (ie current statuses) that can be used locally and ALSO send the same data as a timestamped payload to emoncms also via MQTT if that’s your preference. That way the data is available in either format, if you insist on getting individual topics at emoncms you can. But those of us wanting correctly timestamped data that arrives in a fixed order for accurate processing would no longer be excluded from using MQTT with emoncms.
I think that may be more reliable, but it seems a bit like writing an email and then printing it off and faxing it to the recipient!!!