Figure out why checking robot.model.type fixes it being null

[oysand]

Describe the bug
When isar finished the mission the screen turned white and it complained that type was null. After reproducing it locally the following check #1659 was added during debugging and then the problem dissapeared.

To Reproduce
Steps to reproduce the behavior:

1. Connect to the dev database locally.
2. Revert Check if updated robot model is null #1659
3. Run a mission and observe what happens when the mission completes

Expected behavior
Would like some other fix than just doing an if check

Screenshots
If applicable, add screenshots to help explain your problem.

[oysand]

Connected to #1537

[oysand]

The if check never true, but checking the value makes the system investigate the value and stops it from being treated as null further down the line.

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.