The fix is definitely that simple, and model 3/y doesn’t have (or hasn’t yet had) that issue, so they must have solved it. I think it’s unclear if this issue is still happening with recent software since I can’t find any reports about this message as of recent.