Author Topic: [SOLVED] IP Camera in 1004  (Read 12446 times)

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #75 on: August 09, 2012, 03:18:48 pm »
After a reboot, all seems fine.
Except 4 camera's i'm not sure they should be in there.


I've added a new one, and a child 'motion detector - 210' is created under the 'IPCAM02 camera - 209'.
But can't find anything back in the logs regarding 'motion' or '210'. :$


tail -f /var/log/pluto/DCERouter.log | grep mot
Code: [Select]
^Cbrononius@dcerouter:~$ tail -f /var/log/pluto/DCERouter.log | grep 210
Code: [Select]
^Cbrononius@dcerouter:~$ tail -f /var/log/pluto/DCERouter.log | grep 209
Code: [Select]
05 08/09/12 15:19:46.209 Socket::ReceiveData 0xa1ad900 failed, bytes left 0 start: 910000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 189 Incoming_Conn Socket 189 ::ffff:127.0.0.1 <0x4cda0b70>
05 08/09/12 15:19:46.209 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 189 ::ffff:127.0.0.1 <0x4cda0b70>
05 08/09/12 15:19:46.209 TCPIP: Closing connection to -1003 (Router Dev #0) 0xa1ad900 m_Socket: -1 <0x4cda0b70>
05 08/09/12 15:19:46.209 Router::RemoveAndDeleteSocket 0xa1ad900 -1003 <0x4cda0b70>
^C
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #76 on: August 09, 2012, 03:20:40 pm »
After a reboot, all seems fine.
Except 4 camera's i'm not sure they should be in there.


I've added a new one, and a child 'motion detector - 210' is created under the 'IPCAM02 camera - 209'.
But can't find anything back in the logs regarding 'motion' or '210'. I've let them run for about 3 minutes... :$


tail -f /var/log/pluto/DCERouter.log | grep mot
Code: [Select]
^Cbrononius@dcerouter:~$ tail -f /var/log/pluto/DCERouter.log | grep 210
Code: [Select]
^Cbrononius@dcerouter:~$ tail -f /var/log/pluto/DCERouter.log | grep 209
Code: [Select]
05 08/09/12 15:19:46.209 Socket::ReceiveData 0xa1ad900 failed, bytes left 0 start: 910000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 189 Incoming_Conn Socket 189 ::ffff:127.0.0.1 <0x4cda0b70>
05 08/09/12 15:19:46.209 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 189 ::ffff:127.0.0.1 <0x4cda0b70>
05 08/09/12 15:19:46.209 TCPIP: Closing connection to -1003 (Router Dev #0) 0xa1ad900 m_Socket: -1 <0x4cda0b70>
05 08/09/12 15:19:46.209 Router::RemoveAndDeleteSocket 0xa1ad900 -1003 <0x4cda0b70>
^C
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #77 on: August 09, 2012, 05:38:59 pm »
Sorry to ask, but you are sure that the camera has motion detection enabled (if there is such a setting)?

Is grep case-sensitive? If so, I think the event is Motion Detected or something like that.

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #78 on: August 09, 2012, 07:26:28 pm »
No prob for asking, glad to help...

Motion is activated (i'm recieving mails over that way).
See attached picture for settings...

When I do a grep on Motion, i'm getting not much more...
Shouldn't I see it each x seconds in the log?
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #79 on: August 09, 2012, 08:33:48 pm »
Pardon me, it is the Sensor Tripped event you will see in the log...

You can also manually open /get_status.cgi on your camera and see if the alarm_status line changes when motion is detected.

The Advanced_IP_Camera devices will only send sensor tripped event when a sensor changes state, so only when motion is first detected, and then when the camera resets that status. And how long that is depends on the camera I guess.

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #80 on: August 10, 2012, 06:32:06 am »
Hey,

A get_status.cgi gives me:
Code: [Select]
...200;
var alarm_status=1;
var...

So he sees something.
but in the log, i can't find anything.

sudo grep ensor /var/log/pluto/DCERouter.log

sudo grep ripped /var/log/pluto/DCERouter.log

sudo grep 210 /var/log/pluto/DCERouter.log

sudo grep 209 /var/log/pluto/DCERouter.log

sudo grep Motion /var/log/pluto/DCERouter.log
Code: [Select]
05      08/09/12 15:09:34.128            UpdateEntArea::AddDevicesToEntArea adding device 211 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.131            UpdateEntArea::AddDevicesToEntArea adding device 212 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.132            UpdateEntArea::AddDevicesToEntArea adding device 213 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.134            UpdateEntArea::AddDevicesToEntArea adding device 214 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.146            UpdateEntArea::AddDevicesToEntArea adding device 210 Motion Detector to ent area 1 Rack <0xb09fab70>
(adding the stuff yesterday)

sudo grep Detector /var/log/pluto/DCERouter.log
Code: [Select]
05      08/09/12 15:09:34.128            UpdateEntArea::AddDevicesToEntArea adding device 211 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.131            UpdateEntArea::AddDevicesToEntArea adding device 212 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.132            UpdateEntArea::AddDevicesToEntArea adding device 213 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.134            UpdateEntArea::AddDevicesToEntArea adding device 214 Motion Detector to ent area 1 Rack <0xb09fab70>
05      08/09/12 15:09:34.146            UpdateEntArea::AddDevicesToEntArea adding device 210 Motion Detector to ent area 1 Rack <0xb09fab70>
(adding the stuff yesterday)


« Last Edit: August 10, 2012, 06:35:51 am by brononius »
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #81 on: August 10, 2012, 06:56:19 am »
Ok, just put the logs of pluto on 10 (/etc/pluto.conf).

And now i can see in correct values in the cameras log. But nothing in the global logs.
So apparantly he's reading it correctly. But there's a missing link in linuxMCE?
I don't need to add something extra in linuxMCE? Like for example a 'motion detector' tool? I'm thinking of the 'Motion wrapper'...  ::)

sudo grep alarm_status /var/log/pluto/215_Advanced_IP_Camera.log
Code: [Select]
10      08/10/12 6:47:01.462            EventWriteCallback: s = var alarm_status=0;
var alarm_status=0;
var alarm_status=0;
var alarm_status=0;
10      08/10/12 6:47:11.482            EventWriteCallback: s = var alarm_status=0;
var alarm_status=0;
var alarm_status=0;
var alarm_status=0;
10      08/10/12 6:47:21.497            EventWriteCallback: s = var alarm_status=0;
var alarm_status=1;
var alarm_status=1;
var alarm_status=1;
10      08/10/12 6:47:31.526            EventWriteCallback: s = var alarm_status=1;
var alarm_status=1;
var alarm_status=1;
var alarm_status=1;
10      08/10/12 6:47:41.568            EventWriteCallback: s = var alarm_status=1;


I've created a new camera, and this was all I could found in the DCErouter.log:
Code: [Select]
10      08/10/12 6:44:24.665            Created device 216 Motion Detector (mdl: 54) routed to: 215 (1 CORE) disabled 0 <0xb775e8e0>
10      08/10/12 6:44:25.741            adding device 123 Motion Wrapper to map ent area 1 Rack <0xb775e8e0>
10      08/10/12 6:44:25.745            adding device 216 Motion Detector to map ent area 1 Rack <0xb775e8e0>
10      08/10/12 6:44:24.665            Created DCE device 215 Videre (mdl: 2213) routed to: 215 (1 CORE) disabled 0 <0xb775e8e0>
10      08/10/12 6:44:24.665            Created device 216 Motion Detector (mdl: 54) routed to: 215 (1 CORE) disabled 0 <0xb775e8e0>
10      08/10/12 6:44:25.744            adding device 215 Videre to map ent area 1 Rack <0xb775e8e0>
10      08/10/12 6:44:26.221            Requesthandler 0xac215b98 (device: 8) runThread now running <0x8abe7b70>
10      08/10/12 6:44:31.064            Device 215 connected as foreign template 2208 <0x5b1f1b70>
10      08/10/12 6:44:31.131            Device 215 connected as foreign template 2208 <0x593eeb70>
10      08/10/12 6:44:31.185            Executed query UPDATE Device SET Registered=1,psc_mod=psc_mod WHERE PK_Device=215 (1 rows) <0x589edb70>
« Last Edit: August 10, 2012, 06:57:52 am by brononius »
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #82 on: August 10, 2012, 07:25:15 am »
Can you post more of the Advanced_IP_Camera log, around the place where it says "alarm_status" ?

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #83 on: August 12, 2012, 09:54:10 am »
Sorry for the late answer.

Some extra logging (first event: no alarm, later on: alarms...)

Code: [Select]
10 08/12/12 9:50:59.832 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var id='000DC5D047FF'; <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344757859;
var tz=- <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var alias='videre';
var now=1344757859;
var tz=-7200;
var alarm_status=0;
var ddns_status=0; <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var now=1344757859;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: s = var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:50:59.839 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb77dab70>
10 08/12/12 9:50:59.839 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb77dab70>
10 08/12/12 9:50:59.839 EventMethod::MethodURL(): http OK <0xb77dab70>
10 08/12/12 9:51:09.839 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var id='000DC5D047FF'; <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344757869;
var tz=- <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var alias='videre';
var now=1344757869;
var tz=-7200;
var alarm_status=1;
var ddns_status=0; <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var now=1344757869;
var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: s = var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:09.871 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb77dab70>
10 08/12/12 9:51:09.871 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb77dab70>
10 08/12/12 9:51:09.871 EventMethod::MethodURL(): http OK <0xb77dab70>
10 08/12/12 9:51:19.871 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var id='000DC5D047FF'; <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344757879;
var tz=- <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var alias='videre';
var now=1344757879;
var tz=-7200;
var alarm_status=1;
var ddns_status=0; <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var now=1344757879;
var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: s = var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:19.887 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb77dab70>
10 08/12/12 9:51:19.887 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb77dab70>
10 08/12/12 9:51:19.887 EventMethod::MethodURL(): http OK <0xb77dab70>
10 08/12/12 9:51:29.887 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var id='000DC5D047FF'; <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344757889;
var tz=- <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var alias='videre';
var now=1344757889;
var tz=-7200;
var alarm_status=1;
var ddns_status=0; <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var now=1344757889;
var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb77dab70>
10 08/12/12 9:51:29.894 EventWriteCallback: s = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: s = var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: s = var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:29.895 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb77dab70>
10 08/12/12 9:51:29.895 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb77dab70>
10 08/12/12 9:51:29.895 EventMethod::MethodURL(): http OK <0xb77dab70>
10 08/12/12 9:51:39.895 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var id='000DC5D047FF'; <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344757899;
var tz=- <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var alias='videre';
var now=1344757899;
var tz=-7200;
var alarm_status=1;
var ddns_status=0; <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var now=1344757899;
var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: s = var upnp_status=1;
 <0xb77dab70>
10 08/12/12 9:51:39.902 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb77dab70>
10 08/12/12 9:51:39.902 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb77dab70>
10 08/12/12 9:51:39.902 EventMethod::MethodURL(): http OK <0xb77dab70>
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #84 on: August 12, 2012, 01:43:45 pm »
Can you please post the log right after the device has started, it prints its configuration then, so I'm sure it's got it right?

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #85 on: August 12, 2012, 01:59:30 pm »
This is the part you need?

Code: [Select]
Return code: 2
2 08/12/12 13:51:51 215 (spawning-device) Device requests restart... count=1/50 dev=215
Sun Aug 12 13:51:51 CEST 2012 Restart
========== NEW LOG SECTION ==========
1 08/12/12 13:51:59 215 (spawning-device) Starting... 1
1 08/12/12 13:52:00 215 (spawning-device) Found /usr/pluto/bin/Advanced_IP_Camera
10 08/12/12 13:52:00.198 Device: 215 starting.  Connecting to: localhost <0xb77646f0>
10 08/12/12 13:52:00.256 Setting timeout for socket 4 to 20 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() Configuration = panUpCmd=/decoder_control.cgi?command=0&onestep=1
panDownCmd=/decoder_control.cgi?command=2&onestep=1
panRightCmd=/decoder_control.cgi?command=6&onestep=1
panLeftCmd=/decoder_control.cgi?command=4&onestep=1
eventMethod1=urlPoll
eventURL1=/get_status.cgi <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = panUpCmd, value = /decoder_control.cgi?command=0&onestep=1 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = panDownCmd, value = /decoder_control.cgi?command=2&onestep=1 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = panRightCmd, value = /decoder_control.cgi?command=6&onestep=1 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = panLeftCmd, value = /decoder_control.cgi?command=4&onestep=1 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = eventMethod1, value = urlPoll <0xb77646f0>
10 08/12/12 13:52:00.316 GetEventMethod() requested EventMethod num = 1 <0xb77646f0>
10 08/12/12 13:52:00.316 GetEventMethod() new EventMethod num = 1 <0xb77646f0>
10 08/12/12 13:52:00.316 getConfig() key = eventURL1, value = /get_status.cgi <0xb77646f0>
10 08/12/12 13:52:00.316 GetEventMethod() requested EventMethod num = 1 <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() Children: <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() PK_Device= 216 <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() Motion detector, capabilities = method=1:triggerMethod=pattern:patternOn=var alarm_status=1;:patternOff=var alarm_status=0; <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() key = method, value = 1 <0xb77646f0>
10 08/12/12 13:52:00.317 GetEventMethod() requested EventMethod num = 1 <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() key = triggerMethod, value = pattern <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() key = patternOn, value = var alarm_status=1; <0xb77646f0>
10 08/12/12 13:52:00.317 getConfig() key = patternOff, value = var alarm_status=0; <0xb77646f0>
05 08/12/12 13:52:00.317 m_vectEventMethod.size() = 5. Configured EventMethods: <0xb77646f0>
05 08/12/12 13:52:00.317 GetConfig(): EventMethod 0, m_bRunning = 26, m_sMethod = urlPoll, m_sURL = /get_status.cgi, m_iInterval = 10, m_vectInputDevices = [ m_dwPK_Device = 216, m_dwFK_DeviceTemplate = 54, status = (null), m_sTriggerMethod = pattern, m_sPatternOn = var alarm_status=1;, m_sPatternOff = var alarm_status=0;,  ] <0xb77646f0>
05 08/12/12 13:52:00.317 m_mapPK_Device_OutputDevice.size() = 0. Configured OutputDevices: <0xb77646f0>
10 08/12/12 13:52:00.341 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var id='000DC5D047FF'; <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344772320;
var tz=- <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var alias='videre';
var now=1344772320;
var tz=-7200;
var alarm_status=0;
var ddns_status=0; <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var now=1344772320;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: s = var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:00.355 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb7763b70>
10 08/12/12 13:52:00.355 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb7763b70>
10 08/12/12 13:52:00.355 EventMethod::MethodURL(): http OK <0xb7763b70>
10 08/12/12 13:52:00.359 Connect OK <0xb77646f0>
05 08/12/12 13:52:00.359 Creating child 216 <0xb77646f0>
10 08/12/12 13:52:00.359 Got CreateEvent for unknown type 54. <0xb77646f0>
05 08/12/12 13:52:00.359 Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0xb77646f0>
10 08/12/12 13:52:00.359 Got CreateCommand for unknown type 54. <0xb77646f0>
05 08/12/12 13:52:00.359 Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0xb77646f0>
10 08/12/12 13:52:00.379 Requesthandler 0x9f3c8d0 (device: 215) runThread now running <0xb6361b70>
10 08/12/12 13:52:07.169 Receive string:  <0xb6361b70>
10 08/12/12 13:52:07.169 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:08.474 Receive string:  <0xb6361b70>
10 08/12/12 13:52:08.474 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:09.848 Receive string:  <0xb6361b70>
10 08/12/12 13:52:09.848 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:10.355 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var id='000DC5D047FF'; <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344772330;
var tz=- <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var alias='videre';
var now=1344772330;
var tz=-7200;
var alarm_status=0;
var ddns_status=0; <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var now=1344772330;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: s = var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:10.362 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb7763b70>
10 08/12/12 13:52:10.363 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb7763b70>
10 08/12/12 13:52:10.363 EventMethod::MethodURL(): http OK <0xb7763b70>
10 08/12/12 13:52:11.089 Receive string:  <0xb6361b70>
10 08/12/12 13:52:11.089 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:12.308 Receive string:  <0xb6361b70>
10 08/12/12 13:52:12.309 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:13.436 Receive string:  <0xb6361b70>
10 08/12/12 13:52:13.437 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:14.619 Receive string:  <0xb6361b70>
10 08/12/12 13:52:14.619 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:15.768 Receive string:  <0xb6361b70>
10 08/12/12 13:52:15.768 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:16.898 Receive string:  <0xb6361b70>
10 08/12/12 13:52:16.898 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:17.981 Receive string:  <0xb6361b70>
10 08/12/12 13:52:17.981 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:19.111 Receive string:  <0xb6361b70>
10 08/12/12 13:52:19.111 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:20.299 Receive string:  <0xb6361b70>
10 08/12/12 13:52:20.299 Received  0x9f3c8d0 device: 215 <0xb6361b70>
10 08/12/12 13:52:20.363 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var id='000DC5D047FF'; <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='videre';
var now=1344772340;
var tz=- <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var alias='videre';
var now=1344772340;
var tz=-7200;
var alarm_status=0;
var ddns_status=0; <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var now=1344772340;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var oray_type=0;
var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: s = var upnp_status=1;
 <0xb7763b70>
10 08/12/12 13:52:20.375 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb7763b70>
10 08/12/12 13:52:20.375 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb7763b70>
10 08/12/12 13:52:20.375 EventMethod::MethodURL(): http OK <0xb7763b70>
10 08/12/12 13:52:21.423 Receive string:  <0xb6361b70>
10 08/12/12 13:52:21.423 Received  0x9f3c8d0 device: 215 <0xb6361b70>
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #86 on: August 12, 2012, 05:26:50 pm »
Yes, thanks.

There is an improvement in the latest version(in the last 2-3 days) that might help and let it detect the camera status properly. Feel free to try it out when you get a chance.

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #87 on: August 13, 2012, 11:26:56 am »
Hey,

I've done:
  • sudo apt-get update
  • sudo apt-get upgrade
  • sqlCVS update (DCE all)
  • recreated the camera completly (id 229, template 2213
  • Put /etc/pluto.conf the logs to 4,6,8,10...
  • Restarted the linuxMCE

And in the log  "229_Advanced_IP_Camera.log", i see the motion alarm:
Code: [Select]
10 08/13/12 11:19:43.152 EventWriteCallback: s = var alarm_status=1;
But can't find anything in the DCErouter.log. I've searched with:
  • 229
  • 230
  • ensor
  • ector
  • otion

Not sure what else i can searh for in DCErouter.log.
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02

sambuca

  • Guru
  • ****
  • Posts: 443
    • View Profile
Re: [SOLVED] IP Camera in 1004
« Reply #88 on: August 13, 2012, 01:44:51 pm »
For the record, this is how it looks in the DCERouter log:

Code: [Select]
07      08/13/12 13:36:52.482           Received Message from 139 (Motion Detector / ) to 0 (unknown / ), type 2 id 9 Event:Sensor Tripped, retry none, parameters: <0x587a4b70>
07      08/13/12 13:36:52.482             Parameter 25(Tripped): 1 <0x587a4b70>

And in the Advanced IP Camera log, there should be something like this:
Code: [Select]
05      08/13/12 13:39:32.565           InputStatusChanged: old status = 0, new status = 1 <0xb779fb70>
05      08/13/12 13:39:32.565           InputStatusChanged: trigger = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=1;

I simulate the camera by editing a file on a server, but I don't think that should matter.

br,
sambuca

brononius

  • Guru
  • ****
  • Posts: 376
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog (runs on ... linuxmce server)
Re: [SOLVED] IP Camera in 1004
« Reply #89 on: August 13, 2012, 02:36:44 pm »
I've got the 'var alarm_status' line in my camera log, but nothing of the 'InputStatusChanged'.
I don't know where the 'motion' looks at?

Code: [Select]
10 08/13/12 14:27:59.874 EventWriteCallback: s = var oray_type=0;
var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:27:59.874 EventWriteCallback: s = var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:27:59.874 EventWriteCallback: compacting m_sEventBuffer, new length = 0 <0xb7797b70>
10 08/13/12 14:27:59.874 EventMethod::MethodURL(): curl_Easy_perform has returned <0xb7797b70>
10 08/13/12 14:27:59.874 EventMethod::MethodURL(): http OK <0xb7797b70>
10 08/13/12 14:28:09.874 EventMethod::MethodURL(): sUrl: http://192.168.111.93:80/get_status.cgi <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var id='000DC5D047FF'; <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var sys_ver='11.14.1.46';
var app_ver='2.4.8.12' <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var app_ver='2.4.8.12';
var alias='Videre';
var now=1344860889;
var tz=- <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var alias='Videre';
var now=1344860889;
var tz=-7200;
var alarm_status=1;
var ddns_status=0; <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var now=1344860889;
var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var tz=-7200;
var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var alarm_status=1;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var ddns_host='';
var oray_type=0;
var upnp_status=4;
 <0xb7797b70>
10 08/13/12 14:28:09.907 EventWriteCallback: s = var oray_type=0;


Must I activate somewhere the motion detection module? Or is this by default running?





When i look at wizard > security > ID230 / template 54 (child of the camera), i see in Capabilities following:

Code: [Select]
method=1:triggerMethod=pattern:patternOn=var alarm_status=1;:patternOff=var alarm_status=0;
Is the ;: correct?
« Last Edit: August 13, 2012, 03:08:37 pm by brononius »
Version: linuxMCE 1004 (v 2012-07-01)
Extra's: Cacti, webmin, phpmyadmin, joomla

Server: MSI MS-7519 / E7400 2,8GB / 4GB / SSD 60GB / Radeon HD4350 / RTL8111 - 3C905C-TX
Orbiters: HTC Desire Z, HP PocketPC, Samsung Galaxy S, iPAD, ASUS eeePAD
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7940, Cisco 7960
Camera's: IPCAM02