btsimonh

example: rtmp://192.168.1.173:7010/live/1jfiegbqdqhxq_p0_JCWJXJQCIPOJ example RTSP: rtsp://192.168.1.173:7020/live/1jfiegbqdqhxq_p0_JCWJXJQCIPOJ The JCWJXJQCIPOJ bit changes sometimes. Although trying now, re-logging on to the camera seems to give the same URL; so not sure what prompts it...

ohh.. good find. interesting a google search of v5.7.1.1807031100 gives a set of companies who use this.... And the extraction provides all the mlib. libraries that I had to reverse...

hi Lexridge, if your based version is 4.6.2.1706161621, then the upgrade hack file should take with the manual upgrade method. Would be good to get the url to the v5.1.8.1807231703...

the new upgrade patch is http://209.133.212.170.2080/version/ipc/gm8136/v5.1.6.1804251402/ipc_pack_patch_from_v4.6.2.1706161621.rtl8188fu_to_v5.1.6.1804251402.rtl8188fu.bin I have not yet made a modified upgrade file from this.

@Lexridge - 'I wonder if the fw needs to be signed before it will accept it?' - read the upgradefileformat part of the wiki - yes, it's easy to modify...

you could have a look at my hacked about node-red flow, which operated various interfaces of the camera, including I think getting a URL. It's in the repo. (if you...

it's been a long time since I worked on the camera :). If you have the time, then fire up node-red, and examine the flow; it's a very 'developmenty' flow,...

i don't think so. A small node server which generates the address and serves the image on a static address was my solution.

Hmm... I did not try the USB; you would need a cable with which you could both power it and plug in a usb device; but i suppose there is...

not worked on it for a long while.... so consider it historical information. They probably closed a lot of the holes :(.