eufy-security-ws: `device.stop_livestream` does not generate an event as `livestream stopped`
Describe the bug
When I was using 0.3.3 version device.stop_livestream was succesfully generating livestream stopped event but I had tried latest (0.4.2) and I am not able to get respective event to detect the status
To Reproduce
Steps to reproduce the behavior:
- sent: {“messageId”: “start_livesteam”, “command”: “device.start_livestream”, “serialNumber”: “T8113N1320483643”}
- received: {‘type’: ‘event’, ‘event’: {‘source’: ‘device’, ‘event’: ‘livestream started’, ‘serialNumber’: ‘T8113N1320483643’}}
- sent: {“messageId”: “start_livesteam”, “command”: “device.stop_livestream”, “serialNumber”: “T8113N1320483643”}
- nothing specifically received
Expected behavior
to receive: {‘type’: ‘event’, ‘event’: {‘source’: ‘device’, ‘event’: ‘livestream stopped’, ‘serialNumber’: ‘T8113N1320483643’}}
Screenshots & Logfiles
N/A
Versions:
Docker version 0.4.2 (latest tag(
Additional context
N/A
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 28 (28 by maintainers)
Commits related to this issue
- Incremented schema version to 6 Added new commands `startRTSPLivestream`, `stopRTSPLivestream` and `isRTSPLiveStreaming` to Station Fixed issue #15 Fixed issue #27 Updated dependency eufy-security-cli... — committed to bropat/eufy-security-ws by bropat 3 years ago
- Truly fixed issue #27 Updated dependency eufy-security-client to 1.2.1 Updated dependency commander to 8.3.0 Updated dev dependencies — committed to bropat/eufy-security-ws by bropat 3 years ago
@fuatakgun Version 0.5.1 released
Got it, thanks, i will check