-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
Align consumption sensor names in ViCare integration #127888
Merged
Merged
Changes from 6 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
faa9010
update sensor labels
CFenner 3ced350
revert changes to gas entity description
CFenner 634bab2
use electricity instead of power and energy
CFenner c1ea7f9
revern reuse
CFenner 378f40f
Revert "use electricity instead of power and energy"
CFenner 4fca2de
rename :tada:
CFenner 07d0b56
update
CFenner 5e5e39a
update
CFenner 4dfa954
update
CFenner 4961a92
update
CFenner 4ebcd72
update
CFenner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I saw that there was a whole discussion (I did not read, sorry for that), but let me ask a quick question, would it make sense to keep the start of the name contain the type? Because if I imagine a device with these entities, on the device page everything looks like
Electrical energy consum...
. And if I translate it to DutchEnergie consumptie ...
. (I am not sure how wide it will show, but with this long name, I can see it being cut off, that's my point).Would it make sense to have
Heating electrical energy consumption today
? (under the assumption the reason this PR exists is because of the added emphasis oneletrical
).(I think usually I wouldn't make this big of a deal of this, but in this case it can be 12(?) entities, so that would most likely lead to people renaming the things).
(Also, added question, on what level is this information collected? Would it make sense to only show the heating usage on the heating device and DHW on the DHW device?)