This issue seems fixed in Airwave 8.2.0.2. From the release notes:
DE25333 Symptom: An issue is resolved where AirWave was processing incoming rogue data but not
correctly updating the AP database.
Scenario: In a previous releases of AirWave 8.2.x, rogue AP data was processed by AirWave
but not stored in the database, preventing rogue devices from correctly appearing in the
RAPIDs overview pages.