At debug level you must have a lot of log messages, a lot more.
These dropped messages don’t fit the RFLink parser. It expects something like 20;03;Oregon UVN1x8;ID=EA10;UV=0000;BAT=LOW; but is getting an extra zero (020).
Are just some of the messages from device or are all of them incorrect? Do you have any good read for this UV entity?
The config ID seems wrong to me. It must be something like Oregon_UVN1x8_EA10_uv or similar.
As you have the automatic_add: true in your RFLink configuration if there are no extra entities created from the device (like the battery) it must indicate that RFLink is not able to parse any message. It can be a problem in the device or in the parser, and nothing could be done from the HA side.