Hello, i am releasing Anthem AV integration. integration should support most IP supported moduls. Support single or multi device with single or multi zone. Integration will create a media player entity per zone.
Power Control: On/Off/Toggle
Volume Control: Volume slider (-90dB to 0dB mapped to 0-100)
Volume Buttons: Up/Down with real-time feedback
Mute Control: Toggle, Mute, Unmute
Source Selection: Dropdown with all available inputs in activity
This is another blind integration, therefore i cannot test/replicate/validate.
any issue will require explicit problem statement and logs for further debug.
I also unable to test if initial release work. Please let me know if not.
Thank you.
PS - its best to join the discord channel as i am more active there.
Interesting. I will give this a spin with my AVM60. It’s working right now well enough over IR with a wired blaster, but I’ll give this a shot later in the week. Thanks for the upload.
I am back from vacation, and worked on this since i’m back, i think i am ready for new test. i completely re written and worked to create a simulator script, tested against simulator and it had worked for me.
new integration will automatically detect the model and create a media player AND a a remote entity with full functionality and source input dropdown for activities.
this is a complete re-write. please give it a test and if any issues, describe them and provide log.
I was able to get the integration downloaded to the remote however, the entities still do not work for me. None of the functions actually control my AVM 70.
I think you are very close to figuring it out. I normally can’t even load the integration on to my remote. I was able to load it and add the entities
Thanks for all the work to create an Anthem integration. I tried the other integration on Home Assistant and it works pretty good. The issue that I noticed is that the volume is incremented in 3 db steps. For example if I press the volume button up or down it moves in increments of 3, from 60 to 63 or 57. Has anyone else experienced this behavior, is it my implementation or that particular intergration. Because the Anthem iOS remote, handheld remote or the web browser all increment is 0.5 db steps.
Thank you for this @M.a.S.e! I have tried it with both my MRX720 and my AVM90. Here are my observations:
Power control (switch on/off) works consistently on both units. These commands had been unstable using Text over TCP, but this integration seems both snappy and reliable.
Input selection works perfectly on the MRX720, but not on the AVM90. For the AVM90, it doesn’t pull the input names from the receiver. Manually entering the input name into the “Input Source” command does not provide predictable results.
Mute on/off/toggle works consistently on the MRX720.
Volume up/down does not work on the MRX720. The unit simply doesn’t respond.
I didn’t get around to testing mute or volume control on the AVM90 since the source selection wasn’t working yet.
I couldn’t assign volume to the slider for either receiver. I’m running on 2.6.12, so it may just be that the O/S doesn’t allow that yet.
I would be happy to provide logs or other data. I’m still a novice with this system, so please just help me understand exactly what would be useful and how to provide it. Hopefully I can be of some kind of help!
Hey. I don’t own the device as I mentioned, I wrote this completely blind. So sadly without logs there is nothing I can do. Join discord, replicate, share logs there. Easier for me.
Hi @M.a.S.e. Sorry it took me a while to get back to this. I got wiped out by the flu bug this week. I had a chance to play around a little more today. I’ll break this into pieces to hopefully simplify communication. The integration actually works very well with the AVM90 as-is. It just doesn’t read in the Source list. I was able to work around this by manually typing in “HDMI 1” and “HDMI 2” in the source field. This allows me to switch between the input that’s actually on HDMI 1, and the ARC channel (not on HDMI 2, but that works for now). Power switching, volume control, mute, etc. all work perfectly.
I included a log from the integration when I was testing it out. I rebooted the R3, turned on the AVM90, and attempted to command different inputs. I can’t tell from the log when commands were sent/rejected. Here’s the log. I hope this helps, but please let me know if I can provide anything else. If we get this resolved, we can try working on the MRX720 volume control. Thanks again - this is an awesome step up for my control system!
source list was fixed in latest verison and confirmed working , including virtual . make sure you using latest release. i can see from your logs, you are not.
Updated to v1.4.8. This is working fantastically with the AVM90 now. Thanks! I’ll update the other remote and test it on the MRX720 when I can pry my family away from football…
I’ve been battling to update my other R3 for the MRX720 control for a little while now. It seems to be struggling to load/maintain the source list. I updated to the latest firmware, reloaded the integration, even tried removing all entities and the integration and starting all over. Each time it seems to get the source list initially, but then loses connectivity to the MRX720. When I run the activity “on” sequence, it bombs when it tries to select an input source.
On this remote, I’ve loaded the MRX720 and MRX720 Zone 2 entities, as well as my AVM90 Zone 2 entity. The AVM90 seems to be working fine. The MRX720 was working great on the prior integration version. Now it only powers the device on/off.
Here’s a log file for both the core and Anthem integration services. During this time period, I rebooted the R3, and ran an activity which would power on the MRX720 and select an input. Any clues?