#1 - basic functionality

[maximiliani]

• WiFi login via captive portal
• Switching relays
• Detecting touch buttons
• Configuration of the input and output pins via captive Portal

[maximiliani]

Ports are saved in ports.txt as JSON: "{"ports":[{"port":port, "function":function, "topic":topic},{ ...}]}"
Port is either "D4","D5",... or "16","18",...
Function is a struct, because of the upgradeability --> #5
topic is the decrypted MQTT-topic e.g. "/1", "/2", ...

[maximiliani]

As mentioned in the comment in the WebGUI issue #3, we only want to implement three necessary configuration options. The other ones are going to be configured via encrypted MQTT.

[maximiliani]

Ports are saved in ports.txt as JSON: "{"ports":[{"port":port, "function":function},{ ...}]}"
Port is either "D4","D5",... or "16","18",...
Function is a struct, because of the upgradeability --> #5

Function struct is identified in JSON by the IDs:

• 1 = OUTPUT (High or Low)
• 2 = INPUT (e.g. Button, ... --> High or Low)
  more modes are coming later ...

[maximiliani]

Ports are saved in ports.txt as JSON: "{"ports":[{"port":port, "function":function},{ ...}]}"
Port is either "D4","D5",... or "16","18",...
Function is a struct, because of the upgradeability --> #5

The maximum length of the JSON is 32 ports.

[maximiliani]

The maximum amount of ports, which can be configured is 64. This is due to the length of the array configured ports, which is defined in jsonHandler.cpp and jsonHandler.h.

[maximiliani]

The new configuration JSON has to be published in /home/config/<ID of the main device (5 chars)><Port-SubID(1 char)>/ and has to look like: {"port":<Number` of the hardware Port as uint8_t>, "analog":<analog port? 1 or 0>, "output":<output port? 1 or 0>}