Looking for anyone willing to help me trouble shoot rewriting my Modbus configuration YMAL file transitioning from 2023.9.3 to 2023.11.3. There is apparently an underling component code change that broke the old config file formatting. Trying to re write a simple test from scratch using the current help page is not working.
Modbus - Home Assistant (home-assistant.io)
Using a 3rd party Modbus application, I can see the device is responding if the correct poll is sent. From the debug logs it looks like a different poll is send in 2023.11.3 . Worked in 2023.9.3 and if a restore back to that version. Hope if I waited till 2023.11.3 issue would have been fixed. Reached out to code owner via git hub but issue was closed as a configuration file issue.
Error log 2023.11.3:
[pymodbus.logging] SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x1 0x0 0x1 0x0 0x1
Expected to see:
Poll: 01 04 00 00 00 02
to read addresses 300001 and 300002
running on a yellow.
debug run with custom components disabled.
- Core2023.11.3
- Supervisor2023.11.3
- Operating System11.1
- Frontend20231030.2
old config:
# modbus:
- name: StrideGateway
delay: 5
timeout: 5
host: 192.168.168.xx
type: tcp
port: 502
# Stride Gateway and APM power meter functions
sensors:
- name: APM_Frequancy
slave: 1
address: 1
input_type: input
unit_of_measurement: Hz
state_class: measurement
count: 2
scale: 1
offset: 0
precision: 2
data_type: float32
device_class: frequency'''
new config:
modbus: !include modbus.ymal
# modbus:
- name: StrideGateway
type: tcp
host: 192.168.168.99
port: 502
delay: 5
message_wait_milliseconds: 30
retries: 3
timeout: 5
# Stride Gateway and APM power meter functions
sensors:
- name: APM_Frequancy
slave: 1
address: 1
input_type: input
unit_of_measurement: Hz
state_class: measurement
scale: 1
offset: 0
precision: 2
data_type: float32
device_class: frequency