Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

This plugin generated a warning from the characteristic 'Target Temperature'

See original GitHub issue

Getting this error in the Homebridge log:

[3/1/2021,`` 10:11:01 AM] [homebridge-dyson-pure-cool] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 37.19999999999999 exceeded maximum of 37. See https://git.io/JtMGR for more info.

Error occurs every minute.

Issue Analytics

State:
Created 3 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

ElphaXcommented, Apr 19, 2021

Thanks for doing this Wawoodwa, gonna bump this so there’s a pull.

0reactions

lukasroegnercommented, May 14, 2021

Fixed in 1.8.8, thanks to @wawoodwa

Top Results From Across the Web

This plugin generated a warning from the characteristic 'Target ...

This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 9 exceeded minimum of 10 #389.

Tuya AC shows wrong temperatures, numbers exceed ...

[8/23/2021, 8:18:43 PM] [homebridge-tuya] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': ...

homebridge-nest - Bountysource

[6/3/2021, 9:17:27 AM] [homebridge-nest] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied ...

Rinnai Heating/Cooling Wifi Module - Feature Requests

[homebridge-rinnai-touch-platform] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic ...

Homebridge Broadlink RM Plugin - HomeKit RF and IR

If you're seeing something like ERROR LOADING PLUGIN"..."async setCharacteristicValue (props, value, callback) { then please check your node version before ...