Closed trajano closed 4 months ago
My original idea was to create a climate entity based on device type, and for those devices not create sensor entities for the properties that are used in the climate entity. However, I realised that we needed the data dictionaries first, and maybe add something to the data dictionary to control creating climate entities.
In the meanwhile, you could also try to map sensor entities using Template Climate.
Also, feel free to submit PRs with data dictionaries and/or code!
I created some template sensors for my oven, washing machine and dryer and combine them to the card with most useful sensors. Would it make sense to share them somehow here?
Version 0.3.0 with support for climate devices has just been released.
Note that it lacks some feature that I plan to add over the next few weeks:
More releases today:
current_humidity
and target_humidity
Version 0.10.0 adds support for presets.
Now only target_temperature_max
and target_temperature_min
is missing. I have not yet seen a ConnectLife device that supports this, so closing this issue as completed for now. This is also documented in README.md
Ideally we should use the
Climate
API but obviously this would be device specific. The way I was thinking was that if I use Climate to set the desired humidity to 45% then the following should occurIf present humidity is above 45% then
I did the above as an automation myself, but it would be nice if it had a nicer API.
This should be an extension to #1 and #6 primarily. But perhaps the data dictionary should accommodate for it.