Autolog Foscam HD Controller Discussion

Posted on
Thu May 23, 2019 4:12 pm
whmoorejr offline
User avatar
Posts: 369
Joined: Jan 15, 2013
Location: Houston, TX

Re: Autolog Foscam HD Controller Discussion

autolog wrote:
  • Disable the plugin.
  • Reboot the two cameras.
  • after 5 minutes, re-enable the plugin and see what happens.
First steps in problem support - switch it off and on again. :)


No luck there. I have other triggers that use python to pull camera images, plus I can view them from an NVR or from an IP Camera app on my phone. As far as I can tell, this error message is the only indication that there is something wrong. The only thing I can't do is use for motion triggers in indigo via the plugin.

Bill

Posted on
Fri May 24, 2019 4:49 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

I'll take a look at it but it might take a few days?

Not a lack of enthusiasm on my part but I don't use (my own) plugins any longer. :wink:
I have migrated to using Blue Iris running in a windows VM (VMWare Fusion) on my Indigo iMac.

So I will have to dig out a spare camera, make sure it is up-to-date and then re-install the plugins (Foscam and Dynamic).

I'll get onto that shortly and then I will also investigate the problem you reported with the Dynamic View Controller. :)

Posted on
Fri May 24, 2019 9:42 am
whmoorejr offline
User avatar
Posts: 369
Joined: Jan 15, 2013
Location: Houston, TX

Re: Autolog Foscam HD Controller Discussion

autolog wrote:
I'll take a look at it but it might take a few days?
Not a lack of enthusiasm on my part but I don't use (my own) plugins any longer. :wink:
I have migrated to using Blue Iris running in a windows VM (VMWare Fusion) on my Indigo iMac.


No worries, no rush. I'm actually getting close to scrapping it all for something different. I need to purchase a Lorex DVR (Analog cameras) for an install I'm helping with.... while I have it, I plan on tinkering to see if I can incorporate the CGI snapshots from the DVR into indigo. Why?

Running 10 IP Cameras over 2 NVRs means there are 12 devices that need to be in sync to avoid issues (motion detection settings, time/date, schedules, etc.). A lot of which is dependent on the ability to directly access and maintain each of the 10 IP cameras (staying on top of firmware updates, compatibility with OS X releases, etc.)

So... If I can pull snapshots into indigo from a DVR, that will reduce time spent maintaining cameras. (hopefully)

The next trick will be to figure out the best way to get indigo to recognize a DVR motion event. From https://blueirissoftware.com/technology/, it looks like Blue Iris will support a Lorex analog LHV series DVR if I can't see the DVR directly in indigo.

My favorite thing / use for your plugin was the non-analytic way it brought motion events into indigo.... minimal CPU usage. All the other solutions I'm exploring will probably have a much larger CPU impact.

Since about 98% of the DVRs and NVRs out there are running similar linux based software with digital alarm monitoring outputs... I'm surprised there isn't a generic plugin to act as an alarm center to receive those messages.

Bill

Posted on
Sat May 25, 2019 3:58 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

I have managed to reproduce the issue. :)

I have set up a Foscam R4 updated with the latest firmware (1.11.1.13 / 2.71.1.73).

I think you may have the Device Configuration setting for Camera platform set to Original and not Amba.

If I have it set to Original, I get repeated errors on line 514.

If I have it set to Amba, I get the error once as the states haven't been populated. It then runs OK and motion detection etc works.

Obviously the plugin should handle this situation. :wink:

Can you let me know if this is the case and if not I will dig deeper. :)

Posted on
Sat May 25, 2019 10:03 am
whmoorejr offline
User avatar
Posts: 369
Joined: Jan 15, 2013
Location: Houston, TX

Re: Autolog Foscam HD Controller Discussion

autolog wrote:
set to Original and not Amba.

If I have it set to Original, I get repeated errors on line 514.


That did the trick. You can put your shovel up, no further digging required. Many thanks.

Bill

Posted on
Sat May 25, 2019 10:10 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

Excellent - Thanks for letting me know :)

Posted on
Sat Dec 28, 2019 9:06 pm
Ricco offline
Posts: 6
Joined: Oct 13, 2013

Re: Autolog Foscam HD Controller Discussion

Has Foscam HD Controller disabled the other functions?
Foscam Controller had these settings :
Move Camera
Go to preset position
Set current location as preset
Stop Movement
Enable Streams
Disable Streams
Activate Motion Alarm
Deactivate Motion Alarm
Turn IR on
Turn IR off
Email Snapshot

Does anybody knows how to implement these old settings to the new Foscam HD Controller plugin?
Thank you!

Posted on
Sun Dec 29, 2019 2:59 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

Ricco wrote:
Has Foscam HD Controller disabled the other functions?

I didn't implement them as I didn't need them - so to be pedantic, not disabled (though the effect is the same!). :wink:
The plugin wasn't intended to be a clone of the previous version. :)

Ricco wrote:
Foscam Controller had these settings :
Move Camera
Go to preset position
Set current location as preset
Stop Movement
Enable Streams
Disable Streams
Activate Motion Alarm
Deactivate Motion Alarm
Turn IR on
Turn IR off
Email Snapshot


The plugin has actions for some of the above:
  • Activate Motion Alarm and Deactivate Motion Alarm are implemented as Motion Detection On, Motion Detection Off and Motion Detection Toggle.
  • Turn IR on and Turn IR off are implemented as Infrared On, Infrared Off and Infrared Toggle.

Ricco wrote:
Does anybody knows how to implement these old settings to the new Foscam HD Controller plugin?
Thank you!

Yes I do. :)

Do you need them all or particular ones?

Posted on
Mon Jan 06, 2020 10:50 pm
Ricco offline
Posts: 6
Joined: Oct 13, 2013

Re: Autolog Foscam HD Controller Discussion

I would love to have these back:
Move Camera
Go to preset position
Set current location as preset
Email Snapshot
Also, any idea how to trigger "cruise mode" on and off from indigo action?
https://www.google.com/search?client=sa ... 8&oe=UTF-8

I hope this is not too much to ask, thank you

Posted on
Tue Jan 07, 2020 11:37 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

Ricco wrote:
I would love to have these back:
Move Camera
Go to preset position
Set current location as preset
Email Snapshot
Also, any idea how to trigger "cruise mode" on and off from indigo action?
https://www.google.com/search?client=sa ... 8&oe=UTF-8

I hope this is not too much to ask, thank you

I'll see what I can do but it will be a few weeks before I can get round to it, other commitments permitting.

I will look at adding functions to Start Cruise and Stop Cruise. Setting up the cruise map will be best done in the Foscam App. I might upload the additions as I complete them rather than wait until I have done them all - so at least you will have something. :)

Posted on
Wed Sep 23, 2020 8:18 am
yassi offline
Posts: 419
Joined: Sep 06, 2015
Location: Germany

Re: Autolog Foscam HD Controller Discussion

I'm trying to add a Foscam D4Z camera which is already running and controlled by Surveillance Station on my Synology NAS.

However, in Indigo the camera shows "no ack".
Any ideas? Is maybe the camera not supported?
I've tried "Amba" and "Original"

The connection details are correct, tried already with port 88 and 443 which are defined in the camera settings.

Yassi
Attachments
Bildschirmfoto 2020-09-23 um 16.17.28.png
Bildschirmfoto 2020-09-23 um 16.17.28.png (19.01 KiB) Viewed 106 times
Bildschirmfoto 2020-09-23 um 15.54.35.png
Bildschirmfoto 2020-09-23 um 15.54.35.png (72.99 KiB) Viewed 106 times
Bildschirmfoto 2020-09-23 um 15.54.46.png
Bildschirmfoto 2020-09-23 um 15.54.46.png (12.04 KiB) Viewed 106 times

Posted on
Wed Sep 23, 2020 9:48 am
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

I have just checked the latest API and I can't see anything that has changed that should affect the plugin. :?

You could try turning on all debugging in the plugin config, then reload the plugin and then search the plugin log for your camera's IP string to see if that shows anything.

After the plugin starts, you should see something in the log like:
2020-09-23 16:32:48.885 DEBUG Plugin.MonitorSend.run Command Sent To Camera Gartenamera [192.168.100.???:88]: http://192.168.1.???:88/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getSystemTime
You should then be able to see a response which may be:
2020-09-23 16:34:06.342 DEBUG Plugin.DebugReceive.run No Response from camera Gartenamera [192.168.1.???:88]
or something more useful.

The plugin Log file is accessed by clicking the Show Events Log Folder button at the top of the Indigo Event Log window. The folder you want is com.autologplugin.indigoplugin.foscamhdcontroller and the file is plugin.log.

Also it may be worth checking if you can access the camera via a web browser?

Posted on
Wed Sep 23, 2020 12:42 pm
yassi offline
Posts: 419
Joined: Sep 06, 2015
Location: Germany

Re: Autolog Foscam HD Controller Discussion

autolog wrote:
I have just checked the latest API and I can't see anything that has changed that should affect the plugin. :?

You could try turning on all debugging in the plugin config, then reload the plugin and then search the plugin log for your camera's IP string to see if that shows anything.

After the plugin starts, you should see something in the log like:
2020-09-23 16:32:48.885 DEBUG Plugin.MonitorSend.run Command Sent To Camera Gartenamera [192.168.100.???:88]: http://192.168.1.???:88/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getSystemTime
You should then be able to see a response which may be:
2020-09-23 16:34:06.342 DEBUG Plugin.DebugReceive.run No Response from camera Gartenamera [192.168.1.???:88]
or something more useful.

The plugin Log file is accessed by clicking the Show Events Log Folder button at the top of the Indigo Event Log window. The folder you want is com.autologplugin.indigoplugin.foscamhdcontroller and the file is plugin.log.

Also it may be worth checking if you can access the camera via a web browser?


Hi Jon,

thanks for this.

Have a look please at the log excerpt here:

Code: Select all
2020-09-23 20:19:14.005   WARNING        Plugin.general.setDebuggingLevels        Monitoring enabled for Foscam HD: Send, Receive, Message Handling
2020-09-23 20:19:14.006   WARNING        Plugin.general.setDebuggingLevels        Debugging enabled for Foscam HD: General, Send, Receive, Message Handling, Method Trace, Polling
2020-09-23 20:19:18.947   INFO           Plugin.general.runConcurrentThread       Autolog 'Foscam HD Controller' Plugin shutdown requested
2020-09-23 20:19:18.997   THREADDEBUG    Plugin.method.deviceStopComm            CLASS: Plugin
2020-09-23 20:19:18.998   THREADDEBUG    Plugin.method.shutdown                  CLASS: Plugin
2020-09-23 20:19:18.998   INFO           Plugin.general.shutdown                  Autolog 'Foscam HD Controller' Plugin shutdown complete
2020-09-23 20:19:21.931   INFO           Plugin.general.__init__                  Autolog 'Foscam HD Controller' initializing . . .
2020-09-23 20:19:21.931   WARNING        Plugin.general.setDebuggingLevels        Monitoring enabled for Foscam HD: Send, Receive, Message Handling
2020-09-23 20:19:21.932   WARNING        Plugin.general.setDebuggingLevels        Debugging enabled for Foscam HD: General, Send, Receive, Message Handling, Method Trace, Polling
2020-09-23 20:19:21.966   THREADDEBUG    Plugin.method.startup                   CLASS: Plugin
2020-09-23 20:19:21.966   INFO           Plugin.general.startup                   Autolog 'Foscam HD Controller' initialization complete
2020-09-23 20:19:21.979   THREADDEBUG    Plugin.method.deviceStartComm           CLASS: Plugin
2020-09-23 20:19:21.994   DEBUG          Plugin.DebugSend.__init__                  Initialised 'Send Command' Thread for Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:22.004   THREADDEBUG    Plugin.method.run                       ThreadSendCommand
2020-09-23 20:19:22.009   DEBUG          Plugin.DebugMessageHandling.__init__                  Initialised 'ResponseFromCamera' Thread for Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:22.009   THREADDEBUG    Plugin.method.run                       ThreadResponseFromCamera
2020-09-23 20:19:22.012   INFO           Plugin.polling.__init__                  Initialised 'ThreadPolling' Thread for Gartencamera [192.168.100.XXX:443] to poll at 60 second intervals
2020-09-23 20:19:22.013   THREADDEBUG    Plugin.method.run                       ThreadPolling
2020-09-23 20:19:22.035   DEBUG          Plugin.general.deviceStartComm           Gartencamera Device Start Completed
2020-09-23 20:19:22.044   THREADDEBUG    Plugin.method.runConcurrentThread       CLASS: Plugin
2020-09-23 20:19:24.015   DEBUG          Plugin.DebugMessageHandling.run                       'ResponseFromCamera' Thread for Gartencamera [192.168.100.XXX:443] initialised and now running
2020-09-23 20:19:25.014   DEBUG          Plugin.DebugSend.run                       'Send Command' Thread for Gartencamera [192.168.100.XXX:443] initialised and now running
2020-09-23 20:19:25.014   DEBUG          Plugin.DebugSend.run                       Command: getProductModel [camera]
2020-09-23 20:19:25.015   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getProductModel
2020-09-23 20:19:25.089   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:25.092   DEBUG          Plugin.DebugSend.run                       Command: getProductModelName [camera]
2020-09-23 20:19:25.092   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getProductModelName
2020-09-23 20:19:25.174   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:25.177   DEBUG          Plugin.DebugSend.run                       Command: getDevInfo [camera]
2020-09-23 20:19:25.178   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevInfo
2020-09-23 20:19:25.252   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:25.255   DEBUG          Plugin.DebugSend.run                       Command: getDevState [camera]
2020-09-23 20:19:25.255   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevState
2020-09-23 20:19:25.342   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:25.345   DEBUG          Plugin.DebugSend.run                       Command: getMotionDetectConfig1 [camera]
2020-09-23 20:19:25.346   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getMotionDetectConfig1
2020-09-23 20:19:25.420   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:25.423   DEBUG          Plugin.DebugSend.run                       Command: getScheduleRecordConfig [camera]
2020-09-23 20:19:25.423   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getScheduleRecordConfig
2020-09-23 20:19:25.501   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:19:26.020   THREADDEBUG    Plugin.method.run                       ThreadPolling
2020-09-23 20:19:26.021   DEBUG          Plugin.polling.run                       'Polling' Thread for Gartencamera [192.168.100.XXX:443] initialised and now running
2020-09-23 20:19:26.021   DEBUG          Plugin.polling.run                       'Gartencamera' [192.168.100.XXX:443] Polling thread NOW running and command queued
2020-09-23 20:19:26.052   DEBUG          Plugin.DebugSend.run                       Command: getDevState [camera]
2020-09-23 20:19:26.052   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevState
2020-09-23 20:19:26.150   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:20:26.028   DEBUG          Plugin.polling.run                       'Gartencamera' [192.168.100.XXX:443] Start of While Loop ...
2020-09-23 20:20:26.069   DEBUG          Plugin.DebugSend.run                       Command: getDevState [camera]
2020-09-23 20:20:26.070   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevState
2020-09-23 20:20:26.138   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:21:26.033   DEBUG          Plugin.polling.run                       'Gartencamera' [192.168.100.XXX:443] Start of While Loop ...
2020-09-23 20:21:26.056   DEBUG          Plugin.DebugSend.run                       Command: getDevState [camera]
2020-09-23 20:21:26.057   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevState
2020-09-23 20:21:26.117   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:22:26.043   DEBUG          Plugin.polling.run                       'Gartencamera' [192.168.100.XXX:443] Start of While Loop ...
2020-09-23 20:22:26.090   DEBUG          Plugin.DebugSend.run                       Command: getDevState [camera]
2020-09-23 20:22:26.090   DEBUG          Plugin.MonitorSend.run                       Command Sent To Camera Gartencamera [192.168.100.XXX:443]: http://192.168.100.XXX:443/cgi-bin/CGIProxy.fcgi?usr=<USERNAME>&pwd=<PASSWORD>&cmd=getDevState
2020-09-23 20:22:26.160   DEBUG          Plugin.DebugReceive.run                       No Response from camera Gartencamera [192.168.100.XXX:443]
2020-09-23 20:22:30.511   THREADDEBUG    Plugin.method.validatePrefsConfigUi     CLASS: Plugin
2020-09-23 20:22:30.535   THREADDEBUG    Plugin.method.closedPrefsConfigUi       CLASS: Plugin
2020-09-23 20:22:30.535   DEBUG          Plugin.general.closedPrefsConfigUi       'closePrefsConfigUi' called with userCancelled = False
2020-09-23 20:22:30.535   THREADDEBUG    Plugin.method.setDebuggingLevels        CLASS: Plugin
2020-09-23 20:22:30.535   INFO           Plugin.general.setDebuggingLevels        No monitoring or debugging requested
2020-09-23 20:23:09.502   INFO           Plugin.general.runConcurrentThread       Autolog 'Foscam HD Controller' Plugin shutdown requested
2020-09-23 20:23:09.569   INFO           Plugin.general.shutdown                  Autolog 'Foscam HD Controller' Plugin shutdown complete
2020-09-23 20:23:13.155   INFO           Plugin.general.__init__                  Autolog 'Foscam HD Controller' initializing . . .
2020-09-23 20:23:13.156   INFO           Plugin.general.setDebuggingLevels        No monitoring or debugging requested
2020-09-23 20:23:13.212   INFO           Plugin.general.startup                   Autolog 'Foscam HD Controller' initialization complete
2020-09-23 20:23:13.245   INFO           Plugin.polling.__init__                  Initialised 'ThreadPolling' Thread for Gartencamera [192.168.100.XXX:443] to poll at 60 second


I hav to say, that I can access the cam via the Surveillance Station, DS Cam (iOS/Android), Foscam VMS.
Via browser I can only access it via Internet Explorer (no Chrome, Firefox, etc.) :evil:
But that was enough for me to get it first configured and ready to run with SS on my NAS.

So, it seems so, Indigo has indeed no connection to it.

Yassi
Attachments
Bildschirmfoto 2020-09-23 um 20.32.52.png
Bildschirmfoto 2020-09-23 um 20.32.52.png (157.33 KiB) Viewed 82 times

Posted on
Wed Sep 23, 2020 1:32 pm
autolog offline
Posts: 3304
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Autolog Foscam HD Controller Discussion

I think the log output is similar to what I get when a camera is switched off.

For the next test, try using ping from a terminal session to check the IP Address:
Code: Select all
ping 192.168.100.xxx
You should get output that indicates communication or not, e.g.:
Code: Select all
PING 192.168.100.xxx (192.168.100.xxx): 56 data bytes
64 bytes from 192.168.100.xxx: icmp_seq=0 ttl=64 time=178.385 ms
64 bytes from 192.168.100.xxx: icmp_seq=1 ttl=64 time=2.447 ms
64 bytes from 192.168.100.xxx: icmp_seq=2 ttl=64 time=2.938 ms
64 bytes from 192.168.100.xxx: icmp_seq=3 ttl=64 time=2.397 ms
64 bytes from 192.168.100.xxx: icmp_seq=4 ttl=64 time=2.412 ms
64 bytes from 192.168.100.xxx: icmp_seq=5 ttl=64 time=2.375 ms
64 bytes from 192.168.100.xxx: icmp_seq=6 ttl=64 time=2.362 ms
64 bytes from 192.168.100.xxx: icmp_seq=7 ttl=64 time=2.325 ms
64 bytes from 192.168.100.xxx: icmp_seq=8 ttl=64 time=2.348 ms
64 bytes from 192.168.100.xxx: icmp_seq=9 ttl=64 time=2.390 ms
^C
--- 192.168.100.xxx ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.325/20.038/178.385/52.783 ms

