Reload integration from UI & bugfix

[gigatexel]

A small update for the integration that should make using it a lot more convenient:

init.py

• Implement async_unload_entry to enable reloading the integration
• Add remove_unavailable_entities and remove_unused_devices to avoind orphaned devices/entities when function blocks are removed in Config.
• Removed loading the SCENE platform and let it load as a standard platform from const.py

api.py

Add reconnect try/catch to avoid connecting to MS after the connection was closed

climate.py

Solve this warning:

Entity None (<class 'custom_components.loxone.climate.LoxoneAcControl'>) implements HVACMode(s): off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/JoDehli/PyLoxone/issues

I tested this on my system and works when removing/adding function blocks in Config and then reloading the integration instead of rebooting HA.
Maybe someone else can try and test?

[JoDehli]

@gigatexel thanks for your help. But can you make one pull request for one feature. For example one only for the reload and one for removing entities and so on. I try to make branches from your pull request and cherry pick your commits.

[JoDehli]

@gigatexel I think in the newest pyloxone this was already fixed:

Entity None (<class 'custom_components.loxone.climate.LoxoneAcControl'>) implements HVACMode(s): off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/JoDehli/PyLoxone/issues

[JoDehli]

@gigatexel
Why do you make use of the property supported_features and not use the _attr_supported_features. This should result in the same behavior I think.

In my opinion the property is only useful when you want to change the supported feature dynamically.

[JoDehli]

@gigatexel why do we need this:

• Add remove_unavailable_entities and remove_unused_devices to avoid orphaned devices/entities when function blocks are removed in Config

If something changes you can manually delete it from the entities and devices menu. I think it is not a good idea to delete it automatically without the user interaction. Sometimes a platform has an error an all devices a unavailable. And if you delete them automatically I do not know what happen with the history of this device. Maybe the user wants this entity or device and all the data which the system collected for this devices.

An option could be to provide a service for both or one service which triggers both functions in a row. So the user can decide to call it once or even in a automation.

[JoDehli]

@gigatexel maybe you can make another pull request with a service for both functions.

[JoDehli]

@gigatexel for now I will not include the reloading as it is not stable at all. I tried it a few times to implement and could get to work reliable. What I learned from the last 12 years of maintaining this small integration is that if it is not working reliable do not implement it. You have much more trouble and work.