esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
290 stars 36 forks source link

all adopted esphome devices went off to lunch. (changeing local domain to .local fixed the issue) #5954

Open Bram-diederik opened 4 months ago

Bram-diederik commented 4 months ago

The problem

All Mine home assistant entities (2 echos. 3 bluetooth proxys) where off line. my not adapted smartmeter did work with out any hickup. could not reconnect to home assistant. could only connect to esphome once. (sometimes)

I had a discussion with snowy on discord. and he gave a hint to the fix. I renamed my local domain from .pwap to .local and everything worked out of the box. (install echo using esphome web gui , connect to hass)

Which version of ESPHome has the issue?

2024.6.1

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2024.6.4

What platform are you using?

ESP32

Board

atom echo, M5Stack Atom Lite

Component causing the issue

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Kan geen verbinding maken met ESP. Zorg ervoor dat uw YAML-bestand een regel 'api:' bevat.  Daft_dutch — vandaag om 14:01 (base) daft@Blue-mage:~$ /sbin/arp -a | grep echo m5stack-atom-echo-241ec0.pwap (192.168.5.221) at on wlp3s0 m5stack-atom-echo-238a70.pwap (192.168.5.223) at on wlp3s0

they disaprear from the network  snowy — vandaag om 14:02 how are u running ESPHome?  Daft_dutch — vandaag om 14:02 addon  snowy — vandaag om 14:02 latest version?  Daft_dutch — vandaag om 14:03 yeah. with changed icon  snowy — vandaag om 14:03 ok in HA in the devices page for ESPHome can u sccreenshot that for me?  Daft_dutch — vandaag om 14:03 I could install the software on the echo. I could Adapt it to esp home. [14:04] this?   snowy — vandaag om 14:05 thats the ESPHome dashboard [14:05] are both these atoms plugged in atm?  Daft_dutch — vandaag om 14:05 inside ha you mean?  1  snowy — vandaag om 14:05 I see one is online and one is not  Daft_dutch — vandaag om 14:05 no. I only have a usb cable for one. atm (bewerkt)  1 [14:06]   snowy — vandaag om 14:06 ok so they have been removed from HA  Daft_dutch — vandaag om 14:07 yes sir. I cloud no longer connect to them [14:07] happens before i need to reflash them  snowy — vandaag om 14:07 sometimes what happens is your changing the name or reflashing new projects on the same board HA gets confused on which device is which [14:08] sometime u see apparaten 2 instead of one for the entries on the screenshot [14:08] can u reboot HA  Daft_dutch — vandaag om 14:08 I did.  snowy — vandaag om 14:08 ok good  Daft_dutch — vandaag om 14:09 the whole vm server to be sure.  1  snowy — vandaag om 14:09 can u paste in the config of one of the atoms?  Daft_dutch — vandaag om 14:10 substitutions: name: atom-bluetooth-proxy-b78ee0 friendly_name: Bluetooth Proxy b78ee0 packages: esphome.bluetooth-proxy: github://esphome/firmware/bluetooth-proxy/m5stack-atom-lite.yaml@main esphome: name: ${name} name_add_mac_suffix: false friendly_name: ${friendly_name} api: encryption: key: Ithinkineedtoeditthiswaway

wifi: ssid: !secret wifi_ssid password: !secret wifi_password [14:12] when i try to add the esp echo to ha it drops from the network..  snowy — vandaag om 14:12 ok i am a bit confused - how many devices do u have? because in the ESPHome dash i see 6 [14:12] ones a meter reader right?  Daft_dutch — vandaag om 14:13 Yes i have 6.  snowy — vandaag om 14:13 which devices are the problem?  Daft_dutch — vandaag om 14:13 the esp atom echos [14:13] only those  snowy — vandaag om 14:14 ok but that paste was not from the config on one of those? [14:14] in HA theres 4 devices [14:14] 3 BLE proxies and the smart reader  Daft_dutch — vandaag om 14:15 because in ha the atom echos are removed [14:15] when i tryed to re add them/  snowy — vandaag om 14:15 name: atom-bluetooth-proxy-b78ee0 [14:15] is the config u posted  Daft_dutch — vandaag om 14:15 the ble proxies seems to have trouble also :/ [14:15] Oh.  snowy — vandaag om 14:15 can i see one from the ones called M5stack -  Daft_dutch — vandaag om 14:16 substitutions: name: m5stack-atom-echo-238a70 friendly_name: M5Stack Atom Echo 238a70 packages: m5stack.atom-echo-voice-assistant: github://esphome/firmware/voice-assistant/m5stack-atom-echo.yaml@main esphome: name: ${name} name_add_mac_suffix: false friendly_name: ${friendly_name} api: encryption: key: 7GfoJ8ObjPVu3phHm5Nb3xERIE=

wifi: ssid: !secret wifi_ssid password: !secret wifi_password  snowy — vandaag om 14:16 so u are using the voice assistant ready made project for them  Daft_dutch — vandaag om 14:17 yes.  snowy — vandaag om 14:17 ok make backups of the yaml to a notepad  Daft_dutch — vandaag om 14:17 the bluetooth proxies are offline also. NO online entities  snowy — vandaag om 14:18 i wanna change the api key manually then try to re add manually in HA [14:18] u know how to add a new ESPHome in HA?  Daft_dutch — vandaag om 14:18 cut past the url right. [14:18] ip hostname  snowy — vandaag om 14:19 yeah Add new in the devices page [14:19] so change a couple of characters in the api key and try that  Daft_dutch — vandaag om 14:19 when i try that the wifi drops of the esp device  snowy — vandaag om 14:20 ok so u have one plugged in atm?  Daft_dutch — vandaag om 14:20 yes  snowy — vandaag om 14:20 ones online in ESPHome dash [14:20] what happens if u look at the logs? [14:21] is the wifi block in the secrets 100%  Daft_dutch — vandaag om 14:22 oh i lost ip connection since last try. [14:22] trying the re plug it  snowy — vandaag om 14:22 can u ping it?  Daft_dutch — vandaag om 14:23 INFO ESPHome 2024.6.1 INFO Reading configuration /config/esphome/m5stack-atom-echo-238a70.yaml... INFO Updating https://github.com/esphome/esphome.git@pull/5230/head INFO Starting log output from 192.168.5.223 using esphome API WARNING Can't connect to ESPHome API for m5stack-atom-echo-238a70 @ 192.168.5.223: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.5.223', port=6053))]: [Errno 113] Connect call failed ('192.168.5.223', 6053) (SocketAPIError) INFO Trying to connect to m5stack-atom-echo-238a70 @ 192.168.5.223 in the background (bewerkt) [14:23] no.. [14:23] shall i try to reinstall it. [14:24] Or try to connect to a blanco project 1st?  snowy — vandaag om 14:24 the smart reader is online and working fine right? [14:24] can u show me the same parrt of the log for that?  Daft_dutch — vandaag om 14:24 the smart reader is not addapted to esphome.  snowy — vandaag om 14:25 ok i zoomed in and saw it now   Daft_dutch — vandaag om 14:25 I think thats why its still working..  snowy — vandaag om 14:26 u could remove the device u have plugged in from the ESPHome dashboard then add new from there and start again with a black config [14:26] u have the yaml saved right? [14:27] this could be a networking issue  Daft_dutch — vandaag om 14:28 remove the device from esp home and install a blanco project?  snowy — vandaag om 14:28 yes [14:29] use the NEW Device link on the bootom right of dash  Daft_dutch — vandaag om 14:31 o there. [14:31] I wanted to install a empty project jusing the default projects. [14:32] what device is the echo?  snowy — vandaag om 14:35 standard esp32 for now  Daft_dutch — vandaag om 14:35 I have issues with my https proxy and esp home addon. cant use my https connection.  snowy — vandaag om 14:35 this is probably a networking issue - is mdns working?  Daft_dutch — vandaag om 14:36 how do i check that. [14:36] ha is a bridged vm on my local lan. [14:37] it went not working 2 days ago  snowy — vandaag om 14:38 probably need to look into the network settings of the vm  Daft_dutch — vandaag om 14:39 avahi 631 0.0 0.0 8976 4368 ? Ss 13:43 0:00 avahi-daemon: running [doorman.local] [14:40] Its the vanila kvm settings of haos  snowy — vandaag om 14:40 mdns uses port 5353 i believe [14:41] can u ping .local addresses?  Daft_dutch — vandaag om 14:46 eumm no. [14:46] I have a .pwap as local domain [14:46] but the homeassistant.local never worked with me  snowy — vandaag om 14:46 ok i am bit hazy on this kind of setup then [14:46] i think u have to then specifiy that domain in the config of the device [14:47] all i know is changing the domain to something "non standard" is going to cause problems [14:48] https://esphome.io/components/wifi.html ESPHome WiFi Component Instructions for setting up the WiFi configuration for your ESP node in ESPHome.  [14:49] the settings will be listed there [14:49] domain (Optional, string): Set the domain of the node hostname used for uploading. For example, if it’s set to .local, all uploads will be sent to .local. Defaults to .local.  Daft_dutch — vandaag om 14:53 i try that.  Daft_dutch — vandaag om 15:12 did not work... [15:13] I have troubles with connecting after writing the code from esp home to the echo once.  Daft_dutch — vandaag om 16:07 I guess i make an issue. Droppingoff of all adapted devices is strange  Daft_dutch — vandaag om 16:32 @snowy i found the issue. i changed my local domain to .local now it works.  1 [16:35] but this is a big regression bug. is this for esphome or homeassistant.. [16:35] I know many systems that dont have a .local domain  snowy — vandaag om 16:40 well its probably cos u have did not change in HA at the starrt [16:40] HA and ESPHome would have to know that you are not using .local [16:41] everythign defaults to that because its the most common values  Daft_dutch — vandaag om 16:41 it did work until the latest patch. NIEUW  snowy — vandaag om 16:42 strange cos i dont know of any changes that would have effected that  Bericht sturen naar "cant reconnect my esp echo's to home assistant."

github-actions[bot] commented 2 weeks ago

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.