Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
KC868-M16v2 configure yaml for ESPhome
#54
the log returns this:


"INFO ESPHome 2025.3.3 INFO Reading configuration /config/esphome/m16.yaml... INFO Updating https://github.com/hzkincony/esphome-zmpt101b@None WARNING GPIO5 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-a...pping-pins WARNING `attenuation: 11db` is deprecated, use `attenuation: 12db` instead INFO Detected timezone 'Europe/Rome' INFO Starting log output from m16.local using esphome API WARNING Can't connect to ESPHome API for m16.local: Timeout while resolving IP address for ['m16.local'] (ResolveTimeoutAPIError) INFO Trying to connect to m16.local in the background"

and the new log:


"INFO ESPHome 2025.3.3 INFO Reading configuration /config/esphome/m16.yaml... WARNING GPIO5 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-a...pping-pins WARNING `attenuation: 11db` is deprecated, use `attenuation: 12db` instead INFO Detected timezone 'Europe/Rome' INFO Starting log output from 192.168.0.15 using esphome API WARNING Can't connect to ESPHome API for m16 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError) INFO Trying to connect to m16 @ 192.168.0.15 in the background"
Reply


Messages In This Thread
KC868-M16v2 configure yaml for ESPhome - by admin - 07-18-2023, 01:33 PM
RE: KC868-M16v2 configure yaml for ESPhome - by athxp - 04-07-2025, 04:26 PM

Forum Jump:


Users browsing this thread:
1 Guest(s)