IR sender

Just bumping this in case this has already been added and I've missed it or to see if it's still on the to do list? IR control is the final piece missing from my switch over from Vera.

Another shameless bump!

I really want some sort of IR control for Xmas when SWMBO gets out her IR controlled candles etc. If I'm not going to be able to use my Keene KIRA system (it needs UDP) are there any other ways of connecting an IR sender that doesn't involve a raspi server? Is there anything I can get that I could use via IFTTT?

Take a look at a Flic Hub. That should be able to blast IR under IFTTT.

1 Like

Also take a look

Thanks for that, I haven't come across the Flic Hub but it looks promising for what I want. If UDP isn't coming soon (any news @patrick?) I think I'll get one to try it.

UDP support is already in the hub. We have some changes coming in the next update that should round out the support for it.

1 Like

I didn't know that, Is there any guides as to how to use it?

Nothing public yet. If you are interesting in developing UDP drivers, please pm me and I can provide some non-public examples to get you started. We hope to have this finalized in the next release.

@Geoff_T sorry, it looks like I spoke to soon regarding IR from the Flic hub. It isn’t available yet but is much requested.

I'm a new-ish hubitat owner and new to hub-based smarthome control. I bought the hubitat to move from cloud to local. I'm grinding through the conversion and getting it to work. A good number of us over in reddit use cheap Broadlink RM Mini3 IR blasters to control older appliances with IR remotes. I use two (one upstairs, one down) to fire up some old Roombas. Another popular use is for old paddle fans.

Does this UDP give us a way to control these RM Mini3s? If/when I can do IR blasters, I'm off the apps.


Do you have a UDP Parse example. I am having problem extracting the payload using response.payload (similar to in http).

The response is text and I need to extract the payload (response.payload).
def test = new XmlSlurper().parseText(response)


I know this is dated, and I have not read the whole thread, but by definition UDP is sessionless. so, would it be reasonable to expect a response from a UDP packet? I think if you wanted two way UDP sessions that they would be using something like RTSP, or just use TCP.

Did you look at the Lifx drivers? It's protocol is UDP. That's a working example. :slight_smile:

After flashing the Hub IR Tuya with Tasmota, I started to develop some drivers to use it in Hubitat
Initially I made this driver, which sends an IR command to turn the device on and another IR command to turn it off

Like this

Then I went to a driver where I could control an air conditioner

With this driver you can turn the air conditioning on and off, and adjust the temperature (the reference is the cooling temperature), working very well on Alexa

Then I ended up making a scene driver, where I managed to connect a TV, change the TV's HDMI input and then the channel to a chosen channel on the TV Box

Finally, I'm trying to develop a driver to send TV commands, but unfortunately I'm having problems because the dashboard doesn't accept adding these commands, Alexa doesn't accept it either.

I need help and reviews that can improve these drivers
Regards, Jorge Palmeira

1 Like

Good luck Mr. Palmeira, I look forward for the final result! :grin:

1 Like

Great work. I ordered a hub about 2 months ago but would not flash, as tuya did something with the hub. How did you get yours to flash with tasmota? Or is yours an older tuya hub?

1 Like

Did you tried this tutorial ?

Ah, perfect. I was attempting to use the OTA method and it failed. So this is perfect , I have all the supplies from prior flashing of sonoff devices.
Thanks very much for the reminder and link to instructions.

1 Like

EDIT- My pin pads were in different locations than the device in the tutorial. I hooked them all up and it took the flash, ESPEasy indicated success with Tasmota_IR.bin, but the device is now dead, won't bootup, no led and can no longer connect to it via serial port. I killed it!
Even tho mine is version 1.0 I'm thinking the original device , that the linked tutorial method works on, was somehow different from mine