Jump to content
C4 Forums | Control4

Reednatron

c4Forums Member
  • Posts

    29
  • Joined

  • Last visited

Everything posted by Reednatron

  1. I'm probably in the minority here, but actually prefer the Neeo now that I've upgraded my WiFi. The ability to adjust lighting without going 3 menus deep wins over backlit buttons
  2. I found one, but may be interested in yours as well.
  3. Anyone have a spare charger base for a Neeo remote? With or without charge cable is fine. Sent from my iPhone using Tapatalk
  4. Is there a solid TCL Roku TV driver available? Planning on replacing an ancient plasma tv in my bedroom with a budget TCL / Roku, but wanted to make sure control was solid 1st.
  5. I just have a different point of view I guess. This isn't a mobile phone that travels with me away from home, its a device that stays in my room and controls the C4 system in my house. The charger is literally in the same room as the remote. It feels 1000% better in hand than the playskool 260, and has a nice screen for album art/GUI. In my usage, its way more reliable than the Neeo it replaced, and battery life is comparable. C4 is still making the 260, right? If you need 74 days of battery life and simply cannot stand to put the remote on charge, use the 260 and look at yellow text. $500 is too much for what it is, but the Core controllers are expensive as well. Inflation I suppose. Also: I've used about every Harmony remote that exists and prefer the feel and utility of the Halo.
  6. I'll be honest, I didn't expect much more than a day given the large screen and nature of the remote. There was a bug with mine that didn't allow the screen to time out that drained the remote in a few hours, but a reboot solved that. For us the charge cradle/stand is the logical storage spot for the remote. It's on an end table. I suppose if someone is using this outside, the charge stand might be weird, but that would be a better use case for a 260?
  7. The battery isn't an issue if the charging base is in the room, is it? Put it on the charger at night and it'll be good for a day's use.
  8. Yes, no onscreen in that room. My AV processor does fine with the three other AV sources connected, but loses handshake with the Core 1 after first use, every time.
  9. Mine required a reboot to turn off the screen, it was "always on".
  10. The TV icon above the directional pad button pulls up the On Screen. Or it would if my core controller could maintain a HDMI handshake.
  11. My Halo screen wasn't turning off, a reboot cured the issue.
  12. Is the screen on this remote an "always on" feature or am I missing a setting or something?
  13. Still having the no handshake issue with my Core and Lyngdorf processor as well.
  14. That's good to hear. I didn't know it was developed with Apple's support. Thanks!
  15. My integrator got me up and running with a Halo and IP/Voice control of Apple Tv last night. Do we expect the integration to continue to be solid, or will this be broken in the next Apple software update?
  16. Thanks guys, that's awesome news. Will using the analog preouts from the Core have significant less/more delay than the Triad one that's also in my system? Will there be a noticable difference in audio with all zones playing same material?
  17. As the title says, I’m curious about using a Core 3 for a preamp feeding a “dumb” amplifier for zone audio. What are the issues of doing zone audio this way, other than having limited matrix type control for different sources/zones? Planning on adding 2 outdoor zones with the Core 3 feeding a 4 channel amp via the analog outs. Will this function correctly? Sent from my iPhone using Tapatalk
  18. Yes, no audio/video Sent from my iPhone using Tapatalk
  19. Not just a Core1 Also happening on a Core3 Requires a replacement unit to be sent out. A Lyngdorf processor and a big box Yamaha receiver are pretty far apart in the spectrum, so I seriously doubt that everything in between works perfectly. Sent from my iPhone using Tapatalk
  20. The Core controllers have a HDMI handshake issue with most AVRs. My Core 1 will not handshake after the first handshake unless the controller is rebooted. My Core is connected to a Lyngdorf MP60, but I have a friend who is having the same issue with a mass market AVR, so I know it isn't a Lyngdorf issue. Major bummer to "upgrade" to a new controller, only to have functionality break.
  21. The Core controllers have a HDMI handshake issue with most AVRs. My Core 1 will not handshake after the first handshake unless the controller is rebooted. This is persistent, even after changing the output resolution manually. My Core is connected to a Lyngdorf MP60, but a friend of mine has the same issue with a lower end mass market receiver, so i'd say the issue covers the spectrum of most installs.
  22. Sent you a PM Sent from my iPhone using Tapatalk
  23. Just a quick update, system is working flawlessly. Control4 is awesome Sent from my iPhone using Tapatalk
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.