RyanE

It seemed like the discussion was about 3.3.1, as in "it drops support for a piece of hardware and that has upset some people."  Agree that the jailbreaking stuff is a different deal.

My comment relates to Jailbreaking rather than the HC800 being dropped. 

Or start a new thread (which some will read and some won’t)… as the OP, I would like to see this particular thread stick to OS3.3.1 - please…

The topic of this thread is OS 3.3.1.
No one is going to 'fix' this, either way, or convince those with the opposite opinion on the matter.
My gentle suggestion is to let it go, whatever your opinion.
RyanE

The topic of this thread is OS 3.3.1.
No one is going to 'fix' this, either way, or convince those with the opposite opinion on the matter.
My gentle suggestion is to let it go, whatever your opinion.
RyanE

Never mind, I'm seeing the issue now. Control4 tech support got back to me with a login for your system and I think I know what's going on.

Yes, the phone needs to be logged into the project to complete setup and adding a Halo remote through an iPad or Android tablet will be supported.  No plans to support this from the T3/T4 at the time.  

The user setup on the Halo remotes will be done with the Control4 app on Android or iOS, using a QR code provided by the remote on bootup.  It's similar to the Neeo, but entering the data is done on the phone, which makes it much more convenient than trying to enter wifi data using a list-based interface on the Halo remote...
RyanE

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

The user setup on the Halo remotes will be done with the Control4 app on Android or iOS, using a QR code provided by the remote on bootup.  It's similar to the Neeo, but entering the data is done on the phone, which makes it much more convenient than trying to enter wifi data using a list-based interface on the Halo remote...
RyanE

Roku does not have a Voice API, and Control4 doesn't have contacts within Roku.  That is unlikely to happen anytime soon (although, of course, if a Voice API shows up, it would be fantastic).  The voice APIs in Roku are for the Roku *APPS* to receive data from the voice input of the Roku.
Snap One has not announced integration with Dish, but Control4 does have contacts within Dish, so I'm much more hopeful we will be able to make that work.
The price of the Halo Remote is not much more than the MSRP of the SR260 + the Charging Base, which combined was something like $440 MSRP, and value for money, the Halo remote looks to me to be pretty fantastic.
RyanE

The user setup on the Halo remotes will be done with the Control4 app on Android or iOS, using a QR code provided by the remote on bootup.  It's similar to the Neeo, but entering the data is done on the phone, which makes it much more convenient than trying to enter wifi data using a list-based interface on the Halo remote...
RyanE

Roku does not have a Voice API, and Control4 doesn't have contacts within Roku.  That is unlikely to happen anytime soon (although, of course, if a Voice API shows up, it would be fantastic).  The voice APIs in Roku are for the Roku *APPS* to receive data from the voice input of the Roku.
Snap One has not announced integration with Dish, but Control4 does have contacts within Dish, so I'm much more hopeful we will be able to make that work.
The price of the Halo Remote is not much more than the MSRP of the SR260 + the Charging Base, which combined was something like $440 MSRP, and value for money, the Halo remote looks to me to be pretty fantastic.
RyanE

LOL.  I didn't even realize that it was gone in 3.3.1.
To be fair, my brain is a bit fried post-CEDIA.
RyanE

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

Short anwser is no (with the actual drivers). 
Sony API is HTTP based, and C4 doesnt poll info of status of the TV. At least the tests I had made. 

This problem is not only when you turn on via Sony remote, also if you change the source with phone: Example: You are watching TV from a provider box, and then you launch the Netflix from the phone APP. C4 wont notice the change of sources. 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

A non-official reply to answer a few of the questions / statements posted here:
The 'OFF' ('Room Off') button is on the top of the remote when looking at the remote face. The thing on the top of the remote that looks like an IR window is a light sensor for display auto-dim. The microphone is located on the top of the remote. Both the Halo and Halo Touch are *Wifi* remotes, 2.4GHz + 5GHz.  The Wifi chipsets in these remotes are much more robust than the Neeo.  Despite running at CEDIA (horrible Wifi environment), the remotes did not 'drop offline' or just fail to control the system, although they did from time to time have delays, which is understandable due to the environment and also they are pretty early pre-release firmware. Announced at the show is voice integration with Xfinity X1 and AppleTV, both are updated versions of the existing IP drivers. The 'voice target' for the remote is currently the selected device in the room, so the AppleTV example would require the AppleTV to be the active video device to receive voice. The Halo remote is *NOT* a touchscreen, it is list-based, similar to (but significantly improved on) the SR260.  While you could accurately say it's a replacement for the SR260, Snap One has not to my knowledge expressed an EOL for the SR260. The Halo Touch remote is a touchscreen, and it is a replacement for the Neeo.  The UI is not the Neeo UI, and is not Android. Both remotes are running a more full-blown base OS than the SR260 or the Neeo, and I believe it will allow Snap One to do some really fun update features post-release, although of course, I'm only going to discuss things that are currently announced or were fully discussed at the show. I'm excited for the new remotes, and hope they'll be as awesome as I think they will be at release (and later!).
RyanE
 
 
 

LOL.  I didn't even realize that it was gone in 3.3.1.
To be fair, my brain is a bit fried post-CEDIA.
RyanE