-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firmware version #1
Comments
That still needs to be tested. According to readme the port is still open in newer revisions, but not tested. |
I just bought this camera today and just connected it to power. |
Good stuff, I guess the correct url was just never published. Both of those URLs seem to give us 15FPS @ 1920x1080 with a bitrate of around 750kb/s so no difference from what I can see. I'll update the the readme. |
What version is your firmware, @fightforlife? |
@mouldybread @fightforlife i also got mine today. RTSP working out of the box. Firmware 1.01,09 (3.5.11-b04) |
@bartek810 Nope I haven't. I assumed (maybe incorrectly) that @fightforlife above had a newer device that shipped with a more recent firmware. It should be easy enough to test as you can currently upgrade and downgrade through the versions freely, but I ran out of time and needed to get the thing off my desk. It may forcefully upgrade itself if it can access the internet. I seem to recall a post complaining that their device went from 1.03 to 1.04 without user intervention, but I can't find the post to be refer back to. |
Just updated to 1.04.05 RTSP working well. |
I can confirm that rtsp is working with both "profiles" (or rather urls) with firmware 1.02.02(3.5.16-b06) that came with my cameras. This seems to have a small downside consisting in that the red/orange light on the cam keeps blinking as it's not able to reach dlink servers. Some black electrical tape over the led should fix that :) |
Interesting. I blocked all internet access after setup and have no issues with the LED blinking. This is with 1.02.02. |
For me it is the same as gurkburk76. Also the timestamp will always start at 01.01.2000 after reboot. |
This comment was marked as resolved.
This comment was marked as resolved.
I have the same issue as @waqaslam. I updated to 1.04.05, none of the RTSP urls are working and recovery webpage to invoke the downgrade does not exist. I did a quick nmap and it said the http port is now on 8080, but I think the webserver ignores all requests that don't match a specific path since just going to the 192.168.0.20:8080/ does not work. |
I have upgraded to 1.04.05 and can still access the profile0 stream. profile1 has been converted to some kind of echo show stream. The recovery web page is on port 80. |
This is the url I am using in vlc. Obviously you need to change the ip-address: |
Yep, my bad, I think I pushed the reset button too early in the boot phase. In my defense the orange and red look super similar... I now have the rtsp stream accessible. Thanks @ErikAndren |
yeah, my dcs got force-fed an auto update last night. it went up to 1.04.05. |
You can disable the auto-update in the mydlink app. |
i think that option is lost eh ? |
Indeed, this is because you are on the latest version. |
Hey. So is the highest firmware for RTSP 1.01?
The text was updated successfully, but these errors were encountered: