Also, the second and third are ‘Node emonpi’ and ‘Node emonth’. I understand what those mean but since I have neither an emonPi nor an emonTH they’re just a distracting waste of space. How do I get rid of those three lines?
They could be from a neighbouring OEM system (not likely), the likeliest explanation, after you accidentally used that NodeID when working on something else, is that they are interference that by coincidence happens to have exactly fitted the specification in your emonhub.conf
You can delete all the node specifications in emonhub.conf that you don’t and won’t use, then they should never appear on the inputs page. But even when they do appear there, they don’t cost storage space until you write to a feed. So a distraction yes, but not a waste of storage space.
I haven’t done anything except plug in my two emonTx and create an enphase device that receives updates from a little program that screenscrapes my Enphase Envoy PV-monitoring device and posts the data to emoncms.
Node 28, emonpi and emonth5 all show a status of ‘n/a’. They all have a bunch of input names with no description or process list and an updated status of n/a. So they look completely unused.
Node 28 does not appear in the config file, so that isn’t the problem or the solution. emonpi and emonth5 do, but so do lots of other things that don’t show up on my inputs page, so I don’t think deleting those is terribly sensible either.
Incidentally, when I look at the config view http://emonpi/emoncms/config/view the default is to View log and Auto update log view is ON, but the log display ends part way through a message on 2018-12-08. And indeed /var/log/emonhub/emonhub.log (note extra directory not documented) has exactly the same ending: