You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything works perfectly ever since. But there seems to be a problem with display.brightness datapoint. Full Warning Message in Log:
"You are assigning a number to the state "denon.0.display.brightness" which expects a string. Please fix your code to use a string or change the state type to number. This warning might become an error in future versions."
To Reproduce
Rule/Blockly which change state of display.brightness to any of the available options (off,dark,dimmed,bright).
Expected behavior
No warning in log
Screenshots & Logfiles
Versions:
Adapter version: 1.15.5
JS-Controller version: 6.0.5
Node version: v18.20.3
Operating system: Debian 12
AVR model: Marantz AV8805
Additional context
This error exists like ever since (years). Everything works perfectly fine regarding the script or its functionality, also manually controlling the datapoint is all working fine. it's just the warning in the log. doing what the warning suggests actually does not help fixing the warning.
The text was updated successfully, but these errors were encountered:
Everything works perfectly ever since. But there seems to be a problem with display.brightness datapoint. Full Warning Message in Log:
"You are assigning a number to the state "denon.0.display.brightness" which expects a string. Please fix your code to use a string or change the state type to number. This warning might become an error in future versions."
To Reproduce
Expected behavior
No warning in log
Screenshots & Logfiles
Versions:
Additional context
This error exists like ever since (years). Everything works perfectly fine regarding the script or its functionality, also manually controlling the datapoint is all working fine. it's just the warning in the log. doing what the warning suggests actually does not help fixing the warning.
The text was updated successfully, but these errors were encountered: