Warning "The InfluxDB YAML configuration is being removed"

Configuration
1

After latest update got following warning - anyone knows how to configure InfluxDB connection going forward with this changes in configuration.yaml ?

The InfluxDB YAML configuration is being removed
This stops working in version 2026.9.0. Please address before upgrading.

Configuring InfluxDB connection settings using YAML is being removed. Your existing YAML connection configuration has been imported into the UI automatically.

Remove the influxdb connection and authentication keys from your configuration.yaml file and restart Home Assistant to fix this issue. Other options like include, exclude, and tags remain in YAML for now.

The following keys should be removed:

1 Like
2

Got the same.
Ripped out the YAML and attempted to configure from the GUI, couldnā€™t get data to pass at all. Gave up pretty quick and slammed it back in my yaml.
Hopefully I am just doing it wrong; I depend on this pretty heavily.

3

Where do you see/edit that stuff in UI?

3 Likes
4

I got this issue also.

5

So it is a ā€œAPPā€ formally known as Add-On, can you capture the setup screen and past using the graphics icon? Trying to see what is missing between the UI and using YAML documentation and this error message.

P.S. Love it when they donā€™t update the documentation before making such a change go live

2 Likes
6

Some of your influxdb config has been imported into the gui (Settings ā†’ Devices & Services ā†’ Influxdb).

Comment out the configuration options shown in the repair message. In your case:

Leave all other influxdb config as is.

Restart.

3 Likes
7

Yes, I have done this (host, username etc.) and the repair message disappeared after restart. I just wonder where I could view and edit those imported parameters in the GUI now? I would expect it in the three-dots-menu in the new InfluxDB-integration, but there is nothing, see screenshot. Pretty poor user experience. Or maybe in the InfluxDB-ā€œAppā€-Configuration? There is the port, but nothing elseā€¦

screenshot2
screenshot21759Ɨ797 38 KB

1 Like
8

What about people using HA from docker and infuxdb in another docker? where to configure lines that will not work after 2026.9.0?

9

I had to roll back to the previous full release when testing the beta release (due to an unrelated issue) but I could not find anywhere this information was available when I was running the beta.

I assume the the GUI version is still under development and reconfiguration will come later. You could ask in the release notes topic 2026.3: A clean sweep or it may have been mentioned in the release livestream. I have not had a chance to watch that yet.

Exactly the same as for people running HAOS. In your configuration.yaml file.

10

Where to see the values in the GUI? Before deleting something and push such message after an update, it should be clear where to find what.

2 Likes
11

Read the post directly above yours.

12

So, my influxdb was stopped (manually by me). Then after update, if i try to start the influxdb ā€˜appā€™ i get:

##

Failed to start add-on

An unknown error occurred with addon a0d7b954_influxdb. Check supervisor logs for details (check with 'ha supervisor logs')

And this in supervisor logs:

2026-03-05 14:31:26.414 ERROR (MainThread) [supervisor.docker.manager] Image ghcr.io/hassio-addons/influxdb/amd64:5.0.2 does not exist
2026-03-05 14:31:26.425 ERROR (MainThread) [supervisor.addons.addon] Could not start container for addon a0d7b954_influxdb: Image ghcr.io/hassio-addons/influxdb/amd64:5.0.2 does not exist

The configuration wasnt imported to gui and i cant use the yaml one neither, so right now i am not able to use it.

Trying to add the integration through the UI asks for stuff that i dont know and isnt present in my yaml, like organization, bucket, api tokenā€¦

I am lost here.

Edit:
I can start the ā€˜appā€™ now, probably was a github issue.
But i am still not able to add the integration trough the UI.

13

I got it done. I didnt know what version I had of influxdb, so in the command line:

docker exec -it addon_a0d7b954_influxdb bash

And then which influxd, then

root@a0d7b954-influxdb:/# /usr/bin/influxd version

InfluxDB v1.8.10 (git: 1.8 688e697c51fd)

My version was 1 and after submiting the data of my yaml is working.

I left this in configuration.yaml

influxdb:
  default_measurement: state
  include: # exclude everything but this.
    entities:
      - sensor.example
      - sensor.example2
      - ...
14

Iā€™ve just installed VM for the first time and just crashed right into this. Great first user experience ā€¦

Iā€™m VERY confused about this to be honest. Do I need to have the influxDb App installed as well as VM?

15

Hi,
I get the same warning. Not sure what to do. My HA systems runs on a VM on a Synology NAS with a very extensive InfuxDB setup (Inclusion and exclusion of sensors) and a MariaDb setup. Who can help me out?

influxdb:
host: xxx.xxx.xxx.xx
port: 8086
database: homeassistant
username: xxxxxxxx
password: xxxxxxx

# Recommended stability options
max_retries: 3
default_measurement: state
ssl: false
verify_ssl: false

# Useful for filtering in Grafana / queries
tags:
instance: home
source: hass
tags_attributes:
- friendly_name
- unit_of_measurement

include:
domains:
  - sensor
  - binary_sensor
  - switch
  - light
  - climate
  - cover
  - input_boolean
  - input_number
  - input_select
  - device_tracker

exclude:
domains:
  - camera
  - updater

entity_globs:

  # Signal/quality/uptime etc. (noise)
  - sensor.*_rssi
  - sensor.*_linkquality
  - sensor.*_lqi
  - sensor.*_signal_strength
  - sensor.*_last_seen
  - sensor.*_uptime
  - sensor.*_ping

  # Electrical "instant" sensors (high frequency / many writes)
  - sensor.*_current
  - sensor.*_voltage
  - sensor.*_frequency

entities:
  # time_date platform
  - sensor.time
  - sensor.date
  - sensor.date_time
16

I have explained it here: Warning "The InfluxDB YAML configuration is being removed" - #6 by tom_l

17

I reduced the configuration.yaml to this part but I do not get rid of the initial warning/repair message.

influxdb:
  max_retries: 3
  default_measurement: state
  include:
    domains:
       - metervalues
       - FHEMPowerLog
       - FHEMTemperatureHumidity
       - PV
  tags:
    instance: prod
    source: hass

All keyword mentioned are removed. I reloaded and restarted from the GUI.

Christian

18

Thatā€™s odd. The reload would not do anything but the restart should clear the issue.

Double check your config (did you save the changes?) and restart again. Also clear your web browser cache.

19

+1 same problem as otherā€™s have described above. After the auto-import I can no longer change the host - thereā€™s no option in the UI. Very confusing.

20