As @deckbsd (thanks for answering the questions) already explained, the field cw_beacon is an additional field in lasarsat.ksy.
I missed it to gave you a hint to add a field like that, sorry.
For uploading people it is really nice to see their own and from others uploaded beacons on the dashboard to confirm correct upload and compare it with the others, although it is not mandatory for displaying the beacon values.
You may think about adding this field into your .ksy. It just strings together (+) the already present cw values to reconstruct the original uploaded string.
For LASARsat it’s:
cw_beacon:
value: '"u"+uptime_total_raw+"r"+reset_number_raw+"t"+temp_mcu_raw+"p"+temp_pa_raw'
Just to compare the difference without and with a beacon field:
CO-65 (no beacon field)
CO-57 (with beacon field)
But as you can see, there is no more contribution with having a beacon field.
Anyway, don’t expect many cw beacon upload(er)s.
People have to do it manually and even switching to the comfortable web uploader, the contributors didn’t increase.
I don’t know if uploaders will lose interest earlier if there are no graphs and other visualizations for showing the values.
For me it would be: “I take the effort to receive, read and upload the CW beacon, and you show me the decoded beacon values nicely displayed.”
If time is the problem, also I could assist you or even take over this part of the dashboard.