that does make sense if the command is different, that being said since i cant test myself. do me a favor, load it up via tar.gz and not docker, test again and confirm if volume doesnt work for your model, then share the logs so i can see what happens in the backend. your logic is sound but sicne i cant test anything i will need to see the behavior.
OK. I loaded the tar.gz for 1.4.16 on the remote (running firmware v2.8.3). I rebooted. Ran an activity that turns on my MRX720, tried sending the integration’s volume up (3x) and down (3x). Here is the log for core services and the Anthem integration. I hope it helps!
redo and downlonad ONLY the anthem integration log, not the core logs. you can do as such by choosing from the dropdown ONLY the anthem log.
OK. Here’s a new dump of just the Anthem log:
somrthing is off, i see we getting 200 from ur device meaning it did in fact sent success for volume up
| 2026-02-07 16:04:59.733493 +00:00 | custom-intg-anthemav | INFO | 2026-02-07 09:04:59,732 - ucapi.api - DEBUG - [(‘127.0.0.1’, 33050)] <-: {kind:req,id:11,msg:entity_command,msg_data:{cmd_id:volume_up,entity_id:media_player.anthem_192_168_3_90_14999,entity_type:media_player}} |
|---|---|---|---|
| 2026-02-07 16:04:57.543397 +00:00 | custom-intg-anthemav | INFO | 2026-02-07 09:04:57,542 - ucapi.api - DEBUG - [(‘127.0.0.1’, 33050)] ->: {‘kind’: ‘resp’, ‘req_id’: 10, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}} |
| 2026-02-07 16:04:57.542931 +00:00 | custom-intg-anthemav | INFO | 2026-02-07 09:04:57,541 - uc_intg_anthemav.media_player - INFO - [media_player.anthem_192_168_3_90_14999] Command: volume_up |
which entity u using to use volume, is it inside an activity? outside an activity? from logs it show working
Interesting. I’m not sure I’m following your question, but I have the MRX720 media player entity assigned to several activities. This example sent the volume commands from the media player inside an activity.
I honestly don’t know how to access the commands from outside an activity. Is that an experiment I should try?
For what it’s worth… The reason I asked about the formatting, is that I have the volume control working for both models (MRX/AVM) through the text over TCP integration, and use the two different formats for each.
working on a fix.
1 Like
try the latest version
That was fast! Loaded up and working perfectly. Thanks!
Enjoy. dont forget to hit that like and subscribe button to show your support LMAO
1 Like
Thanks for this Anthem integration - much appreciated! I am using it with my Anthem MRX 1120 and it works fine, except for one thing.
When I run the start sequence of an activity it fails to set/change the Anthem input. In contrast, setting the input manually from the remote works fine.
Is this a known problem or should I submit the logs?
in my honest opinion it is most likely something wrong with how you set it up. it works for others, you need to provide a lot more details, screenshots and explanation of what you are trying to do step by step. the fact it works outside of an activity prove its a config error and not an integration error (i hope). The reason for a lot more details is due to:
“This is another blind integration, therefore i cannot test/replicate/validate.
any issue will require explicit problem statement and logs for further debug.”
Have you tried adding a delay before you set the input in the start sequence?
I have, but it makes no difference - tried 1-5 secs.
Will now delete the Anthem entity and integration and reinstall. Hope it works then!
Here are the Anthem integration logs for an activity that does nothing but turn on the Anthem and setting its input to HDMI 2.
2026-02-13 17:27:21.521103 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,520 - ucapi.api - DEBUG - [(‘127.0.0.1’, 47998)] ->: {‘kind’: ‘resp’, ‘req_id’: 57, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2026-02-13 17:27:21.520273 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,518 - uc_intg_anthemav.media_player - INFO - [media_player.anthem_192_168_1_64_14999] Command: select_source {‘source’: ‘HDMI 2’}
2026-02-13 17:27:21.520273 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,517 - ucapi.api - DEBUG - [(‘127.0.0.1’, 47998)] <-: {“kind”:“req”,“id”:57,“msg”:“entity_command”,“msg_data”:{“cmd_id”:“select_source”,“entity_id”:“media_player.anthem_192_168_1_64_14999”,“entity_type”:“media_player”,“params”:{“source”:“HDMI 2”}}}
2026-02-13 17:27:21.516071 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,512 - ucapi.api - DEBUG - [(‘127.0.0.1’, 47998)] ->: {‘kind’: ‘resp’, ‘req_id’: 56, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2026-02-13 17:27:21.510562 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,509 - uc_intg_anthemav.media_player - INFO - [media_player.anthem_192_168_1_64_14999] Command: on
2026-02-13 17:27:21.510562 +00:00 custom-intg-anthemav INFO 2026-02-13 18:27:21,507 - ucapi.api - DEBUG - [(‘127.0.0.1’, 47998)] <-: {“kind”:“req”,“id”:56,“msg”:“entity_command”,“msg_data”:{“cmd_id”:“on”,“entity_id”:“media_player.anthem_192_168_1_64_14999”,“entity_type”:“media_player”,“params”:{}}}
Before running the start sequence of this activity the Anthem input was set to HDMI 1, and starting the activity did not change it to HDMI 2.
- Show screenshots of your activity setup
- Disable any HDMI-CEC or HDMI controls by/in the devices in the activity.
- Share full log (not in raw, post on pastebin or uplaod the file)
I did some more experimenting and it turns out that my Anthem device needs a delay of no less than six seconds after power on before its input source can be changed. This was causing my problem. After inserting such a delay in my on sequences everything works perfectly. Sorry for the confusion.
Glad you were able to figure it out. Even more glad it’s not a problem with my integration lol
I know the feeling! Once again thanks for the integration.
Hello. My IP control app didn’t work. I installed the app and entered the IP address and port. All device control settings appeared in the UC remote control, but none of them are active. What am I doing wrong? I have an Anthem AVM90 AV processor.