Skip to content

Fix: Correct MinSetpointDeadBand bounds to use int8_t (CON-1986)#1719

Merged
espressif-bot merged 1 commit intoespressif:mainfrom
szsz:fix/minsetpointdeadband
Feb 18, 2026
Merged

Fix: Correct MinSetpointDeadBand bounds to use int8_t (CON-1986)#1719
espressif-bot merged 1 commit intoespressif:mainfrom
szsz:fix/minsetpointdeadband

Conversation

@szsz
Copy link
Contributor

@szsz szsz commented Feb 15, 2026

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?

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).
@github-actions github-actions bot changed the title Fix: Correct MinSetpointDeadBand bounds to use int8_t Fix: Correct MinSetpointDeadBand bounds to use int8_t (CON-1986) Feb 15, 2026
@espressif-bot espressif-bot merged commit 599247e into espressif:main Feb 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments