-
Notifications
You must be signed in to change notification settings - Fork 57
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
Request #55
Comments
Hi I support this request. I use for everything custom-buttons an d I'm using the layout from matt8707. So using a select is not handy. |
As a general rule the UI control to use is automatically detected based on the type of the entity in the HC API. A switch control is used for boolean entities, however the power state entity is not boolean (and in fact it has other states than on/off). All that said I think it does make sense to show a switch for appliances where the entity has exactly two states which happen to be on/off, so I've make that change and you can try it out with beta version 0.5.0-b8. |
Sweet! And one more request: It is showing right here but not when using state templates with like custom:button-card: |
Enum values in history can't be translated, if you're seeing them in current values then please submit a PR with updates to the translation files. See #26 for more info. |
It works for some of the devices, but not all:
|
@pswid I'm not sure what you mean. From what I understand from your description everything seems to be working fine. |
I also noticed that for ovens integration shows PowerStatus as I don't know why the HC API reports four available PowerState options for ovens, while the documentation https://api-docs.home-connect.com/settings#power-state mentions only about two of them (it's probably an API bug). So in the case of ovens, you could also make a |
The integration doesn't know anything about specific appliances or entities, everything is detected and generated on the fly and that is not going to change. If the API returns values other than On and Off then the control will be a select, that too is now a general handling of all entities and is not going to change. I can say that in many cases the documentation doesn't match the actual behavior so I'm not sure which one is wrong but assuming it's the API that HC will have to fix it on their side. |
Hi i tested the new power switch with my dishwasher and it worked excellent. I only have a Bosch Bosch dishwasher so I couldn't test more. But fif you want me to test something please let me know. |
I can understand you don't want to make workarounds of the HC API errors (e.g. for four oven power states available although only two are working). However, why not to replace |
There is nothing special about the power setting either. I added generic handling of enums that only have On/Off values but I don't want to second guess what the other values do. |
Hi, i have a BOSCH dishwasher.
Is it possible to change "select" to a switch to power on & off?
select.010100522145000977_bsh_common_setting_powerstate
The text was updated successfully, but these errors were encountered: