esphome::modbus_client Namespace Reference

Data Structures
class	ClientActionBase
	Shared base for the modbus_client actions. More...
class	ModbusClientSendAction
	modbus_client.send: fire a raw PDU (function code + data; the hub adds address and CRC). More...
class	ReadBitsAction
	modbus_client.read_coils / read_discrete_inputs: on_response delivers the bits as a PackedBits view (bit 0 = the bit at start_address; only valid for the duration of the trigger). More...
class	ReadCommandOptions
	The read-side per-command options (modbus::CommandOptions), declared once for every action that sends a read. More...
class	ReadRegistersAction
	modbus_client.read_holding_registers / read_input_registers: on_response delivers the registers in host byte order as values (only valid for the duration of the trigger). More...
class	ReadWriteMultipleRegistersAction
	modbus_client.read_write_multiple_registers (FC 0x17): writes one register block and reads another back in one transaction (write first, per Modbus 6.17). More...
class	TypedClientActionBase
	Typed actions: these do NOT override the raw on_response, so the base ModbusClientDevice default runs the shared dispatch (validation gate + decode) and the typed callbacks below fire directly on the action. More...
class	WriteMultipleCoilsAction
	modbus_client.write_multiple_coils: on_response is the acknowledgement (no arguments). More...
class	WriteMultipleRegistersAction
	modbus_client.write_multiple_registers: on_response is the acknowledgement (no arguments). More...
class	WriteSingleCoilAction
	modbus_client.write_single_coil: on_response is the acknowledgement (no arguments). More...
class	WriteSingleRegisterAction
	modbus_client.write_single_register: on_response is the acknowledgement (the ack only echoes the request, so it carries no arguments). More...