Problems with automation and my heat pump. (extra keys not allowed @ data ['for'])

I have a Mitsubishi heat pump (air/air) that I have integrated with MELCloud. It has started behaving a little funny by just turning it off ever now and then. I suspect that this might occur when I ask google assistant to stop music etc not sure though. I have somehow intended to set an automation that when the heat pump’s “HVAC mode” changes, I will receive a notification to my mobile. I choose the trigger “Heat pump HVAC mode has changed”, once I select this, I get the error message “Message malformed: extra keys not allowed @ data [‘for’]”. I have no idea what this means? If I change the trigger to “Heat pump measured temperature has changed” it works without problems. Anyone have an idea what the problem might be?

// W

Can we see the automation‘s source, please?

Please bear with mee as I’m very new to this. How do I access the automation source?

//W

  1. Click the overflow menu in the upper right hand corner of the Automation Editor (three vertical dots).

  2. Select ‘YAML mode’.

  3. Copy the displayed text and paste it into your forum post.

1 Like

OKay, thanx! :slight_smile:
Here is my code:

alias: Värmepumpen är avstängd
description: ''
trigger:
  - platform: device
    device_id: 51fda32923dc72ae5719f0dbbc4a4f48
    domain: climate
    entity_id: climate.varmepump
    type: hvac_mode_changed
condition: []
action:
  - service: notify.mobile_app_one_8
    data:
      message: Värmepumpen är avstängd
mode: single

I guess that it has something to do with “condition: [ ]”? As I mentioned eralier, I want HA to send me a notification when the heating pump is turen off.

//W

condition: []

You don‘t have any conditions defined, so it‘s an empty array (list) of conditions (that‘s okay).

Infact, it’s hardly possible to create an invalid automation using the visual editor. Yet, it‘s not impossible.

Anyhow, I cannot figure how that error should be related to the automation shown, sorry.

OK, thanks for the explanation. But it must be something that is connected to the trigger “hvac_mode_changed” due to the fact that it works fine if I change the trigger to something else but with the same unit.

I’ll keep looking for an explanation =)

//W

Reviving an old post but I’m having the exact same error and problem when using the visual editor and trying to set an automation for a Mysa smart thermostat for a in wall electric heater. Any resolution to your issue?

Same problem as well. Trying to trigger on hvac mode change with a thermostat, after 1 minute. Any values for the for cause this bug.

1 Like

Same problem here. The “for” doesn’t seem to work on hvac mode change triggers.