Wouldn't surprise me if it's related, given it doesn't appear that the repeater issue is an issue being reported by others.
Remember that there are two autopilot computer nodes - essentially two independent autopilot computers on the same board. The original idea was to run identical software on both nodes to provide redundancy - which would be needed for level 3 autonomy and higher, to ensure the car can continue safely if one AP node fails whilst AP is driving. However, the current software doesn't work that way - it runs different neural nets on each node. When an AP computer node crashes, the particular behviour you see will depend on which node crashed and very probably on the software version you are running. You sometimes get odd behaviour where some features work and others don't. e.g. you might find that some visualisations are present, and others aren't (e.g. can see other cars but not road markings).
You need to note times and dates of a few AP computer crashes and then raise a service request in the app. They can look at the logs and decide if they need to escalate it to engineering for further investigation. In my case I ultimately needed a new car computer. I should warn you that they had my car for about a week all in, including diagnosis, replacement and then getting the software installed and working properly on the new car computer.
EDIT: OTOH, may well be worth waiting for a few weeks to see if it's a software glitch which is fixed by 2024.6 or 2024.8 or whatever comes next.
roy
. It would be really useful to suggest an arrival % when on a trip to an unfamiliar location.
