5a9c3fea70
Some of the compatible hardware sends event signals that wouldn't map well to entities, e.g. NTP sync notifications, SIP registering information, or « doorbell button pressed » events with no « return to rest state » matching event to have a properly behaved binary sensor. Instead of only monitoring specific events, subscribe to all of them, and pass them through (in addition to handling them as before if they correspond to a configured binary sensor). Also bump python-amcrest to 1.7.2. Digest of the changes: * The library now passes through the event data instead of just presence of a "Start" member in in. * Connection to some devices has been fixed by not throwing the towel on minor errors. https://github.com/tchellomello/python-amcrest/compare/1.7.1...1.7.2 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| binary_sensor.py | ||
| camera.py | ||
| const.py | ||
| helpers.py | ||
| manifest.json | ||
| sensor.py | ||
| services.yaml | ||