-
-
Notifications
You must be signed in to change notification settings - Fork 80
Closed
Description
The problem
The configuration for entity xxx uses the deprecated option object_id to set the default entity id. Replace the "object_id": "xxx" option with "default_entity_id": "xxx" 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.
NetDaemon generated entities generate these warnings in the home assistant logs:
The configuration for entity switch.flexilights_terrace uses the deprecated option `object_id` to set the default entity id. Replace the `"object_id": "flexilights_terrace"` option with `"default_entity_id": "switch.flexilights_terrace"` 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
Environment
Since home assistant 2025.10, not really related to a NetDaemon release
- NetDaemon release with the issue: probably all of them
- Operating environment (Home assistant Add-on/Docker/Dev setup): Docker
Link to or paste code that causes the issue
string SENSOR_CONSUMER_STARTED_AT = "sensor.consumer_started_at";
var startedAtCreationOptions = new EntityCreationOptions(UniqueId: SENSOR_CONSUMER_STARTED_AT, Name: $"Consumer {Name} - Started at", DeviceClass: "timestamp", Persist: true);
var startedAtOptions = new EntityOptions { Icon = "mdi:calendar-start-outline", Device = Device };
await Context.MqttEntityManager.CreateAsync(SENSOR_CONSUMER_STARTED_AT, startedAtCreationOptions, startedAtOptions);
Traceback/Error logs
No errors in NetDaemon, just a depreciation warning in Home assistant.
Metadata
Metadata
Assignees
Labels
No labels