Getting: Could not find appliance 0200000E33F1 in known device list.

[sdelmas]

I assume this is one of those "need others to share their device info" :-). What can I do to help with this?

I am also getting this warning, but I suspect you already know about this:

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:151
First occurred: 9:07:28 AM (43 occurrences)
Last logged: 9:07:35 AM

Detected code that calls async_forward_entry_setup for integration ge_home with title: [email protected] and entry_id: a552ad4a18449ccffd3dd222b925a757, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration midea_ac_lan with title: Shop-Air-South and entry_id: 01J3N3W14Q76RGBK7N63D0XV7T, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration midea_ac_lan with title: Shop-Air-North and entry_id: 01J3N3X21WX9XS88SNJRGGTFMQ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration midea_ac_lan with title: Shop-Air-Upstairs and entry_id: 01J3N3XQMQ27EPXS3WR4QZKMX6, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.

[rohorner]

I started to see this issue recently as well. I have three Monogram kitchen appliances.

2024-08-05 13:20:43.442 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'ge_home' calls async_forward_entry_setup for integration, ge_home with title: [EMAIL REDACTED] and entry_id: f54903b87355bc2b7d488840749bd246, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/ge_home/update_coordinator.py, line 180: self.hass.async_create_task(, please report it to the author of the 'ge_home' custom integration
2024-08-05 13:20:47.235 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance D828C9572782 in known device list.
2024-08-05 13:20:47.277 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance 02000001CE0B in known device list.
2024-08-05 13:20:47.346 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance FCB97E108BD6 in known device list.

2024-08-05 13:20:54.575 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration ge_home with title: [email protected] and entry_id: f54903b87355bc2b7d488840749bd246, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2122, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1175, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
_LOGGER.warning(msg, stack_info=True)
2024-08-05 13:20:54.614 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration ge_home with title: [email protected] and entry_id: f54903b87355bc2b7d488840749bd246, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2122, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1175, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
_LOGGER.warning(msg, stack_info=True)

The above error repeats for each device.

[bmorgenthaler]

I am also getting this message with my dehumidifier with a different device id. What information is helpful to collect?
Could not find appliance 020000253E57 in known device list.

[selrahc13]

I am having the same issue with my GE window air unit. Logs follow:
2024-09-05 21:31:29.006 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance D828C94ACA91 in known device list. 2024-09-05 21:31:29.009 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.ge_home.entities.ac.ge_wac_climate.GeWacClimate'>) implements HVACMode(s): off, auto, cool, fan_only and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please report it to the author of the 'ge_home' custom integration 2024-09-05 21:35:46.821 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'ge_home' accesses hass.helpers.aiohttp_client. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from aiohttp_client directly at custom_components/ge_home/config_flow.py, line 38: session = hass.helpers.aiohttp_client.async_get_clientsession(hass), please report it to the author of the 'ge_home' custom integration 2024-09-05 21:44:16.168 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance D828C94ACA91 in known device list. 2024-09-05 21:44:16.172 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.ge_home.entities.ac.ge_wac_climate.GeWacClimate'>) implements HVACMode(s): off, auto, cool, fan_only and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please report it to the author of the 'ge_home' custom integration