Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

'Target Temperature': characteristic was supplied illegal value #94

Open
MikeMighty opened this issue Aug 30, 2021 · 14 comments
Open

'Target Temperature': characteristic was supplied illegal value #94

MikeMighty opened this issue Aug 30, 2021 · 14 comments
Labels
under investigation

Comments

@MikeMighty
Copy link

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
Copy link
Owner

luc-ass commented Sep 11, 2021

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
Copy link
Author

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
Copy link
Owner

luc-ass commented Sep 12, 2021

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
Copy link

Barloew commented Sep 19, 2021

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
Copy link
Owner

luc-ass commented Sep 19, 2021

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

@MikeMighty
Copy link
Author 

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
Copy link

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
Copy link
Owner

luc-ass commented Aug 22, 2022

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
Copy link

SeaneyC commented Aug 23, 2022 via email

@MikeMighty
Copy link
Author

MikeMighty commented Aug 23, 2022 via email

@SeaneyC
Copy link

SeaneyC commented Aug 23, 2022 via email

@luc-ass
Copy link
Owner

luc-ass commented Aug 24, 2022

Okay, thanks for your vigorous testing 😄
@MikeMighty do your run your Homebridge in DEBUG-Mode?

@PuzzledUser
Copy link

PuzzledUser commented Aug 24, 2022 •
edited
Loading

I tried what proved it previously and there is no error today. I reckon it was to do with OFF setting target to 5°C which is less than my minimum, but it's ok today.

Then I tried a slightly different sequence in DEBUG mode and oops.

[24/08/2022, 13:16:57] [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://homebridge.io/w/JtMGR for more info.
[24/08/2022, 13:16:57] [homebridge-evohome] Error: 
    at TargetTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
    at TargetTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2045:14)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1617:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:10:18
    at EvohomeThermostatAccessory.getTargetTemperature (/usr/local/lib/node_modules/homebridge-evohome/index.js:932:5)
    at TargetTemperature.emit (events.js:315:20)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1592:14
    at new Promise (<anonymous>)
    at TargetTemperature.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1590:12)
    at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)

To reproduce I:

  • Set Off mode in Home
  • Set Away mode in Comfort app (NB my minimum is 10°C)
  • Opened Home app to trigger error (I guess it reads current state)
  • Then cancel away mode (and increase target to above 10°C) to stop the error appearing.

The issue is not dependant on DEBUG mode, just that awkward sequence.

@PuzzledUser
Copy link

Still there in homebridge-evohome v0.11.0

[19/03/2023, 21:56:36] [Evohome] Heating is set off for Dave's Thermostat (set to 5°)
[19/03/2023, 21:56:48] [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://homebridge.io/w/JtMGR for more info.
[19/03/2023, 21:58:04] [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://homebridge.io/w/JtMGR for more info.
[19/03/2023, 22:01:48] [Evohome] Updating: Dave's targetTempChange from: 5 to: 13

Triggered on this occasion by asking the dumb Siri to turn down the heating (it turned it off instead).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
under investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@luc-ass @Barloew @MikeMighty @SeaneyC @PuzzledUser