Hi, my name is Markus and I am one of those disgruntled NEEO backers. Now I’m enthusiastic about YIO.
I’m still using my two NEEO remotes almost daily and have automated pretty much everything in my flat and home theater setup. But since it all came to a harsh end 8 months ago, I haven’t visited NEEO’s forum nor continued my own driver development (myStrom WiFi switch driver and other unpublished stuff). Mentally I already prepared myself to switch back to Logitech Harmony…
What a mistake! I just discovered @Nklerk brain hacking and even more importantly this truly AWESOME project.
YIO is exactly what I am looking for!!! Thanks a lot @marton for your tremendous efforts, the professional look of your project and the upcoming diy kit. So exciting
I am ready to jump in and contribute!
Who am I and what can I offer?
I’m a software engineer living in Bern, Switzerland. Besides mountain biking, I like to tinker with electronics, Arduinos and lately ESP32 in my spare time. Even though my apprenticeship was in electronic engineering almost 25 years ago I’m no hardware guy at all. My passion is designing and writing quality software
I need some time to wrap my head around C++ & Qt again. My last professional Qt project was over 10 years ago… Whenever possible I stick with Java, which might come handy if I see a need writing a custom openHAB integration driver. My specialty is system integration, backend services, service communication and in the past low-level industrial device integration. So don’t expect fancy GUIs from me
After quickly glancing over the GitHub sources I see the following possible contributions:
- Fix initial WiFi setup: doesn’t work with SSIDs containing spaces. I already found what’s wrong and will create a fix & PR in the next few days.
- Setup & development documentation since I have to start at the beginning and get up and running. Should be helpful for other newcomers.
The first challenge is creating the RPI image and get it running on my own hardware, minus the special sensors and battery circuit and using my spare Pimoroni’s Hyperpixel 3.5 as alternative display (it’s a similar DPI display with the same resolution used in YIO, now replaced with HyperPixel 4.0 model).
- Automate the development environment setup. Either with Ansible, Vagrant, Docker, or a combination thereof. Goal: Linux VM or container with all toolchains ready to create an RPI image from GitHub checkout with minimal user interaction.
- Trying to simplify buildroot: instead of the customized forked buildroot project, separate the yio board and pull in a specific buildroot release. This way we can better work together, create GitHub issues, releases etc. Since I haven’t used buildroot before this might take a while…
- Introduce unit tests!
- Modularization / abstraction of hardware devices: simplifies developer setup and opens up future hardware changes / revisions.
- Support for TV, Receivers, Kodi
Just let me know where I could be of most help. I still need a few days to get my initial development environment up and running.
Now off to hacking…