It should be on the foot of each page, but more detailed info is available on the admin page of emoncms.
It is an emonPi, I missed that the first time. If you have updated via the update buttons on the admin page recently you should be all good. The device module in place and using all the latest versions. That said, how old is the emonPi? I wonder what emonSD version number you are running? Again that info is on the admin page
You shouldn’t need to download anything and it might upset things if you do so yes, better to leave that.
Could you post the server info (there is a copy to clipboard button) from the admin page so we can see what you have?
Looking closer at the screenshots I suspect you are not running the latest versions. There is now a lafthand menu side bar throughout emoncms (much like you see for the apps page) but that can be collapsed so it isn’t an absolute indication of version. But I now notice there is no device setup cog at the end of each node header on the inputs page.
Unfortunately no, there is no place to globally declare that. It’s there mainly for you to understand the different ways of setting it up. More recently there are some templates for the emonPi or emonTx that use the “type1” and “type2” in the title to help you select the right device template for your hardware. BUT, I don’t think that will help you much here since it looks like your emonPi is neither type as it doesn’t have a CT on the grid or main consumers. and whilst you MartinR diverter is “type 2” there will not be any device templates for that hardware.
I assume the MartinR diverter posts the PV CT data so I’m wondering why you have chosen to measure that with the emonPi.
Going back to the original question. once you have access to the device module (via the cogs after updating or maybe via the “setup -> device” menu’s currently?) you should be able to auto-configure your openEVSE.
This is the template https://github.com/emoncms/device/blob/2.0.0/data/OpenEVSE/openevse.json you see it has listed feeds like ev_power and ev_energy, hopefully these are the name that the openEVSE app looks for to auto configure.
although it looks like the error message suggests the more generic “use_kwh” feed is undefined. I assume it wasn’t able to “auto-detect” a feed called use_kwh. Whether it is called “use_kwh” or not, you will need phpfina feed that reports your use in kWh’s. If it was named “use_kwh” it will get picked up automatically, otherwise go to the openevse apps config (spanner top right) and use the dropdown for the “use_kwh” feed selection to select the correct feed.
[you posted while I was writing the above so in response to your last post . . ]
Ok the penny’s just dropped why you might want the emonPi PV CT, to help control the EV. If that is the case, I would expect the other emonPi CT is drawn in the wrong location and should be on the grid incomer not the EV charger. Otherwise it cannot know when you are exporting or not.
However, I suspect you need it all setup correctly for the auto control of the EV to work, it’s not just plug and play (as far as I can make out, but we are way out of my area of experience here) especially with the MartinR diverter, if that is working well, the EV will only charge after whatever your diverter loads finish consuming. I imagine you would want the EV to be a higher priority? Then the diverter would mop up the excess PV for each 6A step of the EV charger so it better uses the PV without importing.