diff --git a/KubeEdge v1.14.2/Led-Demo/ReadMe.md b/KubeEdge v1.14.2/Led-Demo/ReadMe.md
new file mode 100644
index 0000000..ffded9a
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/ReadMe.md	
@@ -0,0 +1,11 @@
+# Light Mapper
+
+
+ ## Description
+
+Light Mapper contains code to control an LED light connected to a raspberry Pi through gpio.
+
+Here we are using a push button  switch to test the working condition of the LED, through an independent  circuit.
+
+Depending on the expected state of the light, the program controls whether or not to provide power in pin-18 of the gpio.
+When power is provided in the pin, the LED glows (ON State) and when no power is provided on it then it does not glow (OFF state).
\ No newline at end of file
diff --git a/KubeEdge v1.14.2/Led-Demo/index.json b/KubeEdge v1.14.2/Led-Demo/index.json
new file mode 100644
index 0000000..39df5a9
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/index.json	
@@ -0,0 +1,30 @@
+{
+    "title": "KubeEdge Deployment",
+    "description": "Led-Raspberry-Pi",
+    "details": {
+        "steps": [
+            {
+                "title": "Step 1/4",
+                "text": "step1.md"
+            },
+            {
+                "title": "Step 2/4",
+                "text": "step2.md"
+            },
+            {
+                "title": "Step 3/4",
+                "text": "step3.md"
+            },
+            {
+                "title": "Step 4/4",
+                "text": "step4.md"
+            }
+        ],
+        "intro": {
+            "text": "intro.md"
+        }
+    },
+    "backend": {
+        "imageid": "ubuntu"
+    }
+}
\ No newline at end of file
diff --git a/KubeEdge v1.14.2/Led-Demo/intro.md b/KubeEdge v1.14.2/Led-Demo/intro.md
new file mode 100644
index 0000000..a9aade0
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/intro.md	
@@ -0,0 +1,14 @@
+## Prerequisites
+
+### Hardware Prerequisites
+
+1. RaspBerry-Pi (RaspBerry-Pi 3 has been used for this demo)
+2. GPIO
+3. Breadboard along with wires
+4. LED light
+5. Push Button switch (to test the working condition of the light, this can be skipped if needed)
+
+### Software Prerequisites
+
+1. Golang 1.14+
+2. KubeEdge 1.5+
\ No newline at end of file
diff --git a/KubeEdge v1.14.2/Led-Demo/step1.md b/KubeEdge v1.14.2/Led-Demo/step1.md
new file mode 100644
index 0000000..da86712
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/step1.md	
@@ -0,0 +1,12 @@
+## Steps to reproduce
+
+1. Connect the LED to the RaspBerry-Pi using the GPIO
+
+2. Clone and run KubeEdge.
+    Please ensure that the kubeedge setup is up and running before execution of step 4 (mentioned below).
+
+3. Clone the kubeedge/examples repository.
+
+```
+git clone https://github.com/kubeedge/examples.git $GOPATH/src/github.com/kubeedge/examples
+```
diff --git a/KubeEdge v1.14.2/Led-Demo/step2.md b/KubeEdge v1.14.2/Led-Demo/step2.md
new file mode 100644
index 0000000..9e9a358
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/step2.md	
@@ -0,0 +1,21 @@
+Create the LED device model and device instance.
+
+```
+cd $GOPATH/src/github.com/kubeedge/examples/led-raspberrypi/crds
+```
+```
+kubectl apply -f led-light-device-model.yaml
+```
+```
+kubectl apply -f led-light-device-instance.yaml
+```
+Note: You need to modify led-light-device-instance.yaml: replace string litearl 'edge-node1' with your edge node name at spec.nodeSelector.nodeSelectorTerms.matchExpressions.values
+<br>
+Note: You can change the CRDs to match your requirement
+
+
+ ### Update the name of the device (device instance name) created using the device CRD in the previous step along with the MQTT URL using which edge_core is running in the configuration file present at
+ 
+ ```
+ $GOPATH/src/github.com/kubeedge/examples/led-raspberrypi/configuration/config.yaml
+ ```
\ No newline at end of file
diff --git a/KubeEdge v1.14.2/Led-Demo/step3.md b/KubeEdge v1.14.2/Led-Demo/step3.md
new file mode 100644
index 0000000..fa7a41a
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/step3.md	
@@ -0,0 +1,18 @@
+6. Build the mapper to run in RaspBerry-Pi.
+
+```
+cd $GOPATH/src/github.com/kubeedge/examples/led-raspberrypi/
+make 
+```
+or ***make led_light_mapper***
+
+```
+docker tag led-light-mapper:v1.1 <your_dockerhub_username>/led-light-mapper:v1.1
+docker push <your_dockerhub_username>/led-light-mapper:v1.1
+```
+
+Note: Before trying to push the docker image to the remote repository please ensure that you have signed into docker from your node, if not please type the followig command to sign in <br>
+
+docker login<br>
+
+Please enter your username and password when prompted
\ No newline at end of file
diff --git a/KubeEdge v1.14.2/Led-Demo/step4.md b/KubeEdge v1.14.2/Led-Demo/step4.md
new file mode 100644
index 0000000..a1ef9c1
--- /dev/null
+++ b/KubeEdge v1.14.2/Led-Demo/step4.md	
@@ -0,0 +1,18 @@
+## Deploy the light mapper.
+
+```console
+cd $GOPATH/src/github.com/kubeedge/examples/led-raspberrypi/
+```
+
+Please enter the following details in the deployment.yaml :-
+1. Replace <edge_node_name> with the name of your edge node at spec.template.spec.voluems.configMap.name
+2. Replace <your_dockerhub_username> with your dockerhub username at spec.template.spec.containers.image
+
+```
+kubectl create -f deployment.yaml
+```
+
+
+
+Change the device Twin attribute (expected value) "power-state" of the device to "ON" to turn on the light, and "OFF" to turn off the light using the device CRDs. The mapper will control the LED to match the state mentioned in the cloud and also report back the actual state of the light to the cloud after updating.
+