My complete control suite just updated and the MX900 software has the variables working.

Have you tested yet...?

I am working on one now. Seems to be working great!!

Just like the KP-900, you get a total of eight.

MXEditor Version 1.10.130
Firmware: 1.57

Mike

Any idea if the tx-1000 was updated as well. I know these are all built on the same platform....

Seth

Yes.

This is SOOOOO sweet, but only 8? I suppose it's a memory thing...

Thanks for listening URC! (now how about Device +/- ... heh)

8 seems pretty much in line with what was originally mentioned/promised... if anyone wants more info on how to use 'em in the software I've updated my MX-900 review with a couple of pages at the end.

I read an awful lot of posts and publications about URC, some negative. I just want to say that for them to go back to older line and add this feature is truly exceptional. For all you bashers and complainers, it is very rare in any technical industry to enhance an older product line because your public asked for it even given an alternative.

Thank you URC for making this popular selling remote a great deal more powerful, but most of all for really doing some good old time customer service enhancement.

It's possible this finally got done due to the recent release of the KP-900 (which is a MX-900 in a - oh wait, you'll have to wait for the video...)

Wow, I'm impressed - didn't think this was ever going to happen.

Now the only problem is going back to all the customers with toggle power/input devices and programming the remotes to work as they should :D

As discussed in another thread, variables are really powerful and useful, but they're really not a worthwhile solution for solving power or input TOADs. Without some form of power or state sensing (such as the MSC-400) the remote only THINKS it knows what state the device is in.

As Daniel noted in the article here on Remote Central, it's possible to use variables for power or input tracking to construct a useful "Fix It" screen (such as the MX-810's Help pages). But from what I'm reading here, that's not what many people are planning for; they're imagining the variables as solving the TOAD problem entirely.

In practice, using variables to solve TOADs works great right up until one of your components misses an IR command (and they all do). Then the remote is convinced that your component is in the "Other" state. And trust me, that's a lot more frustrating than the TOAD problem in the first place.

Best regards,
Dale

I rarely use variables to solve TOAD problems - they are nice, but not bulletproof. In the case of the MX3000, I use them more for avoiding delays, tracking zone status, room status, what acrivity user is currently enjoying, etc. If you want to solve TOAD problems you need the MSC-400 at least and a little luck with what your client has out there.

For cable boxes with TOAD, since the power sensors are rearely an answer, I give my client a power on/off button which just applies a power command and sets the variable to on or off. I do not check for status in that case. My reasoning is that he will turn on the system, cable box will for some reason not go on, he will press power on when he gets to the cable menu on the remote, cable will go on, the remote variable is set, hes back on track.

This Daniel guy.. he may not be so dumb.. ;).

From a CI's standpoint, that's true, but you've got two types of users here on Remote Central. If you're programming the remote for yourself, then power variables can be very helpful. If you're programming it for a customer, then they're something to avoid.

Mike