NEEO recipes: Should one NEEO remote be able to control devices belonging to different sets of recipes without conflict?
My NEEO Brain is located in my livingroom.
These are the devices in my Livingroom recipe:
1 Samsung TV, 1 Yamaha A/V receiver, 1 Samsung cable box, 1 Sony Blu-Ray player, 1 Apple TV.
These are the devices in my Bedroom recipe:
1 Samsung TV, 1 Sony A/V receiver, 1 Scientific Atlanta cable box, 1 LG Blu-Ray player, 1 Apple TV.
So far, my Livingroom recipe works (albeit without full automation due to "Stupid device" screens for my receiver and cable box - Issue currently being addressed on different posts). However, the bedroom recipe will not work unless I bring the NEEO Brain into the bedroom.
Once the Brain is inside the bedroom, my devices respond to commands from my NEEO remote, although with similar "Stupid device" screens for my receiver and cable box, so no full automation either.
Question 1: Why does my Bedroom TV respond to Livingroom recipe commands?
Question 2: Why does my Livingroom TV respond to Bedroom recipe commands?
Both TV's are Samsung, but they are different models:
Livingroom TV: Samsung UN65KS8500FXZA
Bedroom TV: Samsung LN40B650T1F
This is a wide speard "Issue" in the use of IR. The Manufacturers doesn't change much (or anything) from the side of the IR Implementation, unless they need to to be able to get more Function implemented, or if they change the Hardware to it.
I don't know if your two Samsung TV's are from within the same model Year or not, but it sounds like they are not far away in the Production run.
For the Apple TV it does have different Code Sets implemented to be used, but NEEO actually only uses the Standard set, don't know if they plan to implement more sets or if they stay with the Standard one.
Normally it should not make a difference in usage, thats because the IR can't be send through walls. Only Issue is, when using a AV-Rack and want be able to get thinks split...
Thanks for the explanations. My bedroom TV was built in 2007 while my livingroom TV (Smart TV and Wifi capable) in 2016. The most disappointing part of all this is that when we were originally told that NEEO was the only remote we would ever need, we were literally expecting that to be the case. We as end users aren't supossed to bother with questions of "IR code-set implementation" or any technical language like that. I can totally understand these and many other technical concepts if explained to me. But even if I do, how do I explain to my grandmother that NEEO can't play her favorite movie because "it only uses a standard Apple TV. IR code set"? When she asks "does it work?", I can only answer " no grandma" because that is all she'll understand. NEEO was suppossed to simplify things, which is the only reason people bought it. For us, it isn't a question of whether NEEO can control every device in our home, because it's pretty clear that for the most part it does. One of the reasons NEEO falls short of its promise is that it doesn't factor in the reality that many of us own multiple same-brand and model devices that we expected to be controlled by NEEO without too much hassle. Even with these issues, NEEO is a wonderful piece of hardware with lots of potential. I can't wait until the day it finally lives up to its promise.
Great stuff. I hope my language in some of these posts isn't too pessimistic. If so, don't let that fool you. I have a lot of faith in the great team you guys have assembled, along with all the collaborators. NEEO is still in its infancy; yet it continues to be one of the most revolutionary electronic products I've ever put my hands on. NEEO IS the wave of the future; I'm just glad to come along for the ride.