Hi @flavio61 . The HACS process is a little odd. In HACS, you need to add peteS-UK/emotiva: Create Home Assistant Media Player for Emotiva Processors (github.com) as a custom repo first. All this does though is tell hacs where to look for downloads - it doesn’t download it. So, right after adding the custom repo, you should search in HACS for “emotiva” and you’ll see the integration there, and you can download it. Then you’ll have to reboot, and then you can add the integration in Settings/Integrations. It would be more obvious if HACS took you to the download step after you add a custom repo, but it doesn’t…
I’d suggest you re-add it from HACS in this way else you won’t get updates. I just pushed a new version which tidies up a couple of things I think will help with 2024.5 and future versions as the HA team continue to deprecate old approaches and we have to update integrations.
Hi Peter thank’s for your help I now installed via HACS.
The problem remained the same as in the previous version. All volume management commands such as volume +, volume -, mute work perfectly. Also on/off works. All the other commands (source as HDMI1, or info, stereo etc. etc. instead of being executed, open the processor status window, this one that I show in the image below:
This is the command I created that is the same for all buttons:
If you use the media player component just from the UI, does it work if you change inputs, mode etc.? I think likely not, but just checking first.
Edit: Or, just send a command directly from the UI (developer tools/services)
BTW - what happens if you send source_2,0 rather than HDMI2,0. I don’t use the HDMI tags directly. With the source_ commands, you’re telling the proc to make that the current source. The sources are what you configure in the setup menus on the proc - e,g. tying a video input and an audio input together. So, the integration uses these. If you’re pressing 2 on the IR remote, it’s selecting source_2, not HDMI2 (although source_2 might be setup as hdmi2 of course).
Look in the media player component. You should see the list of sources and be able to select them. Does that work?
One thing I know won’t work properly is the list of sound modes. that’s hard coded at the moment since the docs don’t tell me what it is. We’ll need to get the debug from you so I can add the right sound modes for the RMC.
Hi Peter thank you for your patience.
I tried the mediaplayer component and I also tried from tools/services and everything works perfectly both the volume control, the source selection and also the audio mode selection.
On the other hand, even changing my code from HDMI1,0 to source_1,0 still has the problem.
Ah, well that’s all good news Glad to hear it works.
The reason your card isn’t working is you’re sending it to the wrong entity. emotiva.send_command is on media_player.emotivaprocessor, not remote.emotivaprocessor. If you’re using remote.emotivaprocessor, then you would use remote. Send, but then you have to combine command and value
I’d stick with using the emotiva.send_command though and just change the entity.
If you get this sorted, I’d be interested in the debug output if you step through all of the music modes using the rmc remote/menus so I can add the music modes the rmc has that the xmc-1 doesn’t
Hi Flavio
Thanks, but I need the debug logs - the internal names won’t be the same. There’s also the Dolby modes etc… If you go to the device in the home assistant integration, you’ll see enable debug logging. Just turn it on, step through all the modes you can, and then disable debug logging and it’ll load the log file for you.
FYI, I’ve posted a new version to the repo which has the sound modes updated for XMC-2 and RMC-1 and has been tested with both and seems to work well within the limitations of the API. The main gap is that the API doesn’t support the speaker presets/dirac approach for the XMC-2 and RMC-1. Emotiva haven’t added that to the API, and don’t intend to do so at present. Other than that, it seems to work fine now.
I recently upgraded my RMC-1L to an RMC-1L+. Now I see both processors in the integration. I’d like to delete the old one (and ideally rename all the entities on the new one to what they were with the old one), but I don’t see any way to delete just the processor. It looks like I can only delete the entire integration. Am I missing something?
Maybe deleting and reinstalling the integration would actually get the entities named correctly again?
Ah - that makes sense. It’s auto discovered the devices so they’re showing up under the same configuration entry - the entry basically says to discover all the devices it can and add them. You’re not really deleting the integration by hitting delete next to Emotiva Processor, but you’re deleting the config entry which says “discover”. So, to get rid of the existing devices, you’ll have to delete the config entry I’m afraid. I should probably move the discovery to the config flow, and then it would create separate config entries, but it’s not been a problem before
Anyone have issues with the new + processors not showing on in HA? Prior to doing the CR8 upgrade it used to work with no issues. Now when my XMC2+ is on HA isn’t reflecting the current state. Once I flip the remote on under control then it actually shows the current state of my XMC2+.
I can’t test things with CR8 (or any of the new gen) I’m afraid, as I don’t have one so it’ll take a bit of digging. First question - could you be a bit more specific on the behaviour. After you’ve turned the XMC on with the remote, does the power state then work (i.e. turning on and off) or if you turn it off again does it stop working until you use the remote again? I wonder if there’s a network standby mode that needs to be enabled perhaps? Can you ping the XMC before you turn it on with the remote? If you’d like to turn on debug on the integration and attach some logs, I’ll take a look.
When I turn on my XMC-2+ using the physical remote in Home Assistant (HA), the power state accurately reflects the current status, i.e., it shows as “on” in HA. I am also using a Sony OLED XR-77A80J TV with CEC control to turn my XMC-2+ on and off. This might be the issue, as HA does not seem to detect or capture the state change when I turn the TV on or off. The state in HA remains unchanged.
Additionally, in HA, I can turn on the XMC-2+ using the remote slider button or the power button. When the unit is off (in standby mode with the orange light), I can ping it successfully with no packet loss.
Can you let me know which logs I can provide to help troubleshoot this?
So, is it only when you’re using the CEC to turn it on that the state isn’t reflected correctly? You say that if you turn on via the remote it works OK. Does the state also get changed if you use the power button the entity?
I need to see the debug logs when it’s not doing something it should be doing. If you go the the integration (Settings/Integrations/Emotiva) three buttons top right, enable debug logging, then do something which doesn’t work, then disable debug logging, then post that section of the logs (i.e. covering the time window in which you did the thing that doesn’t work)
Glad to hear it works.
