Wrong scheule settings for AVATTO ME167

[rolf-achim]

Hi. I'm located in Germany and new to ZigBeeMQTT. I'm running ZigBee2MQTT version 1.33.1 on a windows computer and successfully joined a TRV Avatto ME167. Everything is working like a charm. However, if I'm setting schedules for specific days, they are executed at a different day.
Example:
I configure the MQTT topic "zigbee2mqtt.0.0x84ba20fffe9a64fa.schedule_thursday" with "07:04/21.0 08:04/25.4 19:04/23.4 22:04/18.0",
the ZigBee response I can see in the debug log is
"Zigbee2MQTT:debug 2023-11-09 17:21:27: Received Zigbee message from 'Heizkörperthermostat_Keller', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[4,7,4,0,210,8,4,0,254,19,4,0,234,22,4,0,180],"type":"Buffer"},"datatype":0,"dp":31}],"seq":26880}' from endpoint 1 with groupID 0"
I assume the leading "4" is indicating the fourth day of the week which should be Thursday.
But the setting will be executed from the device on Saturday. I have observed the same two-day shift for every weekday.
Where in the code can I change the weekday mapping from MQTT to the correct position in the device' buffer?

[joba-1]

2 years late, but now I have the same issue with my new installation:

It is monday and right now my thermostat switched temperature like on saturday or sunday:

Received 08:46:59

    QoS: 0
    Payload:

    battery_low: null
    child_lock: UNLOCK
    current_heating_setpoint: 20.5
    error: null
    frost_protection: null
    last_seen: '2025-02-24T08:46:59+01:00'
    linkquality: 65
    local_temperature: 20
    local_temperature_calibration: 3
    running_state: heat
    scale_protection: 'ON'
    schedule_friday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_monday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_saturday: 07:30/20.5 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0
    schedule_sunday: 07:30/20.5 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0
    schedule_thursday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_tuesday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_wednesday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    system_mode: auto

Received 09:00:53

    QoS: 0
    Payload:

    battery_low: null
    child_lock: UNLOCK
    current_heating_setpoint: 18
    error: null
    frost_protection: null
    last_seen: '2025-02-24T09:00:53+01:00'
    linkquality: 69
    local_temperature: 20
    local_temperature_calibration: 3
    running_state: heat
    scale_protection: 'ON'
    schedule_friday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_monday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_saturday: 07:30/20.5 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0
    schedule_sunday: 07:30/20.5 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0 09:00/18.0
    schedule_thursday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_tuesday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    schedule_wednesday: 05:30/20.5 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0 07:00/18.0
    system_mode: auto

How can I fix this or diagnose this further?

[joba-1]

looks like a device bug. Different ME167 stay on different weekdays