Antsy to get a 3000, this is last impediment. In family product support is important.

not yet, but from what I heard it is planned

I can add that reading MX 800 files isn't really as important as you'd think. Yes, it would be nice, but in the long run, you'll be surprised at how much of setting up 3000 is a totally independent activity. The 3000 can do everything the the 800 can do, but the extra things it can do tend to change the logic behind your programming. Take RC5 toggle bits. The 3000 can handle those natively. To accomplish the same thing on the 800, you have to jump through hoops in your programming.

So yes, the feature is coming, but honestly, I wouldn't wait for it. If you think of the 3000 as just an extension of the 800, you'll end up limiting your creativity in what you can do with it.

Dale

I agree about waiting, but as a feature I think it will be a good one. You tend to see often people asking for codes or how to get codes from a different format. I will also guess (due to price if nothing else) that there will always be more codes/remotes for the mx-800 then the 3000

I actually think it's more important to support HTM products vs Pronto in first release (despite the broader range of CCFs to steal from) just for product consistency.

I spent way too many hours programming the Pronto 1000 then the 6000. I understand the differences in programming a GUI based remote, but I really would like to not have to relearn all the source commands even if I do not use the macros (but that would be nice too. Then I can just link to the MX-800 imported hidden pages and I could rock & roll with an ugly interface until I have the time to make it aestetically pleasing.