M5 stack bluetooth proxy stopped working after recent upgrade

ESPHome
1

Hi, I have a M5 stack configured as a bluetooth proxy and it has been working for a few months reporting on a Seplos BMS and some active balancers in my garage. It has now stopped working after a home assistant upgrade. I have erased and rebuilt the bluetooth proxy and it seems to be online but I get the error message below. Can anyone help me move forward?

INFO Starting log output from 192.168.0.48 using esphome API
INFO Successfully resolved esp32-bluetooth-proxy-55417c @ 192.168.0.48 in 0.000s
WARNING Can’t connect to ESPHome API for esp32-bluetooth-proxy-55417c @ 192.168.0.48: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address=‘192.168.0.48’, port=6053))]: [Errno 113] Connect call failed (‘192.168.0.48’, 6053) (SocketAPIError)
INFO Trying to connect to esp32-bluetooth-proxy-55417c @ 192.168.0.48 in the background

2

The log message (from HA) indicates HA can’t talk to the device.

You need to get the log from the device directly (I usually connect them directly to a PC and use a terminal emulator to do this).

Use the code tags on the log content so it displays correctly.

I suspect the IP address has changed and it is no longer what HA thinks it is.

3

Allocating static ip addresses on your router dhcp configuration page so the expected ip address your software is looking for is consistently found will probably resolve your problem long term.

A full power off and on after you have saved the router configuration, followed by a power off and on of all other associated equipment is recommended so the changes can be picked up by the entire network.
If you still have problems, at least you can narrow them down easier.

Did the recent ESPHome BLE changes mentioned in the changelog get applied to your yaml code?

[Please use the forum </> attributes when you post your yaml code, compile log, and debug run outputs for forum readability]

4

Thanks both - there appears to have been a wifi problem on the access point that was supplying wifi to the garage area. A reboot of the access point and all is now working again.