From 0f7eb3835621cfa94d7d7acbf2dc2d5e2eb7fd9b Mon Sep 17 00:00:00 2001 From: Jeroen88 Date: Sat, 29 Oct 2022 10:48:07 +0200 Subject: [PATCH] Type in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1bf5fb9..fabc2f1 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ All these functions take an OpenTherm DATA-ID as _first_ parameter. The DATA-ID ## Error handling The function ```error()``` is used to get information about the last call to one of the functions ```read()```, ```write()``` or ```readWrite()```. All these functions return ```false``` if an error occurred in the _communication_ between thermostat (primary) and boiler or HVAC (secondary). These functions return ```true``` if everything is fine, but also upon an error on -_application level_. You will get this error if e.g. you _read out_ your boiler or HVAC with a DATA-ID that is not supported. Also, if you _write data to_ your boiler or HVAC, the value can be out of range, e.g. a setpoint is to low or to high. In this case ```error()``` will return ```INVALID_DATA```. +_application level_. You will get this error if e.g. you _read out_ your boiler or HVAC with a DATA-ID that is not supported. Also, if you _write data to_ your boiler or HVAC, the value can be out of range, e.g. a setpoint is too low or too high. In this case ```error()``` will return ```INVALID_DATA```. All error codes: - ```OK```: everything is fine! -- libgit2 0.21.4