OK, I am in to test an hourly automation. I have like 8 IP2IRs and IP2SLs, and I never have a problem with my remote control software (The Home Remote), so I wholeheartedly agree this is a Home Assistant issue.
I’ve read just about every post in detail about the global cache transmitters and its a common complaint. It’s even been reported as a bug a long while ago. the problem seems random for me when it fails but I did notice the more I used it, the less issues I had. That’s what sprung the idea for a “keep alive” command.
But I don’t think they are popular with the general HA crowd so a fix is low priority.
I like the format better because they have worked wonderfully for years with demopad, I already have them, and they have a small remote transmitter. I have them velcrow’ed to the back of my TV and a tiny remote emitter with foam tape to the bottom of the TV sending the IR. Cant see it, everything is tidy. The alternatives are a big broadcast things you have to place visibly in the room somewhere.
1 Like
Man I hope you can help. I'm running Home Assistant 2026.4.0 and I'm trying to get my GC100 to work. I added this to my config.yaml:
Example configuration.yaml entry
gc100:
host: 10.10.10.17
port: 4998
Then I restart Home Assistant. When I look into settings and integrations there is no integration. The same happens when I look under settings/devices. No joy.
Not sure what I am doing wrong as I read almost every posting about global cache I can fing.
I have had my GC100 for several years sitting on a shelf as I didn't have a system as good as Home Assistant to try to add it to.
I have several Samsung TV's that I want to be able to turn on in the morning with an automation.
Oh one other thing. Does my GC100 have to powered up and attached to the network?
Thanks
see instructions above but I would suggest you create a new file remote.yaml and add
remote: !include remote.yaml
into your configuration.yaml file.
That separates your new programming changes for the remote into a separate file.
you can copy and past the contents of "remote.yaml" above into your own file, then edit it to your needs.
And yes your GC100 needs to be powered and attached to your network. If that wasn't a joke, you have a steep learning curve ahead of you to make this work.
Am curious if that worked for you as well.
its been solid for me after adding the automation.
Turn on? Did I really say that? 
I loaded everything up like you said, rebooted, and went to Developer tools>Actions and the "damn" thing worked like a charm.
Now all I have to do is go in and change to Samsung and test it with the TV.
Thanks for all the help. I'm chuffed.....
When I fired this up and went to the integration I discovered that I had an integration for my Samsung TV. How would I go about combining the two.
Thanks. Have a great weekend.
Glenn...
Combining the two?
If you are talking about the lovelace/dashboard, I use bubble cards and universal-remote-card.
The "touchpad" and white buttons of that is mostly for Roku, and 2 buttons for lights and "watch TV" and "all Off". The top bubble card has an "all off-on" toggle that changes the tv, amp, and roku. The volume bar controls the amp.
The bottom yellow buttons take you to different pages for "more", "amp", "TV" and a list of roku channels.
So in my dashboard, white is IP commands, Blue is IP-IR commands, Purple are automations or macros that does multiple things, and yellow takes you to a different page.
Thats the buble cards popup for "more"
and "AMP"