Daniel Pernold

I see the following errors in the log. [events.log](https://github.com/openhab/openhab-addons/files/9316847/events.log)

> @dandjo can you please be fully explicit on what version of OH you are running, respectively Stable/Milestone/Snapshot version? Sure. ``` runtimeInfo: version: 3.3.0 buildString: Release Build locale: en-AT systemInfo:...

I was able to reproduce the issue. Steps: 1. Activate Tado with the "timerDuration" Channel setting its value to e.g. 5 (5 Minutes) 2. Changing value from "hvacMode" from "COOL"...

Here's the trace log. Switching from cooling to fan mode and back to cooling. [openhab.log](https://github.com/openhab/openhab-addons/files/9332111/openhab.log)

It is a LG Mono-Split, don't know the exact model. But yes, in FAN mode there is no target temperature. There also none in the Tado app itself. 

Fyi: I'm just setting the states of single Items via separate widgets.

Sure. As I can interpret, the API refuses to update the state. [openhab.log](https://github.com/openhab/openhab-addons/files/9333743/openhab.log)

Beginner questions: * Is this version compatible with OH 3.3.0? * Where do I put the JAR file and should I uninstall the 3.3.0 binding first?

Unfortunately not working. [openhab.log](https://github.com/openhab/openhab-addons/files/9334050/openhab.log) 

Confirmed, when starting the AC in FAN mode, no error. [openhab.1.log](https://github.com/openhab/openhab-addons/files/9339456/openhab.1.log) When switching from COOL to FAN, no error. When setting a target temperature in FAN mode, error. [openhab.2.log](https://github.com/openhab/openhab-addons/files/9339460/openhab.2.log)