Welcome, Pieter, to the OEM forum.
Can you explain this - where are you looking, and where is the right place? You should find all the information you require, if you want to use my ‘Native’ JeeLib format for the radio, here: The emonPiCM
Unfortunately, I haven’t actively worked on LPL nor am I up to date on the latest changes to use the LPL library to be able to help you with that.
If you are looking on the “Inputs” page of emonCMS, then as rupert attempted to explain above, it would seem that you have an incorrect entry for Node 5 in your emonhub.conf file. By way of explanation, data from the “emon” front end is sent as a stream of bytes, it’s emonhub.conf which matches those to what it expects from the front end. If the total number is correct but their order or the data types are wrong, your data gets scrambled.
If you mean the LCD display, then emonhub has no influence there once the data is inside emonCMS and the display is driven by emonCMS. The front end has access to the display data bus, its only direct contribution to the display is the currents when you’re calibrating (because currents are not normally sent out of the front end or from the emonTx) or the more familiar “Booting, please wait…” message.