Unable to control the volume on my TV after updating my Apple TV to tvOS 17.4

I’m having the same problem except I have my 2nd gen HomePods as a stereo pair I reset my HomePods thinking it was them but it’s not I’ve restarted my Apple TV I don’t know how many times this tvOS 17.4 is horrible it really irritates me beyond measure lol I really don’t want to get on a beta if it comes out this week because I’m afraid of more issues I just hope Apple addresses this soon.

I’m having the same problem. I just updated my HomePod speakers hoping that would fix the problem. It did for about thirty seconds. I knew better than to do this last update. Now my Apple TV keeps dropping my WiFi sporadically when my WiFi is working fine for everything else.

It's a bug in the 17.4 release. I'm sure they'll fix it soon. Try my fix above.

I use a Samsung HW-A47M Soundbar on an Apple TV 4K 1st Gen, it worked fine all through tvOS 14, 15, 16 up to 17.3, and 3 remotes, the original black remote and 2 silver ones. Now suddenly the volume doesn’t have any effect. The volume level goes up and down in the BT level, but the actual volume is stuck at full blast unless I use my Samsung Remote. This is quite irritating. I have a smaller Vivitar BT tower, when I connect to that, the volume works fine.

I found a solution that worked for me. Disconnected and reconnected the remote per the article that @unisfromcapetown stated above and that didn’t work. However, after doing that I held down the TV icon button on my TV remote and noticed that another speaker, something from Google Gemini was connected and it was blocking out the other speakers. I simply unselected that unknown google speaker and all started working again. Hope this helps.

I don’t know if this addresses the problem of the OP but here’s my experience since the new 17.4 update…

My Siri remote lost volume control of my AV receiver after working fine for over a year (ATV4k latest gen). When I pushed a volume or mute button, I got the circle with line through it on the screen with ATV as the source. (As if that function was not available.)

Called apple support and went thru the reset, delete remote, reinstall and learn the remote “dance” with no change. Escalated to the next level…

While working with the escalation engineer, I stumbled on what seems to be a workaround….

I did the “learn remote” cycle again but this time I used the AV receiver’s IR remote to program the vol-up/vol-down/mute buttons. VOILA! All of a sudden, the Siri Remote volume & mute buttons worked. I renamed that new remote “AV System”, selected it as the device to use and went back to normal use. I did this while the escalation engineer was puzzled. We decided I created a workaround to this new problem that may be associated with the 17.4 update.

Conclusion-It seems the update erased, eliminated or otherwise deleted any IR references to the ATV Remote volume settings. Using the original remote, I reprogrammed a point of reference for the ATV remote to duplicate (clone?)

I’d imagine Apple will incorporate a fix in future updates. If it goes crazy again, I know where to look.

There was also a more common inability to control Apple TV with many remote CEC, as of this point The latest available firmware update, does NOT fix this issue. My Samsung sound bar cannot be controlled with the Apple remote, although the Apple remote causes the volume indicator to go up and down, but the actual volume out of the Samsung device stays full blast, and the mute button does not work.

One way I have been able to fix this issue is to plug my Samsung directly into my RCA TV through the light pipe. and then the Apple TV is connected via HDMI, so that through a combination of HDMI and infrared, I can use the Apple TV remote to control the volume on the Samsung sound bar.

but it’s simply not as responsive.

I’m on a newer firmware, and it is not fixed. When I connect my Samsung sound bar via Bluetooth, it cannot be controlled with the Apple remote, like it used to under 17.3.

I am now on a firmware higher than 17.4, and it still does not work.

That didn’t work… I’ll try it again later