Trouble Volume Control - Anthem Receiver

I’m having trouble controlling the volume in 1% increments on my Anthem receiver MRX-1140 using RC2 and Home Assistant on a RP5.

When I set up a TV | Movie | 5.1.4 Audio Activity, and edit the User Interface page, go to the volume. It defaults to 20% increments, I then edit to 1%, and it sticks to 1%. Yet when I use the Volume button the UC2, the Volume jumps in 20 increments. I using the Anthem Integration for Home Assistant (Anthem A/V Receivers - Home Assistant) which does not report a problem in this area.

Any ideas ?

If you’re using a receiver / processor Integration on Home Assistant, can you share UC2 your setup?


1 Like

Have you tried to use separate volume up and down commands if they are available? Some HA entities don’t seem to support these commands [feature request] Support HA player entity volume control · Issue #322 · unfoldedcircle/feature-and-bug-tracker · GitHub

@kennymc.c Great call out - thanks. The integration does not have separate up and down available like say Apple TV. Maybe this is something I can request from the Integration owner. I have also asked for an update from Unfolded Circle given this feature request from a year ago.

Hi there! Total noob (just got my 3 today) but to save me some headache, how did you get your 1140 up and running with ‘generic’ codes? I have an MRX 740 and can’t get it running. I do use the IP access on it so would I need to use that on the Remote 3? I know that’s probably not an easy question to answer but the Anthem is complex with its own remote. Is there another group that lists their process somewhere? I’m actually in clinical applications in the medical field so I’m not techno illiterate but I’d rather not have to reinvent the wheel.

Thanks for any advice!

@Dssquared :waving_hand: Welcome to the Unfolded Circle Community! I hope you’re enjoying your Remote 3 experience so far.

While my setup using Home Assistant (HA) and a Raspberry Pi 5 has been largely stable—especially with the Anthem IP integration—there are quirks that take time to untangle. I’ve mentioned a persistent volume issue elsewhere in this thread, for example.

HA’s been solid on the RP5, and there are some great 2025 YouTube tutorials to get you started. This one helped me: https://youtu.be/SBFZuwIhQ8o?si=b9pqYA7FAWKzmZlE

That said, I still find the Remote 3 has capabilities that aren’t exactly plug-and-play. Some issues require deep digging, which can be draining when the solution isn’t obvious. When that happens, I take a breather and keep an eye out for software updates or new community insights—sometimes that’s when the best workarounds surface.

I skipped IR entirely because my gear’s racked in a utility closet, out of range. If yours isn’t, the dock might be a viable IR option. Personally, I went full IP where possible to simplify things long term.

Glad to compare notes and help however I can. If you’ve uncovered any gems or hacks, drop them here!

Thanks so much for the reply!

You are correct, it can be exhausting but I’m someone that has to stew on something, settle down, than tackle it again :grinning_face:

I’ll keep on the lookout for integrations and updates. In the meantime, I need to read up on HA and its uses.

Dale

Did you manage to get this solved?

Creating integration are a bit beyond me, but would be great to have not only volume up/down but ability to switch arc profiles or change speaker levels. I just don’t know where to start finding what IP commands anthems support / provide for.

EDIT: i found the commands online but no idea how to implement as i cant’ find the files within HA to try and figure out how it works

If you provide a link to the doc I might be able to give you a custom entity configuration for the requests integration. But it depends on the command format and the protocol used by the receiver.

Its here, its a massive spreadsheet

https://www.anthemav.com/downloads/MRX-x40-AVM-70-90-IP-RS-232-v5.xls

Can you try if this turns on Zone 1 when entering this in the source field for the text over tcp entity input source command:

ReceiverIP:14999,”Z1POW1;"

ReceiverIP:14999,”Z1POW0;" should power it off.

Make sure IP control in standby is enabled on the receiver. I’m not sure about the correct port number as it’s not mentioned in the doc and I found it somewhere else. Maybe it’s shown in the reciever menu.

Will have to figure out how to send text over TCP, will do some research.

I just explained it to you. You need this integration: GitHub - kennymc-c/ucr2-integration-requests: A network multi tool integration for Unfolded Circle remote devices

1 Like

Thanks thats the thing I was looking for. Will test in the morning.

Unfortunately not, brings up an error and does nothing. 14999 is right, I was able to validate that using the menus on the avr.

Edit: Strangely now it works.

I think the device just doesn’t support volume control, as I tried this and it doesn’t work, tried both volume up and down. Which might explain why it’s absent from the HA integration.

192.168.0.5:14999,“Z1VUP;”

However I think I get the approach now and can map the commands i am looking for, which is great. Will have a proper play at the weekend.

How would I use the reverse, get the response from the avr to the command and display it?

For example ISiSPp to show that it’s switched profile or show current profile

Maybe the percentage variants are working?

You should also look into the new custom entities feature as this will add power state handling and you can simply save your device config as a yaml configuration instead of creating new commands for each command and activity.

Getting a response from text over tcp is currently not implemented. You can only see the answer message in the integration log. Maybe i’ll add this similar to the http requests commands. But you would always just have a single outlet to show any responses for all text oer tcp commands.

In the end this integration will not replace a proper Anthem integration. But its a good workaround until someone will release it.

1 Like

Magically the volume started working. Not sure why or how but it works so happy with that.