馃殌 Feature Request
The Samsung baby cameras seems to somehow reuse the same WyzeCam protocol (at least, I found the same libAVAPIs.so and libIOTCAPIs.so libraries on the device itself). The camera though is not using any cloud, and is only able to connect when in the same WiFi network. The only known application which is able to connect to theese devices is the BabyView application (https://play.google.com/store/apps/details?id=tw.com.surveillance.babyview2&hl=ru&gl=US).
馃攬 Motivation
There is no way to access these cameras data except by the help of the BabyView app, which, let's be honest, is buggy like hell. This could be another way to do it.
馃洶 Alternatives
Except using the BabyView official app, none.
馃搸 Additional context
The cameras aren't using any "tokens", but instead are using a some kind of a static "password". It may be converted into the same "token" by some algorythm (because the password itself is supposed to be only 8-15 characters long, so deriving it to a hex 32 characters seems to be doable). Also, the port on which the "AVAPIs_Server" is listening - is the port 9090/tcp and ports 37507/udp, 32761/udp. Apparently the actual used viewing username is "admin".
馃殌 Feature Request
The Samsung baby cameras seems to somehow reuse the same WyzeCam protocol (at least, I found the same libAVAPIs.so and libIOTCAPIs.so libraries on the device itself). The camera though is not using any cloud, and is only able to connect when in the same WiFi network. The only known application which is able to connect to theese devices is the BabyView application (https://play.google.com/store/apps/details?id=tw.com.surveillance.babyview2&hl=ru&gl=US).
馃攬 Motivation
There is no way to access these cameras data except by the help of the BabyView app, which, let's be honest, is buggy like hell. This could be another way to do it.
馃洶 Alternatives
Except using the BabyView official app, none.
馃搸 Additional context
The cameras aren't using any "tokens", but instead are using a some kind of a static "password". It may be converted into the same "token" by some algorythm (because the password itself is supposed to be only 8-15 characters long, so deriving it to a hex 32 characters seems to be doable). Also, the port on which the "AVAPIs_Server" is listening - is the port 9090/tcp and ports 37507/udp, 32761/udp. Apparently the actual used viewing username is "admin".