Hey @IvanAllegreMM-9898​ 

I feel like we are friends at this point bonding over GO Focus! Thank you for sharing this — the detail you have provided about the intermittent nature and your test setup is really helpful for diagnosing what is going on! 

The message "No sensor items selected for display" appears in the event viewer when the video event does not have sensor data (telemetry channels like speed, acceleration, etc.) associated with it. This is a separate layer from the video footage itself — the event viewer shows both the video clip and a synced data panel, and when no sensor data has been linked to a specific event, you will see that message in the data panel even if the video played back correctly.

 Why this happens intermittently with custom rules

 With GO FOCUS PLUS, video events have two components that need to come together:

 1. The video clip captured by the camera

 2. The sensor/telemetry data from the GO device linked to that same event

 For built-in rules, these are tightly integrated by default. With custom rules, there is an additional configuration step that can sometimes be missed or inconsistently applied — the Media Upload Settings on the rule itself.

 A few things worth checking:

 1. Media Upload Settings on your custom rule — In MyGeotab, go to Groups & Rules → Rules, find your custom rule, and click the Camera icon. Confirm that:

  - The Media type is set to Video or Snapshot and video (not None)

  - Pre- and post-event capture durations are configured

 2. Sensor data selection in the event viewer — When you open a video event, look for a sensor data selector or gear icon in the data panel. It is possible the panel is simply not configured to display any channels for that event  view. Selecting channels like Speed or Acceleration there may resolve what you are seeing.

 3. Timing of the event — If you are viewing the event very shortly after it was triggered, the sensor data pipeline may not have caught up yet. Try revisiting the same event a few minutes later to see if the data appears.

The 50/50 split you are describing is an interesting clue — it could suggest  the rule is occasionally firing in a way that captures video but misses the sensor data linkage (for example, events at trip boundaries or when connectivity between the camera and GO device is briefly interrupted).

If checking the above does not resolve it, it would be worth raising this with our support team with the specific rule configuration and a few example event timestamps. This very well could just be a bug we need to fix

Please let us know if you have any other questions. We are here to help.

Have a great day!

Eishi FUN