Open mwolter805 opened 1 year ago
Left log viewer open for a longer duration and noticed several of the following entries.
E (30884) esp.emac: emac_esp32_transmit(229): insufficient TX buffer size
Noticed the following entry in the change logs for 2022.12.0
Because these core upgrade have aligned the version of ESP-IDF under the hood, ethernet is now able to be used when specifying ESP-IDF as your framework of choice.
This led to attempting to change the sketch to esp-idf and it appeared to resolve the issues.
Notable Changes:
Below is the full config
# substitutions:
# name: matts-esp32
# friendly_name: Matts ESP32
# ip_address: 10.10.21.13
# pzem_1: HVAC
# pzem_2: TV_Equip
# pzem_3: Nightstand
esphome:
name: matts-esp32
# name: ${name}
esp32:
board: wemos_d1_mini32
# board: mhetesp32devkit # this is what's listed in Quin's sketch https://quinled.info/quinled-an-penta-diy-esphome-example-configuration/
framework:
type: esp-idf
ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk_mode: GPIO17_OUT
phy_addr: 0
power_pin: GPIO5
use_address: 10.10.21.13
# use_address: ${ip_address}
mdns:
disabled: true
api:
password: !secret api_password
reboot_timeout: 0s
ota:
password: !secret ota_password
logger:
baud_rate: 0 # Disable UART logging
level: warn # normal level for logger
# level: debug # only use this level when debugging an issue
# level: VERY_VERBOSE # only use this level if debug is not producing enough info to debug an issue
# logs:
# hx711: ERROR
## web_server is not compatible with esp-idf as of v2022.12.7
# web_server:
# port: 80
uart:
# PZEM UART Bus
id: ubus
rx_pin: 15
tx_pin: 13
baud_rate: 9600
stop_bits: 2 # not sure if this should be 1 or 2
modbus:
# PZEM Modbus
uart_id: ubus
id: mbus
switch:
# Switch Virtual Restart
- platform: restart
name: "Matts ESP32 ESP Restart"
# name: "${friendly_name} ESP Restart"
id: restart_switch
# Reset Energy for pzem_1
- platform: uart
uart_id: ubus
id: reset_HVAC
# id: reset_$pzem_1
name: "Matts ESP32 HVAC Energy Reset"
# name: "${friendly_name} ${pzem_1} Energy Reset"
data: [0x02, 0x42, 0x80, 0xE1]
entity_category: config
# Reset Energy for pzem_2
- platform: uart
uart_id: ubus
id: reset_TV_Equip
# id: reset_$pzem_2
name: "Matts ESP32 TV_Equip Energy Reset"
# name: "${friendly_name} ${pzem_2} Energy Reset"
data: [0x03, 0x42, 0x81, 0x71]
entity_category: config
# Reset Energy for pzem_3
- platform: uart
uart_id: ubus
id: reset_Nightstand
# id: reset_$pzem_3
name: "Matts ESP32 Nightstand Energy Reset"
# name: "${friendly_name} ${pzem_3} Energy Reset"
data: [0x04, 0x42, 0x83, 0x41]
entity_category: config
sensor:
# Uptime Sensor
- platform: uptime
name: "Matts ESP32 ESP Uptime"
# name: "${friendly_name} ESP Uptime"
# PZEM 1
- platform: pzemac
modbus_id: mbus
address: 2
energy:
name: "Matts ESP32 HVAC Energy"
# name: "${friendly_name} ${pzem_1} Energy"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kWh
power:
name: "Matts ESP32 HVAC Power"
# name: "${friendly_name} ${pzem_1} Power"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kW
# current:
# name: "${friendly_name} ${pzem_1} Current"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
# voltage:
# name: "${friendly_name} ${pzem_1} Voltage"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# frequency:
# name: "${friendly_name} ${pzem_1} Frequency"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# power_factor:
# name: "${friendly_name} ${pzem_1} Factor"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
update_interval: 10s
# PZEM 2
- platform: pzemac
modbus_id: mbus
address: 3
energy:
name: "Matts ESP32 TV_Equip Energy"
# name: "${friendly_name} ${pzem_2} Energy"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kWh
power:
name: "Matts ESP32 TV_Equip Power"
# name: "${friendly_name} ${pzem_2} Power"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kW
# current:
# name: "${friendly_name} ${pzem_2} Current"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
# voltage:
# name: "${friendly_name} ${pzem_2} Voltage"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# frequency:
# name: "${friendly_name} ${pzem_2} Frequency"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# power_factor:
# name: "${friendly_name} ${pzem_2} Factor"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
update_interval: 10s
# PZEM 3
- platform: pzemac
modbus_id: mbus
address: 4
energy:
name: "Matts ESP32 Nightstand Energy"
# name: "${friendly_name} ${pzem_3} Energy"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kWh
power:
name: "Matts ESP32 Nightstand Power"
# name: "${friendly_name} ${pzem_3} Power"
filters:
- multiply: 0.001
- or:
- throttle: 1min
- delta: .01
accuracy_decimals: 3
unit_of_measurement: kW
# current:
# name: "${friendly_name} ${pzem_3} Current"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
# voltage:
# name: "${friendly_name} ${pzem_3} Voltage"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# frequency:
# name: "${friendly_name} ${pzem_3} Frequency"
# filters:
# - or:
# - throttle: 1min
# - delta: .1
# power_factor:
# name: "${friendly_name} ${pzem_3} Factor"
# filters:
# - or:
# - throttle: 1min
# - delta: .01
update_interval: 10s
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
Upgraded from 2022.9.1 to 2022.12.6 and can no longer connect to my QuinLED-ESP32-ABE board via ethernet. Reverting to 2022.9.1 does not resolve the issue.
Edit: Also tried flashing the same code to a new QuinLED-ESP32-ABE with the same results.
Which version of ESPHome has the issue?
2022.12.6
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
2023.1.5
What platform are you using?
ESP32
Board
QuinLED-ESP32-ABE
Component causing the issue
ethernet or part
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response