HomeDaemon-MCP 4.6.0 -- Errata
The Market Ticker - Commentary on The Capital Markets
Logging in or registering will improve your experience here
Main Navigation
Display list of topics
Sarah's Resources You Should See
Sarah's Blog Buy Sarah's Pictures
Full-Text Search & Archives
Legal Disclaimer

The content on this site is provided without any warranty, express or implied. All opinions expressed on this site are those of the author and may contain errors or omissions.


The author may have a position in any company or security mentioned herein. Actions you undertake as a consequence of any analysis, opinion or advertisement on this site are your sole responsibility.

Market charts, when present, used with permission of TD Ameritrade/ThinkOrSwim Inc. Neither TD Ameritrade or ThinkOrSwim have reviewed, approved or disapproved any content herein.

The Market Ticker content may be sent unmodified to lawmakers via print or electronic means or excerpted online for non-commercial purposes provided full attribution is given and the original article source is linked to. Please contact Karl Denninger for reprint permission in other media, to republish full articles, or for any commercial use (which includes any site where advertising is displayed.)

Submissions or tips on matters of economic or political interest may be sent "over the transom" to The Editor at any time. To be considered for publication your submission must include full and correct contact information and be related to an economic or political matter of the day. All submissions become the property of The Market Ticker.

Considering sending spam? Read this first.

2019-03-11 15:12 by Karl Denninger
in Technology , 64 references Ignore this thread
HomeDaemon-MCP 4.6.0 -- Errata
[Comments enabled]

Two problems have been identified and fixed in the HomeDaemon-MCP code that is in the freeware release at http://homedaemon.net.

The problems impact both the ARM32 (Pi2) and ARM64 (Pi3) versions.

The first issue, which is rated severe, relates specifically to events with time offsets (e.g. "[v Some_Variable]@00:20 = 0") which by way of example expresses a test for a variable that has been of value "0" for 20 minutes or more. A coding error in the statement and internal state classifier can, under certain conditions, cause any test with a time offset to evaluate incorrectly.  This can lead the system to not execute an event that should be run, or run one that should not.

The second issue, which is rated moderate, relates to the "zmodelock" command for thermostats.  This command can fail to actually prohibit mode changes and thus make ineffective manual user mitigation of failed HVAC units (e.g. setting the thermostat to a "locked off") state.  Since a user can accomplish the same intended goal by setting the setpoint well above or below the ambient temperature, and that mitigation is fully effective, this issue is rated "moderate" rather than "severe."

Both issues are corrected in v4.6.1; if you are using the freeware version for evaluation purposes please contact me directly using the information on the right and I will direct you to a replacement binary.  No other changes need be made to the downloaded image and replacement of the impacted binary is simple.  A full download of the SD card image is not required; the SD images have been temporarily disabled and will be replaced when the new full builds are complete.


Go to responses (registration required to post)

No Comments Yet.......
User: Not logged on
Login Register Top Blog Top Blog Topics FAQ