Max! Thermostats : Incorrect mode shown in home app about homebridge-fhem HOT 7 CLOSED

there is no default mapping for CurrentHeatingCoolingState and TargetHeatingCoolingState as the homekit values do not match the MAX modes exactly.

if you want to use this characteristic just provide a homebridgeMapping yourself. without this mapping the characteristics have no connection to the fhem device and just display a default value.

from homebridge-fhem.

Thank you 👍

from homebridge-fhem.

I'm afraid, I have to reopen this issue.

I'm still struggling with the homebridgeMapping. I wanted to do things step by step, so I only defined the CurrentHeatingCoolingState. As far as I understand, I will see the correct mode (at least as defined by the mapping) but I will not be able to change the mode until I define TargetHeatingCoolingState.

I defined the homebridgeMapping like this:

CurrentHeatingCoolingState=mode,values=manual:OFF;boost:HEAT;auto:AUTO

I don't know why but, homebridge returns on the console the following contradictory lines (the second one is marked red):

[2016-10-05 17:41:39] [FHEM] MAX_0716a6-mode values: value auto mapped to AUTO
[2016-10-05 17:41:39] [FHEM] MAX_0716a6-mode not a number: auto

This is what else is on the console:

[2016-10-05 17:41:39] [FHEM] value2homekit: { manual: 0, boost: 1, auto: 'AUTO' }
[2016-10-05 17:41:39] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT' }

Did I do something wrong?

from homebridge-fhem.

for the CurrentHeatingCoolingState there is no AUTO defined. only OFF, HEAT and COOL. see HomeKitTypes.js.

for TargetHeatingCoolingState there ist OFF, HEAT, COOL and AUTO.

the idea is that the current state will display the real current operating mode. and only the target mode will show if the current mode was manualy switched to the current value or automatically switched.

from homebridge-fhem.

Okay. That's really confusing.
So does this mean HomeKit assumes that the mode of thermostats can only be changed through HomeKit?

I don't get the whole point in having an auto mode then...

Doesn't this imply that the system then can have two states at the same time? For example the target decides it's to hot in the room, so it switches automatically to cooling. The state would then be cool AND auto.

from homebridge-fhem.

no...

the idea is that CurrentHeatingCoolingState will display the real current mode. i.e. the result of auto.

TargetHeatingCoolingState can display auto.

so with the target you can set the system to off, heat, cold or auto and current will show the mode that is active off, heat or cold.

the real problem is that this does not map to the way the european heatings systems work that are used with the hm and max thermostats. they do not have a cooling mode.

so CurrentHeatingCoolingState will be off or heat.

from homebridge-fhem.

Okay. Thank you very much for the clarification. Now I get the problem. Maybe Apple will fix this in future versions...

To me it was confusing to see my thermostats in the "off" mode in the home app.
Now I've configured the mapping to always show the HEAT state.

homebridgeMapping:
CurrentHeatingCoolingState=mode,values=manual:HEAT;boost:HEAT;auto:HEAT

from homebridge-fhem.