Init

README.md

@@ -0,0 +1,14 @@
+# Fabpel
+MQTT Topics:
+FABPELID is 5 Digits
+SEGMENTID is 5 Digits
+
+fabpel/FABPELID/SEGMENTID/set_color : Set Segment Color
+Payload == 3 Byte (R/G/B)
+
+fabpel/FABPELID/buzzer : Set State of Buzzer
+Payload == 1 -> ON
+Payload == 0 -> OFF
+
+fabpel/FABPELID/clear : Clear LEDs
+Payload == 0

Software/.gitignore

@@ -0,0 +1,7 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch
+
+src/config.h

Software/.vscode/extensions.json

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

Software/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

Software/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

Software/platformio.ini

@@ -0,0 +1,18 @@
+; 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:esp12e]
+platform = espressif8266
+board = esp12e
+framework = arduino
+lib_deps = 
+	knolleary/PubSubClient@^2.8
+	adafruit/Adafruit NeoPixel@^1.11.0
+monitor_speed = 115200

Software/src/config_example.h

@@ -0,0 +1,7 @@
+#define WLAN_SSID ""
+#define WLAN_PASS ""
+#define MQTT_BROKER ""
+#define MQTT_USERNAME ""
+#define MQTT_PASSWORD ""
+#define FABPELID 1
+#define SEGMENT_COUNT 3

Software/src/main.cpp

@@ -0,0 +1,151 @@
+#include <ESP8266WiFi.h>
+#include <PubSubClient.h>
+#include <Adafruit_NeoPixel.h>
+
+#include "config.h"
+#define PIN_BUZZER D2
+#define PIN_LED D3
+
+WiFiClient espClient;
+PubSubClient client(espClient);
+Adafruit_NeoPixel pixels(SEGMENT_COUNT * 2, PIN_LED, NEO_GRB + NEO_KHZ800);
+
+unsigned long lastMsg = 0;
+#define MSG_BUFFER_SIZE	(50)
+char msg[MSG_BUFFER_SIZE];
+
+#define TOPIC_BUFFER_SIZE (50)
+char topic_recv[TOPIC_BUFFER_SIZE];
+char topic_send[TOPIC_BUFFER_SIZE];
+
+void setup_wifi()
+{
+    delay(10);
+    Serial.println("Connecting Wifi ...");
+
+    WiFi.mode(WIFI_STA);
+    WiFi.begin(WLAN_SSID, WLAN_PASS);
+
+    while (WiFi.status() != WL_CONNECTED) 
+    {
+        delay(500);
+    }
+}
+
+void callback(char* topic, byte* payload, unsigned int length)
+{
+    Serial.println("Receive message");
+
+    int topic_len = (int)strlen(topic);
+    int set_color_len = (int)strlen("/set_color");
+    int buzzer_len = (int)strlen("/buzzer");
+    int clear_len = (int)strlen("/clear");
+    if(!strcmp(topic + topic_len - set_color_len, "/set_color"))
+    {
+        if(length != 3)
+        {
+            return;
+        }
+
+        char str_id[6] = {0};
+        strncpy(str_id, topic  + topic_len - set_color_len - 5, 5);
+        int id = atoi(str_id);
+
+        if(id > SEGMENT_COUNT)
+        {
+            return;
+        }
+
+        pixels.setPixelColor(id * 2, pixels.Color(payload[0], payload[1], payload[2]));
+        pixels.setPixelColor(id * 2 + 1, pixels.Color(payload[0], payload[1], payload[2]));
+        pixels.show();
+    }
+
+    if(!strcmp(topic + topic_len - buzzer_len, "/buzzer"))
+    {
+        if(length != 1)
+        {
+            return;
+        }
+
+        if(payload[0] == 0)
+        {
+            digitalWrite(PIN_BUZZER, LOW);
+        }
+        else
+        {
+            digitalWrite(PIN_BUZZER, HIGH);
+        }
+    }
+
+    if(!strcmp(topic + topic_len - clear_len, "/clear"))
+    {
+        pixels.clear();
+        pixels.show();
+    }
+}
+
+void reconnect()
+{
+    while (!client.connected()) 
+    {
+        Serial.println("Connecting MQTT ...");
+        String clientId = "FABPEL-";
+        clientId += String(random(0xffff), HEX);
+        
+        bool connected = false;
+        
+        if(MQTT_USERNAME == "")
+        {
+            connected = client.connect(clientId.c_str());
+        }
+        else
+        {
+            connected = client.connect(clientId.c_str(), MQTT_USERNAME, MQTT_PASSWORD);
+        }
+        if (connected)
+        {
+            snprintf (topic_recv, TOPIC_BUFFER_SIZE, "fabpel/%05d/+/set_color", FABPELID);
+            client.subscribe(topic_recv);
+            snprintf (topic_recv, TOPIC_BUFFER_SIZE, "fabpel/%05d/buzzer", FABPELID);
+            client.subscribe(topic_recv);
+            snprintf (topic_recv, TOPIC_BUFFER_SIZE, "fabpel/%05d/clear", FABPELID);
+            client.subscribe(topic_recv);
+        }
+        else
+        {
+            Serial.print("failed, rc=");
+            Serial.print(client.state());
+            Serial.println(" try again in 5 seconds");
+            delay(5000);
+        }
+    }
+}
+
+void setup()
+{
+    int i = 0;
+
+    Serial.begin(115200);
+    Serial.println();
+
+    setup_wifi();
+
+    client.setServer(MQTT_BROKER, 1883);
+    client.setCallback(callback);
+
+    pixels.begin();
+    pixels.clear();
+    pixels.show();
+
+    pinMode(PIN_BUZZER, OUTPUT);
+}
+
+void loop()
+{
+    if (!client.connected())
+    {
+        reconnect();
+    }
+    client.loop();
+}

Software/test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner 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/en/latest/advanced/unit-testing/index.html