This shows you the differences between two versions of the page.
hardware:cflink:rules [2014/01/13 05:03] jarrod |
hardware:cflink:rules [2014/01/13 05:04] (current) jarrod |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Rules (Event Triggering) ====== | + | ====== Rules CFLink Protocol (Event Triggering) ====== |
- | ===== Overview ===== | + | ===== Rules Overview ===== |
Rules allow each device on the CFLink network to perform actions based on string matching of outgoing data on the CFLink bus.\\ | Rules allow each device on the CFLink network to perform actions based on string matching of outgoing data on the CFLink bus.\\ | ||
Line 8: | Line 8: | ||
For more details on how to configure rules, please see our [[hardware:rules|general rules tab entry]] on our wiki. | For more details on how to configure rules, please see our [[hardware:rules|general rules tab entry]] on our wiki. | ||
- | ===== Rules Protocol ===== | + | ===== Rules CFLink Protocol ===== |
Due to the storage requirements on CFLink devices, all rules on a device must be transfered in one process. Single rules cannot be added/edited/removed without sending all other rule information stored on the device at the same time. This means there are only three CFLink messages used to manipulate rules on a device, Write, Read and Delete. | Due to the storage requirements on CFLink devices, all rules on a device must be transfered in one process. Single rules cannot be added/edited/removed without sending all other rule information stored on the device at the same time. This means there are only three CFLink messages used to manipulate rules on a device, Write, Read and Delete. |