Author
Topic: Motion sensors, how to get them working? (Read 2168 times)

I have been trying on and off for the last 3 months to get pluto to work for me. In my last attempt this weekend i have managed to get my CM11 to communicate to my lights through the orbiter which is great, but I really need the montion sensors so that lights in the rooms turn on as people enter.

I have setup my W800RF32 through the INTERFACE tab, and after I restarted the pluto box, as soon as I transmit a signal to the W800RF32 either via a motion sensor or a remote control, i start to get

That means the cm11a device is getting incoming data (ie sending something to the PC), but the cm11a software doesn't have a handler for incoming data. This is actually harmless. But what that means is when the device was written, it clearly was only written for handling outgoing commands (like lights on/off) and there's not even a handler for incoming commands (like motion sensor tripped). So I think what you did was correct, it's just that the support wasn't added to the cm11a software.

I am confused as this log was coming up in the W800RF interface log, not the CM11. I would of thought that if I could select the W800RF to be added through the interface tab, that pluto could work with it.

Does the W800RF work in pluto? Has anyone been able to get it to work?

'I looked at the device template for W800RF32. That was user contributed -- nobody at Pluto created it. But, i don't see *any* gsd codes at all for it. So I don't see what anybody would expect it to do.

Regarding my post about cm11a, as I said, when you get that message: Command 350 not supported. that means the device isn't setup to handle incoming data.