github-actions[bot]
commented
1 year ago 
Coverage Report
File Stmts Miss Cover Missing apps/qolsysgw gateway.py 158 31 80% 95–96, 131–154, 162, 187–188, 216–217, 226–227, 236–237, 243, 263–264 apps/qolsysgw/mqtt exceptions.py 17 0 100% listener.py 53 8 85% 42–44, 68–70, 74–75 updater.py 238 7 97% 164, 212, 215, 333, 384, 462, 540 utils.py 5 0 100% apps/qolsysgw/qolsys actions.py 50 2 96% 24, 34 config.py 70 13 81% 63–64, 66, 70, 75, 90–102, 112, 120, 146 control.py 151 7 95% 39, 47, 51, 58, 65, 81, 88 events.py 232 21 91% 64, 69, 100, 104, 130–131, 163, 167, 190, 201, 208, 235, 251, 265, 278–280, 325, 357, 369, 414 exceptions.py 29 0 100% observable.py 17 3 82% 13, 17–18 partition.py 120 7 94% 149–153, 159–163, 166 sensors.py 205 20 90% 57–78, 136, 194, 198, 205, 222, 226 socket.py 93 19 80% 36, 43, 52–54, 83–84, 103–105, 109–110, 114–116, 126–127, 133–134 state.py 64 3 95% 24, 74, 82 utils.py 47 4 91% 11, 14, 20–21 TOTAL 1549 145 91%
| Tests | Skipped | Failures | Errors | Time |
|---|---|---|---|---|
| 118 | 0 :zzz: | 0 :x: | 0 :fire: | 31.115s :stopwatch: |
This adds a
tamperedattribute to sensors indicating if the sensor is currently believed to be tampered with or not.This is not 100% accurate as it depends on specific sets of events that the panel is sending in a given order, which allow to guess if a sensor is currently tampered or not. This should be taken with a huge grain of salt as, for instance, we do not have that information when getting the summary state for the sensors from the panel (and will be able to know a sensor was tampered when it won't be tampered anymore).
More details are available at https://github.com/XaF/qolsysgw/issues/73 as to the identified interactions and how they are implemented here.
Closes #73