Releases: dgtal1/extalife_custom_component
Releases · dgtal1/extalife_custom_component
2.2b6
2.2b5
New features
- attributes' sensors expanded to cover all the platforms, not only sensor
- virtual / attribute sensors are now created also for ROG21 energy measurement attribute & active power attribute
- create battery sensors only for one channel (channel 1) of a multiple-channel device
Fixes
- Updated get_mac_address to correctly handle host name by DNS entry by @gadulowaty
Misc
- code cleanup, pylint issues fixed
- minor code tweaks
2.2b4
2.2b3
2.2b2
New features
- add possibility to add fake channels in pyextalife API for simulation of sensors one doesn't own (fake_channels.py)
Fixes
- fix "value_1" error
- fix error related to unique id generation
- fix invalid values for virtual, attribute-based sensors and their parent device sensor
- fix obsolete Device Registry call
- enhance virtual sensor names (remove double blanks)
Known issues
- RCM-21 will generate 3 battery sensors as technically it reports battery state in all 3 channels. This will also happen for other, devices which send multiple channels. This issue will not be addressed. Redundant entities may be switched off in Home Assistant entity settings.
2.2b1
2.2b0
New features
- New, separate sensor entities are created for sensor attributes. Currently supported attributes: battery_state, and all measurable values of MEM-21 per phase
Breaking changes
- extra state attributes reduced to minimum for the
sensor
entity to b compatible with HA dev guidelines
Fixes
- fixes for ROB-21 by @SebiCo
- align entity state attributes with HA 2021.12 and newer to get rid of warnings in logs
- fixed incompatibility warning "Detected code that uses deprecated
async_get_registry
to access entity registry, use async_get instead." - fixed incompatibility warning "<class 'custom_components.extalife.sensor.ExtaLifeSensor'>) implements device_state_attributes...."
- fixed incompatibility errors for the
light
entity - various smaller fixes
- code reformatted to match HA coding styling
Known issues
None so far
2.1.3a0
New features
- new service
extalife.disconnect
is now available to disconnect from controller on-demand e.g. for controller maintenance works without shutting down Home Assistant instance - new service
extalife.connect
is now available to (re) connect to controller after on-demand disconnection or disconnection caused by other factors e.g. controller wasn't available and the integration didn't yet connect to it
Breaking changes
None
Fixes
- fixes for ROB-21 by @SebiCo
- align entity state attributes with HA 2021.12 and newer to get rid of warnings in logs
- various fixes
- code reformatted to match HA coding styling
Known issues
- errors in logs when receiving state notification from the controller (doesn't break connection and preserves control over HA entities)
- errors in logs when controlling an entity (doesn't break connection and preserves control over HA entities)
2.1.2
2.1.1
Fixes
- fix major reconnection issue, which caused HA and EFC-01 overloading (100% CPU core usage for HA python3 process) and causing potential EFC-01 freeze / hang. The issue occured when the integration lost connection to EFC-01 e.g. EFC-01 was reset
- fix syntax error in notification code handling (thanks @asystentka-jolka )
- fix state attributes' values for the sensor platform