-
Notifications
You must be signed in to change notification settings - Fork 118
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
Renaming heat curve fieldnames to reduce confusion... #492
Comments
Hi This is the default: If you think about what happens, it kind of sounds logical as it is:
I find current situation and your suggestion are both equally fuzzy / difficult. They both require a good 2nd look. I think in this case it is maybe better to increase the documentation. Im not in favor of renaming mqtt topics for only estetic purpose. :) This can give a lot of extra work for others. (I am a victim in this case) But, If it truely has significant benefits it might be worth the effort IMHO. But.. in this case I do not see it that obviously. Just my thoughts about it :) |
I personally prefer to use terms or shorts as used in service manual, Outside High/Water Low, Outside Low/Water Hi (O_Hi/W_Lo, O_Lo/W_Hi) |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Writing and debugging rules I get again and again confused...
"Is high the target or outdoor temperature again?"
Maybe this happens also to other people here - use that thumbs up button down below!
Proposal:
Rename fields to
Maybe that helps - if you don't like that idea use the thumbs down button below...
The text was updated successfully, but these errors were encountered: