This repository has been archived by the owner on Oct 4, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 97
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
2.0.0b11 - with flow/max/min boiler temps - #59
- Loading branch information
Showing
4 changed files
with
110 additions
and
10 deletions.
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
#define EMSESP_APP_VERSION "2.0.0b10" | ||
#define EMSESP_APP_VERSION "2.0.0b11" |
163fbba
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.
I think there is something wrong, reading 0x1A but writing 0x16.
0x1A is a control message from thermostate to boiler, the boiler itself publishes the values by monitor-telegrams. I don't think these values from 0x1A are relevant.
0x16 is the boiler parameter message where we can read an write. (i'm also working on this message for reducing the burner starts and get merge conflicts with this changes).
Is it realy necessary to add these parameters to telnet if you want to reduce the commandset?
Telnet for logging and watching telegrams, mqtt for setting values and web for configuring, if i get you right.
BTW: Also there are some c&p errors like all publishes as
doc["heatWorkMin"]
I will send my changes to 0x16 soon and try to resolve the conflicts.
163fbba
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.
Yeah, thinking about it you're right again. I rushed the implementation. Next time I'll make GitHub branches for major changes and merge when verified.
There's indeed a mixup between the 0x1A and 0x16 values.
The idea is indeed to keep all config in the Web and use the telnet console for tracking to reduce the memory footprint on a ESP8266. If we follow this process then I should remove the device specific commands and replace with a command than simulates the MQTT. Something like 'send '. Thoughts?
I'll be happy if you can fix this. I guess we remove the UBASetPoint and stick to 0x16 for reading/writing values. I will also start on the mqtt/command refactor and create a new Issue for this.