Is there an error message in either the online Authentication Log in the Admin Panel or in the Authentication Proxy’s local log that gives a reason for not accepting the YubiKey OTP?
You did import the YubiKey OTP token as a hardware token to assign to the user performing the test? If a user enrolls a YubiKey that supports both FIDO2 and OTP as a Duo WebAuthn security key it still needs to be imported separately for OTP use.
Does the effective authentication methods policy for the RADIUS application and given user permit use of hardware tokens?
If all those have been checked, is it possible the authenticating RADIUS device or application restricts the length of the user-password attribute (not RFC 2865 compliant) so it can’t accommodate the 44-char YubiKey OTP??