Could not find item ... in registry

I am using Openhab 3.4.3 on Armbian on a Orangepi3 LTS. I am running Control a water heater and ground source heat pump based on cheap hours of spot priced electricity - #152 by masipila on it and it just works. However, I get these errors in the log despite the code running flawlessly and all the listed items being visible and usable from influxdb. What are these and how do I remove them?

2023-05-09 21:19:28.305 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_TotalCloudCover' in registry
2023-05-09 21:19:28.306 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_temperature' in registry
2023-05-09 21:19:28.307 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_TotalCloudCover' in registry
2023-05-09 21:19:28.308 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry
2023-05-09 21:19:28.308 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_temperature' in registry
2023-05-09 21:19:28.308 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_TotalCloudCover' in registry
2023-05-09 21:19:28.310 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry
2023-05-09 21:19:28.310 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_TotalCloudCover' in registry
2023-05-09 21:19:28.310 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_temperature' in registry
2023-05-09 21:19:28.312 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry
2023-05-09 21:19:28.313 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_temperature' in registry
2023-05-09 21:19:28.314 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry
2023-05-09 21:19:28.315 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_temperature' in registry
2023-05-09 21:19:28.316 [INFO ] [b.internal.InfluxDBStateConvertUtils] - Could not find item 'fmi_forecast_WindSpeedMS' in registry

Is there a particular time when you see these errors (e.g. at system startup)?

The registry it mentions is the Item registry and the error means that at the time it checked, the Item didn’t exist. Knowing a bit more about the timing can maybe point at a cause, or at least a path to a cause.

Not really. They come in bursts every so often during the day.

They don’t happen to correspond to editing .items files or anything like that? The only reason I can think of that the InfluxDB add-on would be looking for Items in the registry is to do a restoreOnStartup, which happens during OH start and for file based .items files when the file is reloaded after a change.

Just found out that the errors appear when I refresh my graph:

config:
  chartType: day
  label: Spotsähkön hinta ja ohjaus II
  order: "-15"
  sidebar: true
slots:
  grid:
    - component: oh-chart-grid
      config: {}
  legend:
    - component: oh-chart-legend
      config:
        orient: horizontal
        show: true
  series:
    - component: oh-time-series
      config:
        areaStyle:
          opacity: "0.4"
        gridIndex: 0
        item: spot_price
        markLine:
          data:
            - label:
                distance: -150
              name: Avg
              type: average
        name: Sähkön tuntihinta
        step: end
        type: line
        xAxisIndex: 0
        yAxisIndex: 0
    - component: oh-time-series
      config:
        areaStyle:
          opacity: "0.4"
        gridIndex: 0
        item: nibe1245ReleStatusNumber
        name: Nibe 1245 releen tila
        step: end
        type: line
        xAxisIndex: 0
        yAxisIndex: 2
    - component: oh-time-series
      config:
        areaStyle:
          opacity: "0.4"
        gridIndex: 0
        item: Nibe1245StatusNumber
        name: Nibe 1245 pumpun tila
        step: end
        type: line
        xAxisIndex: 0
        yAxisIndex: 2
    - component: oh-time-series
      config:
        areaStyle:
          opacity: "0.4"
        color: orange
        gridIndex: 0
        item: nibe_control
        name: Nibe 1245 ohjaus
        step: end
        type: line
        xAxisIndex: 0
        yAxisIndex: 2
    - component: oh-time-series
      config:
        gridIndex: 0
        item: fmi_forecast_WindSpeedMS
        markLine:
          data:
            - label:
                distance: -100
              name: Avg
              type: average
        name: Tuuliennuste
        type: line
        xAxisIndex: 0
        yAxisIndex: 1
    - component: oh-time-series
      config:
        gridIndex: 0
        item: fmi_forecast_TotalCloudCover
        markLine:
          data:
            - label:
                distance: -100
              name: Avg
              type: average
        name: Pilvisyysennuste
        type: line
        xAxisIndex: 0
        yAxisIndex: 1
    - component: oh-time-series
      config:
        gridIndex: 0
        item: fmi_forecast_temperature
        markLine:
          data:
            - label:
                distance: -100
              name: Avg
              type: average
        name: Lämpötilaennuste
        type: line
        xAxisIndex: 0
        yAxisIndex: 1
    - component: oh-time-series
      config:
        gridIndex: 0
        item: aaroninHuoneenAnturi
        name: Aaronin MH lämpötila
        type: line
        xAxisIndex: 0
        yAxisIndex: 1
  tooltip:
    - component: oh-chart-tooltip
      config:
        orient: horizontal
        show: true
  xAxis:
    - component: oh-time-axis
      config:
        gridIndex: 0
  yAxis:
    - component: oh-value-axis
      config:
        gridIndex: 0
    - component: oh-value-axis
      config:
        gridIndex: 0
        max: "100"
        splitLine:
          show: false
    - component: oh-value-axis
      config:
        gridIndex: 0
        max: "5"
        min: "0"
        show: false

The graph works right, though.