mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
The model temperature cannot be set in version 1.3 #226
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CCP7 on GitHub (Apr 25, 2025).
Self Checks
Dify version
1.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
In the Dify 1.3 version, the temperature of deepseek - r1 cannot be set. If you need to modify the temperature, where should it be set?
It turns out that in version 0.15, the temperature of deepseek-r1 can be set.
✔️ Expected Behavior
You can set the temperature for deepseek-r1
❌ Actual Behavior
The temperature of deep seek-r1 cannot be set.
@dosubot[bot] commented on GitHub (Apr 25, 2025):
In version 1.3 of Dify, the temperature setting for models like DeepSeek-R1 is not available in the user interface. However, you can still configure the temperature through the YAML configuration files. The default temperature setting is 0.95, and it can be adjusted by modifying the
parameter_rulessection in the relevant YAML file. Here's an example of how the configuration might look:You can find these configuration files in the Dify repository, specifically under the model runtime section for the respective model provider [1].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
@CCP7 commented on GitHub (Apr 25, 2025):
This address returns a 404.
@Dosu
@Moiyu1998 commented on GitHub (Apr 26, 2025):
The r1 model itself does not support the temperature parameter. Entering this parameter will not cause an error, but it will not take effect either, so it makes no difference whether this parameter is included or not. In fact, for the r1 model, only the max_token parameter is effective. For more details, please refer to the official documentation shown in the image above.
@dosubot[bot] commented on GitHub (Aug 19, 2025):
Hi, @CCP7. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!