Yio Remote Community

Out with NEEO, in with the Yio

I’m pretty excited about the Yio remote. Seems like what we were hoping for out of NEEO. I have 2 NEEO’s I’d love to replace both with Yio. I’m looking forward to hearing more. I do have some questions and possible requests.

  • Are infrared sensors included?
  • Will Yio have a base station with IR repeaters?
  • I have a cable box, Apple Tv’s, Nvidia Shield and Fire
    TV’s. Will these work via Bluetooth or IR?

I realize some things are still in the works, I have a house full of tech that I wish to use Yio with. I’ll check back often. Thanks in advance.

Chad

1 Like

The idea of the YIO remote is simply as an interface tool for your connected hub/devices.
At this stage, no direct contact via IR control will be an option.
What is hoped, is that developers will design a plugin/page for control over IP for said devices. Like a cheap Broadlink IR controller, or Global Cache IR emitter.
The remote has the possibility to control devices like Sheild TV over Bluetooth, but again this is up to a developer lending their support to create a device descriptor for the YIO remote.
Basically the YIO remote is an open sourced platform that will allow developers to create their own integrations for their own platforms. Whether it be a simple Sonos Speaker, or a whole Automation system like Control4. Marton is developing the basic platform for this, with some added features and integrations with help from others.

1 Like

woul love to see some more support for a full blown remote. I love the opensource approach but I also think that there are a lot of people not able to work on this. There should at least be some infrared base, a data base with remotes to controll them. there should be some devices supported from the get go like Sonos, Philips Hue, Nest, Shield tv, etc.

if you want to go big, develop a full working one. if you want to stay in the hands of a few the community dies fast im afraid

People have different needs and it’s impossible to cater for all of them. I think key to creating something that works is that a line has to be drawn somewhere. I’d rather have a working version of a remote with less features than a remote with a lot of half-baked promises.

Probably you know that I am doing this next to a full time job :slight_smile: I made this remote for myself first, but after seeing a lot of interest I started developing version 2 with buttons and started to build a platform and community. It slowly progresses and I hope it becomes something that a lot of people use.

3 Likes

Quit your job work on this instead :wink:

Coming from the NEEO there are a lot of things I liked about it, but also a lot of things I didn’t like.
do you have experience with it?

No, I’ve only seen pictures and videos of it.

I’ve ended up with the current UI and behaviours after build a couple of prototypes and trying it out. Basically built it up around common sense. Tried to make it as simple as possible. Also for the users and also for developers to add features to it.

What things did you like and didn’t? Could you share them?

pro’s

  • built quality
  • database
  • z-wave (once used it before i got Homey)
  • app/overal UI
  • screen/response
  • button layout
  • base station was heavy, so the remote came out nicely (magnets)
  • HDMI CEC
  • helpdesk/community responsive
  • SDK

cons

  • bluetooth not activated
  • hand recognition not activated
  • battery life was not as promised
  • needed helpdesk to add devices
  • no infrared learning
  • no device only function (if in activity the remote cant change between devices, for instant if you want to control the TV you need an shortcut/widget in the activity, afterthat you want to change settings in receiver, you need an shortcut/widget for that one. your screen is flooded with digital control pads)

In the app you could add devices that were in the database, if it was not in there you could send a request and usually after a day it was added therefor the database grows, good stuff. I understand they would want to manage the database themselves instead of letting thousands of users adding their learned commands making a mess of the database. points taken.

however, for own use it was really handy to have something like IR learning, something i was used to with my harmony remote.

the one thing the harmony remote also could do over the NEEO was selecting a device and turning the whole remote into that specific device. the hard buttons would become navigation buttons and menu/back buttons, volume and channel while the touchscreen displayed all the less inportant buttons you might need or could rearrange for your needs.
after you were done you could return to an activity like watching tv where the volume controls the receiver, the channel buttons would control the settopbox etc.
switching fast between remotes was really a miss, as i stated above it would create ‘recipes’ with 10 slides each of them with control pads for different devices.
for instance if you were watching tv you need to add controls for receiver, settopbox, tv, and other devices to navigate through different devices. after you were done watching tv and wanted to watch some netflix you walk into the same probblem, the slides you just added to control your devices were left in that ‘recipe’ so you needed to add them again making a lot of slides in different ‘recipes’ consuming a lot of time getting right. note: you were not able to tell wich control pad was which so you needed to remember if the receiver was the first second or third control pad.

anyway, a lot of text for such a simple thing. something they were not compelled to change.

for the rest, adding sliderds and buttons were a breeze, Niels de Klerk wrote a great app for Homey letting you controll everything on the Homey by adding buttons to the NEEO, this was a walkarround the crappy z-wave controller and implementation on NEEO.

simple things as changing the background, adding time, reducing sensitivity, recuding brightness, turning off the LED on the base were all things that were planned but most of them never saw daylight.

customizability was not really the case here, something that I really like about your approach, how ever is that somewhat to complicated for me. if there was an interface (webbased) where you could add different buttons/slides/toggles/displays/information and linking different actions it would be great. If you have to have programming skills this is not for me :wink:

1 Like

Thanks for the detailed descritpion. It sounds quite complex just by reading about it :slight_smile:

The various entities like lights, blinds, etc. won’t be customisable. The UI will change according to what features your device supports, for example: dimming, colour, etc. Same goes for basic entities.

I’m not at the stage where I’d work on TV remote components, but my goal is going to be the same to create a UI that is intuitive and easy to use. Will see how much customisation is needed in these cases.

Hopefully the whole thing is going to be easy to understand, so you won’t need programming skills to configure it for basic needs. However if you want a fully specialised and customised component, you’ll need it :slight_smile:

Thanks for elaborating! I’m very curious how this turns out :slight_smile: will follow this community. Good luck and keep up the good work!

1 Like

dont be that pesimistic. I just wonder why you make a fuzz about infrared and than mention lots of devices which dont even use infrared. Even if it is opensource there can be a third party device which covers that. I for myself dont like infrared and with the new devices you dont even need it at ALL.