Great idea. I’ve got a RM4 Pro that I use to control my ceiling RF fans via Home Assistant.
But, how many IR codes did you have to teach the Pro and how many scripts / automations did you have to create in HA? Sounds like a massive job.
Also, I’m assuming the IR blaster on the Pro is stronger than the R2 hub. Its RF blaster is phenomenal. It covers my entire house.
No the IR module can do both : receive and send IR commands.
The creator of the integration added the possibility to learn IR commands also, but it does not include my fork yet with the ethernet connectivity (or use wifi if ethernet is disconnected).
I use it in my cabinet as a second dock to transmit IR commands to my STB, HT receiver…
Thanks albator. Is there an version without Poe that you can recommend? I just need a „dumb“ ir repeater to address the projector screen and my receiver.
Not that much to be honest. I always try to keep my setup as simple as I can. I have a Draper projector screen that need to be lowered or raised.
This shouldn’t be necessary if the remote has an working ir hardware.
Well, for IR, I need to control a Sky Q Box, Pioneer AVR and LG TV. My Nvidia Shield has no IR control, so I rely on either IP (R2 integration) or Bluetooth for that.
All the IR devices have MANY controls that would need coding.
I’ve done it once with HA scripts in an attempt to get the R2 working without IP integrations for the devices. Successful, but clunky and laggy.
It took ages to code and I don’t relish the idea of doing it again and having to teach all the IR codes to the RM4 as well.
In that case the integration is ready for use : GitHub - petchmakes/ESP32-IRBlaster-UCR2: An ESP32 IR blaster implementing the UCR2 dock websocket API.
It supports WiFi of course, Bluetooth (for hub discovery), and acts like a real dock to transit it commands
Thanks again. I am looking for an hardware solution ready to buy or at least put it together. I have no idea what this schematic means nor I want to solder something.
As I said there is no soldering : the IR module just plugs in the board through a dedicated connector. Then you have the box to buy also to put all in
In that case the schematic is useless, except for me at start to find out the right pins and apply them in the code which is done
Hi, regarding the Olimex POE board there is also a variant with 16MB flash which costs just 1 Euro more. Is it usefull to buy this 16MB flash variant for possible future uses, instead of the basic variant?
I don’t really know, but the dock doesn’t hold any data, everything is on the remote
Thank you for your reply and your opinion. 
Parts just in. Will be tryinfg to figure out installing the patchmaster driver/software load to the divice and adding new hardwiring., then figure out how to bridge over to the wireless different IP range for wireless, then add ing as a doc. POE at least seems convenient for one less wall plug.
Trying to figure out platformio, and making sure ESP32-POE-ISO is the platform, running more cables, etc. A plug in wireless model would be nice.
BOX-ESP32-POE-ISO-F seems to be a good (but snug box).
I have a wired and powered device, just need to get software on it and hopefully setup as a dock.
Finally got Olimex ESP32-POE-ISO recognized on port 3
Trying to get ESP32-IRBlaster-UCR2-main library included after changing settings.h
No luck
Hi @rudolpht,
which branch of code did you use ? My branch is not fully merged on @petch repository.
Here is the link of my (working) branch : GitHub - albaintor/ESP32-IRBlaster-UCR2: An ESP32 IR blaster implementing the UCR2 dock websocket API.
here is what I did as we have the same board :
On vscode plaformio.ini :
[env:esp32-poe-iso]
board = esp32-poe-iso
platform = espressif32 @ ^6.5.0
framework = arduino
build_flags = -DBLASTER_PIN_IR_INTERNAL=GPIO_NUM4 -DBLASTER_PIN_IR_OUT_1=0 -DBLASTER_PIN_IR_OUT_2=0
The board should not be powered with POE while plugging it through USB to upload the software.
Then you just have to :
1/Select build
2/Select upload
My fork is configured to upload the additional files for the webserver, so nothing more to be done.
EDIT : you have to edit secrets.h first with your wifi credentials if you don’t intend to use and configure the dock through ethernet
EDIT 2: I guess you did it but you need to install the following extension “PlatformIO IDE”
Otherwise you can get help from discord Discord
First off. thank you. As somebody who hasn’t programmed until before C became come, and my last soldering job was piggybacking chips and running tracers to make a 4K main memory computer to a huge 8K computer, the hand holding should be unnecessary.
I was using the wrong fork, had the secrets correct but not the platform10 header (thank you).
However, I’m throwing errors. One quick question am I creating an existing project buy indicating the folder where the correct fork unzipped with two changes sit, then do the steps above. I know, I’m scouring the web to fill in gaps. Once I get this down i have a second set of boards and I’ll be off.
No problem, this has been a long time I have not coded in C too, and especially on embedded device development…
You don’t have to create any project : just File > Open folder
on the location of the files and that’s all.
I am doing the whole process from scratch currently from the new fork from alex.koe:
gh repo clone itcorner/ESP32-IRBlaster-UCR2
One thing : don’t forget to select the right platform, on my fork this is esp32-poe-iso
Just click on the bottom to select it :
I’ll report back
Something stopped working in the compilation, to fix it you have to modify the platformio.ini
[env:esp32-poe-iso]
board = esp32-poe-iso
platform = espressif32 @ ^6.5.0
framework = arduino
build_flags = -DBLASTER_PIN_IR_INTERNAL=4 -DBLASTER_PIN_IR_OUT_1=0 -DBLASTER_PIN_IR_OUT_2=0
Then click on the left panel on PlatformIO icon : click Build, then upload
Update : it works with the modification
Also I tested the latest integration from Alex with bluetooth paring, IR learning and bugs fixed
Like here you just have to modify the platformio.ini file for env:esp32-poe-iso on IR_INTERNAL like this : -DBLASTER_PIN_IR_INTERNAL=4
Built and uploaded successfully : this time no need to prefill wifi password or connect through the webserver, just launch discovery from the remote
So close I can taste it. But I did a quick step ahead which may be biting me. I took the latest branch (17 hours old) which had platform10.ini branching logic, and successfully built and uploaded. Wow. All lights a blinking (with power & wired e net), added as mentioned on the remote. Found and updated hard IP on webconfigurator.
Not seeing any lights on the MOD-IRDA board, so maybe I need to grab another one if hardware.
So I’ll go back and download the main branch of the repo and make edits you mentioned and not skip to latest branch. I know the later branch is trying to add IR receipt, and probably needs a different module, and probably why its not working.
That said thanks for the continued help.
I am amazed it is finding as a new dock etc.