First the simple... Does anyone make an ambient light sensor of any kind suitable for use with the MSC-400?

Are the MSC-400's sensor inputs limited to high/low? In other words, on/off reported from the sensor. Or are do the inputs accept a range of values?

Can logic (if/else) test the sensor inputs for more than high/low (bool)? If not, then the above question is moot. :)

I was getting ready to set up an MX-980 with MRF-350 system but have since started looking at the possibility of using an MSC-400 with an MX-880. The hope here is that the logic capabilities of the MSC-400 would overcome the shortcomings of the MX-880 in this regard. Basically offloading as much as possible to the MSC instead of relying on the remote.

Obviously the expanded logic of the MSC won't help affect the displays/layout of the MX-880 since neither is 2-way capable. I also realize that the 880 will never have the freedoms the 980 has in terms of customization. But it does bring a (subjectively) better button layout and that's very important.

The most important question is an expansion on the above. At this time there likely won't be much use for the external sensor nor RS-232 capabilities of the MSC-400. It's primarily intended to beef up the capabilities of the MX-880. Is this a reasonable idea?

Lastly, does the MX-880 support timer events in the same vein as the MX-980? Namely is it possible to have an event set for a specific time of day to then trigger a macro/button which then sets a variable? Basically the functionality described in this thread: [Link: remotecentral.com]

Thanks.

I looked at the MSC-400s and the programming guides and can only find booleans (on/off) for the sensor input. Now having said that URC makes a voltage sensor that a ambient light sensor could be hooked up to, according to the users guide information. The light sensor would have to generate between 3VDC and 25VDC, when "on".

Don't know the MX-880 to give you a good answer on the MX-880 capabilities.

I did a little more rooting around this afternoon and have pretty much come to the conclusion that the MSC-400 will work well for my setup and should allow a few interesting choices down the road. I'll also be using the RS232 capabilities sooner than expected, as the spec I've just obtained for my new PrePro shows it offers a much better level of control versus its IR input. I should be able to create some really versatile macros.

I'd still love to find out if the 880 is capable of the same timer event as described in that other thread for the 980. This is more of a desire than an absolute requirement, but being able to set at least one variable to indicate a time threshold will go a long way to automate a few extras that should be based on an evening-only schedule (such as certain lighting).

The 880 will not do timed events.

I have a MSC-400/MX-880 setup and I am using, RS232, video sensors and variables to control several zones. What is odd is that the MSC-400 does not do timed events either.

Umm, that's really too bad. I knew the MSC-400 didn't support timed events, as it doesn't have an internal clock (shame). I recall that the 880 does have a clock, but I suppose URC could have dropped the timed event capability to keep the remote below the higher end 980 model.

If this is the case, it means I may have to go with 980/MSC-400 in the end as I very much want to have the ability to have the controls differ at certain periods of the day.

You will love the 980 by the way.

I've confirmed what ADK mentioned by referencing the 2008 line catalog which contains a feature table. No event timers on the 880. Only on 980 and up.

The 980 offers great programming ability, but some of it is going to be duplicated and rendered moot by using the MSC-400. It's a shame to have all that extra juice and not actually be using it. :)

It still looks like the 880 will do for some clients though, so that's good news.

The MX-980 is about 30% more in price but offers 100% more in functionality.

The MX-880 is a quirky remote to program in the CCP. Not being able to change font sizes or easily put graphics on device pages makes upgrading to a MX-980 well worth it.

Unless there is a deal going on for a MX-880, I will eat the price difference and always upgrade the customer to the MX-980.

Its to bad because I personally prefer the layout and feel of the MX-880 over the 980.

I really like the MX-980 (have three at home). Easy programming, good graphics and good button feel. Very intuitive layout. I don't think you'll regret the choice (except for the lighter wallet).

Don't get me wrong, I really enjoy using the MX-6000 for the 2-way capability but for ease-of-use the MX-980 wins the WAF award.

Everyone nailed it. The issue with the 980 isn't necessarily price (and it isn't in this case), but rather that it's based on an older physical design. The 880 (and 810 for that matter) are a newer design that frankly, is just better laid out.

In terms of what's under the hood, I think saying that the 980 is 100% greater than the 880 is an understatement. :) The 980 has a lot more memory and processing power.

Both of them will still program easier than the custom stuff I work on now, so we'll see how it goes.

Well, we do have the MX-5000 for 2-way in a wand format. It is, by far, my favorite of our remotes.

The MX-5000 is a fine looking product. Too bad the MSC-400 isn't also 2-way however. BTW, physical number buttons aren't needed on a remote primarily intended to control current equipment (so well-decided choice there). Just thought I'd toss that in since I noticed you getting a lot of undeserved heat in another thread about that.