Releases · RogerSelwyn/O365-HomeAssistant

27 May 12:44

v4.8.0

b6adf69

v4.8.0

💥 Breaking Changes (Potentially)
Note I've decided with this release to remove a whole raft of complex logic around minimum permissions. When I took this on and made permissions more granular I maintained a capability such that if you set the configuration to enable updates, but actually only granted read permissions on the Azure App the integration would still create the sensors.

To be honest, this is a pain to maintain and makes the code confusing. Since it is now possible to set the permissions you require to the right level of granularity via the configuration, I've removed this code complexity.

I have maintained an ability whereby if the config is set to have Read only permissions, but the Azure app has been granted ReadWrite, then the Read functionality will still work. This enables the situation where the same Azure App is used in multiple configurations with different permission sets.

I've tested as thoroughly as I can, butI've set this as Beta for now, so a slow take up picks up any remaining bugs. If you get an error in your logs along the lines of Minimum required permissions: 'Calendars.ReadWrite'. Not available in token 'o365_primary.token' for account 'primary', then check your configuration to ensure it matches what you intended and what your Azure App permissions enable.

Remove complex logic around minimum permissions - @RogerSelwyn

The below fix may break your setup, the enable_update parameter at the top level was incorrectly defaulting to True, when it should be False. If you were relying on the default, you will have to add enable_update: true to your config.

Correct default of calendar enable_update to False - @RogerSelwyn

✨ Enhancements

Add ability to disable calendar - @RogerSelwyn

The rational for adding this enhancement is that the integration is becoming too unwieldy, so I'm moving to a point where I break it out into 3 integrations, calendar, email and other. These could all use the same azure app, but would potentially run from ui based setup (running both yaml and UI is a pain). The first one I would break out is calendar, which is I think how this integration started. So to create a painless transition, there is a need to be able to disable calendar in this integration.