Skip to content

Troubleshooting guide

This page explains how to diagnose and fix dashboard problems with data that does not update or display, performance, and individual components.

Dashboard does not load

A dashboard that fails to load, or that cannot be saved, has a validation error, because Profinity does not load an invalid dashboard. Open Edit Dashboard from the title bar, read the Schema validation issues list, which names each problem, and correct each entry. The usual causes are a missing colon, wrong indentation, an invalid property name, or an absent required property. The editor blocks SAVE while any entry remains, so save once the list is empty and close the editor to see the result.

A dashboard whose saved layout no longer matches the schema shows the message "This dashboard no longer matches the schema", with the buttons Reset from Template and View Logs.

Warning

Reset from Template replaces the dashboard with the latest template and loses every customisation, so use it only when the dashboard is not needed.

Data binding issues

Data not updating

Components that show static values, or do not update when the data changes, usually have a source that does not match a tag. Check the following in the Tag Explorer:

  • The path in the binding matches the tag path exactly, including a leading / for a tag of another component.
  • The tag exists and shows a current value with a good quality flag.

For a DBC/ tag, check that the CAN database (DBC) file defines the signal and that the component is connected and sending data. If the tag shows a value but the component does not, check that toType, when it is set, matches the type that the tag publishes. A number treated as a string displays, but it does not drive a lamp or a chart.

To separate a binding fault from a data fault, temporarily replace the binding with a static value. If the readout shows it, the readout displays correctly and the fault is in the binding or the data. Add the binding back one element at a time to find the element that fails.

# Replace the binding with a static value to test the readout
dashboard:
  items:
    - row:
        items:
          - readouts:
              items:
                - readout:
                    label: "TEST"
                    value: 42.5

# Verify the source path matches the tag path in the Tag Explorer
dashboard:
  items:
    - row:
        items:
          - readouts:
              items:
                - readout:
                    label: "Bus Voltage"
                    bind:
                      - target: value
                        source: DBC/BusMeasurement/BusVoltage
                        toType: number

Binding to logged data not working

A logged binding that returns no data usually means that data logging is not configured and enabled for the profile, or that the time range is invalid. For data logging, refer to How to configure data logging. Set timeRangeStart in the past (for example -10m) and timeRangeStop after it, where 0m means now. An invalid time range or aggregation window makes the binding return no data. Start with the simple binding in this example, and add the aggregation back once it returns data.

# Start with a simple logged data binding
dashboard:
  items:
    - row:
        items:
          - chart:
              type: line
              bind:
                - target: value
                  source: DBC/Temperature/Value
                  store: logged
                  timeRangeStart: "-10m"
                  timeRangeStop: "0m"
                  aggregationWindow: "1m"
                  aggregationFunction: "mean"

Type conversion errors

Values that display incorrectly are usually the result of a toType that does not suit the data, such as toType: number on a non-numeric tag. Components convert most targets themselves, so set toType only where a value displays incorrectly: boolean for a flag bound to enabled or visible, and number for a numeric value.

# For boolean values
dashboard:
  items:
    - row:
        items:
          - lamps:
              items:
                - lampgroup:
                    items:
                      - lamp:
                          color: "green"
                          value: 1
                          label: "Bus current limit"
                          bind:
                            - target: enabled
                              source: DBC/Status/LimitBusCurrent
                              toType: boolean

# For numeric values
dashboard:
  items:
    - row:
        items:
          - readouts:
              items:
                - readout:
                    label: "Temperature"
                    bind:
                      - target: value
                        source: DBC/Temperature/Value
                        toType: number

Charts not rendering

A chart that appears blank shows only the latest value unless its binding sets seriesMode: timeSeries, so add the series settings first. Then check in the Tag Explorer that the tag has a current value. For logged data, check that the time range is valid. A chart that is given static data in its value property, rather than a binding, needs that data to have labels and datasets.

# For time series data
dashboard:
  items:
    - row:
        items:
          - chart:
              type: line
              bind:
                - target: value
                  source: DBC/Data/Value
                  seriesMode: timeSeries
                  timeRangeStart: "-5m"
                  timeRangeStop: "0m"

# For structured data
dashboard:
  items:
    - row:
        items:
          - chart:
              type: bar
              value:
                labels: ["Jan", "Feb", "Mar"]
                datasets:
                  - label: "Sales"
                    data: [10, 20, 30]

Performance

A dashboard that loads slowly or becomes unresponsive usually holds many components or charts with very frequent updates. Place unused sections in an accordion or tabs. Set refreshInterval (in milliseconds, minimum 1000) on a chart to poll it at a fixed interval instead of updating it live.

# Poll the chart every second instead of updating it live
dashboard:
  items:
    - row:
        items:
          - chart:
              type: line
              refreshInterval: 1000
              bind:
                - target: value
                  source: DBC/Data/Value
                  seriesMode: timeSeries
                  timeRangeStart: "-5m"
                  timeRangeStop: "0m"

# Use accordions to hide unused sections
dashboard:
  items:
    - accordion:
        label: "Detailed Data"
        items:
          - row:
              items:
                - readouts:
                    items:
                      - readout:
                          label: "Value"
                          value: 0

Component-specific troubleshooting

Image does not appear

An icon or image that does not display is not being found. Check that the file exists in the images folder of the profile, that the filename matches exactly, including its case, and that the property holds the filename alone and not a full path. A profile image with the same name as a built-in image is never used, so rename it. For the accepted file types and the lookup order, refer to Store dashboard files in a profile.

Style has no effect

The web interface loads only profile.css from the styles folder of the profile, so import any other stylesheet from profile.css. The class named in the dashboard must match the one in the CSS exactly. A class on a readout item has no effect, so put it on the readouts element. For where the file goes, refer to Store dashboard files in a profile.

Pill values do not group

Each pillgroup must contain an items array, and each item must be wrapped in a value object.

Lamps do not light or change colour

An enabled binding must return 0 or 1 (or false or true), and a lamp that is greyed out has enabled set to false. A lamp bound to color takes the colour name that the binding returns, as described in Conditional styling. The value property of the lamp must be set, typically to 1.

Table shows no data or no highlighting

Check the following:

  • tableHeaders has the structure shown under Table header parameters.
  • Each accessorKey matches a data property name.
  • The data array is bound.

Highlighting needs numeric data values and threshold properties such as highlightAtOrBelow or highlightAtOrAbove.

Chart type is not supported or a time series chart does not update

The type property (not charttype) must be one of bar, line, radar, doughnut, pie, polarArea, bubble or scatter. A time series chart needs seriesMode: timeSeries in its binding, or store: logged with data logging enabled, and a suitable time range.

Image regions are not clickable or data values are missing

A region needs x, y, width and height values, which are percentages of the image size. It also needs an action that is an object with an invoke value of Navigate, Component, System or Endpoint. The action needs a target when invoke is Navigate, or an actionId when invoke is Component or System. A data value that does not display needs a correct bind, a suitable displayType, and maxValue for the graph display type.

HTML content does not render

The HTML must be valid and properly escaped in YAML, and multi-line content uses a literal block (| or >). The HTML sanitiser removes the script, embed, object, form, input and button elements, so content that depends on them does not appear. Images in HTML use the full URL path, and the file must exist in the images folder of the profile. A stylesheet cannot be linked from the HTML, because the sanitiser removes a link element. Style rules go in profile.css in the styles folder, as described in Store dashboard files in a profile.

Getting more help

To find a problem early:

If the problem persists, contact Prohelion through the Prohelion website and include the YAML configuration, any error messages, and the expected and actual behaviour.