v0.2.0
What's Changed
- BREAKING: Use fully qualified names for attributes by @Meatballs1 in #109
Full Changelog: v0.1.8...v0.2.0
Previously we relied on the final section of an entity (e.g. DoorState
within BSH.Common.Status.DoorState
) to be unique, but this is not the case across a number of devices, therefore we have changed the naming convention to use the fully qualified entity name. This will break existing MQTT configurations and change auto discovered instances, so please review all configurations.
The AutoDiscovery also made modifications to devices.json but this is no longer a very viable approach as the login process has become more complex after having CAPTCHAs introduced.
Autodiscovery also treated many entities as binary_sensors (e.g. a door), however HomeConnect may have several different states for a door such as Open, Closed, Ajar. We treat these entities as sensor with a device_class of enum now.
Events are no longer passed as sensors, but now will be registered as events by Autodiscovery.