Open sm79 opened 1 year ago
mcuiobroker
commented
1 year ago Bitte einmal die v3.1.3-beta.31probieren. NICHT die aktuelle v3.1.3-beta.40.
Vorher Sicherung der einzelnen Jarvis-DPs als txt-Dateien machen.
Zugehörigen Link findet man: https://mcuiobroker.gitbook.io/jarvis-infos/system-jarvis-neuigkeiten
sm79
commented
1 year ago Issue still persists. :(
What I did:
v3.1.3-beta.31 (v3.1.3-beta.31) the way it is described here: https://mcuiobroker.gitbook.io/jarvis-infos/jarvis-v3/v3-fuer-einsteiger/installation-jarvis-v3#installation-commit-version-bestimmte-alpha-versionState value to set for "shelly.0.SHDM-2#C45BBE47163C#1.lights.brightness" has to be type "number" but received type "string"
Zefau
commented
1 year ago @sm79 sollte mit v3.1.4-beta.5 behoben sein
sm79
commented
1 year ago Leider haben weder Update auf v3.1.4-beta.5, noch ein Update auf v3.1.4-beta.6 die Situation verändert.
Update-Prozedur wurde wie in meinem Kommentar weiter oben durchgeführt.
Welche Datei(en) hätte(n) sich denn eigentlich updaten/aktualisieren müssen?
Zefau
commented
1 month ago @sm79 kannst du dir mal anschauen, ob das mit v3.2 behoben ist?
Running on Jarvis 3.1.2, incl PRO account features Browser Console shows no relevant errors.
Brief overview: To change brightness level (of a Shelly Dimmer 2) to predefined settings I want to use ButtonGroupAction instead of DropDownAction. However using ButtonGroupAction on predefined state values, the brightness is not updating due to data type error shown in iobroker log:
State value to set for "shelly.0.SHDM-2#C45BBE47163C#1.lights.brightness" has to be type "number" but received type "string"Long story:
At first I set predefined values and options on the "brightness" state of the Shelly Dimmer 2:
The values set in "Anzeigevariante" are then used for certain buttons in ButtonGroupAction:
The widget looks like this:
Pressing on any of the three buttons, the following errors are shown in the iobroker log:
Using these settings in DropDownAction, everything works fine - It's just not as convenient as just pressing a button. Using these settings in ButtonGroupAction, the state value data type would need to be converted.
So it would be great if ButtonGroupAction could handle such type inconsistencies by itself or at least provides a setting or switch to enable type conversion.