maybe you can try also the log file, to see what arrives there
$ tail /var/log/emonhub/emonhub.log
in general this is the correct way of sending multiple values, and the fact that in the device log there is
MQTT Connected]
[Mqtt Dest: sending: to topic:emon/vthings1/temp, msg: 22.58]
[Mqtt Dest: sending: to topic:emon/vthings1/co2, msg: 564]
[Mqtt Dest: sending: to topic:emon/vthings1/hum, msg: 59.30]
[MQTT : 1346ms
means that they have been parsed and the messages sent
what is more weird, is that you are receiving the “hum” value, but not the others
If you are publishing to emoncms directly there will be no related info in emonhub.log as it is not part of the route and therefore unaware of that traffic.
That’s precisely why I suggested checking the published MQTT via the commandline, there is a known issue with the mqtt input to emoncms, If the Pi has not been rebooted, this behaviour is unsurprising, See the first link I posted, the issue is comprehensively documented and as yet unresolved.
Finally I solve this issue using HTTP instead of MQTT.
With MQTT I think that each line overwrites the previous line, and with the correct configuration of HTTP works fine.
Thanks a lot for your comments. It is a pity that I not have been able to configure the device with MQTT
I really wish this project were still going.
I need multiple WIFI based devices (20+) to log temperature across a large estate so we can match mechanical systems energy usage to environmental data and refine our HVAC scheduling/programming.