7ba79d5c92
* first version of "modular-approach" * changed keyboard commands for HOME and BACK * Update README.md * only some typos in comments * readability * comment for what the mqtt keyboard is used * removed numbering of tab variables. not needed anymore * changed the default keyboard from "´mqtt keyboard" to "BLE keyboard" * updated to latest version of keypad library from Github, changes for inverted logic are explicitely marked * added comment for key repeatModes * added comment for MQTT keyboard * setting timout via GUI now works, not only dropdown without functionality * BLE indicator added; separation of BLE/WiFi activation from activation of devices using it * report battery level to BLE device * Dynamic keyboard commands, so you can safely deactivate BLE and/or WiFi and not break the example code * reorganized files into folders * moved lv_conf.h into the gui folder * added devices for appleTV and smarthome * assets.c broken up and placed them where they are used * added support for IR RC5 * reorganization of files and folder * added comment * renamed assets files * introduction of gui_registry * removed unnecessary functions from sleep.h * use gui_registry.h only once * some files renamed for better understandability * minor renaming * some more renaming * check if WiFi label was instantiated before using it * introduction of a scene registry * save prefs directly after timeout is changed * renaming of preferencesStorage * comment added * only readability * detailled definition of key layout for the diferrent scenes * made code compile for "device_smarthome" when WiFi is deactivated * fixed access violation when no scene was active * added support for IR DENON commands * increased lvgl heap from 32K to 48K |
||
|---|---|---|
| .github/workflows | ||
| CAD | ||
| LVGL Simulator | ||
| PCB | ||
| Platformio | ||
| LICENSE | ||
| Menu.gif | ||
| P1030424_small.jpg | ||
| parts.jpg | ||
| README.md | ||
| sim GIF.gif | ||
| Solder GIF.gif | ||
Changes in this fork
For changes in this fork, please see https://github.com/CoretechR/OMOTE/discussions/58
OMOTE - Open Universal Remote
Overview
OMOTE is an ESP32 based open source universal remote. Its capacitive 2.8” touchscreen provides an intuitive and snappy user interface for switching devices and settings. No hub or docking station is required as the remote features infrared, Wi-Fi and Bluetooth connectivity. With its well optimized power consumption, OMOTE can run for months on a charge. And since the design files are open source, you can fully customize them to your devices and needs.
Features
- 2.8” 320x240px capacitive touchscreen
- Ergonomic, fully 3D printed case
- Responsive LVGL user interface
- Built in infrared, Wi-Fi and Bluetooth
- Press any button or simply lift the remote to wake it up
- Up to 6 months of battery life using a 2000 mAh Li-Po battery
Dependencies
- espressif32@^6.1.0
- lvgl/lvgl@^8.3.4
- bodmer/TFT_eSPI@^2.5.23
- sparkfun/SparkFun LIS3DH Arduino Library@^1.0.3
- crankyoldgit/IRremoteESP8266@^2.8.4
- adafruit/Adafruit FT6206 Library@^1.0.6
- knolleary/PubSubClient@^2.8
- Chris--A/Keypad (modified for inverted logic)
The State of This Project
The hardware for OMOTE is designed to be easily replicated, using 3D-printed parts, a 2-layer PCB and commonly available components. The mechanical and PCB design can be considered mostly complete. Still, there might be areas for improvement, for example the IR range could be further optimized.
There is still a lot of work left to be done in terms of software. Right now, network settings, buttons and screen layouts are hard-coded. Controlling devices via MQTT is more of a tech demo at the moment and the network connection might not be perfectly reliable. Making the interface configurable, e.g. using a web interface, is a long-term goal.
To Do
Currently I have no idea if and when this will be done. But these would be the next steps:
- Easier configuration
- Document the current process of customization
- Store the configuration in Flash (e.g. as a editable json file)
- Add an interface for graphically editing the configuration
- Complete the on-device settings page
- Make the Wi-Fi connection more stable
See the open issues and discussions for a full list of proposed features (and known issues).
Getting Started
OMOTE might look like a finished product, but especially the software is not "consumer-friendly" yet. If you want to build your own remote and customize it to your devices, you should be somewhat experienced with electronics and programming.
Simulator
You can try the user interface on your PC using the LVGL simulator. Just follow these steps:
- Install Visual Studio, including the "Desktop development with C++" workload. You can use the free Community edition.
- Start Visual Studio and open LVGL.Simulator.sln
- Make sure that the build target is set to x64 and then run the local Windows debugger.
Hardware
The central component of OMOTE is its PCB. If you want to build the PCB yourself, you will need SMT-reflow tools like a hot plate or a hot-air station. The 2-layered board and a solder paste stencil can be ordered from any PCB manufacturer using the KiCad files. Manufacturers like OSHPARK or Aisler will accept these files directly. For JLCPCB or PCBWay, you can use their plugin to export the optimized Gerber files. A zip archive with theses Gerber files is also included in this repository.
I sourced the electrical parts from LCSC, but most of them should be available from the usual suppliers like Digikey or Mouser as well. You can check out the BOM for all the necessary components.
The project uses a 2000mAh Li-Ion battery with a JST-PHR-2 connector. Any 3.7V Li-Ion battery that fits into the 50x34x10mm dimensions should work alright. Please make sure to choose a battery with integrated undervoltage protection (usually visible as a small PCB under Kapton tape between the battery cables).
The 2.8" capacitive touchscreen can be sourced from Adafruit (2770). If you look for the part number CH280QV10-CT, you can also buy this display directly from the manufacturer via Alibaba. Shipping from China is expensive, so this only makes sense if you order multiple displays. In general, the cost for a single OMOTE is quite high. Check out the buy-sell page on the Discord to see if you can share the cost of the PCBs and components with others.
The housing and buttons can be printed using PLA or PETG. I sliced the models with PrusaSlicer with a layer height of 0.25mm and printed them using ColorFabb PETG. It is important that the case part is printed with its flat side towards the print bed using lots of support structures. If your printer is well calibrated, the cover plate will snap onto the case.
Software
The remote can be charged and programmed via its USB-C port. Open the PlatformIO project to compile and upload the code to the ESP32. Within the code, you can edit the Wi-Fi settings and the button mapping. OMOTE features a IR-receiver which is not currently implemented in the code. You can still modify the ESp8266-IRRemote RecvDump example to read the codes from your TV remote.
Contributing
If you have a suggestion for an improvement, please fork the repo and create a pull request. You can also simply open an issue or for more general feature requests, head over to the discussions.
License
Distributed under the GPL v3 License. See LICENSE for more information.
Contact
Join the OMOTE Discord: https://discord.gg/5PnYFAsKsG
Maximilian Kern - kernm.de
Project Page on Hackaday.io: https://hackaday.io/project/191752-omote-diy-universal-remote