Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dvsar]

Hi,

I just bought a DCS-2132LB after owning a DCS-933L for a while, and am having trouble
getting the DCS-2132LB to execute an Action in an Event which has been triggered.

I am running firmware 2.11.

I Enabled Video Motion on the Motion Detection setup screen, and added areas to trigger.
I verified the trigger is working from the system logs.

I went to the Event Setup.

I added a mail server, which is nothing fancy, but is reliable.

I ran a test and received an OK on the setup screen and received the test notification
on the email server.  (I also have photos arriving fine from the DCS-933L which is on
the same network.)

I added a Media of photo snapshots.  (I also tried syslog media with the same result I'm describing.)

I added an Event, enabled it, set the trigger to Video motion detection, and an action to
use my mail server and the snapshot media.  (I also used periodic trigger later which also shows up
in the log, but does not run the action.)

With this done, I see in the log trigger events, but the action does not seem to
be executed.

Since I can successfully create trigger events which are clearly logged, and since my
mail server test does work, as well as the 933L, it seems like something is going wrong
between the trigger and the action, preventing the action from executing.

I loaded firmware version 2.02 and this executes the action fine, photos are received in mail.
(Although video streaming seems less capable and I guess there's security fixes, so I'm
not happy with running the old version.)

I tried firmware version 2.10 and that does NOT work (same as 2.11.)  So with this amount of
experimenting, it seems as if there's a problem since 2.10.

So I'm hoping someone can tell me if I'm doing something wrong, or verify what I'm seeing,
and suggest a workaround or report that a fixed version on the firmware is being made?

I am in the US, and downloaded the firmware from the DLINK site.  I did not notice any
country specific information.  The file for the 2.11 version was named DCS-2132L_B1_FW_V2.11.00.bin

Thanks for any help,

Scott

[RYAT3]

I Enabled Video Motion on the Motion Detection setup screen, and added areas to trigger.
I verified the trigger is working from the system logs.

I added an Event, enabled it, set the trigger to Video motion detection, and an action to
use my mail server and the snapshot media.  (I also used periodic trigger later which also shows up
in the log, but does not run the action.)

With this done, I see in the log trigger events, but the action does not seem to
be executed.

Do you have sensitivity and percentage set properly on the motion screen?

Can you try another method, like to SD CARD?

[dvsar]

Do you have sensitivity and percentage set properly on the motion screen?

Can you try another method, like to SD CARD?

Yes, I have sensitivity set to 85% and verify the motion triggers in the syslog when I walk in front of the camera.

I also switched to use periodic triggers which also were shown in the syslog, yet still neither executed the action.

I do not have an sd card.  But since the mail test works on both ends, and since the 933L can send OK from the same location and basic config, and since the earlier firmware can send, I'm initially suspecting it's not the mail server.

Thanks,

Scott

[RYAT3]

I only have a dcs-2132l h/w A... so any test I'd do would be useless. Sorry. 
I do have ftp working on it.

[dvsar]

Thanks Ryat3,

Scott

[dvsar]

Hello?

Anyone from D-Link Technical Services going to reply?

What's the status on the DCS-2132LB Firmware?  Looks like there have been updates for other products.  This product seems relatively new so I'm assuming it's still supported?  When is an update for it due?

I really like the product.  But it's simply not functioning, and until someone at D-Link says otherwise, it looks as if it's been broke for a couple firmware releases?

Thanks,

Scott

[FurryNutz]

Link>Welcome!

• Link>What Firmware version is currently loaded? Found on the DCSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?

• Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
• Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.21  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

I see there is a v2.11 on the mydlink.com site....

1. Updated agent to 2.0.19b51n
2. Updated Digital Signature

Is all I see for this update. 

[dvsar]

Link>Welcome!

• Link>What Firmware version is currently loaded? Found on the DCSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?

• Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
• Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.21  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

I see there is a v2.11 on the mydlink.com site....

1. Updated agent to 2.0.19b51n
2. Updated Digital Signature

Is all I see for this update. 

Thanks for the reply.

I think I already answered what firmware I've tested and am using.  I've already stated I'm in the USA.

I'm using a linksys wrt54g under an Arris tg862g/ct.

My first post does have a lot of debug information.

Thanks,

Scott

[FurryNutz]

Thanks for the reply.

I think I already answered what firmware I've tested and am using.  I've already stated I'm in the USA.

I'm using a linksys wrt54g under an Arris tg862g/ct. <This maybe your problem here. This is a older class router and the wireless only supports 54Mb wirelesss connections. For this camera to work well you need a router with at least 300Mb 2.4Ghz or 5Ghz wireless connection rate speeds.

My first post does have a lot of debug information.

Thanks,

Scott

[dvsar]

Thanks for the reply.

I think I already answered what firmware I've tested and am using.  I've already stated I'm in the USA.

I'm using a linksys wrt54g under an Arris tg862g/ct. <This maybe your problem here. This is a older class router and the wireless only supports 54Mb wirelesss connections. For this camera to work well you need a router with at least 300Mb 2.4Ghz or 5Ghz wireless connection rate speeds.

My first post does have a lot of debug information.

Thanks,

Scott

Hi,

Thanks for the reply.

Actually I made a mistake in my reply.  The cameras are not under the wrt54g.  Sorry about that.  Nothing in my first post involves the wrt54g.  I'm just use to including it when I'm describing my network.

Backing the firmware to 2.02 does work fine for delivery through the router (Arris).  And the 933L works fine through the Arris also.

So along with the other information I supply above, it looks like a firmware problem, no?  Something having to do with firing off an action in an event.

Thanks,

Scott

[FurryNutz]

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.21  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras.

I'd turn OFF one camera and reset one and set it up from scratch and configure triggers. Try to manually create the even or motion and see what happens.

Does this happen on the 933L?

[dvsar]

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.21  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras.

I'd turn OFF one camera and reset one and set it up from scratch and configure triggers. Try to manually create the even or motion and see what happens.

Does this happen on the 933L?

Hi,

The DCS-933L works fine all the time.

I've reconfigured this camera about a zillion times.  Before I go off to do that again, could you explain what each suggestion above is trying to address?  I'm not sure what the static IP and PnP setting have to do with sending an email out.  And as I said before, the old firmware does this fine, along side of the 933.

Are you sure there's not an issue with some of the newer firmware?

Thanks,

Scott

Editing to add more information:

The test email works every time, so I do not think it's a problem sending out emails.
Also I never mentioned that the camera also streams to mydlink lite on my phone just fine also.  It's just the Action under the Event which does not seem to fire.
Thanks.

[FurryNutz]

You could try going back to prior FW version and test.

There may have been some uPnP updates on recent FW versions and not having these features enabled could cause issues. I'd re-load prior FW and test.

[dvsar]

You could try going back to prior FW version and test.

There may have been some uPnP updates on recent FW versions and not having these features enabled could cause issues. I'd re-load prior FW and test.

Hi,

I tried the static IP and uPnP settings and they appear to have made no difference in the problem.

Edited to add: I also did these tests with the 933 unplugged this time.

I did try previous FW versions and the problem goes away when using version 2.02.

However, there's other issues in 2.02 which appear fixed since that version, so I can't use it as a solution.

Could you check to see if there's FW problems on this model and see when the next FW version is due?

Thanks,

Scott

[FurryNutz]

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.