msgreenf

Except that stuff is still supported.  Nobody is making you update, all of those products will still work, and you'll continue to receive C4 support on all of them.  I'll never understand why people would want C4 (or any manufacturer) to throw engineering resources at things like making new systems backward compatible with old hardware that isn't designed for the new systems vs working on innovation and new products.  

It's much more of an engineering effort than "didn't try very hard".
The new OS3.0 UI is Android-based (like the EA series and T3 touchscreens), and running that on the HC800 that has never run Android (and the hardware was *not* chosen to be Android-compatible) is very much a non-trivial task.
If it were easy, Control4 could've done that when they came out with the OS2.X Android UI...
The HC series were specced and built to run dual Android / Linux.
RyanE

This site is very similar to Instagram and other social media.  Makes me laugh.
I also find it funny when people are saying they won't upgrade because of potential bugs and they don't want to be a "beta" tester.  However, I've seen the same people say they are waiting for the "New" hardware to drop then will upgrade. 
1.  Pretty sure you are going to have to be on 3.0+ with this "New" hardware.  The HC series will be EOL and top out at 2.10.6 (basically) for full functionality.
2.  New hardware - so that's not "Beta" testing when it's first released?
3.  People are just mad that they don't have EA series controllers and that's why most of them are not updating.  If that wasn't the case, why did you go to ZigBee Pro instead of embernet?  Why go past 2.9.1?  Why did you get rid of the HC500 and HC1000?  I mean, the original portable touch screen was nice. lol. Good thing humans didn't just invent fire.
4.  Update is good - Much needed.  Does it need more, yes.  But, they just started a new foundation for the way their vision is heading.

Blazing clarity

Sent from my Pixel 3 using Tapatalk

All the Domosapiens drivers available on DriverCentral are now JIT-enabled to benefit from this new execution environment under OS 3.0.  Either Auto Update or download the most recent versions.
Paul Biron

And kudos to C4 and Domosapiens... for anyone else with this issue, whatever the original cause, it has now been unblocked and Domosapiens have kept me in the loop with hourly emails, so I can’t complain...
Now the upgrade has begun and I should wake up tomorrow to a new system - I hope!

it's version 3  lol  But i hear you - early adopters should expect some level of pain. 

The answer is no it does not support 1080.
The EA controllers display cameras at a maximum of 720. The EA controllers can only perform software decoding of H.264 so they are limited to 720.

Isn’t the Ring elite like $500? No cutting required cause they’re all surface mounted beauties. Looks like you screwed a 3 musketeers bar to the side of your house. 
Are we talking the original C4 door stations? Those things gotta be pretty ancient. 

i have same exact TV... works 100% perfectly over ip

I don't disagree, and hope full control will return at some point, but the focus has been on media and cameras from what I've seen, and creating an OSD that isn't 'just a port' from the T3 screens with somewhat awkward controls instead of touch control.
It seems clear to me that a LOT of work went into the OSD so far, more may yet be coming.

I wouldn't bet on it. If there is enough interest, it may make sense to make a new app to accompany 3.0, but that's the issue, the interest is and has been extremely minimal from what I've heard and seen.

You hear a lot of things on these boards that are quite inaccurate. 😉

If I had to guess, the driver was built using the original DSC driver, and that's why it got flagged. As I understand it, Composer checks the source codes for drivers, not any name etc. In other words, drivers aren't blacklisted as such, specific codes and tags are.

Kudos to Domosapiens who replied to my email within 10 minutes to say that they identified the problem over the weekend and believe that the issue arose in the last 2 weeks with some final change to Composer 3.0... They had also identified that the driver was showing as obsolete in the driver database which it shouldn’t (and they are happy that it was working fine in the beta versions of Composer 3.0 up until 2 weeks ago).  Interestingly when my dealer looked to see the obsolete status, he noted that the driver has now vanished from the online driver database... hopefully this means that it will reappear shortly and no longer be obsolete!  They are liaising with C4 to sort the issue.
Waiting on tenterhooks!

it's just been very clearly stated many times. asking again isn't going to change the outcome

So if I financed c4 hardware you would upgrade?

Sent from my BBF100-2 using Tapatalk

You're right. The touch screens aren't iPhones. You paid $1k every (or at least every other) year for 5 years to keep your iPhones up to date.

for the 5th or 6th time in this thread - having an HC250 ANYWHERE in your project will block the upgrade. 
NO 250s allowed - not for anything - again like the 6th time
 

Read out tweets via text to speech.

Control4 never really pre-announced, even before they went to the stock market

it's just been very clearly stated many times. asking again isn't going to change the outcome

for the 5th or 6th time in this thread - having an HC250 ANYWHERE in your project will block the upgrade. 
NO 250s allowed - not for anything - again like the 6th time
 

No. The driver doesn't use the v1 proxy

Sent from my Pixel 3 using Tapatalk

There is a supported QMotion driver. Obviously not sure what one is in your project, but worst case your dealer will have to swap out the blind driver as part of your upgrade. (But if I were a betting man, I’d say you already have the compatible driver installed.)


Sent from my iPhone using Tapatalk