SONOFF SWV-ZFE: error on irrigation_plan_report

[elle2]

I use Z2M to control the Sonoff SWV-ZFE water valve. The irrigation schedule is set up correctly, and it starts up properly with the configured duration. I’m having a problem when I use the “irrigation_plan_report” function in the Z2M web interface: the error “No converter available for ‘irrigation_plan_report’” appears, and the values shown in the interface don’t match the ones I set (which are working).
What am I doing wrong, and how is the “irrigation_plan_report” command supposed to work?
thank you

[andrei-lazarov]

cc @CubeZ2mDeveloper

[CubeZ2mDeveloper]

Hi @elle2, thanks for reporting this, and sorry for the confusion and inconvenience caused by the current behavior.

We investigated this and would like to clarify the purpose of irrigation_plan_report.

irrigation_plan_report is a report-only composite expose intended for gateway-side synchronization. For example, when a device joins the network without being factory-reset, it will report the irrigation plans previously stored on the device.

On SONOFF gateways, these reports are collected and merged by plan index, allowing the complete irrigation schedule list to be reconstructed and displayed in the app.

When we initially added support for this device to Zigbee2MQTT, we focused on covering the available Zigbee protocol capabilities as completely as possible, but did not fully consider whether every protocol feature would provide a meaningful user experience when exposed directly in Zigbee2MQTT.

We have since removed some exposes that are not practically usable in Zigbee2MQTT. For example, weather-adaptive irrigation settings were removed because Zigbee2MQTT does not provide a suitable weather data source, so configuring them there would not actually make the feature work.

irrigation_plan_report appears to be another case that we overlooked. Since it is mainly intended for gateway-side synchronization rather than direct user interaction, its practical value when exposed in Zigbee2MQTT is limited, and we are considering removing it to avoid further confusion.

Why do the values shown in Zigbee2MQTT differ from the configured values?

All irrigation plans are reported through the same Zigbee attribute and are distinguished only by their plan index.

In Zigbee2MQTT, these reports are exposed through the same irrigation_plan_report property. As each plan is reported, the newly reported value replaces the previously shown one. Zigbee2MQTT does not currently collect and merge these reports by index into a complete schedule list.

As a result, the value shown in irrigation_plan_report only represents the most recently reported plan. It should not be treated as the complete irrigation schedule or expected to match a specific configured plan.

To check the schedule that is currently running or scheduled to run next, please refer to Irrigation schedule status instead.

Why does No converter available for 'irrigation_plan_report' appear?

irrigation_plan_report is report-only and does not support writes.

However, Zigbee2MQTT currently shows an Apply button for composite exposes. Clicking Apply attempts to write the value, but there is no toZigbee converter for irrigation_plan_report, so Zigbee2MQTT reports:

No converter available for 'irrigation_plan_report'

In other words, this message appears because a write is being attempted on a report-only expose that is not intended to be set.

For the complete device experience and full irrigation features, you can also use the eWeLink app, which provides complete schedule management together with additional features such as weather-adaptive irrigation.

We apologize again for the confusing presentation of this expose in Zigbee2MQTT, and appreciate you bringing this to our attention.

[EW00D]

Hallo, can I ask if there is any update on this issue? I have just installed my valve but am unable to set up the irrigation plan because of a similar issue, like "zhc:sonoff: irrigation_plan_settings invalid start_time, expected HH:mm." or "zhc:sonoff: irrigation_plan_settings invalid enable_date, expected local date in YYYY-MM-DD format."

And yes, the time and date are in the proper format.

[enigma76]

I think I have the same problem too. I can set the schedules, but I can't read them directly, and I don't think the global state gives me correct information.

For example, to set a schedule I use a payload like the following and everything works fine
{
"irrigation_plan_settings": {
"plan_index": 5,
"enable": 0,
"start_time": "05:13"
}
}

in the global state I have:
"irrigation_plan_settings": {
......
"enable": 0,
.....
"plan_index": 5,
"start_time": "05:13",

},

but if set an other plan with other parameter

{
  "irrigation_plan_settings": {
    "plan_index": 4,
    "enable": 0,
     "duration": 47
  }
}

The state is:

"irrigation_plan_settings": {
.....
"enable": 0,
.....
"interval_duration": 7,

    "plan_index": 4,
    "start_time": "05:13",
   
},

but the start_time is not correct. IT is refered to plan number 5.

Could you please send me the script to fix the problem?

Thanks

[CubeZ2mDeveloper]

I think I have the same problem too. I can set the schedules, but I can't read them directly, and I don't think the global state gives me correct information.

For example, to set a schedule I use a payload like the following and everything works fine { "irrigation_plan_settings": { "plan_index": 5, "enable": 0, "start_time": "05:13" } }

in the global state I have: "irrigation_plan_settings": { ...... "enable": 0, ..... "plan_index": 5, "start_time": "05:13",

},

but if set an other plan with other parameter

{
  "irrigation_plan_settings": {
    "plan_index": 4,
    "enable": 0,
     "duration": 47
  }
}

The state is:

"irrigation_plan_settings": { ..... "enable": 0, ..... "interval_duration": 7,

    "plan_index": 4,
    "start_time": "05:13",
   
},

but the start_time is not correct. IT is refered to plan number 5.

Could you please send me the script to fix the problem?

Thanks

Hi @enigma76,

Sure, please find the external converter script below:
SWV-external-converter.js

[enigma76]

Thanks!!
ll check online how to charge it.

[enigma76]

I'm going crazy with the irrigation plans... I sent this configuration, but the water valve won't start. I've also tried changing the start time multiple times, but still nothing. I haven't tried loading the external converter yet... What could it be?

{
"irrigation_plan_settings": {
"plan_index": 1,
"enable": 1,
"enable_state": true,
"loop_type_mode": "day_interval",
"loop_type_interval_days": 1,
"enable_date": "2026-07-25",
"start_time": "09:35",
"duration": 45,
"irrigation_mode": "duration_with_interval",
"irrigation_plan_type": "duration",
"irrigation_total_duration": 45,
"irrigation_duration": 3,
"interval_duration": 7
}
}

[enigma76]

I re-paired the water valve and now it works!