Can not connect to esphome over ethernet after changes from 22 march 2023

[teklabania]

Hi, I'm using zigbee coordinator with ESP32 and Ethernet, like this one. Lately I upgraded esphome on the device, and esphome-stream-server was also upgraded. The changes from your commits from 22.03.2023 made me unable to connect to my esphome device. I could only ping it but couldn't connect to web_server on port 80 nor api on port 6053

WARNING Can't connect to ESPHome API for device-name.my.domain: Error connecting to ('192.168.1.10', 6053): [Errno 111] Connect call failed ('192.168.1.10', 6053)

This is my configuration:

substitutions:
  device_name: cc2652p01
  friendly_name: ${device_name} over LAN

esphome:
  name: ${device_name}
  comment: ${friendly_name}
  platform: ESP32
  board: esp-wrover-kit

web_server:
  port: 80

ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO0_IN
  phy_addr: 1
  power_pin: GPIO16

external_components:
  - source: github://oxan/esphome-stream-server

stream_server:
  uart_id: uart_bus

uart:
  id: uart_bus
  rx_pin: GPIO5
  tx_pin: GPIO17
  baud_rate: 115200

I forked your repository and created a tag at a commit 53a7260e0158f99f57763a7e41eb76afac309506 from 07.02.2023, then set up external_components.source pointing to my repository with reference to the tag I created and everything works perfectly:

external_components:
  - source: github://teklabania/esphome-stream-server@v0.0.1

[piotrrekkk]

Confirmed, I had same issue.

[oxan]

Crap, I messed up. Will fix tomorrow (don't have access to a PC anymore today). You can define both sensors for now to workaround it.

[teklabania]

@oxan , how about tagging your commits in the future so we could pin to the tag?

[skipfire]

@oxan I tried the update and it is still causing loading errors. API and web server do not load, and the WiFi keeps bouncing on and off.

[kluszczyn]

@oxan I tried the update and it is still causing loading errors. API and web server do not load, and the WiFi keeps bouncing on and off.

same issue here

[oxan]

@teklabania Yeah, that's not a bad idea; but I've had vanishingly little time to actually make a proper release, and I don't really want to just tag any random commit (especially if it has known issues). Also, ideally ESPHome would just allow you to pin any commit instead of just branches or tags.

@skipfire @kluszczyn Are you sure ESPHome actually downloaded the new version? By default it only checks git repositories for new versions once a ~week~day. See documentation.

[skipfire]

Yes I'm sure. I have a test unit that I removed the stream server from, then added it back after you indicated it was fixed. When I remove stream-server it comes back up but with the wifi instability I have to push it manually over USB if it has the current stream-server code on it.

[oxan]

I have a test unit that I removed the stream server from, then added it back after you indicated it was fixed.

That does not actually ensure ESPHome updates the stream server code with the latest version from GitHub. Can you try adding refresh: 0s to the external component, as explained in the docs I linked?

[skipfire]

I lost the refresh 0 along the way, it is working with the new code.

[kluszczyn]

I've purged .build folder inside esphome, recompiled, and it is working now too! Thanks!