-
Notifications
You must be signed in to change notification settings - Fork 195
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
support for raspyrfm hardware with unittest
- Loading branch information
1 parent
2ffea92
commit fddae90
Showing
12 changed files
with
1,086 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
Hardware | ||
======== | ||
|
||
- `Disabled`_ | ||
- `433.92Mhz`_ | ||
- `433lirc`_ | ||
- `433gpio`_ | ||
- `433nano`_ | ||
|
||
Introduction | ||
------------ | ||
|
||
.. warning:: | ||
|
||
Make sure pilight is not running before editing your configuration or else all changes will be lost. | ||
|
||
Since pilight 3.0 the feature to send and receive from multiple hardware modules has been introduced. This means you can control various different frequencies at the same time. However, only one module per frequency is supported. Each hardware module has its own syntax as listed below. | ||
|
||
Disabled | ||
-------- | ||
|
||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"none": { } | ||
} | ||
} | ||
433.92Mhz | ||
--------- | ||
|
||
.. _433lirc: | ||
.. rubric:: Lirc Kernel Module | ||
|
||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"433lirc": { | ||
"socket": "/dev/lirc0" | ||
} | ||
} | ||
} | ||
.. _433gpio: | ||
.. rubric:: Direct GPIO Access | ||
|
||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"433gpio": { | ||
"sender": 0, | ||
"receiver": 1 | ||
} | ||
} | ||
} | ||
The default configuration to be used with the pilight PCB. When using custom wiring, refer to http://www.wiringx.org for the pin numbering of the various supported devices. If you want to disable the sender or receiver pin, set it to | ||
-1. | ||
|
||
.. versionchanged:: 8.0 | ||
|
||
You must now specify which GPIO platform pilight is running on. Refer to the settings page for more information. | ||
|
||
.. _433nano: | ||
.. rubric:: pilight USB Nano | ||
|
||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"433nano": { | ||
"comport": "/dev/ttyUSB0" | ||
} | ||
} | ||
} | ||
The comport value needs to correspond to a valid COM device on your platform. On Windows this value is generally formatted as COM1, on Linux as /dev/ttyUSB0, and on FreeBSD /dev/cuau0. | ||
|
||
433.92Mhz / 868Mhz | ||
------------------ | ||
|
||
.. include:: ../hardware/_raspyrfm.rst | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
.. image:: ../images/raspyrfm.jpg | ||
|
||
.. rubric:: Config | ||
|
||
Example configuration for a RaspyRFM single 868 MHz | ||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"raspyrfm": { | ||
"spi-channel": 0, | ||
"frequency": 868350 | ||
} | ||
} | ||
} | ||
Example configuration for a RaspyRFM single 433 MHz | ||
.. code-block:: json | ||
:linenos: | ||
{ | ||
"hardware": { | ||
"raspyrfm": { | ||
"spi-channel": 0, | ||
"frequency": 433920 | ||
} | ||
} | ||
} | ||
.. note:: **RaspyRFM** | ||
|
||
The RaspyRFM is a radiomodule using the RFM69 from HopeRF. | ||
https://www.seegel-systeme.de/produkt/raspyrfm-ii/ |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
Oops, something went wrong.