doc: Update README.md

README.md

@@ -2,8 +2,11 @@
 
 [![GitHub release](https://img.shields.io/github/v/release/RogerSelwyn/O365-HomeAssistant)](https://github.com/RogerSelwyn/O365-HomeAssistant/releases/latest) [![maintained](https://img.shields.io/maintenance/yes/2024.svg)](#) [![maintainer](https://img.shields.io/badge/maintainer-%20%40RogerSelwyn-blue.svg)](https://github.com/RogerSelwyn) [![hacs_badge](https://img.shields.io/badge/HACS-Default-41BDF5.svg)](https://github.com/hacs/integration) [![Community Forum](https://img.shields.io/badge/community-forum-brightgreen.svg)](https://community.home-assistant.io/t/office-365-calendar-access)
 
-# 💥💥💥 Views Wanted 💥💥💥
-I'm considering breaking up the monolithic O365 integration into smaller, more manageable items. If you have a view, please comment here:
+# Note: 
+
+This integration is slowly moving towards EOL. I have already created integrations which will replace it - MS365-Calendar/Mail/Teams/ToDo, these can be used now using HACS Custom. When these are available on HACS Default I will then stop work on O365-HomeAssistant. 
+
+Many will have seen a warning in the logs - `Detected that custom integration 'o365' uses 'async_config_entry_first_refresh', which is only supported for coordinators with a config entry and will stop working in Home Assistant 2025.11` - this further forces the EOL due to a change in HA Core, which means that the integration will cease to work after the 2025.11 HA release without really significant re-work. Because this integration is setup via YAML, it does not have a `config_entry`, the replacements listed above do.
 
 [O365 --> MS365 - A potential big change - your views needed](https://github.com/RogerSelwyn/O365-HomeAssistant/discussions/234)