D-Link Forums
The Graveyard - Products No Longer Supported => IP Cameras => DCS-932L => Topic started by: JavaLawyer on January 02, 2014, 10:52:51 AM
-
D-Link released firmware version 1.07 build 02, located here: DCS-932L Firmware v1.07b02 (http://pmdap.dlink.com.tw/PMD/GetAgileFile?itemNumber=FIR1300699&fileName=DCS-932L_A2_FWv107%20b2.zip&fileSize=3648558.0;437760.0;).
If not already present, please be sure to add the .zip extension on the downloaded file and extract the contents prior to uploading to the DCS-932L.
Please post your comments and observations on this thread. :)
-
This latest firmware is a major release with new functionality we've requested over the past year:
Firmware: 1.07b02 - Date: 12/26/2013
- [New Feature] Add schedule feature for motion detection function (Thank you D-Link!!!!)
- [New Feature] Add user can configure interval setting for motion detection of mail/ftp
- [New Feature] NTP source port change to port 123
- [New Feature] User account name is limit as: 0-9, a-z, A-Z, ., -, _
- [New Feature] Update Mydlink agent to v2.0.17-b31
- [New Feature] Limit Auto FTP image frequency not over 5 frames/second
- [Bug Fix] Fixed ip task will be restarted issue on DHCP renew time
- [Bug Fix] Fixed E-mail/FTP cannot be started issue if motion detection is enabled first
- [Bug Fix] Fixed UpnP issue with DIR-826L router
- [Bug Fix] The max length of Admin password change to 32 characters
DCS-932L - Cumulative Firmware Release Notes (http://forums.dlink.com/index.php?topic=42617.0)
-
On testing it seems to work OK. Just one point, when I first set a schedule it didn't work. Probably because the current time was already between the start and stop times. I'm guessing it just sets system events to turn it on and off. When I tested it again by setting the start time a few minutes from the time when I saved the changes, it did start detecting motion at the set time. I would have thought that when you saved the schedule settings that it would detect from the system time whether it was inside the set interval and turn detection on or off accordingly, but it doesn't seem to work that way. I guess I can live with that as long as I know.
-
On testing it seems to work OK. Just one point, when I first set a schedule it didn't work. Probably because the current time was already between the start and stop times. I'm guessing it just sets system events to turn it on and off. When I tested it again by setting the start time a few minutes from the time when I saved the changes, it did start detecting motion at the set time. I would have thought that when you saved the schedule settings that it would detect from the system time whether it was inside the set interval and turn detection on or off accordingly, but it doesn't seem to work that way. I guess I can live with that as long as I know.
I believe the scheduled start time is the trigger that executes the motion detection tracking. If the scheduled start time already passed when the event is created/saved, then the FW waits for the start of the next scheduled event. :-\
-
The new firmware is working well for me although there is a bug that has carried over which I will detail here for you
The bug is in the daylight saving time feature where the daylight saving time period encompasses two calendar years, which is the case for us in the Southern Hemisphere (as opposed to the Northern Hemisphere where the daylight saving time is all contained in one calendar year).
(Setup-Time and Date-Automatic Time Configuration-Daylight Saving)
Our daylight saving runs from 2am 1st Sunday in October to 2am 1st Sunday in April. Entering those details into the DCS-932L (firmware 1.06 and 1.07) and then rebooting does not effect the correct change in the unit's time during daylight saving time.
The firmware seems to struggle with the end date crossing over into a new year - to prove this theory I put in a start day at the start of the calendar year (1st Thursday in January) and the end day as our correct ending day of 1st Sunday in April, following rebooting the correct Daylight Saving time is displayed (given the current date is within that period).
Moving the start date back to the 1st Sunday in October and re-booting results in the standard "non daylight saving time" being incorrectly displayed.
I expect this bug is easily reproduced on any DCS-932L by entering our daylight saving details (2am 1st Sunday in October to 2am 1st Sunday in April).
FWIW Time Zone is +10 (Melbourne)
Cheers
Scott
-
Hello, i recently purchased the DCS-932L, (Jan. 8, 2014) works wonderfully but 2 days after install i received a message on my cell phone upon opening the "MyDlink" App on my iPhone saying that a new firmware is ready to download. I went thru the process of going to the website, settings etc. And also taking my cameras down and connecting them to my router (3 cams total) and i received a message saying that my cams have been successfully updated I CAN SEE MY CAMS but now on my iPhone App an
" ! " mark shows up on the day/night icon and every time i try to use the day/night button option it says that "A new firmware is ready" over and over and cannot get rid of it or use the option of switching from day to night view because this message keeps popping up. I also tried deleting the App and re-downloading on my phone but nothing... Any advise? Is it a bug? My Laptop says i have Version/Firmware 1.07 after "update"
-
I am having the exact same issue as leoboy692000. After successfully upgrading two DCS-932L cameras to 1.07b02, the Day/Night button on the iPhone mydlink Lite app is overlaid with an exclamation mark and prompts for a firmware upgrade when pressed (making it impossible to toggle views). Both the mydlink web access and the mydlink+ app (iPad) work fine.
-
Having the same issue above. On the DLINK app, when selecting "remote" I have an ! on the day/night toggle. Message says that there is a new firmware available. When selecting "local" there is no day/night toggle available. Seems maybe there needs to be a DLINK app update?
-
I have the same issue as those 3 above on the Android app. The famous "!" on the day/night toggle. I guess we see an updated app or an updated firmware soon to resolve this issue?
-
I replicated this error with my DCS-932L using mydlink+ on an iPhone. :-[
-
I have the same issue as well. The upgrade was done correctly and the device shows the correct version in the web interface of the camera and mydlink site, but in the mydlink lite application on my iPhone, it shows the "!" on the day/night toggle icon. Clicking the day/night toggle icon in the mydlink lite app will cause the update attempt and soon a message appears saying it has completed successfully. But the icon doesn't change and will still prompt to update after clicking it.
I have done the following and still get the same results, so it is either an issue with the new firmware (or newer mydlink agent) or the iOS mydlink lite application doesn't support this firmware/agent version yet:
Removed and reinstalled mydlink lite application => No change, problem still exists
Removed and readded camera from mydlink account => No change, problem still exists
Initialized/reset camera running the 1.07 firmware => No change, problem still exists
Downgraded firmware to 1.06 => Problem resolved, but new features in 1.07 not available
Upgraded back to firmware 1.07 => Problem is back
-
I can't find the option to send the notification emails to my gmail account which I had setup for this purpose only. It was working fine before the upgrade, now the setting defaults to my main email address ("When enabled, notifications will be sent to your mydlink registered e-mail address when specific events occur.") and there's no option to change that. I can receive hundreds of emails during the week and I don't want them coming into my main email account. When I click on Advanced Setting, it opens up the camera settings which has the old settings (gmail) but I can't use motion detection settings there as it complains about invalid certificate and the video doesn't appear at all even though I have latest Java version. I don't even know which setting is going to be used by the camera - the actual camera setting (accessed via the IP address of the camera) has different email address than the one setup by the dylink website.
-
. . . I can't use motion detection settings there as it complains about invalid certificate and the video doesn't appear at all even though I have latest Java version. I don't even know which setting is going to be used by the camera - the actual camera setting (accessed via the IP address of the camera) has different email address than the one setup by the dylink website.
Updating to the most recent version of Java may cause the Live View for some D-Link network camera models to not work properly when viewed from a web browser. This latest update may impact other browser-based network camera functions as well. The procedure described in the link below be used to adjust the Java security exceptions in Windows after updating to the latest Java version to restore access.
Network Cameras - Lost "Live View" After Installing Java Version 7 Update 51 (http://forums.dlink.com/index.php?topic=57476.0)
-
To my observation, interval setting for motion detection email sending does work as I expected : with the default value of 300s I would expect that after a first motion detection email, no email would be sent during the next 5 minutes ... and I can receive at least 2 or 3 emails per minutes if any activity continues in the field of view.
Maybe I misunderstood the purpose of this parameter.
-
Hi bollee,
you took me speed, I think like you, the New Feature "Add user can configure interval setting for motion detection of mail/ftp" doesn't exist ??? or maybe it's very well hidden...
Because for me the setting 'Interval' was already there in the last FW 1.06. It is used for the 2 options 'always' and 'schedule' but absolutly not for the motion detection.
I hope I'm wrong and someone nice tells us where this feature are.
++
-
What happened to receiving notifications with photos with motion detection ??? I used to be able to get photos emailed to me when there was motion detected. Now all I get is an email with says motion was detected. What the hell am I supposed to do with that ??? I bought 4 cameras for this feature so that I can keep evidence of any intruders. Having just a notification is completely useless to me as most of them are caused by background movements (etc wind or shadows). I am ready to return all my cameras. The upgrade has f***ed up a perfectly working solution. >:(
-
I actually receive pictures with notification email in motion detection mode (3 pics before and 3 after).
Works great with my gmail account, but had issue with another account (probably need to find the right smtp port/auth combination).
-
Updating to the most recent version of Java may cause the Live View for some D-Link network camera models to not work properly when viewed from a web browser. This latest update may impact other browser-based network camera functions as well. The procedure described in the link below be used to adjust the Java security exceptions in Windows after updating to the latest Java version to restore access.
Network Cameras - Lost "Live View" After Installing Java Version 7 Update 51 (http://forums.dlink.com/index.php?topic=57476.0)
This trick works for me when using firmware 1.06, but not with 1.07. With 1.07 it won't show any Java picture, including the one used to setup motion detection. There is no error message, just a message asking to go to Java website and install Java. I have Java 7U51. I came back to 1.06 with my 4 cams.
-
I'm having the issue that I can't access the cam after upgrade via the iPhone App.
That's for the 'Remote' view. it shows the white cross in a red circle and is not accessible...
Local works...
Anyone?
Thanks!
-
can't get the upgrade to take. I tried 3 times on both the 930 and 932 using the proper file. They seem to upload okay the devices reset and come back online. When I go to check their status they still show the older version. I am doing this over wifi, do they need to be hard connected to my router or is there another issue I am not aware of at this time?
-
can't get the upgrade to take. I tried 3 times on both the 930 and 932 using the proper file. They seem to upload okay the devices reset and come back online. When I go to check their status they still show the older version. I am doing this over wifi, do they need to be hard connected to my router or is there another issue I am not aware of at this time?
What browser are you using (there may be some UI dependencies)?
-
tried Chrome and IE11.
-
tried Chrome and IE11.
Try Firefox or an earlier version of IE.
-
Hello, all.
I'm attempting to do a firmware upgrade on my 932L with the upgrade linked to in the opening post to this thread, but, although I get a 'Firmware upgrade completed' message when done, I'm showing no change to the firmware currently installed.
Firmware prior to AND post upgrade:
Current Firmware version: 1.07
Current Firmware date: 2013-07-30
Current Agent version: 2.0.17-b31
I've attempted to install the new firmware using IE 11 running in compatibility mode and from Chrome. I confirm that both the 932L and the computer being used are both connected to the router via ethernet cable.
I attempted to do a 'factory reset' using the 932L's UI, but this fails as well.
Can anyone help?
TIA.
-
Hello, all.
I'm attempting to do a firmware upgrade on my 932L with the upgrade linked to in the opening post to this thread, but, although I get a 'Firmware upgrade completed' message when done, I'm showing no change to the firmware currently installed.
Firmware prior to AND post upgrade:
Current Firmware version: 1.07
Current Firmware date: 2013-07-30
Current Agent version: 2.0.17-b31
I've attempted to install the new firmware using IE 11 running in compatibility mode and from Chrome. I confirm that both the 932L and the computer being used are both connected to the router via ethernet cable.
I attempted to do a 'factory reset' using the 932L's UI, but this fails as well.
Can anyone help?
TIA.
The firmware file in the first post to this thread is v1.07 which matches the results you are posting in your post. The version should read "1.07" following the upgrade. It sounds like you already had that version installed if the web UI indicated the same version before and after.
-
perhaps the date code of the file is what was throwing me off. If there is a new downloadable file the date code of the file should be different on the camera after the upgrade but for me it was not.
-
perhaps the date code of the file is what was throwing me off. If there is a new downloadable file the date code of the file should be different on the camera after the upgrade but for me it was not.
Is it possible your devices may have already had the 1.07 firmware installed to begin with?
Also, have you considered installing the new 1.08 firmware (http://forums.dlink.com/index.php?topic=58241.0)?
-
The firmware file in the first post to this thread is v1.07 which matches the results you are posting in your post. The version should read "1.07" following the upgrade. It sounds like you already had that version installed if the web UI indicated the same version before and after.
Very odd given that - as DryBnz noted - I would have expected the date code to be recent. From the camera's support page, I would have expected a 2014-02-11 date [see: http://support.dlink.com/ProductInfo.aspx?m=DCS-932L]
If you're running a 932L as well, would you confirm the Agent version via your web UI?
TIA.
-
Very odd given that - as DryBnz noted - I would have expected the date code to be recent. From the camera's support page, I would have expected a 2014-02-11 date [see: http://support.dlink.com/ProductInfo.aspx?m=DCS-932L]
If you're running a 932L as well, would you confirm the Agent version via your web UI?
TIA.
The dates on the support site "may" be the dates the files were posted on the website (not sure). The date that you see after you install the firmware is the build date (i.e. date the code was compiled), which is unrelated to when it was posted.
-
so the build date of the patched version is the same build date at the original version. I get it now.... :D
-
so the build date of the patched version is the same build date at the original version. I get it now.... :D
I would focus on the installed version number rather than the date.
-
So how will you know which version of 1.07 you have installed if there are multiple versions With the same build date and version number? This doesn't make sense. I'm done with this nonsense.
-
So how will you know which version of 1.07 you have installed if there are multiple versions With the same build date and version number? This doesn't make sense. I'm done with this nonsense.
There is only one v1.07 marked for ww distribution with multiple download locations available to obtain the file.
If you know of multiple versions, please provide the download locations.
-
The dates on the support site "may" be the dates the files were posted on the website (not sure). The date that you see after you install the firmware is the build date (i.e. date the code was compiled), which is unrelated to when it was posted.
I think something else is going on here as I again experienced issues with the cam yesterday, at which point I did a factory reset. The firmware, however, still reads as v1.07, which doesn't make sense as the camera was purchased in January 2012.
-
I think something else is going on here as I again experienced issues with the cam yesterday, at which point I did a factory reset. The firmware, however, still reads as v1.07, which doesn't make sense as the camera was purchased in January 2012.
The factory reset procedure purges all user settings, but does not impact the currently installed firmware version (i.e. these cameras do not store factory installed FW in ROM memory)
-
The factory reset procedure purges all user settings, but does not impact the currently installed firmware version (i.e. these cameras do not store factory installed FW in ROM memory)
Good to know, thanks.
I'm having connection issues, both on the smartphone and the laptop. Same issues that lead me to upgrade the firmware, but they still persist. Odd thing is that these issues have only cropped up in the past week. Same wifi, same placement in the house, nothing has changed except the cam's performance.
-
Good to know, thanks.
I'm having connection issues, both on the smartphone and the laptop. Same issues that lead me to upgrade the firmware, but they still persist. Odd thing is that these issues have only cropped up in the past week. Same wifi, same placement in the house, nothing has changed except the cam's performance.
On your laptop, do these issues present themselves while connected to the web UI (on the same LAN as the camera) or only through mydlink?
-
On your laptop, do these issues present themselves while connected to the web UI (on the same LAN as the camera) or only through mydlink?
Both, whether wired or wireless.
Do you suspect something?
-
I presume the router and DCS-932L are set to DHCP? You may want to try reserving an IP address in the router (a good practice even if the camera was working properly). Also, for good measure, did you try changing channels on the router? Do you live in an area with significant wireless network congestion?
DCS Network Cameras - Should I Use DHCP, Static IP, or Reserved IP Address? (http://forums.dlink.com/index.php?topic=58018.0)
Network Cameras - Important Posts & Information (http://forums.dlink.com/index.php?topic=58121.0) (see included thread
-
I presume the router and DCS-932L are set to DHCP? You may want to try reserving an IP address in the router (a good practice even if the camera was working properly). Also, for good measure, did you try changing channels on the router? Do you live in an area with significant wireless network congestion?
DCS Network Cameras - Should I Use DHCP, Static IP, or Reserved IP Address? (http://forums.dlink.com/index.php?topic=58018.0)
Network Cameras - Important Posts & Information (http://forums.dlink.com/index.php?topic=58121.0) (see included thread
Just spent the past hour on the phone with Verizon FIOS tech support to assign the 932L its own IP addy. Still no joy as the connection remains unstable via mydlink and the web UI. I'm wondering if the server inside the webcam is going bad.
Bah.
-
Just spent the past hour on the phone with Verizon FIOS tech support to assign the 932L its own IP addy. Still no joy as the connection remains unstable via mydlink and the web UI. I'm wondering if the server inside the webcam is going bad.
Bah.
Forget about Internet access for a while and let's see if we can get this working in your LAN first. Assign a reserved IP address to the DCS-932L through your router. See if you can maintain a persistent connection to the camera in your LAN. . . You shouldn't have any issue leaving an open connection to the LIVE VIDEO page in the web UI in a browser on a PC within your LAN. Also, try moving the camera closer to the router to ensure the wireless signal is strong (ruling out other factors). The router should contain a status page indicating the signal strength of connected devices.
-
Forget about Internet access for a while and let's see if we can get this working in your LAN first. Assign a reserved IP address to the DCS-932L through your router. See if you can maintain a persistent connection to the camera in your LAN. . . You shouldn't have any issue leaving an open connection to the LIVE VIDEO page in the web UI in a browser on a PC within your LAN. Also, try moving the camera closer to the router to ensure the wireless signal is strong (ruling out other factors). The router should contain a status page indicating the signal strength of connected devices.
Right, so I've managed to maintain a persistent connection to it by assigning it a Static IP address, Primary and Secondary DNS and by selecting 'Infrastructure' as the network type.
Trouble is that I'm now ONLY able to access said connection via the the 'Local' on mydlink's app on my phone. If I go through www.mydlink.com, I'm told that I have no devices on my account.
So, how do I add a device to the 'Remote' portion of the mydlink app?
-
Right, so I've managed to maintain a persistent connection to it by assigning it a Static IP address, Primary and Secondary DNS and by selecting 'Infrastructure' as the network type.
Trouble is that I'm now ONLY able to access said connection via the the 'Local' on mydlink's app on my phone. If I go through www.mydlink.com, I'm told that I have no devices on my account.
So, how do I add a device to the 'Remote' portion of the mydlink app?
You need to run the Setup Wizard application again to add the device to your mydlink account. There's no other way to add the device.
-
1 hour, 6 mins into tech support and I've been kicked to level 2 support.
-
1 hour, 6 mins into tech support and I've been kicked to level 2 support.
Did you run the Setup Wizard again?
-
Firmware v1.08b02 is now out and addresses a critical security issue.
- DCS-932L - Firmware v1.08b02 - Comments & Observations (http://forums.dlink.com/index.php?topic=58727.0)
- DCS-932L - Cumulative Firmware Release Notes (http://forums.dlink.com/index.php?topic=42617.0)
- Network Cameras - Security Patch for Select Cloud Camera
(http://forums.dlink.com/index.php?topic=58241.0)