If you use /usr/pluto/bin/WakeMD.sh --mac xxxx then it should work anyway. You could also play around with /usr/sbin/etherwake which is used in WakeMD.sh to try and wake the MD.
Using WakeMD.sh --dev will look up the MAC address from the web-admin for the MD.

I haven't heard of any problems with the drivers in 1004, but one time have to be the first 

br,
sambuca

Do you use the motion wrapper to detect motion? It might be that this is causing your problem, as you say that you get an image when accessing the camera directly. I suppose you could try to configure the camera without using motion, and see if the problem goes away.

Btw, what camera do you have? I'm currently trying to make a more advanced IP camera template for LMCE, which takes advantage of build-in motion detection support. Do you know if your camera have that?

br,
sambuca

From memory, this is what is required for wake-on-lan to work:
* It must be enabled in the BIOS
* The network card must have been enabled (by ethtool)
* The system must have wake-up enabled
   - This is done in /proc/acpi/wakeup iirc, see if there is some entries there that match your network card, or a generic PCI entry. Some googling may be required to figure this one out (I don't recall the exact command at the moment)
* The driver must support wake-on-lan. What LMCE version are you using 810 or 1004? In 810 there was some network drivers that did not set the wake-up flag correctly, and wouldn't wake-on-lan. I think it is fixed in the kernel used in 1004 but still...

br,
sambuca

If you set up the AP to use a static IP, I guess you need to configure a default gateway too. Alternatively, you can set up the AP to receive a DHCP address from LMCE.

Also check the MAC addresses of your cards (it is often printed on the back of the device or laptop) and compare that to what the web admin says, so you are sure that the correct one is used as external by LMCE.

br,
sambuca

It is normal that the output you select will disappear from the -L list. In some cases, it will remove several entries from the list, if the same hardware device is used for several of the listed output devices.

I think the bt_audio_service_open is a bluetooth related error. Are you sure that it actually is relevant in your case?

Setting this up can sometimes be tricky. What I find useful, is to use the squeezeserver web-admin to check if the slave has registered, and try to play something to it from there. This will test the non-LMCE part of the setup. When that works, go on to set up the LMCE part. As others have said, the correct room must be selected for the slave.

br,
sambuca

There is someone who already made a DCE implementation in Java that posted here a while ago. You should search the forums for it if you are going for that option.

br,
sambuca

Yes, I think so. You could also try to send the command then press the button afterwards. The command should(!) be added to a queue for sleeping devices and sent when they wake up (the blue button wakes it up).

br,
sambuca

When setting configuration parameters on the EZMotion you need to press the blue button to wake the device up for it to receive the command.

br,
sambuca

I can't say 100% what your actual problem is based on what you write, so I'll describe my setup:
When the EZMotion first detects motion, its led lights up and an event is emitted, the led goes dark again almost immediately after. Now the detector is active, and is not sending any more motion detected events. When no motion is detected for a specified amount of time, the detector send a new motion event, with a value of 0 (iirc). When the motion detector again detects motion at this point, the led blinks again and a new event is emitted.

The motion sensor always detects motion, but it also has a brightness sensor that allows you to set a certain light level where it triggers an event. So if it is very bright, no event is emitted. This is configurable.

br,
sambuca

Both tschak and posde are correct, when you decide to do things on your own (mount a RAID on /home) you are doing things the system does not expect. When I first started using LMCE I also had my share of problems because I decided to get smart. Now I have learnt to do it the LMCE way instead. Much easier  

When that is said, you could try to disable the RAID device in the web admin. Not sure if it helps, but its worth a shot.

br,
sambuca

I think we all want to see media playback on hand-held devices, and I have some ideas regarding this that I thought I'd share.

First, we may have problems with the media formats supported on various devices. Android for instance, does not play flac files (afaik). And when you think about video files, I suspect it will be even more limitations (given the large number of format available).

So we have two options: use the native android media playback system, or implement a layer on top of that to support more formats. I don't know if qt-media uses the native android media system or adds support for more formats on its own, so using that may or may not be an advantage in this regard.

Using the native playback system will probably be more power-efficient than implementing decoding support, as hardware acceleration exists for the first option.

Adding decoding support for the same formats as the "standard" LMCE devices like Xine and Squeezeboxes to android or other devices will probably not be feasible.

Realizing that playing media seamlessly to hand-held devices probably needs transcoding, we are very much approaching what UPnP are attempting to do. Several of the media servera available do some kind of transcoding.

UPnP clients are available for android already, so they could be used for our purpose. What is missing in this picture is a LMCE-UPnP bridge.
During my work with the LMCE-Coherence media backend (which is still not released), I played around with the idea that we could create a bridge that exposed UPnP devices to LMCE and allow them to be added as a media player device in LMCE. I did not do any experiments regarding this, but I didn't find any show stoppers either.
Using this approach will enable us to use existing frameworks (UPnP clients/renderer on the device, UPnP media server - coherence), and also give us other benefits as well (possible to add other playback devices supporting UPnP).

I'm not saying what we should do, but simply stating that there are alternative ways to creating a new media player for Android. Maybe we end up doing both, just to see which approach works best. I will probably do the UPnP stuff anyway at some point, to support playing on UPnP clients.

This post is long enough already, but I can elaborate on the idea if anyone wants to listen.

br,
sambuca

I'm just trying to confirm that it doesn't have an idle shutdown;

No. There is no idle shutdown.

But you can manually suspend MDs, as JaseP mentiones. If you look at the article he linked, you will find how to set it up. The reason you have to manually set this up, is that not all hardware(drivers) play nice when suspended and resumed. So by default, we use power off instead of suspend. Simply change the PowerOffMode device data for the MD in question to "S", reload, and power the MD down from the orbiter.

br,
sambuca

You can create a GSD device, which is a simple way to create new device templates in LMCE. GSDs will set up a serial connection for you and allow you to write code to communicate with your particular hardware.

Search for GSD in the wiki to get started.

br,
sambuca

Hi Raymond,

I haven't tried what you are suggesting, so ymmv.

But I do have a Merten push-button with two buttons (or four as the two are spring-loaded and you can press both up and down on them), so I guess it will appear much the same to LMCE.
The problem with your scenario is that the device will only appear as one device for LMCE. So whenever one of the sensors trigger, LMCE will see an event from the same device. In other words you have no way of telling sensor 1 from sensor 2 etc...

At least, this is how I understand the problem.

br,
sambuca

You're correct, freepbx is not used anymore, and the Advanced -> Configuration -> Phone Setup menu should be removed. Instead, use Wizard - devices - phone lines to set up trunks.
Choose the SPA protocol, and iirc; the username and phone number needs to be equal. It is quite simple.

The SPA configuration is more difficult though, but that should be the same as for 810, so the wiki article still applies.

- sambuca