info._connectionStatus" and "info._online" have no existing objects

[Schattenruf]

!!! Before you start !!!

• [ x] I have verified that there is not already an issue with the same problem
• [x ] This is really a bug of current code, not an enhancement request (f.e. adding support for a new device type). There is a dedicated template for feature-requests.

Describe the bug
I have one ESPHome Device. It is recognized by the Adapter and gets all the states. After the initialization it throws an error that abx.info._connectionStatus and _Online are not present.

The interesting part is, that they were created in the first batch but deleted after the device has been implemented. Log attached.

To Reproduce
Steps to reproduce the behavior:

1. Start the Adapter set it to debug mode for logging
2. Add the new device
3. Wait until initlaization is complete

Minimal! Yaml config to reproduce.
Keep all that is required to copy-paste, compile, flash and reproduce the issue - but try to remove as much as possible that is not relevant to this issue!
Just an example, insert you own yaml!:

  name: ledbrickhome-16ch-64b6dc
  friendly_name: LEDBrickHome
  project_name: SenseAtHome.ledbrickhome-16ch
  project_version: '1.0'
  hidden_ssid: 'false'

esphome:
  name: ${name}
  name_add_mac_suffix: false
  project:
    name: ${project_name}
    version: ${project_version}

esp32:
  board: esp32dev
  framework:
    type: arduino
    version: recommended

logger:

api:

ota:
- platform: esphome

wifi:
  fast_connect: ${hidden_ssid}
  ap: {}

captive_portal:

improv_serial:

esp32_improv:
  authorizer: none

dashboard_import:
  package_import_url: github://AlexCPU/LEDBrickHome/Code/16ch-v1.yaml@main
  import_full_config: true

binary_sensor:
- platform: status
  name: ${friendly_name} Status

sensor:
- platform: uptime
  name: ${friendly_name} Uptime

button:
- platform: restart
  id: restart_button
  name: ${friendly_name} Restart
- platform: factory_reset
  name: Restart with Factory Default Settings

time:
- platform: sntp

switch:
- platform: factory_reset
  name: Factory Reset

text_sensor:
- platform: wifi_info
  ip_address:
    name: ${friendly_name} IP Address
    disabled_by_default: true

light:
# Details for each of the outputs.
# see https://esphome.io/components/light/index.html#light-effects for configuration
# of light effects

# Group 1:
# to use RGB light, uncomment it's section and comment the monochromatic lights
- platform: monochromatic
  name: Channel 1
  output: output_ch1
  gamma_correct: 1.0
  effects:
  - pulse:
  - pulse:
          name: "Fast Pulse"
          transition_length: 0.5s
          update_interval: 0.5s
          min_brightness: 0%
          max_brightness: 100%
  - pulse:
          name: "Slow Pulse"
          transition_length: 500ms
          update_interval: 2s
  - pulse:
          name: "Asymmetrical Pulse"
          transition_length:
            on_length: 1s
            off_length: 500ms
          min_brightness: 50%
          max_brightness: 75%
          update_interval: 1.5s
  - flicker:
          name: Flicker
          alpha: 95%
          intensity: 5%
  - strobe:

# The output definitions should not need to be changed
output:
- platform: ledc
  pin: GPIO25
  id: output_ch1
  frequency: 500 Hz

Expected behavior
That this info block does not get deleted or that the adapter does not throw an error because of this missing piece.

Logs (as screenshot and in text-form)
The cleanup purges these states completely at 2026-04-27 10:43:20.600. After that those states remain in:

And then those errors follow.

Log;

