search

jeffschubert / homebridge-daikin-oneplus

Homebridge plugin to control a Daikin One+ thermostat
Apache License 2.0
18 stars 7 forks source link

This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value. #32

Open garyhooper opened 1 year ago

garyhooper commented 1 year ago

Describe Your Problem: In the Homebridge status window, I am seeing this message, repeating:

This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 31 exceeded maximum of 30.

Any ideas?

Environment:

jeffschubert commented 1 year ago

Looks like you have a target heating temperature set higher than 30C (86F). Apple/HomeKit allows you to specify a target temperature between 10-38C (50-100F), but the native Daikin app only allows target heating temps between 10-30C. I coded the plugin to only allow the same 10-30C range to avoid the possibility of breaking the Daikin unit.

If you switch the mode to Heat and then set the target temp to 30C or 86F (or lower) then the warning should go away.

When cooling there's a similar range of 12-32C (53-89F) that you're restricted to setting the target cooling temp to.

garyhooper commented 1 year ago

This was my suspicion, but...

My thermostat is in Auto mode. My daytime schedule has a range of 64F-87F. Although the 87F clearly exceeds the 30C, this is the temperature for cooling not heating. (The Daikin range max on my thermostat and Daikin app is 90F, or 32C.)

The messages start when the schedule (automatically) changes to daytime. The Daikin One is changing it, not Homekit/Homebridge. When the schedule changes to evening, the error is no longer appearing, because the range max falls below 30C.

Would this be a plug-in, Homebridge, or Homekit issue?

jeffschubert commented 1 year ago

Ahh, interesting. I'm not sure where the issue would lie at this point. I'll need to recreate it here and see exactly where it is generating the warning. I bet I'll find a way to work around it.

jonnyborbs commented 1 year ago

I see the same warning on startup. I also can’t change temperatures, though reading data from the thermostats and sensors works fine. I’ve tried resetting the HB cache and that was no help either.

I’m also using auto mode, with both cooling and heating thresholds set at once.

jeffschubert commented 11 months ago

Sorry for the slow response. I was able to rework the thresholds and auto mode so that it'll actually set the two thresholds as expected in the next release. I discovered a regression that caused it to stop working. I think the illegal value warning may still show up in your specific case @garyhooper, but I'm hoping to nail that down next.

jonnyborbs commented 11 months ago

No worries at all! The prior version is working properly less the enhancements added in 3.1.2, and I'm sure we all appreciate you building this in the first place. Thanks for looking into it (and the other related issue!)

jeffschubert commented 6 months ago

@jonnyborbs Just published 3.2.0 which should fix the thresholds. @garyhooper let me know if you're still seeing issues with this version. (I didn't have much time over the past year for the plugin so I'm fuzzy on what might still remain to be fixed, if anything.)

garyhooper commented 5 months ago

@jeffschubert, I've upgraded to 3.2.0, and I'm still seeing the problem:

This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 32 exceeded maximum of 30.