The default presentation is generated based on the components and capabilities defined in the profile. From what I’ve seen, a profile that lacks a custom-defined vid works equally well regardless of whether the profile has one or many components.
Getting back on topic:
The device has been functioning properly in routines since post 3. No changes to the presentation are necessary.
The question is what changed between post 1 and post 3 to fix the issue. It could be something that @blueyetisoftware did while troubleshooting, such as re-packaging the driver. Or it could be cloud delays, possibly related to what was going on in that timeframe.