Fix: Correct MinSetpointDeadBand bounds to use int8_t (CON-1986)#1719
Merged
espressif-bot merged 1 commit intoespressif:mainfrom Feb 18, 2026
Merged
Fix: Correct MinSetpointDeadBand bounds to use int8_t (CON-1986)#1719espressif-bot merged 1 commit intoespressif:mainfrom
espressif-bot merged 1 commit intoespressif:mainfrom
Conversation
MinSetpointDeadBand is defined as an int8_t, but the bounds were incorrectly created using int16_t. Updated bounds to use int8_t with the correct range (0–127).
shubhamdp
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
MinSetpointDeadBand is defined as an int8_t, but the bounds were incorrectly created using int16_t. Updated bounds to use int8_t with the correct range (0–127).
Description
I was receiving this error while prorgramming a thermosatat.
E (2778) data_model: Cannot set bounds because of val type mismatch: expected: 7, min: 9, max: 9
Related
Testing
After patch there is no such error.
Checklist
I unfortunatley do not have these CI tests set up. Should I rather open an issue or create PR to other branch?