-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement request. Add is_locked attribute to climate entities #374
Comments
Had a look at this but struggling with how to make this make sense. The hub supports lights and blinds too in France so it doesnt necessarily make sense to just show all devices. What is your use case and maybe i can come up with something that helps. |
@pcaouolte i haven't forgotten about this and will look at it during Nov. |
Sorry for the very long wait. This is now in v3.4.4, released earlier today. |
Thank you 👍 |
Would it be possible to add an is_locked attribute to the Wiser climate entities please?
This would simplify automations by avoiding the need to check which devices are in the same room as a climate entity and then checking if those devices are locked.
It is possible that only some devices in the same room as the climate entity are locked so I suppose that the is_locked attribute state could be 'true', 'false' or 'part'. Alternatively the is_locked attribute state could contain the number of devices in the room which are locked.
Apologies if this is not the appropriate way to make this request. I am very new to github.
The text was updated successfully, but these errors were encountered: