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
{{ message }}
This repository has been archived by the owner on Oct 7, 2021. It is now read-only.
Hi. I was a bit confused when setting up the config for this component that the "friendly name" is used to identify devices instead of the entity id. I would assume that the entity is more stable and more standardised so I was wondering why the name is used instead. Probably there are good reasons for this design choice, in this case please just close the issue.
Thanks for this custom component. Nice to see that some of the flaws in the tuya integration are getting fixed here.
The text was updated successfully, but these errors were encountered:
Actually this is already possible, you can you use both friendly name or entity id. I just do not mention this option in ReadMe to avoid confusion and friendly name seemed easier to identify for all.
But if you can better clarify and explain usage, a PR to the ReadMe is really welcome.
I see, i tried with climate.86806317a4cf12xfb8f9 first which did not work and read the instructions more careful then and got it working with the friendly name. Now I checked again and indeed it is working with 86806317a4cf12xfb8f9 only. But I agree that its not so easy to make the option accessible and clear in the instruction.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi. I was a bit confused when setting up the config for this component that the "friendly name" is used to identify devices instead of the entity id. I would assume that the entity is more stable and more standardised so I was wondering why the name is used instead. Probably there are good reasons for this design choice, in this case please just close the issue.
Thanks for this custom component. Nice to see that some of the flaws in the tuya integration are getting fixed here.
The text was updated successfully, but these errors were encountered: