This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 16 exceeded minimum of 18. See https://homebridge.io/w/JtMGR for more info.

[grunchy99]

This message appear in the log of HomeBridge :

This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 16 exceeded minimum of 18. See https://homebridge.io/w/JtMGR for more info.

Heat Pump is set to heating at 16° Celsius.

http://192.168.1.88/aircon/get_model_info :

ret=OK,model=135E,type=N,pv=3.20,cpv=3,cpv_minor=20,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=1,temp=1,temp_rng=0,m_dtct=0,ac_dst=--,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=1,en_rtemp_a=0,en_spmode=3,en_ipw_sep=1,en_mompow=1,hmlmt_l=10.0

[cbrandlehner]

Cooling Threshold Temperature is about cooling, not heating. The lowest value allowed is 18 (or higher), up to32.

This is the code, starting line 970 in index.js:

 this.heaterCoolerService
      .getCharacteristic(Characteristic.CoolingThresholdTemperature)
      .setProps({minValue: Number.parseFloat('18'),
                 maxValue: Number.parseFloat('32'),
                 minStep: Number.parseFloat('0.5')})
      .on('get', this.getCoolingTemperatureFV.bind(this))
      .on('set', this.setCoolingTemperature.bind(this));

HomeKit should not allow you to set a lower value than what's configured here. Can you provide a reproduceable scenario how to set a target value of 16?

[grunchy99]

I just set heating mode and select 16 via Home App, like this screenshot :

[cbrandlehner]

I see. I tried to reproduce on my iPhone with iOS 16.1 (Beta) and could not reproduce in cool mode. The lowest value I can choose is 18°C. I am using HomeBridge version 1.5.0.

It seems that this might be a problem with either HomeBridge or Apple HomeKit unless somebody can show me a way to fix this in the plugin code.

[grunchy99]

Hi, thanks for your reply :-)

I'm not in cooling mode, but in heating mode. I'm also using HomeBridge 1.5. Can you try to reproduce in heating mode ?

[cbrandlehner]

Now I see the issue. I will have to investigate the issue but now I can reproduce.

Test procedure: Set Daikin to HEAT and choose a temp lower 18, maybe 17. Restart Homebridge or the Daikin plugin if you are using child-bridges (which is recommended). The error will display in the log. No interaction in HomeKit necessary to cause the warning message to occur.

[grunchy99]

Yes perfect, you have successfully reproduce my case :-)

Thanks for your help,

[grunchy99]

Hi cbrandlehner,

Did you find a solution for the problem ?

Kind Regards,

[garionw]

I'm also having this issue (although I'm struggling to replicate it exactly at the moment), but it only seems to occur when I'm using Automation on iOS. In my case, I want to set the temperature to 12 degrees (celsius) on heating overnight, then I want another one at 5:30am to set it to 16 degrees.

I think it's related to the configured settings for 'auto' in homekit, even if it's not currently selected. In screenshot 1 you can see my 'auto' settings, and in screenshot 2 you can see the settings for 5:30am (setting it to 16 degrees heating)

It appears to be related to the temperatures selected under the 'auto' mode, even if auto isn't being used. I've tried removing the device in Homebridge and re-adding it, I've also tried resetting Homebridge. It hasn't always worked like this, but I can't remember when it started and when I used older versions of the plugin the same behaviour was seen.

At the moment auto is set to 16 to 20 (temperature 1) and I'm testing on the 5:30am automation (setting the temperature to heating 16 - temperature 2). I've attached a copy of the logs from homebridge (daikin 1) and you can see on lines 65 and 75 that it's trying to set the heating temperature to the correct value (16), but then on lines 83 and 93 it tries to set the cooling temperature to 20 degrees - which is the highest value I selected for 'auto'

If I change auto to be between 15 and 18 and run the test again (temperature 3 and daikin 2) you can see similar things. Lines 96 and 106 set the temperature to the desired value, but these are quickly overwritten on lines 114 and 124 when it gets set to 18 degrees (again the maximum of the 'auto' temperature.

Finally, if I set auto to 12 to 16, and set the automation to heating 18, you can see (daikin 3) that it sets the temperature to 18 twice (on lines 94 and 104, but there isn't a secondary update. This means I've been able to work around the problem by setting the automatic scales to 10-10.5.

I hope this helps!

Daikin 3.txt Daikin 2.txt Daikin 1.txt

[grunchy99]

Hi,

Maybe a problem due to Homebridge 1.6, like this plugin release : homebridge-melcloud-control https://github.com/grzegorz914/homebridge-melcloud-control/blob/main/CHANGELOG.md

[0.4.3] - (06.12.2022) Changes Homebridge >= 1.6 fix characteristic was supplied illegal value: number 0 exceeded minimum of 10

[martinschki]

Hi, same here I have the Unit set to "heat" and receive the following in log:

[12/02/2023, 12:00:34] [homebridge-daikin-local] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 12 exceeded minimum of 18. See https://homebridge.io/w/JtMGR for more info.

I have set heating to 12°C

Homebridge: 1.6.0 Plugin: 1.0.0

[cbrandlehner]

Tried to fix this with version 1.0.1.