For those who are interested, the other post I just mentioned is now here:
http://forum.micasaverde.com/index.php/topic,11971.msg86883.html
Thanks
I don’t see how the camera plugin will cause the DSC plugin to fail. There must be something else that causes that.
Agreed - it’s still circumstantial at this point - other than the fact that the problem and the plugin happened at the same time, I don’t see a connection either, but will continue to t/s.
Does the camera plug-in do any thing out of the ordinary, or put any undue stress on any part of of the OS like the TCP/IP stack?
Only on the second run it sends some messages to the camera to configure it. Other than that no, it only registers a handler for a GET request from the camera, which runs only when the camera sends an alarm notification. But if I’m not mistaken, the camera doesn’t send these notifications continuously to put stress on the network and Vera.
To find if it’s this plugin that’s causing the issues with the DSC, temporarily disable the motion notification on the camera:
http://<camera_IP>/set_alarm.cgi?motion_armed=0&user=<user_name>&pwd=<password>To enable it use this URL:
http://<camera_IP>/set_alarm.cgi?motion_armed=1&user=<username>&pwd=<password>@MCVFLorin - Thank you for all your work on this plugin. I hooked my 2 new Foscam’s up to my Vera 3, configured them via my laptop, opened up the UI5 dashboard and both are present with a camera and a sensor. The cam image says ‘camera not responding’ but when clicking the View button, the image is fine. Not getting ‘not implemented’ on arm/bypass, but I;ve not checked that functionality yet. The are currently sitting in my office until I get power wired so they can go to the livingroom and be installed as ‘pooch cams’ so I can check on my dogs while at work.
This will save me some $$ as now I have a HTPC running with 4 webcams and the Athome solution to view those on my iPhone.
Now I should be able to check on my iPhone, Android tablet and hopefully my work PC.
If this works well, I may get a few more (when on sale again) and hook them up as outside camera’s under my eve.
Looks amazon has spillters that allow passive PoE for these. Will have to get the right plug size and see how much of a voltage drop I would get with about 40’ of cat6…
Amazon splitter → http://www.amazon.com/AIR802-POEPASS-01-Injector-Splitter-Connector/dp/B003DLJNWE/ref=sr_1_5?ie=UTF8&qid=1349562342&sr=8-5&keywords=foscam+poe
(Not sure if this is the right size plug, they have multiple sizes)
I’m having difficulty in getting motion detection to work on my foscam camera. Vera firmware is 1.5.408 and UI5. Using Foscam plug-in 2.4. Tried changing the ConfiguredMD to 1 to reset (after save and reload it reverted to 2). IP and MAC addresses look accurate. impl_file (I_FoscamPTZ.xml) and device_file (D_DigitalSecurityCamera2.xml) look accurate. Admin id and password are being used. I can switch between ARM and BYPASS without any issues. The Foscam camera is set to alarm mode and i have the camera sending notices when motion is detected so the camera’s motion sensor is working. When I poll the motion sensor within Vera I get Command Failed: No Implementation.
I have notification set in Vera whenever the sensor is tripped. Also set to archive a photo. No notifications or archived photos when the camera alarm occurs. Any ideas? Probably missing something basic, but have tried options from this and other forum threads.
What model cameras do you have?
If they are the H264 versions, then the motion sensor won’t work.
I have two FI8905W outdoor cameras. I plan to purchase a couple of add’l Foscam cameras, but I want to get motion detection working first with Vera. Motion Detection is working on the cameras themselves, but it is not being picked up by Vera. Also, this Vera is not secured (which another post indicated could be an issue).
The Secure This Vera issue was resolved in Foscam Plugin v2.3 (and newer)
http://forum.micasaverde.com/index.php/topic,11027.msg86586.html#msg86586
Please open this URL:
http://camera_ip/get_params.cgi?user=username&pwd=passwordand tell me the values of these parameters
[ul][li]alarm_http[/li]
[li]alarm_http_url[/li][/ul]
var alarm_http_url=‘http://192.168.1.149:3480/data_request?id=lr_foscam_tripped&sensor_id=38’;
var alarm_http=1;
sensor_id 38 is the id of the motion sensor for the camera that is at id 37.
Thanks
Those parameters look OK if that is the correct Vera IP. There’s one more parameter I forgot about, which also ca be seen with get_params.cgi:
alarm_motion_armed
It should be ‘1’.
You should look in the logs to see what happens when the camera notifies Vera about movement. The instructions to log in the console are here: http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
And to view the logs are here: http://wiki.micasaverde.com/index.php/Logs
Use this command to view the logs:
tail -f /var/log/cmh/LuaUPnP.log | grep 'lr_foscam_tripped'Upon future analysis by mcvflorin, the Vera IP address is stored in the camera’s advanced settings (VeraAddress). I’m using DHCP on the router, so there are situations in which the IP address for my Vera will change. This IP address in the camera’s advanced settings is not currently being updated by the Foscam app. Until the app is updated, the IP address must be manually adjusted in the camera’s advanced settings.
After making this change, I also changed the ConfiguredMD setting to 0, saved the changes and then reloaded LUUP. Afterwards, the motion detection appears to be working correctly.
Thanks mcvflorin!!!
I also had the issue of Motion Detection ceasing to work on one of my cameras. The solution for me was to add the Port Number to the IP address.
I then changed the ConfiguredMD setting to 0, saved the changes and then reloaded LUUP.
The result was that Motion Detection is now working correctly again.
Hello
I am having Trouble see my new foscam camera FI9820W with vera. I have tried to manually set it up but it will not recognize the camera. any help please
Scott
quick observations regarding motion detect and ptz on f18910w with firmware 11.37.2.46 and vera 1.5.408 firmware. first, if you didn’t catch it elsewhere in this forum topic, the foscam plugin changes hidden variables for motion detection on the foscam including whether or not to notify a server via http. if the ip of the camera or the ip of the vera or the id of the “virtual” motion detector device created by the plugin changes, that change will break motion detection. i believe that this is the cause of many of the “unable to configure camera” errors for ip-camera devices that are currently installed.
also, it appears that if the camera has been previously added to its current or a previous mios system and was then deleted or moved to another system, the current system will fail to automatically detect and install the camera. while one can still manually install the camera, he will have to send the arm-and-notify, http string mentioned above to the camera in order to restore motion detection on the vera3.
alternatively, one can reset the camera to factory settings. once this is done, the vera3 will see the camera and automatically install it as a wintop zcam as well as a foscam camera, if the foscam plugin is already installed on the system.
however, be sure that the ip and mac addresses in the new ip camera devices are correct because vera will create the devices as soon as the reset is done. since the foscam requires the user to connect to it via ethernet for initial setup, vera will create the devices using the ethernet ip and mac. if the user decides to access the camera via wifi subsequent to the initial setup, the ip will likely be different and the mac will certainly be different thus breaking the newly minted ip-camera devices that vera so kindly made just moments ago. replacing at least the ethernet ip with the wifi ip in the camera’s advanced settings and removing the ethernet mac will fix it. adding the wifi mac may be useful as well but i’m not sure.
finally, i have not been able to control pan and tilt with my setup as of yet. motion detection for scene control and security were my main concerns and it has taken me far too long to decipher that problem. so, it may be awhile before i devote significant time to ptz.
I did get ptz (not zoom) to work. In order for it to work, I had to keep the user name as admin with no password. For better security, I changed the port numbers by changing the ip address using the 192.xxx.xxx.xxx:xxx after the foscam plug-in automatically created the camera and motion-detecter devices. I also disabled dynamic dns and upnp.
[quote=“cableguy, post:115, topic:171931”]Hello
I am having Trouble see my new foscam camera FI9820W with vera. I have tried to manually set it up but it will not recognize the camera. any help please
Scott[/quote]
I do not believe the 8920 (H.264 model?) is fully supported yet.
I appreciate the plug in, worked the first time with the 8910 with no issues so far. I was wondering if it is possible to make the infrared portion work? Can the zoom be used to toggle the IR on and off?
Thanks.
the plug-in is not creating motion sensor devices for the latest batch of 8910’s with the 11.37.2.48 firmware. among other things, something prevents the creation of the VeraAddress field.
it could be the latest update of the plug-in (2.5). at any rate, i manually changed the ConfiguredMD variable to 0 (zero). this setting created motion sensor devices for me.
pan and tilt work now with 8910’s using username/password combinations and ports other than 80. attaboy.
don’t know if you’ve started coding sound sensor device. should be fairly simple addition. will look at i_foscam.xml and motion_device.xml tomorrow.