or
PING 192.168.100.xxx (192.168.100.xxx): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
If you can't get through then that suggests that there might be a network / firewall problem with the Mac running Indigo or there is something wrong with the sign-in credentials (probably unlikely)? I would also suggest using port 88 to start with.

Posted on
Wed Sep 23, 2020 1:54 pm
yassi offline
Posts: 419
Joined: Sep 06, 2015
Location: Germany

Re: Autolog Foscam HD Controller Discussion

autolog wrote:
I think the log output is similar to what I get when a camera is switched off.

For the next test, try using ping from a terminal session to check the IP Address:
Code: Select all
ping 192.168.100.xxx
You should get output that indicates communication or not, e.g.:
Code: Select all
PING 192.168.100.xxx (192.168.100.xxx): 56 data bytes
64 bytes from 192.168.100.xxx: icmp_seq=0 ttl=64 time=178.385 ms
64 bytes from 192.168.100.xxx: icmp_seq=1 ttl=64 time=2.447 ms
64 bytes from 192.168.100.xxx: icmp_seq=2 ttl=64 time=2.938 ms
64 bytes from 192.168.100.xxx: icmp_seq=3 ttl=64 time=2.397 ms
64 bytes from 192.168.100.xxx: icmp_seq=4 ttl=64 time=2.412 ms
64 bytes from 192.168.100.xxx: icmp_seq=5 ttl=64 time=2.375 ms
64 bytes from 192.168.100.xxx: icmp_seq=6 ttl=64 time=2.362 ms
64 bytes from 192.168.100.xxx: icmp_seq=7 ttl=64 time=2.325 ms
64 bytes from 192.168.100.xxx: icmp_seq=8 ttl=64 time=2.348 ms
64 bytes from 192.168.100.xxx: icmp_seq=9 ttl=64 time=2.390 ms
^C
--- 192.168.100.xxx ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.325/20.038/178.385/52.783 ms

or
PING 192.168.100.xxx (192.168.100.xxx): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
If you can't get through then that suggests that there might be a network / firewall problem with the Mac running Indigo or there is something wrong with the sign-in credentials (probably unlikely)? I would also suggest using port 88 to start with.


I can ping it, no prob.
On port 88 I have now an access denied, but the password is correct, I can sign in with it.

Code: Select all
Indigo:~ indigo$ ping 192.168.100.XXX
PING 192.168.100.XXX (192.168.100.XXX): 56 data bytes
64 bytes from 192.168.100.XXX: icmp_seq=0 ttl=64 time=92.030 ms
64 bytes from 192.168.100.XXX: icmp_seq=1 ttl=64 time=43.053 ms
64 bytes from 192.168.100.XXX: icmp_seq=2 ttl=64 time=6.729 ms
64 bytes from 192.168.100.XXX: icmp_seq=3 ttl=64 time=22.862 ms
64 bytes from 192.168.100.XXX: icmp_seq=4 ttl=64 time=514.172 ms
64 bytes from 192.168.100.XXX: icmp_seq=5 ttl=64 time=52.282 ms
64 bytes from 192.168.100.XXX: icmp_seq=6 ttl=64 time=38.492 ms
64 bytes from 192.168.100.XXX: icmp_seq=7 ttl=64 time=8.195 ms
64 bytes from 192.168.100.XXX: icmp_seq=8 ttl=64 time=18.680 ms
^C
--- 192.168.100.XXX ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 6.729/88.499/514.172/152.536 ms
Indigo:~ indigo$








23.09.2020, 21:45:35
   Foscam HD Controller            Initialised 'ThreadPolling' Thread for Gartencamera [192.168.100.XXX:88] to poll at 60 second intervals
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]

23.09.2020, 21:46:39
   Foscam HD Controller Error      Response received from camera: Gartencamera [192.168.100.XXX:88], Error -3:Access deny [51:<CGI_Result>
    <result>-3</result>
</CGI_Result>
]


Crazy.

Who is online

Users browsing this forum: No registered users and 1 guest