> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-api-documentation/control-devices-1/vicki/summer-mode.md).

# Summer Mode

### **Output of the sent command if the mode is enabled:** 

* It will set the Vicki to ‘summer mode’
  * Turn off the algorithm for this Vicki; 
  * Turn off the automatic recalibration for this Vicki;
  * Block the new incoming display digits/set point/target temperature requests from the “app”;
* It will change Vicki settings as follows: 
  * The valve will be fully open; 
  * The display digits/set point/target temperature will be set to 30; 
  * The “child lock” function will be enabled; 

### **Output of the sent command if the mode is disabled:** 

* It will set the Vicki to ‘v1’ (the latest algorithm version)
  * Turn on the algorithm for this Vicki;
  * Turn on the automatic recalibration for this Vicki; 
  * Unblock the new incoming display digits/set point/target temperature requests from the “app”; 
* It will change Vicki settings as follows: 
  * The valve will be fully closed (set to max range); 
  * The display digits/set point/target temperature will be set to 20; 
  * The “child lock” function will be disabled; 

*\*Have in mind that all the commands are being written in the High Priority Command Queue, which means that Vicki will be receiving one command per keep alive. If the Vicki is set to 15 minutes keep alive time, it can take up to 50 minutes for a Vicki to be fully set in “summer mode”.* 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mclimate.eu/mclimate-api-documentation/control-devices-1/vicki/summer-mode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.