I had exactly this with the a few devices, after repairing the info was proper populated. Note; the trick is to not save the device if info is not correct.
Thanks! I should have 10x of the Xiaomi/Aquara sensors this afternoon to play with (if delivered on time)...
I'll see if they like my Ikea Tradfri outlets I put in just for their pleasure. lol
Interesting, at least it's not related to the sensor but something during pairing.
Maybe that's because now I've paired it over a Tradfri outlet repeater instead other ones were directly to the hub?
Seems anyway that it's still working properly, it's just a minor graphic issue.
But as @mike.maxwell suggested can you check the version number? I just did a more detailed look into your screenshot and my errors although similar were not as yours, mine often would leave fields blank or truncated
Now I'd prefer to don't remove the one that it's already fixed in position, but other ones from the same order have: MCCGQ11LM 2016DP2461
You got the same message in all?
I'll try to pair another one now
Tried with another one, half a meter from the hub (so no repeaters in the middle) and I had the same result
Hmmm.
Not sure if it is the same issue to tbh.
I leave it with Mike
Only my leak sensors show this.
Personally, and no offense to anyone's sensibilities, I don't care as long as they work. And they do work perfectly. I test the leak sensors often and they respond as expected every time.
No problems on my side too, I was just asking because previously was fine.
Spot on...
Saw this also with mine. I could remove and repair them too and it would fix itself. But either way they always worked fine.
I just paired one of my new Xiaomi Aquara temp/humidity sensors. So far so good - it has reported in a few times. Time will tell, I guess.
In case there is interest it is: WSDCGQ11LM
Manufacturer is blank in details.
That's strange too because on mine the same humidity/temp sensors (paired around a month ago) have the right manufacturer (LUMI), but until they are working fine it doesn't matter..
Yes.
I wouldn't worry about it, though.
The only issue that could arise is that the correct device driver isn't chosen when the sensor is paired. The model / manufacturer data isn't used in any other ways for the door/window contact sensors or the leak sensors.
I believe what happens is that during the pairing process the value telling the hub the length the model text string is missed somehow, so extra "garbage" characters are picked up as part of the model name.
As other have suggested, you could try repairing the sensor if the "garbage" characters really really bother you, but nothing is "broken". The devices for the above screenshots have been connected and working just fine with my hub for over 8 months now.
Thank you, no worries on my side, just curious..
Not sure what is 'normal', but the one temp/humidity sensor I've paired so far has checked in ~20 times in the last hour... Actually 62 times, but each time it checks in there seem to be 3 Checkin events in the log within ~1 second.
Seems like a lot, but at least it is working. 
Are you talking about the custom checkin attribute events? All the Xiaomi/Aqara device drivers are set up to produce a checkin events every time any kind of message is received from the sensor.
Either way, the Xiaomi and Aqara Temp/Humidity sensors are hardware programmed to send reports when there's X amount of change in temperature / humidity (and pressure on the Aqara model). In my experience, the frequency of temp/humidity/pressure reports can vary wildly. This is just normal behavior for these sensors, and there is no way to change the frequency of reports nor the amount of change that is required before a report is generated.
For people who don't like their events list cluttered up by the additional checkin time/date stamp events, I am in the process of adding a preference setting to disable/enable them.
Yes, I was referring to the custom checkin events.
Not a big deal, but I would turn them off if there were an option. I was going to mod the driver and add a toggle (like I did for Konnect and a few other drivers), but won't bother if you already are planning it. 
Edit - Never mind, I already did it on my system - I just changed the checkin event line to a debug log, and removed the checkin ATTRIBUTE altogether.
