That usually represents a configuration fail at the time of pairing of the device. Usually just removing and repairing it again will fix it. It’s unfortunately pretty common. I know Mike Maxwell has run into it with a brand-new device.
If it’s a real report because a variable load, there are some device handler changes you can make so you can parameterize the reporting interval:
I think somebody was going to submit that as a pull request for the official device handler. @tgauchat might know if that was actually done.