1. The 932L does NOT have an OSD. Wish dlink would add it to the next FW upgrade.
2. Safari 6.0.5 with Mac OS 10.75 will NOT allow time, camera name, and some other changes in the ROM page. Sure, the entry is allowed, and it appears to have saved changes, but it does not change. Using Opera or SeaMonkey, the changes are always successful. It's ironic that Opera cannot be used to access mydlink.com, but can be used to change the camera settings via IP-ROM, while the reverse is true with Safari.
3. With Safari, the "Live Video" on the ROM page accessed by the IP in the URL line is static. It is not "live". The page can be refreshed or reloaded, but it remains updated and static. Quicktime often doesn't load. Not a big deal so long as mydlink website works.
4. There's no audio from the ROM page Live View.
5. In the settings section of "mydlink.com" the camera name is a selectable modifiable field. This is silly, as the camera name cannot be saved and changed here.
6. The 2132L and 932L really suck at WiFi reception. They should be more sensitive and perhaps have an exterior antenna. In order to make my cameras work well or work at all, three dlink routers are in my small 1200 square foot home. To have good audio and video, five to ten feet camera to router distance works. Most of the issues with my setup were just that. Being more than 25 feet from the wireless router. As the distance was shortened from 25+ to 5 feet, the progression was: no connection at all ----> connection with black view -----> video stuttering and buffering ----> video uttering ---> video and audio fine.
7. Waiting on hold for 10-50 minutes with dlink support really sucks. It's not so much the long wait, as the obnoxious, repetitive, constant, non-stop, loud male voice announcing dlink products and the apologies for the "unexpected" number of calls. Very irritating. Improve these cameras and there will be fewer calls needed.
8. The faq browser page at mydlink needs an overhaul (https://www.mydlink.com/faq/mydlink/ans3)
a) what do the "x" and "o" represent ? There is no legend.
b) IE8 is not available for Macintosh, but it's marked as it is available.
c) dlink should add more browser selections for both PCs and Macs
9. Several of my cameras would not connect wirelessly. After the usual ten seconds of a hard reset (using the recessed contact) and the latest setup program, they still would not detect a network. However, after using 40 second depression of the reset button, then unplugging the camera for ten seconds, then it would detect the wireless signal. Now I never use anything less than a 30 second reset depression.
10. The many reviews and documentation of these cameras document that the IR transmission is poor. Separate and mountable IR LED lamps are available, nearly invisible (much less apparent that the IR light(s) on these DCS cameras), and work well with a range 25 to 100 feet. There have light sensors and the LEDs produce very little heat.
11. Don't upgrade the firmware unless it's necessary, and save the older firmware file in case you need to downgrade. "If it isn't broken, don't fix it" and "newer isn't always better".
12. Wish these cameras were not white. I'm experimenting with ways to make them less obvious and blend with the background, such as plastic paint, adhering colored paper, etc. but without covering up the important structures, such as the lens and sensors.
13. For convenience, I've added the last one or two digits of the IP address to the OSD camera name. So "Attic23" means that this camera is accessible via 192.168.0.23.
14. Some users do not want their cameras posted on mydlink. There are ways to view them remotely via port forwarding when the user is not home. Amazon comments have suggestions on accessing these cameras NOT through mydlink.com. Does this forum here have such directions on how to reprogram one's router to access the audio and video of each camera if not using mydlink.com ?
NEXT: Add microSDs to the 2132L and setup video captures.