Denon Volume Control Not Working Correctly

The code:

      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.key == 'Rev' }}"
        sequence:
          - action: denonavr.get_command
            metadata: {}
            data:
              command: /goform/formiPhoneAppDirect.xml?MV775
            target:
              entity_id: media_player.denon_avc_x3800h
        alias: Vol -2.5
      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.key == 'Fwd' }}"
        sequence:
          - action: denonavr.get_command
            metadata: {}
            data:
              command: /goform/formiPhoneAppDirect.xml?MV675
            target:
              entity_id: media_player.denon_avc_x3800h
        alias: Vol -12.5
      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.key == 'Play' }}"
        sequence:
          - action: denonavr.get_command
            metadata: {}
            data:
              command: /goform/formiPhoneAppDirect.xml?MV575
            target:
              entity_id: media_player.denon_avc_x3800h
        alias: Vol -22.5
      - conditions:
          - condition: template
            value_template: "{{ trigger.event.data.key == 'Select' }}"
        sequence:
          - action: denonavr.get_command
            metadata: {}
            data:
              command: /goform/formiPhoneAppDirect.xml?MV450
            target:
              entity_id: media_player.denon_avc_x3800h
        alias: Vol -35

Pretty simple setup: using a simulated Roku, I’ve created buttons on my Logitech Harmony remote to set the volume to specific levels I frequently use. The latter three work just fine.

-2.5, on the other hand…does not. Seems to be a recent thing, too. At least, I’ve not noticed it until the last few days. When pressing the -2.5 button, it sets the volume to a seemingly random number, usually in the -5 to -9 range. Pressing it again sets the volume to -2.5, without fail.

This…makes no sense? I sat there a couple of days ago just pushing all the volume buttons in random orders and -2.5 only rarely worked the first time, while the others never misfired. They’re exactly the same code. I’m confused.

Anyone have any idea what’s going on here? I’m not even sure how to really begin tracking this under the hood to figure out where things might be going wrong. It’s not like it’s setting it to the same wrong number every time, or like it’s setting it to one of the other numbers.

I just tested this as a simple service/action, with 400 and 555 and 675 and this works fine, I am also on a 3800h and the integration is without telnet connection. on HA 2026.1
Any log items? … maybe you need to activate the debug log for this one…I believe it is this one in configyaml

logger:
  default: info
  logs:
    homeassistant.components.denonavr: debug

A lot, as it turns out. I’ve never had any reason to look at the logs, but there’s a ton of warnings and errors in there, most uselessly vague. None relating to the Denon, though.

Did you increase it to debug level logging?

Not yet, I just looked at what was already there.

Just checked this with me, nothing comes back in my case, 0 entries when I change the volume… with (!) debug level on…
EDIT; not sure if this integration has debug messages

Yeah, I’m not seeing anything.

I’m wondering if a Denon update limited volume increase? If it’s on -35, trying to change it to -2.5 sets it to -7.5. Trying to change it from any of the other volume presets, or from -7.5, sets it correctly to -2.5. Manually setting it to -34 means the -2.5 button sets it to -7.0.

As I said, it’s worked fine in the past. I think? Maybe it’s been broken this whole time and I only just noticed.

My 3800h is on firmware: 6000-2123-4035-8880
I cannot say if this works or not as I am not using that functionality since a few years. An alternative might be to use media_payer.volume_set instead or add a delay after each other command and/or make sure the automation is in mode restart or queued.

I’m not firing these off in rapid succession, though. Timing is irrelevant. And given that increasing the volume from -35 means the -2.5 button gets closer to -2.5, it does seem to be some sort of threshold thing.

If it were threshold then imo it should not work at all and I understand it does work ‘sometimes’
It is a pitty that one cannot read/log the incoming data at the 3800-side. To rule out HA a bit more, can you reduce the automation to have just this one?

It works “sometimes” because the volume is not always as low as -35. If the volume is -35, the -2.5 button always sets it to -7.5. If the volume is -34, the -2.5 button always sets it to -7.0.

I’m not sure what you mean by this?

That indeed shounds like a limit, so when on 30, setting 775 does it go to 68 (note that I use the 0-98 scale, not the -db)? I have none of these, whatever low or high it is, I can change it with any rate (max 98, being my 3800 range). I also switched the denon to the db range but it still behaves as expected.

forget it, with above this is no longer a possible source imo