MQTT HomeAssistant with inversion on channel from zigbee2mqtt

OH 5.0 M2. I’m just starting to use zigbee2mqtt through the MQTT binding. I’ve got it set up and it appears to work. My first test is with a door contact sensor linked to a Switch Item. I prefer that the Switch be ON when the contact is closed (“true” according to the zigbee2mqtt log), so I tried to use inversion in the channel link. But I get a warning every time a message comes in. Any ideas?

2025-05-19 22:05:57.661 [WARN ] [l.HomeAssistantChannelTransformation] - Applying template {"latest_version":"{{ value_json['update']['latest_version'] }}","installed_version":"{{ value_json['update']['installed_version'] }}","update_percentage":{{ value_json['update'].get('progress', 'null') }},"in_progress":{{ (value_json['update']['state'] == 'updating')|lower }}} for component update/0x282c02bfffe6668d/update failed: Cannot find method get with 2 parameters in class com.hubspot.jinjava.objects.collections.SizeLimitingPyMap (class com.hubspot.jinjava.interpret.FatalTemplateErrorsException)

The corresponding log from zigbee2mqtt is this:

[2025-05-19 22:05:57] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/DoorSensor1', payload '{"battery":100,"battery_low":false,"contact":true,"linkquality":156,"tamper":false,"update":{"installed_version":48,"latest_version":63,"state":"available"},"voltage":3000}'

Link configuration:

  "DoorSensor1 -\u003e mqtt:homeassistant:ChelanMQTTBroker:zigbee2mqttDoorSensor1:contact_binary_sensor": {
    "class": "org.openhab.core.thing.link.ItemChannelLink",
    "value": {
      "channelUID": {
        "segments": [
          "mqtt",
          "homeassistant",
          "ChelanMQTTBroker",
          "zigbee2mqttDoorSensor1",
          "contact_binary_sensor"
        ],
        "uid": "mqtt:homeassistant:ChelanMQTTBroker:zigbee2mqttDoorSensor1:contact_binary_sensor"
      },
      "configuration": {
        "properties": {
          "profile": "basic-profiles:invert"
        }
      },
      "itemName": "DoorSensor1"
    }
  },

Looks like it is this issue. Hopefully the fix makes into M3: