'Target Temperature': characteristic was supplied illegal value

MikeMighty commented 3 years ago

Hi there,

Not really a master or king with the codes. My homebridge works without issues, only the following gets spammed in the log:

[8/30/2021, 10:43:32 PM] [homebridge-evohome] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 5 exceeded minimum of 10. See https://git.io/JtMGR for more info. [8/30/2021, 10:43:32 PM] [homebridge-evohome] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 5 exceeded minimum of 10. See https://git.io/JtMGR for more info. [8/30/2021, 10:43:32 PM] [homebridge-evohome] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 5 exceeded minimum of 10. See https://git.io/JtMGR for more info. [8/30/2021, 10:43:32 PM] [homebridge-evohome] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 5 exceeded minimum of 10. See https://git.io/JtMGR for more info.

Can or should i do anything about this?

luc-ass commented 3 years ago

That's a new one... I haven't found similar stuff in my logs. Anyone?

As an Explaination: It seems, that homebridge is not fond of accepting temperatures below 5 degrees. This is used as off in homebridge-evohome. Are some of your thermostats turned off? Can you set them to 10 °C and keep an eye on your logs?

MikeMighty commented 3 years ago

Yes, that seems to solve the problem. I had the system in off mode for the summer. The standard 5 degrees in off mode cant be set to 10 or higher it seems. So the only workarround is to not put evohome in off mode.

Thanks for the reply.

luc-ass commented 3 years ago

Okay, now that we know what causes this bug, can you give me some context?

Hardware you are running homebridge on
OS and version on your system
NPM/Node version
Homebridge version
Plugin version

Barloew commented 3 years ago

I get a similar error in my log:

[homebridge-evohome] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://git.io/JtMGR for more info.

I am running Dockerized Homebridge on Synology hardware. Alpine Linux (3.12.8) Node.js v14.17.6 Npm v6.14.15 Homebridge v1.3.4 homebridge-evohome v0.8.4

in my case, I have two thermostats at 5°. This has never been been an issue before. What was new is that one of my thermostats ran out of battery. This thermostat created a log file entry with a temperature of undefined°. As soon as I replaced the battery, the issue was gone.

Hope this helps. Thanks for the great plugin.

luc-ass commented 3 years ago

As a workaround you can set your system to "away" and set away to something like 12 degrees...

MikeMighty commented 3 years ago

Hardware you are running homebridge on: RPI3
OS and version on your system: Alpine Linux (3.12.7) 
NPM/Node version: v14.17.5 
Homebridge version: homebridge-config-ui-x v4.41.2
Plugin version: homebridge-evohome v0.8.3

PuzzledUser commented 2 years ago

FYI, I produced this error by setting OFF on the HEAT, COOL, AUTO control. My system has a configured min value of 10°C, hence it complained when 5°C was selected. Shortly later it noticed that 10°C was set as target. No great shakes...

[02/01/2022, 14:50:54] [Evohome] Current temperature of XX Thermostat is 15.5°
[02/01/2022, 14:50:54] [Evohome] Target temperature for XX Thermostat is 5°
[02/01/2022, 14:50:54] [homebridge-evohome] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 5 exceeded minimum of 10. See https://git.io/JtMGR for more info.
[02/01/2022, 14:51:23] [Evohome] Updating: XX targetTempChange from: 5 to: 10

luc-ass commented 2 years ago

Okay - I tried to reproduce the error but got only valid responses. Could one of you check out the latest version and check wether it still produces the error?

SeaneyC commented 2 years ago

I messed about with various combinations of 15, 10, and 5 degree settings with away turned off and on, and wasn’t able to generate any errors like the 2 users above

Hardware you are running homebridge on: 2GB rPi4
OS and version on your system: Raspbian GNU/Linux Bullseye (11)
NPM/Node version: v16.14.0
Homebridge version: v1.5.0
Plugin version: 0.9

On Mon, 22 Aug 2022 at 17:54, Lucas Gasenzer @.***> wrote:

Okay - I tried to reproduce the error but got only valid responses. Could one of you check out the latest version and check wether it still produces the error?

— Reply to this email directly, view it on GitHub https://github.com/luc-ass/homebridge-evohome/issues/94#issuecomment-1222633435, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT4A6BOWTBY3KRF63BGRCQ3V2OWC3ANCNFSM5DCVIHRA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

MikeMighty commented 2 years ago

It produces the error in off-mode, system default 5 degrees. Away-mode gives no errors.

[23/08/2022, 23:08:40] [Evohome] System mode Away is false

[23/08/2022, 23:08:40] [Evohome] System mode DayOff is false

[23/08/2022, 23:08:40] [Evohome] System mode HeatingOff is true

[23/08/2022, 23:08:40] [Evohome] System mode AutoWithEco is false

[23/08/2022, 23:08:40] [Evohome] System mode Custom is false

[23/08/2022, 23:08:43] [Evohome] Current temperature of Woonkamer Thermostat is 25°

[23/08/2022, 23:08:43] [Evohome] Target temperature for Woonkamer Thermostat is 5°