InfluxDB - no way of configuring the integration except for `configuration.yaml`

[husjon]

The problem

Since the 2026 release and with the deprecation of configuring InfluxDB via the configuration.yaml file, there are currently no way of configuring the integration once it's set up, I would currently need to remove the integration, then set it up all over again just to change a single parameter, for example adding an exclusion / inclusion.

With the configuration.yaml setup for the integration ending support in the 2026.9 release, this really needs to be fixed or the deprecation timeframe should extend/removed entirely until an actual solution is in place.
According to the integration page over 6% of all instances use the integration which is quite a few.

No option to configure the integration and clicking the add entry gives me the message that "Only one InfluxdB instance can be configured"

What version of Home Assistant Core has the issue?

core-2026.3.2

What was the last working version of Home Assistant Core?

core-2025

What type of installation are you running?

Home Assistant OS

Integration causing the issue

InfluxDB

Link to integration documentation on our website

https://www.home-assistant.io/integrations/influxdb/

Diagnostics information

No response

Example YAML snippet

Example configuration I am using as of today, where if I wanted to change any of the parameters, I would need to set up the entire integration again from scratch.

influxdb:
  api_version: 2
  ssl: true
  host: !secret influxdb_host
  port: 443
  token: !secret influxdb
  organization: !secret influxdb_org
  bucket: homeassistant
  tags:
    source: homeassistant
  tags_attributes:
    - friendly_name
  default_measurement: units
  exclude:
    entities:
      - zone.home
    # entity_globs:
    #   - "*.0x[a-f]*_*" # ignore all Zigbee2MQTT devices that have not had their name set, like `0xdeadbeef12345678`
    domains:
      - persistent_notification
      - person
  include:
    domains:
      - sensor
      - binary_sensor
      - sun
    entities:
      - weather.home

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @mdegat01, @RobBie1221, mind taking a look at this issue as it has been labeled with an integration (influxdb) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of influxdb can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign influxdb Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@husjon Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20influxdb%22%20
_{^{(message by IssueContext)}}

---

influxdb documentation
influxdb source
_{^{(message by IssueLinks)}}

[mdegat01]

With the configuration.yaml setup for the integration ending support in the 2026.9 release, this really needs to be fixed or the deprecation timeframe should extend/removed entirely until an actual solution is in place.

That's not what the warning says though. It says specifically that the keys related to connection details are no longer supported in YAML. So that's things like host, api_version, ssl, etc. Essentially all the config options for where is your service hosted and how does HA talk to it. Those are UI configurable only. And I would imagine those aren't changing much at all unless you're frequently changing the deployment of the InfluxDB service.

then set it up all over again just to change a single parameter, for example adding an exclusion / inclusion.

The warning listed this specific example as an exclusion. As something that isn't set up in the UI and is still configured in YAML.

Does this warning not match the behavior you're seeing? Is the entire integration UI-configurable only? If so I guess that's the bug here.

[husjon]

Ok, so if I understand it correctly only the host related fields are migrated and not things like which entities etc are going to be excluded etc (these will still stay in the configuration.yaml file?

---

Those are UI configurable only. And I would imagine those aren't changing much at all unless you're frequently changing the deployment of the InfluxDB service.

Well, I guess host / port / organization might not change often, but for example the token / password might change on a regular basis (say 3-6 months) depending on setup etc.
This is currently not possible once the integration has been set up, the only way I can get to change the token used in my case is to remove and set it up again.

Once I do remove the integation and set it up again, I do see the following (once I select InfluxDB 2.0/3.0), but I would argue these fields should still be possible to change after it has been initialized and currently there are no way of doing so.

[RobBie1221]

Re-configuration via UI will be available in next home assistant release.

[husjon]

Ok, that's good. I just wish it was already in place or some message about it coming before / in the deprecation message.

I understand now that I did indeed misunderstand the warning.
The first part of the message reads as if the entire option for configuring the integration in the yaml file is being removed, even the first paragraph does do, the warning (in norwegian) makes it quite urgent too (reads as, after 2026.9 it will be final).
When we then find that the configuration cannot be done yet in the UI, it just enhances the likelihood of misunderstanding.

[ibtissamassifar-droid]

Thanks for the detailed report very helpful

…

On Tue, Mar 17, 2026, 10:46 AM Jon Erling Hustadnes < ***@***.***> wrote: *husjon* left a comment (home-assistant/core#165712) <#165712 (comment)> Ok, that's good. I just wish it was already in place or some message about it coming before the deprecation message. I understand now that I did indeed misunderstand the warning. The first part of the message reads as if the entire option for configuring the integration in the yaml file is being removed, even the first paragraph does do, when we then find that the configuration cannot be done yet in the UI, it enhances the likelihood of misunderstanding. image.png (view on web) <https://github.com/user-attachments/assets/e2b5595f-77b9-4242-92a0-aba1fbef1233> — Reply to this email directly, view it on GitHub <#165712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7HZ64UCDXV4FATEVISQQ3L4REUG3AVCNFSM6AAAAACWTWO4MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANZUGAZDGOJZGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kub3let]

@RobBie1221 will it restore all the configuration options like measurement_attr etc. ?

For me the upgrade completely broke influx since all the entities have changed now, need to rollback homeassistant.

[RobBie1221]

Please read the docs. Thinks like measurement_attr still need to be configured via yaml.

Only communication parameters are merged to the UI. Again, the docs mention all keys under the 'options' section which still need to be configured via yaml.

Nothing has changed that would break something.

[kub3let]

Ah thanks, my bad.

[dotdoom]

I've tried a few different approaches but I can't get the sensors to work without having host/password etc. I'm using influxdb1 and my WRITE config is similar to OPs, my sensors (READ) currently look like this:

sensor:
  - platform: influxdb
    host: !secret influxdb_host
    port: 8086
    username: home_assistant
    password: !secret influxdb_home_assistant_password

    # Influxdb sensors are updated once per minute by default.
    queries:
      - name: "NOHIST Influxdb ping reply"
        measurement: s
        where: >-
          "entity_id"::tag = 'nohist_influxdb_ping_start'
        group_function: last
        unit_of_measurement: s

      - name: "NAS power"
        database: telegraf
        measurement: ipmi_sensor
        where: >-
          "name"::tag = 'instantaneous_power_reading' AND
          "host"::tag = 'nas.home.arpa'
        group_function: last
        unit_of_measurement: W

If I remove host/port/username/password, the entities are just gone from HA after a restart.

[RobBie1221]

Sensor platform has not been migrated to the UI. You also don't get a deprecation warning off those. If you look in the docs, you can see that under sensor the keys for host/password are still there.

[kabukimandelux]

With the update and depreciation warning I also removed my influx config from donfiguration.yaml.
I just noticed my data is missing in influx since this day.

I readded all my Include / exclude yaml configs, except the token/host/buckets... ( which are now UI configured) and all works fine again.

Just a thumbs up for other people landing here with the same problem.

Continue the great work!

[moritzthecat]

I also must admit having overlooked / percieved less of an imact reading the release notes ... somehow.
To be honest update frequency is much too high and I wish there could be like stable and less frequent update path when features have been completly implemented. Also I am aware of dependecies that may not allow for this approach in every case though.

Anyway I was totally confused about what to do now after updating to 2026.3.4 reading this warning and how to configure my external Influx2.x instance now in GUI. Now I will wait for 2026.4 release and spend time then to better understand.

Thanx @RobBie1221 for clarification

Re-configuration via UI will be available in next home assistant release.

Appreciated, If this clarification woud have been added to the issued warning.

Having read again through the warning I am still not clear though if migration went well, as I would expect credentials have been imported as well.

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.

In my case of Influx2.x the GUI shows only the IP address of the Influx2.x instance. And no way to add the credentials.