Migrate imap_email_content integration to config entry#89707
Conversation
|
I'd suggest to deprecate this integration instead and fire an event in the imap integration that users can automate on. |
I'll have a look at that possibility |
|
Will set this PR to draft for two reasons:
|
|
Hi @jbouwh I tested locally this integration and it works great. I've a quick question: once a sensor is created, shouldn't the entry reflect that there is an entity belonging to it? In my case it never appears. Thanks in advance. |
May be it should (thnx), but for now it is not clear yet if we continue with this PT. Plans are to extend the |
|
I've read about it, thanks. Ok, in case we go further with this please let me know if I can help with testing. Cheers. |
|
Superseded by #90429 and home-assistant/home-assistant.io#26792 |

Proposed change
Migrate imap_email_content integration to config entry.
The existing sensor items from configuration.yaml will be migrated to config entries automatically.
Users need to remove the configuration from
configuration.yamlafter the migration.In issue was added for the yaml deprecation.
Advise is to merge #89563 first, as this fixes some bugs.
The
codeownerlist in the manifest was updated.Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.To help with the load of incoming pull requests: