From 3c120eda2472ad05a29a8d1c5130f9b2ea766fa8 Mon Sep 17 00:00:00 2001 From: Beta-User <> Date: Sat, 21 May 2022 10:36:30 +0000 Subject: [PATCH] 10_RHASSPY: enhance docu for Factor field (SetNumeric) git-svn-id: https://svn.fhem.de/fhem/trunk@26074 2b470e98-0d58-463d-a4d8-8e2adae1ed80 --- fhem/contrib/RHASSPY/10_RHASSPY.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fhem/contrib/RHASSPY/10_RHASSPY.pm b/fhem/contrib/RHASSPY/10_RHASSPY.pm index 538437199..e32437a41 100644 --- a/fhem/contrib/RHASSPY/10_RHASSPY.pm +++ b/fhem/contrib/RHASSPY/10_RHASSPY.pm @@ -6629,7 +6629,7 @@ yellow=rgb FFFF00

  • GetOnOff
  • (for keywords see SetOnOff)
  • SetNumeric
  • Dependend on the specific surrounding informations, a combination of {Device}, {Value} (nummeric value), {Change} and/or {Type} are sufficient, {Room} is optional. Additional optional field is {Unit} (value percent will be interprated as request to calculate, others will be ignored). - Alternatively to {Unit:percent} you may combine {Value} with {Factor} (nummeric value) to increase or reduce the stepwidth of the desired change (both values will be multiplied). {Change} can be with one of ({Type}) + {Change} can be with one of ({Type}) - allowing to decide on calculation scheme and to guess for the proper device and/or answer. + allowing to decide on calculation scheme and to guess for the appropiate device and/or answer. Optionally you may combine {Change} with {Factor} (nummeric value) to increase or reduce the stepwidth (typically derived from device, if {Value} is not provided) of the desired change (both values will be multiplied). experimental multicommand feature should work also with this intent (switching intent to SetNumericGroup).
  • SetNumericGroup
  • (as SetNumeric, except for {Group} instead of {Device}).