Add new device definition to fix weekly schedule day mapping for _TZE200_p3dbf6qs thermostat #10561
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new device definition to fix a weekday mapping issue for the Avatto MS167/TS0601 TRV
(fingerprint: _TZE200_p3dbf6qs).
Issue:
The thermostat internally shifts the weekly schedule by +2 days.
For example, the schedule configured for Sunday is actually applied on Tuesday,
Monday is applied on Wednesday, etc. This causes the Zigbee2MQTT UI to display
the wrong schedule values on the wrong days.
Fix:
A dedicated device definition has been added for this fingerprint. The datapoint-to-day
mapping for DPs 28–34 has been corrected to align with the actual behavior of the device,
so each schedule is now applied to its correct weekday.
Impact:
Only this fingerprint is affected; no changes for other TS0601 TRVs.
The core value converters remain unchanged.
The UI now reflects the correct days, and schedules are applied correctly
by the TRV.
Testing:
Verified reading existing schedules.
Verified writing new schedules.
Confirmed that the schedules match the correct weekdays after TRV reboot.
This approach avoids modifying the core logic and keeps the fix isolated to the affected device.
Thanks!