MQTT object_id vs default_entity_id warning

Configuration
1

I have manual created MQTT sensors and now get e.g.

The configuration for entity sensor.rasenmaher_modus_raw uses the deprecated option object_id to set the default entity id. Replace the "object_id": "rasenmaher_modus_raw" option with "default_entity_id": "sensor.rasenmaher_modus_raw" in your published discovery configuration to fix this issue or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4

They were created long time ago via:

      topic: homeassistant/sensor/rasenmaher_modus_raw/config
      retain: true
      payload: |
        {
          "state_topic": "automower/mower/mode",
          "name": "Rasenmäher Modus Raw",
          "unique_id": "unique_id_rasenmaher_modus_raw",
          "object_id": "rasenmaher_modus_raw",
          "icon": "mdi:state-machine",
          "device": {
              "identifiers": ["330x"],
              "name": "Husqvarna Automower 330x",
              "model": "330x",
              "manufacturer": "Husqvarna",
              "sw_version": "7.04.00"
          }
        }
    action: mqtt.publish

But this script is not running. First, I though it is a spook-kind warning about the content of this script ans I changed it, but warning remain.

Then I searched in my configs and entity registry but can’t find, where I can or have to adjust here.

I found only one related issue, but this was related to a real integration, which have been fixed.

Any hints/ideas?

2

Getting the same error, but specifically with my MQTT update entities. I’m currently researching a solution.

My error log entry:

Replace the "object_id": "bed_spot_2" option with "default_entity_id": "update.bed_spot_2" in your published discovery configuration to fix this issue

UPDATE

I run Z2M and MQTT in separate Docker containers on my NAS. Updating to the latest image solved my issues!