genericprontocommander
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| genericprontocommander [2010/07/29 20:53] – sestst | genericprontocommander [2018/11/03 02:59] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{:remotecontrol3_64.png|Control Item}} | + | {{:server: |
| ====== GenericProntoCommander ====== | ====== GenericProntoCommander ====== | ||
| This module is a part of the [[start|NetHomeServer]]. The GenericProntoCommander is dynamic control Item. You can add the available actions by specifying them in a Configuration File. Each action is defined as a Pronto Command that will be sent when the corresponding action is invoked. The GenericProntoCommander used is when you have a device (for example a radio controlled switch) which is not yet supported by NetHomeServer, | This module is a part of the [[start|NetHomeServer]]. The GenericProntoCommander is dynamic control Item. You can add the available actions by specifying them in a Configuration File. Each action is defined as a Pronto Command that will be sent when the corresponding action is invoked. The GenericProntoCommander used is when you have a device (for example a radio controlled switch) which is not yet supported by NetHomeServer, | ||
| The Configuration File is a text file with the following format: | The Configuration File is a text file with the following format: | ||
| - | //<Action Name1>//,//<Pronto Code1>// | + | < |
| - | //<Action Name2>//,//<Pronto Code3>// | + | < |
| - | //...// | + | ... |
| For example: | For example: | ||
genericprontocommander.1280429608.txt.gz · Last modified: 2018/11/03 02:57 (external edit)