Hello Kevin,
the problem you describe may be an issue with the device, i.e. simply the device is reporting this error. I would turn on ned tracing for this device to check that.
I've looked at the yang model here revision 2019-07-01 and this value is in range but there is no default for this leaf. So its not purely a yang issue, but could be something like a mismatch between the capability of the device and what the model describes.
Realize I'm being a little vague here, but its hard to tell for sure from the info you posted.
You mention that you are not even using multicast. In that case a quick solution may be to exclude this yang module from the NED you use.
Best regards
Stefano