Development (#112)

* updated build instructions

* edit readme

* edit platformio.ini to USB upload as default

* Commented platformio.ini

* Changed crazy pin numbers

* added serial bypass test

* MQTT message on pressed button
Add link /dir/ to show files on system

* Only send MQTT button msg if state changed

* Timer handling (#101)

* Handling capital H on display

* Ignoring Atom temp files

* If display shows 'H' then don't update the temperature value.

* Cosmetic changes in code.

* Avoid update temperature to 0 when display is blinking.

Co-authored-by: visualapproach <[email protected]>

* include 'h' and 'H' in character set

* Update flows.json

made for use in homeassistant

* Update readme.md

* Updated build instructions

* Update README.md

link to FAQ

* build instructions updated

* target temp slider fix

Co-authored-by: Denes Varga <[email protected]>

Code/4-wire-version/lib/BWC4W/BWC_8266_4w.cpp

@@ -1,11 +1,17 @@
 #include "BWC_8266_4w.h"
 
 void CIO::begin() {
-  //Setup serial to CIO here
-  //Using hardware UART/Serial on default pins (RX/TX)
-  cio_serial.begin(9600, SWSERIAL_8N1, D6, D7, false, 64);
+  //Setup serial to CIO and DSP here according to my PCB
+  /*
+    CIO_RX = D3
+    CIO_TX = D2
+    DSP_TX = D6
+    DSP_RX = D7
+    Devices are sending on their TX lines, so we read that with RX pins on the ESP
+  */
+  cio_serial.begin(9600, SWSERIAL_8N1, D2, D3, false, 64);
   cio_serial.setTimeout(50);
-  dsp_serial.begin(9600, SWSERIAL_8N1, D1, D2, false, 64);
+  dsp_serial.begin(9600, SWSERIAL_8N1, D6, D7, false, 64);
   dsp_serial.setTimeout(50);
 
   states[TARGET] = 20;

Code/4-wire-version/test-hardware/4-wire-serial-bypass/.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

Code/4-wire-version/test-hardware/4-wire-serial-bypass/.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ]
+}

Code/4-wire-version/test-hardware/4-wire-serial-bypass/include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

Code/4-wire-version/test-hardware/4-wire-serial-bypass/lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

Code/4-wire-version/test-hardware/4-wire-serial-bypass/platformio.ini

@@ -0,0 +1,14 @@
+; PlatformIO Project Configuration File
+;
+;   Build options: build flags, source filter
+;   Upload options: custom upload port, speed and extra flags
+;   Library options: dependencies, extra library storages
+;   Advanced options: extra scripting
+;
+; Please visit documentation for the other options and examples
+; https://docs.platformio.org/page/projectconf.html
+
+[env:nodemcuv2]
+platform = espressif8266
+board = nodemcuv2
+framework = arduino

Code/4-wire-version/test-hardware/4-wire-serial-bypass/src/main.cpp

@@ -0,0 +1,20 @@
+#include <Arduino.h>
+
+const int CIO_TX = D2;
+const int CIO_RX = D3;
+const int DSP_TX = D6;
+const int DSP_RX = D7;
+
+void setup() {
+  // put your setup code here, to run once:
+  pinMode(CIO_TX, INPUT);
+  pinMode(CIO_RX, OUTPUT);
+  pinMode(DSP_TX, INPUT);
+  pinMode(DSP_RX, OUTPUT);
+}
+
+void loop() {
+  // put your main code here, to run repeatedly:
+  digitalWrite(DSP_RX, digitalRead(CIO_TX));
+  digitalWrite(CIO_RX, digitalRead(DSP_TX));
+}

Code/4-wire-version/test-hardware/4-wire-serial-bypass/test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Unit Testing and project tests.
+
+Unit Testing is a software testing method by which individual units of
+source code, sets of one or more MCU program modules together with associated
+control data, usage procedures, and operating procedures, are tested to
+determine whether they are fit for use. Unit testing finds problems early
+in the development cycle.
+
+More information about PlatformIO Unit Testing:
+- https://docs.platformio.org/page/plus/unit-testing.html

Code/6-wire-version/.gitignore

@@ -3,3 +3,5 @@
 .vscode/c_cpp_properties.json
 .vscode/launch.json
 .vscode/ipch
+.clang_complete
+.gcc-flags.json