Window open feature Danfoss Ally (eTRV0103)

[MSL-DA]

Can someone explain to me the purpose and what Window Open Internal "quarantine" does after the window is closed? It takes approximately 40 minutes before it switches to closed.

[lux73]

You have to use Window open external to signal an open window

Window open internal try to detect open/closed Window via Temperature difference inside the TRV.
Working not reliable

[MSL-DA]

You have to use Window open external to signal an open window

Window open internal try to detect open/closed Window via Temperature difference inside the TRV. Working not reliable

@lux73 Do you have the thermostat?

[lux73]

Sure, working flawless with z2m & OpenHAB

[MSL-DA]

But you are not using Window open feature / Window open external?

[lux73]

of course I use it... works as expected for me

but I have never dealt with any of your Quarantine Settings...

Window Contact report open -> OpenHAB sends Window open to the TRV and ther TRV closes the Valve

If Window closed then OpenHAB sends Window closed to the TRV and it opens the Valve

[MSL-DA]

Do you want to share your state in z2m when a window is open and when you close the window?

[MSL-DA]

I can add that when I change the desired temperature, or change the Setpoint Change Source, Window Open Internal changes to quarantine.

[manuelkue]

As far as I know, the internal quarantine state is there to signal that the TRV has noticed a window being closed again but assuring it's really closed.
This has to do with the reason mentioned by @lux73, that the internal window open detection is not perfectly reliable.

So if you notice that the quarantine state is set too long it indicates the TRV has problems in detecting if the window is really closed. It may be because of a strange temperature curve or something else.
As @lux73 mentioned, the only reliable way of telling the TRV that a window is open, is, to use the external detection by setting the window open external which will overwrite the internal detection.

[MSL-DA]

@lux73 Seriously... 🥹 There is nothing wrong, I have written all along that my thermostats open as they should despite the quarantine.

You've written several times that you're not familiar with the quarantine status and that yours changes to closed when you send window_open_external: false

Now I can see that your status also changes to quarantine

Quote from my original post

Can someone explain to me the purpose and what Window Open Internal "quarantine" does after the window is closed? It takes approximately 40 minutes before it switches to closed.

[MSL-DA]

@manuelkue I have 16 thermostats, all with external temperature sensors and all are triggered via an external contact sensor window_open_external: true/false

I can see that they are responding as they should, so I return to my original question

Can someone explain to me the purpose and what Window Open Internal quarantine does after the window is closed? It takes approximately 40 minutes before it switches to closed.

[manuelkue]

@MSL-DA Do all these 16 thermostats' window_open_internal states respond only after 40min? That would be strange. When I did not have my external window contact sensors this quarantine state was active for around 5min at maximum after closing a window.

For your question I can only repeat myself:
The internal quarantine state is there to signal that the thermostat has noticed a window being closed but it must assure that it's really closed. In my understanding, it does this by analyzing the temperature curve of the internal temperature sensor. If it detects a stop of the temperature drop or even an increase again, it will switch from quarantine to closed.
If this analysis does not work properly because the temperature drop-stop cannot be detected reliably, the quarantine state will be present a longer time.

If you would not have external window contacts this would lead to the thermostat not opening the valve despite the window has been closed actually. But because you have external window contacts, and because you use them to set the window_open_external your valve works as expected.

By the way: This state is created by the thermostat itself and this state handling does not have to do anything with Zigbee2MQTT. If you have further questions you should probably contact Danfoss directly ;-)

[MSL-DA]

MSL-DA Do all these 16 thermostats' window_open_internal states respond only after 40min?

@manuelkue Yes.

[MSL-DA]

{
    "adaptation_run_control": "none",
    "adaptation_run_settings": true,
    "adaptation_run_status": "found",
    "algorithm_scale_factor": 1,
    "battery": 81,
    "day_of_week": "thursday",
    "external_measured_room_sensor": 2114,
    "heat_available": true,
    "heat_required": true,
    "keypad_lockout": "lock1",
    "last_seen": "2025-01-27T17:57:59+01:00",
    "linkquality": 255,
    "load_balancing_enable": false,
    "load_estimate": 213,
    "load_room_mean": -8000,
    "local_temperature": 21.85,
    "mounted_mode_active": false,
    "mounted_mode_control": true,
    "occupied_heating_setpoint": 21,
    "occupied_heating_setpoint_scheduled": 21,
    "pi_heating_demand": 21,
    "preheat_status": false,
    "programming_operation_mode": "schedule_with_preheat",
    "radiator_covered": false,
    "running_state": "heat",
    "setpoint_change_source": "schedule",
    "system_mode": "heat",
    "thermostat_vertical_orientation": false,
    "trigger_time": 660,
    "update": {
        "installed_version": 28,
        "latest_version": 28,
        "state": "idle"
    },
    "viewing_direction": false,
    "weekly_schedule": {
        "days": [
            "sunday"
        ],
        "transitions": [
            {
                "heating_setpoint": 21,
                "time": 420
            },
            {
                "heating_setpoint": 18,
                "time": 1320
            }
        ]
    },
    "window_open_external": false,
    "window_open_feature": true,
    "window_open_internal": "closed",
    "regulation_setpoint_offset": 0
}