Ok, that is the result I was expecting. Now I wonder if the camera shuts down the connection immediately, or if it sends more data along as things change (D-Link camera does this). Don't know if this is easy to test with a browser, but you could use wget on the command line: wget <url> and see if it finishes, or just keeps going (stop with CTRL+C in that case).

It's quite easy to a motion detection to this template, but depending on how the camera uses the connection, I might have to make a small code change first.

I have updated the template a bit, and added motion detection capabilities. The necessary code hasn't been released yet, but you can download the recent binary from the same url as before. You would have to update sqlCVS too, and only new devices will be set up with the new template data.

So: update sqlCVS, download new binary - place it in /usr/pluto/bin, create a new device with the template, reload. (and cross fingers )

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.

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_maindelete from DeviceData where FK_Device=xx;delete from Device where PK_Device=xx;

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_mainupdate Device set FK_DeviceTemplate = 2213 where PK_Device = xx;