You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent efforts to document Packet 0x7B have given us the ability to programmatically detect what any given heat pump can do and what features exist on any given unit.
Instead of having to manually set our unit capabilities as part of ESPHome configuration, it would be nice if the library could instead read and automatically determine what is available and expose those things appropriately.
Special Considerations
ESPHome's docs say that the climate traits field is intended to be static across all of execution time. Further research may be needed into how to dynamically create a Climate entity (if that's even possible).
As a stopgap measure, simply printing the device capabilities to log would be a good first step.
Prior Art
The ESPHome integration for Midea ACs has autoconf support that we might be able to leverage if we're fast enough.
Per ESPHome discord, we can set traits in code, but we need to be quick about it. Unsure if we can satisfy that guarantee with the current setup, but worth a shot.
The text was updated successfully, but these errors were encountered:
Recent efforts to document Packet 0x7B have given us the ability to programmatically detect what any given heat pump can do and what features exist on any given unit.
Instead of having to manually set our unit capabilities as part of ESPHome configuration, it would be nice if the library could instead read and automatically determine what is available and expose those things appropriately.
Special Considerations
Climate
entity (if that's even possible).Prior Art
The text was updated successfully, but these errors were encountered: