Differences

This shows you the differences between two versions of the page.

--- livebox:hah_hahnode [2014/01/20 09:01] – [Output Node] brett
+++ livebox:hah_hahnode [2014/01/20 09:10] – [Configuring the jeenodeApplet.lua] brett
@@ Line 269: / Line 269: @@
 dbzoo.livebox.jeenode:attic.light
 </code>
+See [[livebox/hah_hahnode/nanode_gateway]] for advanced integration concepts.
 ===== Disabling / Renaming endpoints =====
@@ Line 347: / Line 349: @@
 So 120 is too small... 180 is fine - Personally I would make the TTL at least 2x the reporting cycle, this way you can miss ONE event and it won't time out as the 2nd one will reset things.  So I would use a TTL of 300 seconds.
-====== The Nodules ======
-===== Infrared Receiver node =====
-Block diagram of how the IRnode fits into the system
-{{:livebox:irnode-block-diagram.png}}
-{{ :livebox:35200_pv.jpg?200}} By attaching a Infrared receiver to a JeeNode unit we can relay the signal transmitted from the Remote Control to the HAH and produce an xAP message.  This message then becomes the hook for //User Applet// scripts to attach and take action.
-Typical configuration in the JeeNodeApplet.lua
-<code>
-IRNode = require("xap.irnode").IRNode
-...
-local nodes = {
-   [2] = IRNode{instance="jeenode:ir"},
-}
-</code>
-This configures the JeeNode with ID of 5 and with an attached IR sensor to relay messages, via RF, to the HAH unit.
-The IR sensor data pin is connected to
-^^ Port ^^ Type ^^ Arduino ^^ Signal ^^ Chip ^^
-|| Port 2 || DIO || Digital 5 || PD5 || pin 11 ||
-Once the IRnode.pde sketch is loaded onto your jeenode and the HAH is correctly configured, pressing a button on your remote control should produce a message like this.
-<code>
-xap-header
-{
-uid=FF08DBFE
-source=dbzoo.livebox.jeenode:ir
-hop=1
-class=IR.Comms
-v=12
-}
-ir.received
-{
-value=550717623
-type=1
-bits=32
-}
-</code>
-Note that this configuration is better suited to a JeeNode that is not battery powered.
 ====== Nodule I/O pins ======