求解求解，困扰好久了。esp8266接串口助手收发数据不一致

tomcat_zh

esp8266刷ESPHome固件做测试，仅做一个串口发数据的测试，烧写完固件后，esp8266TX和RX接USB/串口线，在电脑上打开串口助手显示接收的信息，结果固件里发送的数据和电脑串口助手接收到的数据不一致。
波特率9600和115200都做过测试，结果一样。
esphome代码如下：

esphome:
  name: uart-lcd
  platform: esp8266
  board: esp01_1m

api:

ota:
  password: ""

wifi:
  ssid: "HZGH-2G"
  password: meiyoumima

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esp8266 Fallback Hotspot"
    password: "12345678"

captive_portal:

# 禁用串口log，因为ESP8266的log可能会和uart输出冲突
logger:
  baud_rate: 0

# 启用web界面，可以通过web界面查看效果
web_server:
  port: 55555
  
uart:
  id: uart_bus
  tx_pin: GPIO13
  rx_pin: GPIO15
  baud_rate: 115200

interval:
  - interval: 10s
    then:
      - uart.write: [0xF0, 0x01, 0x00, 0x0A]

复制代码

间隔十秒发送[0xF0, 0x01, 0x00, 0x0A]
但串口助手只接收到：00 D0 FF EB

tomcat_zh

串口助手接收信息如下：

[21:01:14.423]收←◆00 D0 FF EB
[21:01:24.421]收←◆00 D0 FF EB
[21:01:34.418]收←◆00 D0 FF EB
[21:01:44.419]收←◆00 D0 FF EB
[21:01:54.418]收←◆00 D0 FF EB
[21:02:04.423]收←◆00 D0 FF EB
[21:02:14.419]收←◆00 D0 FF EB
[21:02:24.418]收←◆00 D0 FF EB
[21:02:34.419]收←◆00 D0 FF EB
[21:02:44.424]收←◆00 D0 FF EB
[21:02:54.425]收←◆00 D0 FF EB
[21:03:04.419]收←◆00 D0 FF EB
[21:03:14.424]收←◆00 D0 FF EB
[21:03:24.419]收←◆00 D0 FF EB
[21:03:34.421]收←◆00 D0 FF EB
[21:03:44.424]收←◆00 D0 FF EB
[21:03:54.423]收←◆00 D0 FF EB
[21:04:04.425]收←◆00 D0 FF EB
[21:04:14.427]收←◆00 D0 FF EB
[21:04:24.420]收←◆00 D0 FF EB
[21:04:34.423]收←◆00 D0 FF EB
[21:04:44.424]收←◆00 D0 FF EB
[21:04:54.423]收←◆00 D0 FF EB
[21:05:04.424]收←◆00 D0 FF EB
[21:05:14.423]收←◆00 D0 FF EB
[21:05:24.424]收←◆00 D0 FF EB
[21:05:34.421]收←◆00 D0 FF EB
[21:05:44.426]收←◆00 D0 FF EB
[21:05:54.423]收←◆00 D0 FF EB
[21:06:04.424]收←◆00 D0 FF EB
[21:06:14.426]收←◆00 D0 FF EB

困扰好几天了，一直无法继续进行下一步的工作，请大神们帮忙瞅瞅问题出在哪里。
注：uart的tx和rx换过GPIO01和GPIO03，结果是一样的。

xuzuxiong

是不是字符或者进值问题用串口调试工具查看楼主用的什么工具观察的呢

XCray

怀疑两边校验位停止位不一样，建议再仔细看看文档，https://esphome.io/components/uart.html
尤其是这一段：

Note
From ESPHome 2021.8 the ESP8266SoftwareSerial UART write_byte function had the parity bit fixed to be correct for the data being sent. This could cause unexpected issues if you are using the Software Serial and have devices that explicity check the parity. Most likely you will need to flip the parity flag in YAML.

tomcat_zh

感谢楼上两位，问题原因没找到，我怀疑是我字符格式转换没做好。现在不用串口了，用别的方式替代了。