esphome.0	2026-04-27 10:44:10.328	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:44:10.327	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:44:05.700	debug	Create_state called for : 04830864B6DC.Sensor.1197691501.state with value : 1981
esphome.0	2026-04-27 10:44:05.700	debug	Value "1981" for name "[object Object]" after function modify with method "round(0)"
esphome.0	2026-04-27 10:44:05.700	debug	Function modify with method "round(0)" and value "1980.6610107421875"
esphome.0	2026-04-27 10:44:05.700	debug	Value "1980.6610107421875" for name "[object Object]" before function modify with method "round(0)"
esphome.0	2026-04-27 10:44:05.700	debug	[entityStateData] {"key":1197691501,"state":1980.6610107421875,"missingState":false,"deviceId":0}
esphome.0	2026-04-27 10:44:05.700	debug	[entityStateConfig] {"config":{"objectId":"ledbrickhome_uptime","key":1197691501,"name":"LEDBrickHome Uptime","icon":"mdi:timer-outline","unitOfMeasurement":"s","accuracyDecimals":0,"forceUpdate":false,"deviceClass":"duration","stateClass":2,"legacyLastResetType":0,"disabledByDefault":false,"entityCategory":2,"deviceId":0},"name":"LEDBrickHome Uptime","type":"Sensor","unit":"s"}
esphome.0	2026-04-27 10:44:05.699	debug	StateData: {"key":1197691501,"state":1980.6610107421875,"missingState":false,"deviceId":0}
esphome.0	2026-04-27 10:44:05.656	warn	State "esphome.0.04830864B6DC.info._connectionStatus" has no existing object, this might lead to an error in future versions
esphome.0	2026-04-27 10:44:05.655	debug	Create_state called for : 04830864B6DC.info._connectionStatus with value : connected
esphome.0	2026-04-27 10:44:05.613	warn	State "esphome.0.04830864B6DC.info._online" has no existing object, this might lead to an error in future versions
esphome.0	2026-04-27 10:44:05.610	debug	[ESPHome Device Message] 192.168.1.75 client log SensorStateResponse
esphome.0	2026-04-27 10:44:05.610	debug	Create_state called for : 04830864B6DC.info._online with value : true
esphome.0	2026-04-27 10:44:05.609	debug	[ESPHome Device Data] 192.168.1.75 client data � mRcG�'��D
esphome.0	2026-04-27 10:44:05.310	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:44:05.309	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:44:00.297	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:44:00.297	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:55.282	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:55.281	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:50.363	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:50.362	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:45.342	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:45.341	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:40.332	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:40.331	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:35.307	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:35.306	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:30.289	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:30.288	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:25.272	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:25.271	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:23.984	debug	[ESPHome - Console] 2026-04-27 10:43:23,984 INFO Started dashboard event loop
esphome.0	2026-04-27 10:43:23.983	debug	[ESPHome - Console] 2026-04-27 10:43:23,982 INFO 101 GET /events (192.168.1.28) 0.89ms
esphome.0	2026-04-27 10:43:20.600	debug	[objectCleanup] Unknown Channel found, delete esphome.0.04830864B6DC.info
esphome.0	2026-04-27 10:43:20.578	debug	[objectCleanup] Starting channel and state cleanup for ledbrickhome-16ch-64b6dc | 192.168.1.75
esphome.0	2026-04-27 10:43:20.356	debug	[ESPHome Device Message] 192.168.1.75 client log PingResponse
esphome.0	2026-04-27 10:43:20.356	debug	[ESPHome Device Data] 192.168.1.75 client data �
esphome.0	2026-04-27 10:43:17.053	debug	Create_state called for : 04830864B6DC.info.zwaveHomeId with value : 0
esphome.0	2026-04-27 10:43:17.053	debug	create id 04830864B6DC.info.zwaveHomeId with value 0 and name zwaveHomeId
esphome.0	2026-04-27 10:43:17.002	debug	Create_state called for : 04830864B6DC.info.zwaveProxyFeatureFlags with value : 0
esphome.0	2026-04-27 10:43:17.002	debug	create id 04830864B6DC.info.zwaveProxyFeatureFlags with value 0 and name zwaveProxyFeatureFlags
esphome.0	2026-04-27 10:43:16.997	warn	Object esphome.0.04830864B6DC.info.area is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, json This will throw an error up from js-controller version 7.0.0!
esphome.0	2026-04-27 10:43:16.990	warn	Object 04830864B6DC.info.area is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, json This will throw an error up from js-controller version 7.0.0!
esphome.0	2026-04-27 10:43:16.990	debug	Create_state called for : 04830864B6DC.info.area with value : undefined
esphome.0	2026-04-27 10:43:16.990	debug	create id 04830864B6DC.info.area with value undefined and name area
esphome.0	2026-04-27 10:43:16.942	debug	Create_state called for : 04830864B6DC.info.apiEncryptionSupported with value : false
esphome.0	2026-04-27 10:43:16.942	debug	create id 04830864B6DC.info.apiEncryptionSupported with value false and name apiEncryptionSupported

Versions:

• Adapter version: 0.7.0-beta.1
• ESPHome Dashboard version: 2026.4.2
• JS-Controller version: 7.1.1
• Node version: v22.21.0
• Operating system: Debian GNU/Linux 12 (bookworm)
• Installation Method: Docker