Where I’m hitting a snag is that on the inputs page of the local emonCMS I don’t see the three values transmitted by the router, I only see the rssi, which I think is the signal strength.
I think that I’ll need to see the three values as inputs from the router before I can start logging them in the emonCMS, but I don’t know what is my next step. Do I need to edit emonhub.conf to enable the rx from the router in some way?
It maybe a little premature, but I’m going to hazard a guess here that it’s the underscores causing an issue.
The “Publishing: …” lines in emonhub.log suggest emonHub is publishing to MQTT ok, but recent debugging has suggested the emoncms’s MQTT input code is quite fussy about what is will or won’t process.
If you get output you have confirmed the MQTT is there for the taking, but emoncms isn’t processing.
You could set the logging level to info in emoncms/settings.php and restart the mqtt_input script with
sudo service mqtt_input stop
sudo service mqtt_input start
then you will have more debugging info available in /var/log/emoncms.log, to view via emoncms or by reading the file directly.
Could you try removing the underscores from both the node name and the input names and try it again?
As for the rest of the node configuration in emonhub.conf, I cannot comment as I do not know the sketch output nor is there enough emonhub.log to deduce it.
For debugging would you mind copying and pasting logs and confs excerpts into the post rather than using screenshots, it makes debugging so much easier. If you use 3x backticks on the lines before and after the excerpt it will retain the formating and add vertical and horizontal scroll bars if required.
change it to “1” for a more verbose log, the mqtt_input requires restarting to take on the change, I doubt is was needed to the changes you made to be taken in, but no harm restarting it anyway. Although hopefully you will not be seeing any errors with the new naming, minus the underscores.