LinuxMCE only uses still images from cameras. There is no support for video streams. One of the goals of the Advanced IP Camera was to look into also supporting video streams, but this requires changes to the orbiters too. Maybe the qOrbiter will come to the rescue on this.

As far as the motion wrapper, I'm not sure, but I think it uses the video stream, and outputs still images to LinuxMCE.

br,
sambuca

3. The nic is shut down when you do "ifconfig eth0 down". The reason your system hung is that NFS is trying to communicate with the core, and it can't as the network is gone.

Do you suspend the MD or do you shut it down?

br,
sambuca

I know some people have bad experiences with creating device templates and sqlCVS.

I'm here to present the opposite view. I have no problem with sqlCVS. But the key is to work with one device template at a time. If you have done several changes in your system at once, failure is much more likely.

The easiest option in that case is to revert all changes (also done on the sqlCVS diff page), and re-do your changes.

br,
sambuca

That is great 

I was a bit puzzled about what to check next, so I'm glad it works.

I don't have anything else for you to test now. Thank you very much for you help.

br,
sambuca

You can create an event handler for this. Create an event handler for the sensor, and add a criteria on the device status of the front door (or the house mode/status, if you prefer that route).

LinuxMCE should already have created an event for "Leave home" that turns off all lights. It should do this automatically, although I can't find that event in my installation.

Edit: There are events for this, but they were taken away from the event pages in the web-admin 10 months ago as they couldn't be changed anyway. I would still like to see them though...

br,
sambuca

It simply looks for the text "var alarm_status=1;" in the text it receives from the camera. So I can't see why it does not work.

The configuration sets up the Advanced IP Camera to check for this text, and there is nothing more to it. The device needs a child device of the type Motion Detector with the correct data(like what text to look for).
So the ;: is correct. When defining child devices in the template, you cannot use line breaks, so we need to separate the data with : instead.

You could always try to change the Capabilities device data of the motion detector child and see if that helps... Perhaps try to substitute "patternOn=var alarm_status=1;" with "patternOn=alarm_status=1" to keep it simple.

br,
sambuca

For the record, this is how it looks in the DCERouter log:

Code:

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:

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

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

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

Can you post more of the Advanced_IP_Camera log, around the place where it says "alarm_status" ?

br,
sambuca

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

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

posde, you're right, that should have read Device_DeviceData.

brononius, check first that you don't find the devices under Advanced -> Configuration -> Devices. If you find them there, delete them there.

But for the reasons posde mention, if you need to change it in the database, a better solution could be to update the FK_DeviceTemplate of the Devices:
sudo mysql pluto_main
update Device set FK_DeviceTemplate = 2213 where PK_Device = xx;

and do the last one for each of you old device IDs.

br,
sambuca

Something seems to crash the DCERouter.. Don't think it is the template. Did you upgrade everything or just some packages? If you got conflicting versions of LinuxMCE libraries and binaries, this can happen.

You can delete the old camera devices from your database using the mysql tool.
sudo mysql pluto_main
delete from DeviceData where FK_Device=xx;
delete from Device where PK_Device=xx;


br,
sambuca

Are you using device template #2211? that is wrong on my install. The IPCAM02 template should now have ID 2213. If you used 2211 previously, that is probably why your devices disappeared, the template ID was probably changed when you did an sqlCVS update.

The error in the log suggests that there is something wrong with the device, and that it cannot load its device data. Make sure you are using the correct template, and you should check that the template look correct too.

The motion detection can be see in the DCERouter.log as an event sent from the cameras motion detector. The new template should automatically create a motion detector child under the camera device.

The current template will poll the camera every 10 seconds for any changes in motion detection status, so event might not be instant.

br,
sambuca