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.
See this the tests I performed here
and also the more recent “Unable to use certain symbols in MQTT topics with emonCMS mqtt_input” discussion about certain characters in MQTT topics too.
As a quick test you can try subscribing to that topic from the command-line using
mosquitto_sub -v -u 'emonpi' -P 'emonpimqtt2016' -t 'emon/DW_mk2PVrouter/#'
(assuming the password etc is still stock)
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.
insert code, log or conf here