experimenting/Transfer-light-value-1.md

+# Heartbeat
+
+In Octave, display **Resources** page:
+
+![light1-resources](uploads/9422750ba71f2b4c7c4e4e8a95c75eae/light1-resources.png)
+
+Set following resources:
+* **cloudInterface/store_forward/heartbeat_on_empty**: **true**
+* **cloudInterface/store_forward/period**: **60**
+
+This guarantees that the board contacts the cloud every 60 s at least.
+
+[Reference](https://docs.octave.dev/guides/control_edge_data/control_device_comm/#configuring-and-understanding-heartbeat)
+
+# Developer mode
+
+To check system behaviour in real conditions, we disable *Developer Mode*:
+* **cloudInterface/developer_mode/enable**: **false**
+
+[Reference](https://docs.octave.dev/guides/control_edge_data/control_device_comm/#configuring-developer-mode)
+
+# Light
+
+## Resource configuration
+
+Now, let's configure light sensor handling in such a way that its value is sent to the cloud every two minutes:
+* **light/enable**: **true**
+* **light/period**: **120**
+
+## Observation
+
+Create an observation for the light value, on the **Observations** page:
+* click on **ADD OBSERVATION...** 
+* for **Observed resource**, select **/light/value/**
+* for **Observation name**, you can keep the proposed default value, **light**
+* for **Send events to**, select **Cloud Stream**
+* enter a description
+* click on **SAVE**
+
+The newly created observation is added to the list of observations:
+
+![light1-observation](uploads/ee388e7c6e4d3816ebee50f7b3a32d30/light1-observation.png)
+
+## Stream
+
+Go to the **Streams** page. Click on the **light** stream that has been automatically created. All received values are displayed there:
+
+![light1-stream](uploads/d4ce258fab7ef132f4c7e6be8fe5500b/light1-stream.png)
+
+(Don't pay attention to the strange name that appears in the stream path. [I renamed my device, but the path kept the original name](https://forum.sierrawireless.com/t/renaming-a-device/18171).) 
\ No newline at end of file