setting–>Devices&Services–>Universal Devices ISY/IoX–>nn devices–>(type into search)lock–>DoorLock.On
In the Controls card the controls are grayed out.
Click on one of the controls, then trying lock or unlock gets the error “Failed to perform the action lock/lock. Unable to lock device hh hh hh 2”
OK, fine. I’ll send a raw command. Documentation: Universal Devices ISY/IoX
This script works to turn on the entry light:
alias: test door lock
sequence:
- action: light.turn_off
target:
entity_id: light.entry_ha_chandelier
description:
The following script, created by the visual editor, fails with the same error message:
alias: test door lock
sequence:
- action: lock.unlock
target:
entity_id: 366bea1f60124d135853f20d7829b4da
description: Entity entered in the visual editor as DoorLock.On
Now I want to try to send a command. Send node command does not include the command DON, the most common command in ISY, so Send raw node command must be used.
Using the visual editor, the ISY send command does not appear in the Add action drop-down box nor under the last drop-down box entry Other Actions. Unbeknownst to me, this is not just a drop-down box but a combination drop-down/dialog box. I stumbled upon this undocumented feature of HA when I typed in “ISY” into the Search action dialog box. It then turned into a drop-down box with a list of items that contained the sequence of letters I typed.
I choose my device, DoorLock.On which yields a 16 byte device_id number in the YAML. (I could have chosen the entity, DoorLock.On, which would appear in the YAML as lock.doorlock_on) Enter the command, exactly as in the documentation. DON. Since DON has no parameters, I un-check Parameters
The successful YAML is now:
alias: front door lock
sequence:
- action: isy994.send_raw_node_command
data:
command: DON
target:
device_id: 366bea1f60124d135853f30d7829b4da
description: ""
Most importantly, the documentation had no example on how to send a [raw] command. It stated that “command:” was required, but not where it goes.
Also, the documentation implied that the command itself must be in quotes. I see now that DON and DOF don’t have that implication, an inconsistency. Lower case does not work.
Having the YAML allows me to view then entire code and also use this code in scripts and automations that can only be done in YAML.
A search for documentation on the Visual editor yielded: Automation editor This link can also be found on the main documentation page of HA It is inadequate to the task. I would love to improve the document going to the “Help us improve our documentation page”. Unfortunately, I don’t know enough about the editor to make coherent suggestions. And since the editor is called visual editor when switching between it and YAML even the title needs to be changed.
-OSD