Replies: 61 comments 235 replies
-
|
It get multiple registers? count? |
Beta Was this translation helpful? Give feedback.
-
|
yes The code scans for consecutive addresses and calculates the count by looking at ModbusFunctionCode + addresses + offset. From that ranges of addresses are created that are requested in one modbus call. If you have to spilt a range because it contains too many fields start with a new address and adjust the offset. |
Beta Was this translation helpful? Give feedback.
-
|
I will try it later |
Beta Was this translation helpful? Give feedback.
-
|
Dont work with api only? |
Beta Was this translation helpful? Give feedback.
-
|
yes looks like there is a dependency on mqtt - not sure it's really required but for now it's a requirement |
Beta Was this translation helpful? Give feedback.
-
|
Working code ###
#sensor:
- platform: modbus_component
#modbus_id: modbus_serial
id: meter1
address: 0x1
sensors:
- id: raw_voltage_1
name: "EB1 Voltage L1"
address: 0x006C
offset: 0
unit_of_measurement: "V"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:flash
- id: raw_current_1
name: "EB1 Current L1"
address: 0x006C
offset: 1
unit_of_measurement: "A"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:power-socket
- id: raw_voltage_2
name: "EB1 Voltage L2"
address: 0x006C
offset: 2
unit_of_measurement: "V"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:flash
- id: raw_current_2
name: "EB1 Current L2"
address: 0x006C
offset: 3
unit_of_measurement: "A"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:power-socket
- id: raw_voltage_3
name: "EB1 Voltage L3"
address: 0x006C
offset: 4
unit_of_measurement: "V"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:flash
- id: raw_current_3
name: "EB1 Current L3"
address: 0x006C
offset: 5
unit_of_measurement: "A"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:power-socket
- id: raw_current_total
name: "EB1 Current Total"
address: 0x006C
offset: 6
unit_of_measurement: "A"
modbus_functioncode: "read_input_registers"
value_type: U_SINGLE
scale_factor: 0.1
accuracy_decimals: 1
icon: mdi:power-socket
### |
Beta Was this translation helpful? Give feedback.
-
|
nice |
Beta Was this translation helpful? Give feedback.
-
|
Do you have queue? Or some congestion control? I can only send one command per second to my meter. Between sends at least 1s is mandatory |
Beta Was this translation helpful? Give feedback.
-
|
UDOUBLE [17:53:46][D][ModbusComponent:031]: Modbus data 32 |
Beta Was this translation helpful? Give feedback.
-
|
Needs to be sequencial in yaml Added unused too |
Beta Was this translation helpful? Give feedback.
-
|
Still have an error |
Beta Was this translation helpful? Give feedback.
-
###
- id: raw_power_1
name: "EB1 Power L1"
address: 0x0073
offset: 0
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_1_export
name: "EB1 Power L1 Export"
address: 0x0073
offset: 1
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_2
name: "EB1 Power L2"
address: 0x0073
offset: 2
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_2_export
name: "EB1 Power L2 Export"
address: 0x0073
offset: 3
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_3
name: "EB1 Power L3"
address: 0x0073
offset: 4
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_3_export
name: "EB1 Power L3 Export"
address: 0x0073
offset: 5
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
- id: raw_power_total
name: "EB1 Power Total"
address: 0x0073
offset: 6
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug
### |
Beta Was this translation helpful? Give feedback.
-
|
Add a delay, is requesting too fast. You cannot use delay(); Some function based on milis(); |
Beta Was this translation helpful? Give feedback.
-
|
try if if adding delay(100) ; just before the return helps |
Beta Was this translation helpful? Give feedback.
-
|
Dont fix error 32 > 16 @@ -19,6 +19,9 @@ void ModbusComponent::setup() { this->create_register_ranges(); }
bool ModbusComponent::send_next_command_() {
if (!command_queue_.empty()) {
auto &command = command_queue_.front();
delay(500); //
delay(500); // will fail lint
delay(500); //
command->send();
if (!command->on_data_func) // No handler remove from queue directly after sending
command_queue_.pop(); |
Beta Was this translation helpful? Give feedback.
-
|
It count hex values? |
Beta Was this translation helpful? Give feedback.
-
|
Id fc size 00 00 00 00 crc crc DOUBLE? Id fc size 00 00 crc crc SINGLE? |
Beta Was this translation helpful? Give feedback.
-
|
Using U_SINGLE Edit: it's correct |
Beta Was this translation helpful? Give feedback.
-
|
Can you set logging to VERBOSE it will then show the bytes received from modbus |
Beta Was this translation helpful? Give feedback.
-
|
for testing you can also comment out the check at |
Beta Was this translation helpful? Give feedback.
-
- id: raw_power_1
name: "EB1 Power L1"
address: 0x0073
offset: 0
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_DOUBLE
scale_factor: 1
accuracy_decimals: 1
icon: mdi:power-plug |
Beta Was this translation helpful? Give feedback.
-
|
Easy to see |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Here I suppose you won't get help from glmnet which is very valuable. Btw: I'm not esphome expert but your code seems nice to me. And the approach is quite similar to my first attempt :-). I'd suggest you to switch back to original discussion and kick in your pull request. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks that is the idea once the issues are sorted @nikito7 trying commenting out the check here Not sure why 128 bits instead of 64 are returned but the check is not really required |
Beta Was this translation helpful? Give feedback.
-
|
Check this #12 |
Beta Was this translation helpful? Give feedback.
-
sensor_entry = sensor.SENSOR_SCHEMA.extend(
{
cv.Optional(CONF_MODBUS_FUNCTIONCODE): cv.enum(MODBUS_FUNCTION_CODE),
cv.Optional(CONF_ADDRESS): cv.int_,
cv.Optional(CONF_OFFSET): cv.int_,
cv.Optional(CONF_BITMASK, default=0xFFFF): cv.int_,
cv.Optional(CONF_VALUE_TYPE): cv.enum(SENSOR_VALUE_TYPE),
cv.Optional(CONF_SCALE_FACTOR): cv.float_,
}
)You don't really need offset and scale_factor: they are already provided by offset and multiply filters |
Beta Was this translation helpful? Give feedback.
-
|
This offset is an index |
Beta Was this translation helpful? Give feedback.
-
|
I see, but why not instead of ? |
Beta Was this translation helpful? Give feedback.
-
|
He have a register scanner / counter for sequencial registers You need a index or a group of sensors |
Beta Was this translation helpful? Give feedback.
-
|
Check this config: https://github.com/nikito7/edp_box_han_modbus/blob/dev/esphome/cfg-activepower.yaml Just one modbus request is done |
Beta Was this translation helpful? Give feedback.
-
command_throttle: time in ms between sending modbus commands
epever: A 32 bit value like pv input value is returned inb 2 registers EBL Box: A 32 bit value like pv input value is returned in 2 registers
|
Beta Was this translation helpful? Give feedback.
-
|
I think I know why 8 bytes instead of 4 bytes were returned . |
Beta Was this translation helpful? Give feedback.
-
|
Error command_trottle at most 255 |
Beta Was this translation helpful? Give feedback.
-
|
Send command in loop error |
Beta Was this translation helpful? Give feedback.
-
|
just added an attempt to fix the throttle errors |
Beta Was this translation helpful? Give feedback.
-
|
Dont use 'delay' as variable name Now I checking U_LONG |
Beta Was this translation helpful? Give feedback.
-
Compiling .pioenvs\tulipas5esp\src\main.cpp.o
In file included from src\esphome\components\modbus_component\modbuscomponent.cpp:1:0:
src\esphome\components\modbus_component\modbuscomponent.h: In member function 'void esphome::modbus_component::ModbusComponent::set_command_throttle(uint16_t)':
src\esphome\components\modbus_component\modbuscomponent.h:241:53: error: 'ESP_LOGE' was not declared in this scope
ESP_LOGE("MMMM","Throttle = %d",command_throttle);
^
*** [.pioenvs\tulipas5esp\src\esphome\components\modbus_component\modbuscomponent.cpp.o] Error 1
===================== [FAILED] Took 7.00 seconds ===================== |
Beta Was this translation helpful? Give feedback.
-
|
Raw bytes are OK. In tasmota we have: uu - single byte But is somewhat regex stuff Second NOT Second register start at half of first |
Beta Was this translation helpful? Give feedback.
-
|
Or weird stuff like bit strings |
Beta Was this translation helpful? Give feedback.
-
|
yes I know but in esphome a sensor can only publish floating point numbers . Therefore a hex string isn't an option . |
Beta Was this translation helpful? Give feedback.
-
|
Also about the offset. It was easy when I coded for my device only :) |
Beta Was this translation helpful? Give feedback.
-
|
Parsing ok [19:52:24][V][ModbusComponent:132]: Range : 73 Size: 3 (4)
[19:52:24][D][ModbusComponent:025]: Sending next modbus command 18458 1500
[19:52:24][V][ModbusComponent:365]: Command sent 4 0x73 3
[19:52:24][D][ModbusComponent:138]: Modbus update complete
[19:52:24][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[19:52:24][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[19:52:24][V][modbus:046]: Modbus recieved Byte 12 (0Xc)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 114 (0X72)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[19:52:24][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[19:52:24][V][modbus:046]: Modbus recieved Byte 39 (0X27)
[19:52:24][V][modbus:046]: Modbus recieved Byte 168 (0Xa8)
[19:52:24][V][modbus:046]: Modbus recieved Byte 159 (0X9f)
[19:52:24][D][ModbusComponent:037]: Modbus data 12
[19:52:24][D][ModbusComponent:082]: data for register address : 0x73 :
[19:52:24][V][sensor:013]: 'EB1 Active Power L1 Import': Received new state 114.000000
[19:52:24][D][sensor:099]: 'EB1 Active Power L1 Import': Sending state 114.00000 W with 0 decimals of accuracy
[19:52:24][D][ModbusComponent:100]: Sensor : EB1 Active Power L1 Import = 114.00
[19:52:24][V][sensor:013]: 'EB1 Active Power L1 Export': Received new state 0.000000
[19:52:24][D][sensor:099]: 'EB1 Active Power L1 Export': Sending state 0.00000 W with 0 decimals of accuracy
[19:52:24][D][ModbusComponent:100]: Sensor : EB1 Active Power L1 Export = 0.00 - id: Active_Power_L1_Import
name: "EB1 Active Power L1 Import"
address: 0x0073
offset: 0
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_LONG
accuracy_decimals: 0
- id: Active_Power_L1_Export
name: "EB1 Active Power L1 Export"
address: 0x0073
offset: 2
unit_of_measurement: "W"
modbus_functioncode: "read_input_registers"
value_type: U_LONG
accuracy_decimals: 0
|
Beta Was this translation helpful? Give feedback.
-
|
Request extra registers but it's ok [20:04:33][V][ModbusComponent:132]: Range : 73 Size: f (4)
[20:04:33][D][ModbusComponent:025]: Sending next modbus command 19987 1500
[20:04:33][V][ModbusComponent:365]: Command sent 4 0x73 15
[20:04:33][D][ModbusComponent:138]: Modbus update complete
[20:04:33][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[20:04:33][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[20:04:33][V][modbus:046]: Modbus recieved Byte 54 (0X36) |
Beta Was this translation helpful? Give feedback.
-
|
You need fix register count [02:09:45][V][ModbusComponent:365]: Command sent 4 0x73 21
[02:09:45][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[02:09:45][V][modbus:046]: Modbus recieved Byte 132 (0X84)
[02:09:45][V][modbus:046]: Modbus recieved Byte 129 (0X81)
[02:09:45][V][modbus:046]: Modbus recieved Byte 131 (0X83)
[02:09:45][V][modbus:046]: Modbus recieved Byte 96 (0X60)
[02:09:45][W][modbus:096]: Modbus error function code: 0x84 exception: 129
[02:09:45][E][ModbusComponent:063]: Modbus error function code: 0x4 exception: 129
[02:09:45][W][ModbusComponent:072]: last command: expected response size=42 function code=0x4 register adddress = 0x73 registers count=21 payload size=0 |
Beta Was this translation helpful? Give feedback.
-
|
The problem it's in request - id: Active_Power_L1
name: "EB1 Active Power L1"
address: 0x0073
offset: 0
modbus_functioncode: "read_input_registers"
value_type: U_DWORD
accuracy_decimals: 0
device_class: power
unit_of_measurement: "W"[14:12:33][V][ModbusComponent:145]: Register:: 0x73 1 0 0x730000ffffffff (1) buffer_offset = 0 (0x0)
[14:12:33][V][ModbusComponent:121]: Range : 73 Size: 2 (4)
[14:12:33][D][ModbusComponent:127]: Modbus update complete
[14:12:33][D][ModbusComponent:023]: Sending next modbus command 9979 1000
[14:12:33][V][ModbusComponent:499]: Command sent 4 0x73 2
[14:12:33][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[14:12:33][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[14:12:33][V][modbus:046]: Modbus recieved Byte 8 (0X8)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 58 (0X3a)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[14:12:33][V][modbus:046]: Modbus recieved Byte 252 (0Xfc)
[14:12:33][V][modbus:046]: Modbus recieved Byte 8 (0X8)
[14:12:33][D][ModbusComponent:038]: Modbus data 8
[14:12:33][D][ModbusComponent:083]: data for register address : 0x73 :
[14:12:33][V][sensor:013]: 'EB1 Active Power L1': Received new state 58.000000
[14:12:33][D][sensor:099]: 'EB1 Active Power L1': Sending state 58.00000 W with 0 decimals of accuracy
[14:12:33][D][ModbusComponent:101]: Sensor : EB1 Active Power L1 = 58.00
[14:12:33][V][sensor:013]: 'T5 ESP Signal': Received new state -70.000000
[14:12:33][D][sensor:099]: 'T5 ESP Signal': Sending state -70.00000 dB with 0 decimals of accuracy |
Beta Was this translation helpful? Give feedback.
-
|
try again please - should be fixed now |
Beta Was this translation helpful? Give feedback.
-
|
Request is ok. Parsing with 1 register ok. [15:44:59][V][ModbusComponent:146]: Register:: 0x73 1 0 0x730000ffffffff (0) buffer_offset = 0 (0x0)
[15:44:59][V][ModbusComponent:146]: Register:: 0x73 1 4 0x730004ffffffff (1) buffer_offset = 2 (0x2)
[15:44:59][V][ModbusComponent:121]: Range : 73 Size: 2 (4)
[15:44:59][D][ModbusComponent:127]: Modbus update complete
[15:44:59][D][ModbusComponent:023]: Sending next modbus command 9975 1000
[15:44:59][V][ModbusComponent:492]: Command sent 4 0x73 2
[15:44:59][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[15:45:00][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[15:45:00][V][modbus:046]: Modbus recieved Byte 8 (0X8)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 94 (0X5e)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:45:00][V][modbus:046]: Modbus recieved Byte 141 (0X8d)
[15:45:00][V][modbus:046]: Modbus recieved Byte 192 (0Xc0)
[15:45:00][D][ModbusComponent:038]: Modbus data 8
[15:45:00][D][ModbusComponent:083]: data for register address : 0x73 :
[15:45:00][D][ModbusComponent:101]: Sensor : EB1 Active Power L1 = 0.00
[15:45:00][D][ModbusComponent:101]: Sensor : EB1 Active Power L1 Export = 0.00
[15:45:01][V][sensor:013]: 'T5 ESP Uptime': Received new state 205.117996
[15:45:01][D][sensor:099]: 'T5 ESP Uptime': Sending state 0.05698 h with 1 decimals of accuracy name: "EB1 Active Power L1"
address: 0x0073
offset: 0
modbus_functioncode: "read_input_registers"
value_type: U_WORD
accuracy_decimals: 0
device_class: power
unit_of_measurement: "W"
- id: Active_Power_L1_Export
name: "EB1 Active Power L1 Export"
address: 0x0073
offset: 4
modbus_functioncode: "read_input_registers"
value_type: U_WORD
accuracy_decimals: 0
device_class: power
unit_of_measurement: "W" |
Beta Was this translation helpful? Give feedback.
-
|
Correction: parsing is not working at all [15:49:42][V][ModbusComponent:146]: Register:: 0x73 1 0 0x730000ffffffff (0) buffer_offset = 0 (0x0)
[15:49:42][V][ModbusComponent:121]: Range : 73 Size: 1 (4)
[15:49:42][D][ModbusComponent:127]: Modbus update complete
[15:49:42][D][ModbusComponent:023]: Sending next modbus command 9979 1000
[15:49:42][V][ModbusComponent:492]: Command sent 4 0x73 1
[15:49:42][V][modbus:046]: Modbus recieved Byte 1 (0X1)
[15:49:42][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[15:49:42][V][modbus:046]: Modbus recieved Byte 4 (0X4)
[15:49:42][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:49:42][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:49:42][V][modbus:046]: Modbus recieved Byte 0 (0X0)
[15:49:42][V][modbus:046]: Modbus recieved Byte 183 (0Xb7)
[15:49:42][V][modbus:046]: Modbus recieved Byte 187 (0Xbb)
[15:49:42][V][modbus:046]: Modbus recieved Byte 242 (0Xf2)
[15:49:42][D][ModbusComponent:038]: Modbus data 4
[15:49:42][D][ModbusComponent:083]: data for register address : 0x73 :
[15:49:42][D][ModbusComponent:101]: Sensor : EB1 Active Power L1 = 0.00 |
Beta Was this translation helpful? Give feedback.
-
|
value_type must be U_DWORD |
Beta Was this translation helpful? Give feedback.
-
|
Hi As I read the documentation for the meter, all 3 above are INT32 with LSW->MSW. All setting in the meter are default. Output is (where only first one are in a valid range: I tried various addresses, offsets and value_types, but no luck. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. sorry for late reply. modbus: modbus_controller:
sensor:
|
Beta Was this translation helpful? Give feedback.
-
|
Please add external_components:
- source:
type: git
url: https://github.com/esphome/esphome
ref: dev
components: [ modbus, modbus_controller ] |
Beta Was this translation helpful? Give feedback.
-
|
Already did. I use the full sample you provided in the wiki. |
Beta Was this translation helpful? Give feedback.
-
|
That is strange - maybe a caching issue because the error message indicate that the external components are not up to date. |
Beta Was this translation helpful? Give feedback.
-
|
Clearing the cache made me able to compile and upload. Now it fails in retrieving: |
Beta Was this translation helpful? Give feedback.
-
|
I'm away this week and will try to answer next week.
|
Beta Was this translation helpful? Give feedback.
-
|
I think my problem is with modbus Converter without Automatic Flow Control, EM340 has default settings and address is 1. I ordered from Amazon the same noname Converter ....
Config: external_components:
uart: modbus_controller:
" |
Beta Was this translation helpful? Give feedback.
-
|
I have the same modbus Converter and it´s work for me. |
Beta Was this translation helpful? Give feedback.
-
How would I set the following?
I have When I watch the log viewer I'm not getting any data back from the device. I'm using a ESP32 dev board and I have tried setting the UART to different TX/RX pins, but still can't get any data. Wiring:
Config:external_components:
### https://github.com/martgras/esphome/tree/modbus_component/esphome/components/modbus_controller
- source:
type: git
url: https://github.com/martgras/esphome
ref: modbus_component
components: [ modbus_controller ]
uart:
id: solark_uart
tx_pin: 16
rx_pin: 17
baud_rate: 9600
parity: none
data_bits: 8
stop_bits: 1
# RTU Settings: Baud rate: 9600bps, Parity: None, Data Bits: 8, Stop Bits: 1
modbus_controller:
uart_id: solark_uart
command_throttle: 1s
id: solark
address: 0x01
update_interval: 30s
sensor:
- platform: modbus_controller
modbus_controller_id: solark
name: "SolArk Battery Voltage"
address: 0xB7 #0x3000 183 #
offset: 0
unit_of_measurement: "V"
modbus_functioncode: "read_input_registers"
value_type: U_WORD
accuracy_decimals: 2
filters:
- multiply: 0.01 |
Beta Was this translation helpful? Give feedback.
-
|
The Uart settings are defined here: https://esphome.io/components/uart.html |
Beta Was this translation helpful? Give feedback.
-
So it looks like I have the basic standard setting of 8N1.
I quoted in the text from the manual, but I wasnt super clear about it.
No, and I'm wondering if that's normal.
Yes, double-checked but still not seeing lights. |
Beta Was this translation helpful? Give feedback.
-
|
The tx diode should flash, even without a device connected, so make sure the pin settings are correct between your ESP and the converter board. |
Beta Was this translation helpful? Give feedback.
-
|
Having this as a electricity meter: but I'd like to move it to ESP out of my PC. As all of those values are ints (and I want to only read values without writing anything), I guess best would be to have it as type U_WORD. |
Beta Was this translation helpful? Give feedback.
-
|
you've used mbpoll to confirm you can read modbus data from your device via your pc |
Beta Was this translation helpful? Give feedback.
-
|
@poldim I have (as you can see on image) whole table describing those values, I know I can read them. |
Beta Was this translation helpful? Give feedback.
-
|
The address you use is just a number (it doesnt have to be hex format) but you have to offset 1 digit. There are more examples in the readme here. Here's a regular setup for my modbus meter with HA (not this ESPHome component) but it should give you some basic reference: modbus:
- name: "pm8210"
type: tcp
host: 10.30.30.30
port: 502
sensors:
- name: Current A
unit_of_measurement: A
device_class: current
slave: 1
address: 2999
count: 2
precision: 2
input_type: holding
data_type: float
scan_interval: 10
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply, but still there's small shade of not understanding left. And I can see address 2999 referenced to 3000 in documentation, so I guess offset here was '1'? |
Beta Was this translation helpful? Give feedback.
-
|
The 2999 vs 3000 is as I understand just an offset of starting counting
from 0 vs 1.
But don't confuse that with the offset option. That's defined in the docs
here:
https://github.com/martgras/esphome/tree/modbus_component/esphome/components/modbus_controller#format.
You should always read up on value_type
…On Mon, Sep 6, 2021 at 10:09 AM Andrzej ***@***.***> wrote:
Thanks for the reply, but still there's small shade of not understanding
left.
As the example - the value is float, so it's "longer" in bytes than int
[take more bytes] it has to be offset.
But if my energy meter only has int's, then do I need to offset more than
1?
And I can see address 2999 referenced to 3000 in documentation, so I guess
offset here was '1'?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEAWSUNJQTE3FCYKADHKWP3UARSLNANCNFSM4ZCEHTHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Right, so basically having: as it's one register. |
Beta Was this translation helpful? Give feedback.
-
|
Please have a look at the testing tree https://github.com/martgras/esphome/blob/testing/esphome/components/modbus_controller/readme.md this should work - platform: modbus_controller
modbus_controller_id: epever
id: voltage1
address: 0x1
name: "Voltage 1"
modbus_functioncode: read_holding_registers
value_type: U_WORD
filters:
- multiply: 0.01
- platform: modbus_controller
modbus_controller_id: epever
id: voltage2
address: 0x2
name: "Voltage 2"
modbus_functioncode: read_holding_registers
value_type: U_WORD
filters:
- multiply: 0.01 |
Beta Was this translation helpful? Give feedback.
-
|
Today I finally had an oppoturnity to have hands on yaml and electricity meter by myself. RX/TX leds are blinking, even indicator on electricity meter that transmission is ongoing too, but no data is being read.
There are two things that makes me wonder: 2nd. It makes rx/tx and indicator blink every like 200ms. -- EDIT; |
Beta Was this translation helpful? Give feedback.
-
|
So it sees that some data is coming back otherwise you won't see CRC errors at all. |
Beta Was this translation helpful? Give feedback.
-
|
I've been trying some more at night but with no success. |
Beta Was this translation helpful? Give feedback.
-
|
Promoting the testing tree with a breaking change :) breaking changesI am going to archive this fork and not update it anymore.
external_components:
# use GitHub
- source:
type: git
url: https://github.com/martgras/esphome
ref: testing
components: [modbus, modbus_controller]
Other changes in the testing tree
See the readme in testing for more details about the new features |
Beta Was this translation helpful? Give feedback.
-
|
So basically, when I prepare code right now with external_components you've mentioned and it will be sooner or later part of esphome main repo, I won't need any more changes except removing external_components declaration? :) |
Beta Was this translation helpful? Give feedback.
-
|
Yes that is the plan - there were code reviews but since then there wasn't more activity. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also trying to improve the docs but not really my favorite job. https://webtestesphome.z1.web.core.windows.net/components/modbus_controller.html brings you directly to the controller Feel free to add to it or correct my typos and other errors :) |
Beta Was this translation helpful? Give feedback.
-
|
FYI.
I suspect it is related to esphome/aioesphomeapi#87 See also esphome/issues#2427 |
Beta Was this translation helpful? Give feedback.
-
|
The modbus_controller component is now part of esphome. esphome#1779 has been merged. Thanks for all your input - without it the component would lack a lot of features. Your feedback encouraged me to keep improving. |
Beta Was this translation helpful? Give feedback.
-
|
Congratulations. It was a long and hard way for you ;-) . Here is the updated YAML File for the Heidelberg Wallbox. |
Beta Was this translation helpful? Give feedback.
-
|
While the wiki is nice I was playing with esphome packages to make configuration easier @derwolff - the maximum "skip_updates" value is 255 (this is the reason why you get a warning for the pcb_temp sensor). I replaced 2 of your sensors with numbers for read/write access - does that work for you? But back to packages - using the config below pulls all sensors from a github repository. external_components:
- source:
type: git
url: https://github.com/esphome/esphome
ref: dev
components: [modbus, modbus_controller]
substitutions:
devicename: heidelberg-wb-example
modbus_controller_name: heidelberg_wb
esphome:
name: $devicename
platform: ESP8266
board: nodemcuv2
wifi:
ssid: "any123"
password: "veryverysecret"
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "${devicename}"
password: "veryverysecret"
# Enable Home Assistant API
api:
reboot_timeout: 60min #Reboot when no connection
uart:
id: uart_${modbus_controller_name}
tx_pin: 5
rx_pin: 2
modbus:
id: mod_bus_${modbus_controller_name}
flow_control_pin: 4
send_wait_time: 200ms
modbus_controller:
id: ${modbus_controller_name}
address: 0x1
modbus_id: mod_bus_${modbus_controller_name}
command_throttle: 200ms
setup_priority: -10
update_interval: 60s
packages:
#wallbox: !include packages/heidelberg_wb.yaml
wallbox: github://martgras/esphome-modbus/packages/heidelberg_wb.yaml@main
sensor:
- platform: wifi_signal
name: "WiFi Signal ${devicename}"
update_interval: 300s
binary_sensor:
- platform: homeassistant
entity_id: input_boolean.wb_remote_lock
id: wb_remote_lock
internal: true
on_state:
then:
- lambda: |-
uint16_t payload = 1;
if ( id(wb_remote_lock).state == true ) {
payload = 0;
}
ESP_LOGI("main", "set remote lock %d", payload);
esphome::modbus_controller::ModbusCommandItem set_payload_command = esphome::modbus_controller::ModbusCommandItem::create_write_single_command(${modbus_controller_name}, 0x0103, payload);
${modbus_controller_name}->queue_command(set_payload_command);
- platform: homeassistant
entity_id: input_boolean.wb_standby_control
id: wb_standby_control
internal: true
on_state:
then:
- lambda: |-
uint16_t payload = 4;
if ( id(wb_standby_control).state == true ) {
payload = 0;
}
ESP_LOGI("main", "set standby control %d", payload);
esphome::modbus_controller::ModbusCommandItem set_payload_command = esphome::modbus_controller::ModbusCommandItem::create_write_single_command(${modbus_controller_name}, 0x0102, payload);
${modbus_controller_name}->queue_command(set_payload_command);
Maybe that would be a nice way to build a repository of modbus devices Comments? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delay. |
Beta Was this translation helpful? Give feedback.
-
|
Hey I just enabled the wiki feature. |
Beta Was this translation helpful? Give feedback.
-
|
Tricky to troubleshoot without the device 🙂
Can you remove a couple of registers. Maybe I made a mistake when I converted the yaml you provided
May start a test with only the first register defined in YAML.
|
Beta Was this translation helpful? Give feedback.
-
|
Guess that's for me.. Also, when it work, I read 30 registers, but it only returns 27 values. So it seems I hit the limit. There was no issues in the old implementation. |
Beta Was this translation helpful? Give feedback.
-
|
You add `force_new_range: true` to one of the sensor in the middle.
That will result in a new request starting at that request.
I guess your assumption is correct that there is a limit somewhere
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Martin,
https://paste.kr33.de/?a7a3f2f3d8a20e6d#4hrL7K4KTzD8MBb6RMzUMnBuSeuEiNXmKdfpB7gGVEU7 |
Beta Was this translation helpful? Give feedback.
-
|
Nice - I tend to consider it as a bug of your froehling device but the change doesn't harm and avoids messing up the send queue. |
Beta Was this translation helpful? Give feedback.
-
looks like this might be the case... will try to debug with my laptop directly attached once I find the time.
same thing will try to debug this one once I find the time and hook my laptop up to the serial port of the esp.
I'm not using force_newrange or do you mean force_update which I need for my grafana graphs to be displayed correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Nope I meant force_new_range |
Beta Was this translation helpful? Give feedback.
-
|
The fix is merged into esphome and included in beta 8 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info, already saw that and updated this morning, works like a charm :) |
Beta Was this translation helpful? Give feedback.
-
|
Die deutsche Doku ist schon ok auch wenn ich aus Bayern komme 🙂
Switching back to English for anyone else following.
I'll have a look at it tomorrow.
<http://www.9folders.com/>
|
Beta Was this translation helpful? Give feedback.
-
|
Ha alles klar :) Have a nice Sunday and no hurry! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
To get started, comment below with an introduction of yourself and tell us about what you do with this community.
Beta Was this translation helpful? Give feedback.
All reactions