This adapter can convert normal sentences, like Switch light in kitchen on to specific command and sets the state adapter.0.device.kitchenLight to true.

This adapter makes no sense to be activated standalone. It should be used with other adapters like telegram or Android app iobroker.vis.

To execute command, write state text2command.<INSTANCE>.text with sentence. You will always get the answer in text2command.<INSTANCE>.response.

If you define Answer to ID, the answer will be written in this ID too. This is required for e.g. to realise the voice acknowledges.

You can send a message via sendTo from javascript. The answer will come in the message back:

sendTo('text2command', 'Switch light in kitchen on', function (err, response) {
    console.log('Response is: ' + response);
});

Regular expressions can be used, like: /^light\son|^lamp\son/. Regular expressions are always case-insensitive.

To use "Switch on/off by function" you should care of functions.

Keywords work as following:

• space divides keywords
• all keywords must present in a sentence to trigger a rule: e.g., keyword: light on will trigger on switch light on, make light on everywhere and do not trigger on switch on, make light.
• one keyword can have many forms. Variations of keyword must be divided by "/". E.g., keywords: switch/make/do light on/true will trigger on: do light true, make please light on.
• if keyword can come in many cases (nom, gen, accusative, plural, ...) they all must be listed as variations, like: switch light/lights on.

Following functions will be interpreted as

enum.functions:

enum.functions.light (Licht | Свет):

• roles - level.dimmer
• roles - switch.light

enum.functions.backlight (Beleuchtung | Подсветка):

• roles - level.backlight
• roles - switch.backlight

enum.functions.blinds/shutter (Rollladen | Жалюзи/окна)

• roles - level.blind
• roles - switch.blind

enum.functions.curtain (Vorhänge | Шторы)

• roles - level.curtain
• roles - switch.curtain

enum.functions.heating (Heizung | Отопление/Подогрев)

• roles - level.temperature
• roles - switch.temperature

enum.functions.music (Musik | Музыка)

• roles - button.play
• roles - button.stop / button.pause

enum.functions.alarm/security (Alarmanlage / Alarm | Охрана)

• roles - switch.security

enum.functions.lock (Schloß / Schloss | Замок)

• roles - switch.open
• roles - switch.lock

Following rooms are supported:

You can use patterns in acknowledgements:

• %s: value
• %u: unit
• %n: name (planned!)
• {objectId}: the state of this objectID will be placed here. Actually, it will be the same bindings supported as by iobroker.vis, except special bindings.

The following commands are supported:

Answer: 14:56 (current time)

Answer is customizable. Default: My name is Alpha

User must specify the state ID, where to read outside temperature. The answer is customizable. Default: Outside temperature is %s %u %s will be replaced by temperature, rounded to integer. %u will be replaced by units of this state or by system temperature units.

User must specify the state ID, where to read inside temperature. The answer is customizable. Default: Inside temperature is %s %u %s will be replaced by temperature, rounded to integer. %u will be replaced by units of this state or by system temperature units.

This command reads information from enums. It uses enum.functions to find type of device (e.g., light, alarm, music) and enum.rooms to detect room name.

Example in german:

Keywords to switch on are: switch on, e.g. switch rear light in bath on

Keywords to switch off are: switch off, e.g. switch light in living room off

Answer will be generated automatically if desired: Switch off %function% in %room%, where %function% and %room% will be replaced by found device type and location.

Command accepts the numeric value too. It has priority, e.g. in command switch light off in living room on 15% the light will be set to 15% and not in off state.

You can define default room in []. E.g. switch the light on[sleepingroom]

This command reads information from enums. It uses enum.functions.blind to find type blinds or shutter and enum.rooms to detect room name.

Keywords to move blinds up are: blinds up, e.g. set blinds up in sleeping room

Keywords to move blinds down are: blinds down, e.g. move blinds down in office

You can specify the exact position of blind in percent, e.g. move blinds to 40 percent in office

Answer will be generated automatically if desired: in %room%, where %room% will be replaced by found device type and location.

User must specify state ID of a device, which must be controlled and value, which must be written.

You should create rule for every position (e.g., for on and for off).

Answer is customizable. Default: Switched on

E.g.:

• Deactivate alarm, Object ID: hm-rpc.0.alarm, Value: false, Answer: Alarm is deactivated/Deactivated. In this case, the answer will be randomized between Alarm is deactivated and Deactivated.
• Activate alarm, Object ID: hm-rpc.0.alarm, Value: true, Answer: Alarm is activated/Activated/Done . In this case, the answer will be randomized between Alarm is activated, Activated and Done.

Deactivate must be first in the list, because it is longer.

You can use float values in the control commands. If some numeric value is in the text, it will be used as a control value and the predefined value will be ignored.

E.G. for rule:

• Set light level, Object ID: hm-rpc.0.light.STATE, Value: 10, Answer: Level set to %s%.

If command is like Set light level to 50%, so into the hm-rpc.0.light.STATE will be written 50 and answer will be Level set to 50%.

If command is like Set light level, so into the hm-rpc.0.light.STATE will be written 10 and answer will be Level set to 10%.

User must specify state ID of a device, which value will be read. This template will answer with information from some state.

E.g.:

• windows opened, Object ID: javascript.0.countOpenedWindows, Acknowledge: Actual %s windows opened
• temperature sleeping room, Object ID: hm-rpc.0.sleepingRoomSensor.TEMPERATURE, Acknowledge: Actual temperature in sleeping room is %s %u/%s %u. In this case, the answer will be randomized between Actual temperature in sleeping room is %s %u and %s %u.

You can write some text into state. User must specify state ID to write text into it.

E.g. rule: email [to] wife, Object ID: javascript.0.emailToWife, Acknowledge: Email sent Text: Send email to my wife: I will be late. Adapter looks for the last word from keywords (in this case wife), extracts text from the next word (in this case I will be late) and writes this text into javascript.0.emailToWife. Word to is not required to trigger the rule, but will be removed from a text.

The answer is customizable. Default: Thank you or You are welcome

The answer is customizable. Default: No problem or You are welcome

You can generate answer with bindings {objectId} in acknowledgement. Used for alexa.

E.g.:

• windows opened, Acknowledge: Actual {javascript.0.countOpenedWindows} windows opened
• temperature sleeping room, Acknowledge: Actual temperature in sleeping room is {t: hm-rpc.0.sleepingRoomSensor.TEMPERATURE; Math.round(t)}/{hm-rpc.0.sleepingRoomSensor.TEMPERATURE; round(1)} degree. In this case the answer will be randomized between Actual temperature in sleeping room is and .

You can read more about bindings here: (Bindings of objects)[https://github.com/ioBroker/ioBroker.vis#bindings-of-objects]

Additionally, you can get time until now by {hm-rpc.0.light.STATE.lc;dateinterval} (2 minutes and 12 seconds) or {hm-rpc.0.light.STATE.lc;dateinterval(true)} (2 minutes and 12 seconds ago)

There is a possibility to use javascript engine to process commands in text2command. To do that, you must specify some state in "Processor state ID" (Advanced settings) and to listen to this state in some JS or Blockly script. You can create some state manually in admin or in script. Processing script can look like this one:

createState("textProcessor", '', function () {
    // text2command writes the value with ack=false. Change "any" is important too, to process repeated commands.
    on({id: "javascript.0.textProcessor", ack: false, change: 'any'}, function (obj) {
         var task = JSON.parse(obj.state.val);
         // value looks like
         // {
         //     "command":      "text to process", // command that was received by text2command
         //     "language":     "en",              // language in command or system language
         //     "withLanguage": false              // indicator if language was defined in command (true) or used default language (false)
         // }
         // response to text2command with ack=true
         if (task.command === 'switch light on') {
            setState("hm-rpc.0.light", true);
            setState("javascript.0.textProcessor", 'light is on', true);
         } else {
            // let it process with predefined rules
            setState("javascript.0.textProcessor", '', true);
         }
    });
});

Set in settings of text2command Processor state ID as javascript.0.textProcessor to let this example work.

The first, the command will be processed with your javascript, and if javascript answers with '' or not answer in predefined time (1 second by default) the command will be processed by rules.

If activated so by every command (no matter if the request came via state or sendTo) the text2command.X.response will be written with the answer.

• in Russian, male and female answers.

• (bluefox) Corrected GUI

• (bluefox) Corrected link from admin

• (bluefox) Corrected many GUI errors

• (bluefox) Migrated GUI to v5

• (Apollon77) Fix crash cases reported by Sentry

• (bluefox) Checked the existence of sayit instance before output
• (bluefox) Added the decimal places settings to temperature
• (bluefox) Added the second object ID to user queries
• (bluefox) Added the option: "No negative answer"

• (bluefox) Corrected GUI

• (bluefox) Some errors will be caught at start

• (bluefox) Updated GUI.
• (bluefox) Updated releaser

• (PeterVoronov) Corrected usage of regex

• (bluefox) Updated GUI.

• (Apollon77) Prevent crash case (Sentry IOBROKER-TEXT2COMMAND-J)

• (Apollon77) Prevent crash case (Sentry IOBROKER-TEXT2COMMAND-D, IOBROKER-TEXT2COMMAND-C)

• (bluefox) Updated the select ID dialog.

• (bluefox) Fixed GUI errors

• (bluefox) Fixed GUI errors

• (bluefox) Fixed select ID dialog

• (bluefox) New GUI

• (unltdnetworx) changed copyright year to 2019, according to issue #41
• (unltdnetworx) additional words for blinds and functions in english and german
• (unltdnetworx) fixed typo

• (bluefox) Using the defined language by words

• (unltdnetworx) description in german corrected
• (unltdnetworx) added percent to true/false rules

• (Apollon77) Fix

• (bluefox) Support of bindings in answer {objId}

• (bluefox) Support of Admin3 (but not materialize style)

• (bluefox) The parsing error was fixed

• (bluefox) Check if units are undefined

• (bluefox) Support of iobroker.pro

• (bluefox) translations

• (bluefox) russian translations

• (bluefox) fix the russian temperature text
• (bluefox) extend rule "control device" with option 0/1
• (bluefox) use by control of devices min/max values if set

• (bluefox) add additional info for external text processor

• (bluefox) add text processor state ID

• (bluefox) fix error with detection of numeric values

• (bluefox) fix: send text command

• (bluefox) replace special chars in input text: #'"$&/!?.,;:(){}^

• (bluefox) fix double pronunciation of some answers

• (bluefox) ignore spaces

• (bluefox) fix error with enums

• (bluefox) implement "say something"

• (bluefox) fix temperature

• (bluefox) fix russian outputs

• (bluefox) fix russian outputs

• (bluefox) round temperature in answers

• (bluefox) implement russian time

• (bluefox) check invalid commands

• (bluefox) fix problem with controlling of channels
• (bluefox) enable write JSON as argument

• (bluefox) remove unused files

• (bluefox) extend readme

• (bluefox) initial commit

The MIT License (MIT)

Copyright (c) 2014-2023, bluefox dogafox@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.