update esppilight lib

content of the library is not filtered on 433mhz only
This commit is contained in:
Florian committed 2018-11-28 20:41:37 +01:00
1 parent a275e48ee1
commit 67dd7ac078
1030 files changed
+203335 -116

No files matched your search

@@ -0,0 +1,187 @@
.. |yes| image:: ../../../images/yes.png
.. |no| image:: ../../../images/no.png
.. role:: underline
:class: underline
+------------------+-------------+
| **Feature** | **Support** |
+------------------+-------------+
| Sending | |no| |
+------------------+-------------+
| Receiving | |yes| |
+------------------+-------------+
| Config | |yes| |
+------------------+-------------+
.. rubric:: Supported Brands
+------------------+--------------+
| **Brand** | **Protocol** |
+------------------+--------------+
| KlikAanKlikUit | kaku_screen |
+------------------+--------------+
| DI-O (Chacon) | dio_screen |
+------------------+--------------+
.. rubric:: Sender Arguments
.. code-block:: console
-t --up send an up signal
-f --down send an down signal
-u --unit=unit control a device with this unit code
-i --id=id control a device with this id
-a --all send command to all devices with this id
-l --learn send multiple streams so screen can learn
.. rubric:: Config
.. code-block:: json
:linenos:
{
"devices": {
"screen": {
"protocol": [ "kaku_screen" ],
"id": [{
"id": 100,
"unit": 0
}],
"state": "down"
}
},
"gui": {
"screen": {
"name": "Screen",
"group": [ "Living" ],
"media": [ "all" ]
}
}
}
+------------------+-----------------+
| **Option** | **Value** |
+------------------+-----------------+
| id | 0 - 67108863 |
+------------------+-----------------+
| unit | 0 - 15 |
+------------------+-----------------+
| state | on / off |
+------------------+-----------------+
.. rubric:: Optional Settings
:underline:`GUI Settings`
+------------------+-------------+------------+-----------------------------------------------+
| **Setting** | **Default** | **Format** | **Description** |
+------------------+-------------+------------+-----------------------------------------------+
| readonly | 0 | 1 or 0 | Disable controlling this device from the GUIs |
+------------------+-------------+------------+-----------------------------------------------+
| confirm | 0 | 1 or 0 | Ask for confirmation when switching device |
+------------------+-------------+------------+-----------------------------------------------+
.. rubric:: Notes
If you want your switch to learn new codes, you can use the following command:
.. code-block:: console
pilight-send -p kaku_screen -i 1 -u 1 -t -l
If you want your switch to remove a learned code, you can use the following command:
.. code-block:: console
pilight-send -p kaku_screen -i 1 -u 1 -f -l
.. rubric:: Protocol
This protocol sends 132 pulses like this
.. code-block:: guess
286 2825 286 201 289 1337 287 209 283 1351 287 204 289 1339 288 207 288 1341 289 207 281 1343 284 205 292 1346 282 212 283 1348 282 213 279 1352 282 211 281 1349 282 210 283 1347 284 211 288 1348 281 211 285 1353 278 213 280 1351 280 232 282 1356 279 213 285 1351 276 215 285 1348 277 216 278 1359 278 216 279 1353 272 214 283 1358 276 216 276 1351 278 214 284 1357 275 217 276 1353 270 217 277 1353 272 220 277 1351 275 220 272 1356 275 1353 273 224 277 236 282 1355 272 1353 273 233 273 222 268 1358 270 219 277 1361 274 218 280 1358 272 1355 271 243 251 11302
The first 2 pulses are the ``header`` and the last 2 pulses are the ``footer``. These are meant to identify the pulses as genuine. We don't use them for further processing. The next step is to transform this output into 36 groups of 4 pulses (and thereby dropping the ``header`` and ``footer`` pulses).
.. code-block:: guess
286 201 289 1337
287 209 283 1351
287 204 289 1339
288 207 288 1341
289 207 281 1343
284 205 292 1346
282 212 283 1348
282 213 279 1352
282 211 281 1349
282 210 283 1347
284 211 288 1348
281 211 285 1353
278 213 280 1351
280 232 282 1356
279 213 285 1351
276 215 285 1348
277 216 278 1359
278 216 279 1353
272 214 283 1358
276 216 276 1351
278 214 284 1357
275 217 276 1353
270 217 277 1353
272 220 277 1351
275 220 272 1356
275 1353 273 224
277 236 282 1355
272 1353 273 233
273 222 268 1358
270 219 277 1361
274 218 280 1358
272 1355 271 243
If we now look at carefully at these groups you can distinguish two types of groups:
#. 272 1355 271 243
#. 274 218 280 1358
So the first group is defined by a high 2nd and the second group has a high 4th pulse. So we take either of these two pulses to define a 0 or a 1. In this case we say a high 2nd pulse means a 1 and a low 2nd pulse means a 0. We then get the following output:
.. code-block:: guess
00000000000000000000000001010001
Each (group) of numbers has a specific meaning:
- ID: 0 till 25
- All: 26
- State: 27
- Unit: 28 till 31
.. code-block:: guess
00000000000000000000000001 0 1 0001
- The ``ID`` is defined as a binary number
- The ``All`` tells us if a code was meant for all devices with the same ID
- The ``State`` defines whether a devices is opened or closed
- The ``Unit`` is also defined as a binary number
So this code represents:
- ID: 1
- All: Single
- State: Up
- Unit: 1
Another example:
- ID: 123456
- All: All
- State: Down
- Unit: 15
.. code-block:: guess
00000000011110001001000000101111
@@ -0,0 +1,4 @@
D-IO (Chacon)
=============
.. include:: _kaku.rst
@@ -0,0 +1,9 @@
Screens
=======
.. toctree::
:maxdepth: 1
kaku
d_io
kaku_old
@@ -0,0 +1,4 @@
KlikAanKlikUit
==============
.. include:: _kaku.rst
@@ -0,0 +1,173 @@
.. |yes| image:: ../../../images/yes.png
.. |no| image:: ../../../images/no.png
.. role:: underline
:class: underline
KlikAanKlikUit (Old)
====================
+------------------+-------------+
| **Feature** | **Support** |
+------------------+-------------+
| Sending | |no| |
+------------------+-------------+
| Receiving | |yes| |
+------------------+-------------+
| Config | |yes| |
+------------------+-------------+
.. rubric:: Supported Brands
+------------------+------------------+
| **Brand** | **Protocol** |
+------------------+------------------+
| KlikAanKlikUit | kaku_screen_old |
+------------------+------------------+
.. rubric:: Sender Arguments
.. code-block:: console
-t --up send an up signal
-f --down send an down signal
-u --unit=unit control a device with this unit code
-i --id=id control a device with this id
.. rubric:: Config
.. code-block:: json
:linenos:
{
"devices": {
"screen": {
"protocol": [ "kaku_screen_old" ],
"id": [{
"id": 16,
"unit": 0
}],
"state": "down"
}
},
"gui": {
"screen": {
"name": "Screen",
"group": [ "Living" ],
"media": [ "all" ]
}
}
}
+------------------+-----------------+
| **Option** | **Value** |
+------------------+-----------------+
| id | 0 - 31 |
+------------------+-----------------+
| unit | 0 - 15 |
+------------------+-----------------+
| state | on / off |
+------------------+-----------------+
.. rubric:: Optional Settings
:underline:`GUI Settings`
+------------------+-------------+------------+-----------------------------------------------+
| **Setting** | **Default** | **Format** | **Description** |
+------------------+-------------+------------+-----------------------------------------------+
| readonly | 0 | 1 or 0 | Disable controlling this device from the GUIs |
+------------------+-------------+------------+-----------------------------------------------+
| confirm | 0 | 1 or 0 | Ask for confirmation when switching device |
+------------------+-------------+------------+-----------------------------------------------+
.. rubric:: Notes
The old KlikAanKlikUit devices work setting two wheels: group (0-H) and device number (0-16). To control a device from pilight you need to send the correct group and unit id, these do not correspond 1:1.
A-1 on the unit corresponds with unit 0 id 0 in pilight A-2 on the unit corresponds with unit 0 id 1 in pilight etc.
.. rubric:: Protocol
This protocol sends 50 pulses like this
.. code-block:: guess
295 1180 295 1180 295 1180 1180 295 295 1180 295 1180 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 1180 295 1180 295 1180 1180 295 295 1180 1180 295 295 1180 1180 295 295 11210
It has no ``header`` and the last 2 pulses are the ``footer``. These are meant to identify the pulses as genuine, and the protocol also has some bit checks to filter false positives. We don't use them for further processing. The next step is to transform this output into 12 groups of 4 pulses (and thereby dropping the ``footer`` pulses).
.. code-block:: guess
295 1180 295 1180
295 1180 1180 295
295 1180 295 1180
295 1180 1180 295
295 1180 1180 295
295 1180 1180 295
295 1180 1180 295
295 1180 1180 295
295 1180 295 1180
295 1180 1180 295
295 1180 1180 295
295 1180 1180 295
295 11210
If we now look at carefully at these groups you can distinguish two types of groups:
#. 295 1180 1180 295
#. 295 1180 295 1180
So the first group is defined by a high 3th pulse and the second group has a low 3rd pulse. In this case we say a high 3rd pulse means a 0 and a high 3rd pulse means a 1. We then get the following output:
.. code-block:: guess
10100 00010 0 0
Each (group) of numbers has a specific meaning:
- Unit: 0 till 5 (inversed)
- ID: 6 till 10 (inversed)
- Fixed: 11 (always 0)
- State: 12 (inversed)
.. code-block:: guess
10100 00010 0 0
- The ``Unit`` is defined as a binary number
- The ``ID`` is defined as a binary number
- The ``Fixed`` is always 0
- The ``State`` defines whether a devices needs to be go Up or Down
So this code represents:
- Unit: 20
- ID: 1
- Fixed: always 0
- State: Down
Another example:
- Unit: 0
- ID: 4
- Fixed: always 0
- State: Up
.. code-block:: guess
00000 00100 0 1
Furthermore the protocol filters out false positives by checking if:
#. Every 1st bit of the first 12 groups of 4 bits is always LOW (0)
#. 2nd bit of the first 12 groups of 4 bits is always HIGH (1)
#. 3rd and 4th bit of the first 12 groups of 4 bits are different (NOT EQUAL)
#. Bits 49 and 50 are LOW (0) and HIGH (1) respectively (fixed footer)
This makes the protocol more accurate because it will respond rarely now when sartano commands are sent.