Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| ezeio2:apiref:control [2021-09-23 01:40] – andreh | ezeio2:apiref:control [2023-08-08 23:26] (current) – andreh | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| < | < | ||
| - | Directly control a field value or output status of a controller. Note that this command will generate traffic to the controller, and is therefore rate limited to avoid excessive traffic. The field has to be set as "Writeable". | + | Directly control a field value or output status of a controller. Note that this command will generate traffic to the controller, and is therefore rate limited to avoid excessive traffic. The field has to be set as "Writable". |
| The immediate return data is a confirmation from the servers that the command was accepted. It is not an acknowledgement that the command(s) were actually received or executed on the controller. | The immediate return data is a confirmation from the servers that the command was accepted. It is not an acknowledgement that the command(s) were actually received or executed on the controller. | ||
| Line 35: | Line 35: | ||
| Set the value of two fields: | Set the value of two fields: | ||
| < | < | ||
| + | |||
| + | == Log flush == | ||
| + | Setting the value of a field will also cause any pending buffered log samples to be sent to the servers. This only applies to the control field command. Setting register or output value does not cause a log flush. | ||
| + | |||
| + | Tip: To force a log flush without making any changes to field values, write value 0 to field[0]. This has no effect on any valid field, but will still cause a log flush. | ||
| === Return value === | === Return value === | ||