tutk xiaomi source camera not working using master docker version

[ptbsare]

Hi, @AlexxIT , I noticed you added support for the Xiaomi source tutk protocol in commit 5b1da84 - great work, by the way.

I'm using the Docker image ghcr.io/alexxit/go2rtc:master , but my tutk-protocol camera still isn't working. The camera model is chuangmi.camera.ipc019. Do I need to add special configuration parameters?

{
  "producers": [
    {
      "url": "xiaomi://xxx:cn@192.168.195.78?did=xxx\u0026model=chuangmi.camera.ipc019"
    }
  ],
  "consumers": null
}

I'm not seeing any related warnings in the logs. Also, my other cameras with cs2 protocol are working fine. Thanks again for your work.

[AlexxIT]

Looks like it works only for DaFang camera.
Now I'm trying to add mijia.camera.v1.
It's VERY crazy and difficult protocol. Can't promise anything.

[ptbsare]

hi @AlexxIT Yes! Absolutely, I completely understand and agree. You've already done excellent work.

Because a very large number of cameras within the Mi ecosystem still use the tutk protocol, adapting this protocol would provide a significant improvement. Adapting this protocol probably isn't easy, and I'm not asking for any promises, it's just that I happen to have quite a few of these cameras myself. If needed, I'd be happy to provide some testing.

The models I have are:

chuangmi.camera.029a02
chuangmi.camera.ip029a
chuangmi.camera.029a02
isa.camera.hlc6
chuangmi.camera.ipc019
madv.cateye.miowlv2

Currently, the first few models listed all work fine with CS2, but the last two (chuangmi.camera.ipc019 and madv.cateye.miowlv2) seem to use the tutk protocol and don't work.

[AlexxIT]

Some cameras have an error - no vendor available. This means that they are using a completely outdated protocol.
They are marked with a dash in the vendor column in my table: #1982

Are you sure madv.cateye.miowlv2 has "unsupported vendor: tutk" error on latest release?