That shouldn’t be necessary - the default settings should be there and you should see the inputs.
A quick rundown of emonCMS:
Data comes in to emonhub. If the structure/format of the data doesn’t fit one of the specifications in emonhub.conf, everything from that device in the data feed grinds to a halt there. If it does fit, it gets passed on to the Inputs page. There you can ‘fiddle’ with it. Click the spanner icon on the end of the line for each value, and you can add a ‘process’ that, for example, scales the value, converts power to accumulated energy, and so on. From there, you must “Log to Feed” to store the data. A Feed is a database - one for each quantity you want to store. Once the data is in there, you can look at it with Graphs or assemble a ‘Dashboard’ with dials etc, or use a pre-built ‘Visualisation’.
If you can’t see anything, the first place to look is the emonhub log file. If it’s in there with no errors, go to the Inputs page. If it’s getting to the Inputs page, is it logged to a Feed? If yes, go to the Feeds page to check. There, you can trigger a graph (but leave this for a while so that you have enough data to see). If you get this far, then you have something to work with.
Your emonPi is Node 5. This is what emonhub log looks like for Node 5 (Yours won’t be identical, this is the CM version)
2022-12-19 23:22:50,147 DEBUG RFM2Pi 3509089 NEW FRAME : OK 5 142 0 132 0 18 1 99 93 0 0 0 0 0 0 0 0 0 0 0 0 127 172 31 0 0 0 0 0 25 162 31 0 178 98 33 0 (-0)
2022-12-19 23:22:50,151 DEBUG RFM2Pi 3509089 Timestamp : 1671492170.146580
2022-12-19 23:22:50,152 DEBUG RFM2Pi 3509089 From Node : 5
2022-12-19 23:22:50,152 DEBUG RFM2Pi 3509089 Values : [142, 132, 274, 239.07, 0, 0, 0, 0, 0, 0, 2075775, 0, 2073113, 2187954]
2022-12-19 23:22:50,153 DEBUG RFM2Pi 3509089 Sent to channel(start)' : ToEmonCMS
2022-12-19 23:22:50,154 DEBUG RFM2Pi 3509089 Sent to channel(end)' : ToEmonCMS
2022-12-19 23:22:50,201 DEBUG MQTT Publishing: emon/emonpi/power1 142
2022-12-19 23:22:50,204 DEBUG MQTT Publishing: emon/emonpi/power2 132
2022-12-19 23:22:50,206 DEBUG MQTT Publishing: emon/emonpi/power1pluspower2 274
2022-12-19 23:22:50,208 DEBUG MQTT Publishing: emon/emonpi/vrms 239.07
2022-12-19 23:22:50,211 DEBUG MQTT Publishing: emon/emonpi/t1 0
2022-12-19 23:22:50,213 DEBUG MQTT Publishing: emon/emonpi/t2 0
2022-12-19 23:22:50,215 DEBUG MQTT Publishing: emon/emonpi/t3 0
2022-12-19 23:22:50,216 DEBUG MQTT Publishing: emon/emonpi/t4 0
2022-12-19 23:22:50,218 DEBUG MQTT Publishing: emon/emonpi/t5 0
2022-12-19 23:22:50,220 DEBUG MQTT Publishing: emon/emonpi/t6 0
2022-12-19 23:22:50,222 DEBUG MQTT Publishing: emon/emonpi/pulse1count 2075775
2022-12-19 23:22:50,224 DEBUG MQTT Publishing: emon/emonpi/pulse2count 0
2022-12-19 23:22:50,225 DEBUG MQTT Publishing: emon/emonpi/E1 2073113
2022-12-19 23:22:50,227 DEBUG MQTT Publishing: emon/emonpi/E2 2187954
2022-12-19 23:22:50,229 INFO MQTT Publishing 'node' formatted msg
2022-12-19 23:22:50,230 DEBUG MQTT Publishing: emonhub/rx/5/values 142,132,274,239.07,0,0,0,0,0,0,2075775,0,2073113,2187954
On the first line, OK says the message is intact, 5 is the Node ID - which is what you look for.