Set point temperature can show incorrectly if Eco Mode enabled about wiserhomeassistantplatform HOT 5 CLOSED

thanks this, im travelling for work at the moment. Does sound like this may have changed or currentSetPoint was the wrong one to use in the first place.

I'll dive deeper soon

from wiserhomeassistantplatform.

I can definitely say that nothing has changed.

CurrentSetPoint - is the temperature that is currently set for the room as target. It can be equal to scheduled, to override or to away temperature.

ScheduledSetPoint - would always represent what temperature is currently set in schedule.

from wiserhomeassistantplatform.

Observed this different behaviour myself for the first time this evening when Eco mode switched on.

Pretty sure the firmware version number on all of my TRV's and the Roomstat has changed within the last few days to '42002', think it was previously something like '36001'.
Hub is on firmware '2.44.0' but I'm not sure if that has changed or not.

from wiserhomeassistantplatform.

from wiserhomeassistantplatform.

This is now fixed in PR#54

Fix was in climate.py

@property
    def target_temperature(self):
        target = (
            self.handler.get_hub_data()
            .getRoom(self.roomId)
            .get("CurrentSetPoint")
            / 10
        )

to

    @property
    def target_temperature(self):
        target = (
            self.data.wiserhub
            .getRoom(self.room_id)
            .get("DisplayedSetPoint")
            / 10
        )

Be released in R1.9, currently in dev

from wiserhomeassistantplatform.