Add rudimentary WebRTC support via go2rtc #162
Closed
Conversation
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
closes Ankermgmt#131 Starting with the new firmware releases to anker make printers in the past few weeks, MQTT no longer connects. There is a field in the mqtt msg that expects 11 zeroes. these 11 bytes are no longer all zeroes. I switched the protocol to expect just bytes here since we did nothing with the zeroes to begin with this should be a backwards compatible change. Pasted below is a snippet from my terminal printing out the padding field. you'll see 2 bytes in the middle of the 11 that are no longer zeros. ``` [*] Padding: 0x0 0x0 0x0 0x3c 0x11 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0x95 0x15 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0xc6 0x20 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0x5c 0x1d 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0xa9 0x18 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0xfa 0xf 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0x99 0x21 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0xd6 0x15 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0x4c 0x9 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0x3d 0x13 0x0 0x0 0x0 0x0 0x0 0x0 [*] Padding: 0x0 0x0 0x0 0xe3 0xb 0x0 0x0 0x0 0x0 0x0 0x0 ``` Screenshot showing all green on the web ui after my change <img width="1036" alt="image" src="https://github.com/Ankermgmt/ankermake-m5-protocol/assets/22949655/9efce17f-a1e2-44cc-b2a7-1550c211a10c">
1.0.1 - Fix mqtt bug release
Enables the `/video` endpoint to work with WebRTC. (At least via go2rtc using `ffmpeg:<url>/video`)
Honestly I have no idea why this wasn't throwing errors at me before
Closed
|
superseded by #160 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I didn't explore too many options here, but I was able to get a restream via go2rtc/frigate by simply running the ServiceManager on the
/videoendpoint. Using this I am able to add a low latency camera feed to my Home Assistant dashboard.EDIT:
Usage in Home Assistant:
Using go2rtc
go2rtc.yaml(https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#go2rtc-home-assistant-add-on)Alt: Frigate config
Note: Frigate just runs go2rtc
config.ymlLovelace Card (Home Assistant)
Add WebRTC integration from HACS (https://github.com/AlexxIT/WebRTC?tab=readme-ov-file#installation)
Use either
http://<go2rtc_ip>:1984orhttp://<frigate_ip>:1984when configuring the integration, reboot and add aCustom: WebRTC Cameracard to the dashboard:PPPP has a tendency to crash after a while - I'm working on a PR (which I've drafted into #160) that seems to be stable, but I'm still testing to make sure.