canot run make

[icho40]

Hi,
I have tried to compile OnvifSoapLib as you suggested.
git clone https://github.com/Quedale/OnvifSoapLib.git
./bootstrap.sh
./configure --prefix=$(pwd)/build
make
Making all in src/generated
make[1]: Verzeichnis „/home/willi/onvif/OnvifSoapLib/src/generated“ wird betreten
CC /home/willi/onvif/OnvifSoapLib/subprojects/gsoap-2.8/gsoap/libgeneratedsoap_la-dom.lo
In file included from /home/willi/onvif/OnvifSoapLib/subprojects/gsoap-2.8/gsoap/dom.c:73:
/home/willi/onvif/OnvifSoapLib/subprojects/gsoap-2.8/gsoap/stdsoap2.h:743:11: fatal error: ntlm.h: Datei oder Verzeichnis nicht gefunden
743 | # include <ntlm.h> | ^~~~~~~~ compilation terminated.

[Quedale]

I just updated the README.md.
I've had too many issues with automake, so I now only support cmake builds.
You can try the updated instructions.

I know you have issue with OnvifDeviceManager and this project have sample files that could potentially help narrow down the issue.

After building this repository, you will have two executable samples.

1. ./release/client-test --ip=??? --port=??? --username=??? --password=??? --protocol=http
2. ./release/udp-test

client-test allows to test soap calls directly, while udp-test allows to perform discovery.

These samples allow you to perform isolated tests instead of running the entire OnvifDeviceManager client.

[icho40]

i got it running.
here are my logfiles
imou-error.log
udp-test-error.log
yi-error.log

[Quedale]

In regards to yi-error.log, it seems that the camera doesn't return the appropriate IP.

<tt:XAddr>http://192.168.178.13/onvif/media_service</tt:XAddr>
See how it didn't return 192.168.178.130. (Missing '0')
I would imagine this issue lies within your custom yi-hack firmware...

Now, this isn't exactly a correct behaviour, BUT it should be relatively common sense to fallback on the original IP provided.
I already do something similar with the port number and I highly suspect other clients does the same.

I'll try to handle such fallback gracefully and get back to you.

In regards to imou-error.log, is it possible you entered the wrong info by accident?
The first line shows creating device... [http://133:80/onvif/device_service.
133:80 is clearly not a valid ip:port, unless the 133 is the actual registered hostname.

[Quedale]

I just added rudimentary fallback mechanism which should allow your yi camera to work properly.

Although I would recommend looking into it. There may be some internal device configuration about which IP is advertised from the ONVIF device_service GetCapabilities.
Such configuration is often allowed to support reverse proxy frontend.
Basically having the camera returning a reverse proxy IP instead of its own.
In your case, it looks like a simple typo.

That being said, it should work now regardless...