diff --git a/fhem/contrib/RHASSPY/10_RHASSPY.pm b/fhem/contrib/RHASSPY/10_RHASSPY.pm index 0e60471bb..134a1f2a0 100644 --- a/fhem/contrib/RHASSPY/10_RHASSPY.pm +++ b/fhem/contrib/RHASSPY/10_RHASSPY.pm @@ -5056,7 +5056,10 @@ sub handleIntentMediaControls { return $hash->{NAME} if !$data->{Confirmation} && getNeedsConfirmation( $hash, $data, 'MediaControls', $device ); my $cmd = $mapping->{$command}; - $cmd .= " $data->{Playlist}" if $command eq 'cmdPlaylist'; + if ( $command eq 'cmdPlaylist') { + return respond( $hash, $data, getResponse($hash, 'NoValidData') ) if !defined $data->{Playlist}; + $cmd .= " $data->{Playlist}"; + } if ( $command eq 'cmdPlaySelected'|| $command eq 'cmdAddSelected' ) { #hand over method! playSelection or addSelection return respond( $hash, $data, getResponse($hash, 'NoMappingFound') ) if InternalVal($device, 'TYPE', 'unknown') ne 'MPD'; @@ -6167,6 +6170,17 @@ So all parameters in define should be provided in the key=value form. In
  • homebridgeMapping atm. is not used as source for appropriate mappings in RHASSPY.
    • + + +
  • siteId: To some extend, you may (indirectly) want or need a RHASSPY device to act as a satellite in the Rhasspy ecosystem. So it may be a good idea to add the siteId (no matter if it's the automatically generated one) to the satellite list in the intent recognition component in Rhasspy. Otherwise the following features will not work: + +
    • + +
  • noChangeover: By default, RHASSPY will first try to execute the intent as handed over by Rhasspy. In case there's no strict match, RHASSPY then will do a check, if the single device intent could be executed as group intent (vice versa; to do this, the {Group} key value will be used as {Device} key). Setting this key to '1' will completely prevent this check, '2' will stop changeover from single device intent to respective group intent, but allow to switch from group to single device.
  • handleHotword: Trigger Reading hotword in case of a hotword is detected. See attribute rhasspyHotwords for further reference.
    • @@ -6322,12 +6336,11 @@ After changing something relevant within FHEM for either the data structure in test_file <path and filename>

    Checks the provided text file. Content will be sent to Rhasspy NLU for recognition (line by line), result will be written to the file '<input without ending.txt>_result.txt'. stop as filename will stop test mode if sth. goes wrong. No commands will be executed towards FHEM devices while test mode is active.

    -

    Note: To get test results, RHASSPY's siteId has to be configured for intent recognition in Rhasspy as well.

    +

    Note: To get test results, some additional configuration in Rhasspy is required!

  • test_sentence <sentence to be analyzed> -

    Checks the provided sentence for recognition by Rhasspy NLU. No commands to be executed as well.

    -

    Note: wrt. to RHASSPY's siteId for NLU see remark get test_file.

    +

    Checks the provided sentence for recognition by Rhasspy NLU. No commands to be executed as well, needs also additional configuration in Rhasspy.

    • @@ -6518,7 +6531,7 @@ i="i am hungry" f="set Stove on" d="Stove" c="would you like roast pork"<
  • rhasspyMsgDialog -

    If some key in this attribute are set, RHASSPY will react somehow like a msgDialog device. This needs some configuration in the central msgConfig device first, and additionally for each RHASSPY instance a siteId has to be added to the intent recognition service.

    +

    If some key in this attribute are set, RHASSPY will react somehow like a msgDialog device. This needs some configuration in the central msgConfig device first, and additional configuration in Rhasspy!

    Keys that may be set in this attribute: