If you can’t connect via USB that points to a hardware problem with the device.
same problem on 2 different computers?? Completely different computers? I dont think that would be likely.
Err what? If there is a hardware problem with the ESP then it won’t work trying to connect to any computer.
You can download the .bin file from ESPhome and then use any PC to load it onto the ESP. See the process here.
Yes this was the only way i was able to get the software onto the ESP-07 and Wemos D1. However, as mentioned above, the issues is the inconsistent functioning of said devices. Coming online and offline. The ESP-07 is the only one not letting me update OTA.
This issues is now fixed. I noticed there was an update to ESPHomeYaml 1.10 to EPSHome 1.11 after upgrading and updating OTA the Wemos D1 device all is working well. The ESP-07 will still not update OTA.
I see that you were able to upgrade ESPHomeyaml…I can’t seem to get it to upgrade (I’m not a developer)
Running ESPHomeyaml ver. 1.10.1 on Rasp.Pi 3 B+ With Home Assistant on Hassio 2.11. Need to upgrade ESPHomeyaml to ver. 1.12.0… Per instructions on WEB page… https://esphomelib.com/……(I ASSUME I enter the command directly in hassio> ???) With keyboard and monitor, directly logged onto Rasp Pi hassio> …tried…. pip2 install -U esphome, Got “ERROR Unknown COMMAND “pip2”…….(Not a developer so I don’t know docker) On the Rasp Pi, tried .‘docker pull esphome/esphome:latest Got “ERROR Unknown COMMAND “docker” Any suggestions would be appreciated.
PS: I am able to update OTA but NOT when the ESP8266 is first flashed with Tasmota.(and enter SSID + password in ‘Terminal’)…In the node configuration, I have to: ENETR the MANUAL IP Address of the newly flashed device (without this step, ESPHome could NEVER find the device):
wifi:
ssid: ‘myssid’
password: ‘mypassword’
manual_ip:
static_ip: 192.168.y.xxx
gateway: 192.168.y.zzz
subnet: 255.255.255.01.
Save/Validate
Compile (on the 3 dots to the right of the node name in ESPHome Dashboard), 'Download Binary (when compiled), 2.Copy the downloaded .bin file to a folder that’s easy for me to get at. 3.Open my browser and go to the IP address of the newly flashed ESP8266 device, go to the URL (browser), select ‘Firmware Upgrade’ 'Brows for file (.bin in my desktop folder), Start upgrade.
On the ESPHome Dashboard, I CHECK TO MAKE SURE that the GREEN dot is on, in front of my new node…
Then, to check, I click “SHOW LOGS”…if all is OK, a stream of data, in white, then purple, then green…stepping through each line of programming in the node and confirming connection to the API node then Home Assistant.
From that point on, I can upload OTA…Hope this helps
there is a new repo as its called ESPhome now, not ESPhomeYAML. Check the install docs for the new repo detail
Yes, I know it has changed. The address I got the instructions from is: https://esphomelib.com/esphomeyaml/guides/faq.html#how-do-i-update-to-the-latest-version
That is where I ran into the problem…
How do I update to the latest beta release?
For pip-based installs
pip2 install --pre -U esphome
For docker-based installs
docker run […] -it esphome/esphome:beta livingroom.yaml run
I simply do not know where to enter the commands…Directly in my Rasp Pi? Somewhere under hassio>? Another directory? Via SSH? Via a .yaml file in HA?
The Beta is a separate add-on:
And for Hass.io, you will see a “ESPHome Beta” Add-On for the beta channel.
I had similar issues with a bunch of Gosund SP1’s (platform: esp8266 / board: esp8285), Sonoff Basic’s (platform: esp8266 / board: esp01_1m) and a Sonoff RF Bridge (also platform: esp8266 / board: esp01_1m) that I managed to flash to ESPHOME using a USB serial adapter / pin soldering.
All units would drop every minute or so, showing the dreaded “WARNING Disconnected from API: Timeout while waiting for message response!” in the logs.
Initial suspicion was WIFI signal strength, but all were mid-50 dB’s or better (ie. lower). Then looked at my ASUS RT-AC68U wifi settings and messed with the professional settings on the 2.4 GHz band (Bluetooth co-existence from Disble to Enable, and Preamble Type from Long to Short). This improved things marginally.
Finally followed a number of cross-referenced posts by almighty Otto, that lead me to the suggestion that the arduino platform libraries could be causing these wifi issues.
Added arduino_version: dev to the esphome.yaml for each device like so:
esphome:
name: sonoff_rf_bridge_new
platform: ESP8266
board: esp01_1m
arduino_version: dev
This appears to have severely reduced the disconnects. Word is still out if this can be considered a permanent fix, but I am hopeful. 
Update: HA logs overnight showing over 9 hours of uninterrupted connection on all devices!
1 Like
I confirm.
arduino_version: dev
did the trick. No more disconnects. But mDNS also stops working 
I also tried
arduino_version: 2.5.2
- it not work. Disconnecting. But mDNS works
Adding use_address solves the mDNS issues. Not ideal but better than continual disconnects…
wifi:
use_address: 192.168.1.xxx
networks:
- ssid: MYSSID
password: MYPW
1 Like
How do you know whether this is working or not?
I’ll concur that using dev solves the WiFi issues.
I added this in (don’t know if I had an issue), there seemed to be no downside in doing so as I use static addresses anyway.
Spoke too soon. Still disconnecting 
Are you d’not know what is mDNS? mDNS - this is name resolution without DNS server (the node work as DNS server itself). So, if it works, you can reach the node by it name (name from the node config in “esphome” “name” section). For example, “ping node_name.local” (domain “.local” - is reserved for mDNS queries). If you can do like this - mDNS working, if not - not working. It is simple.
“use_address” have nothing related to mDNS. It is used to reach the node by old ip address, if you changed the network, where node was connected before.
Do you meen “esphome dev” or “arduino version dev”? For me the “arduino_version: dev” solves the issue complitely. I have 5 esphome nodes. Before i have many disconnects for each node, now - zero. All nodes always connected. So, this is not the esphome, but underleing libraries (yes, esphome uses Arduino esp8266 Wfi library) issue. Of course, it is all correct, if you not have another issues in you WiFi network…
arduino_version dev
WiFi is not simple. I have a couple of different APs (from different manufacturers) I could connect to some are better than others (RSSI is pretty similar), with channels etc not conflicting.
I feel that it is probably an authentication issue with how the protocol is implemented on different devices.
One particular AP absolutely hates the old Android tablets I have - disconnects all the time, so I have a cheap TP-Link AP for those to connect to.
Which version of esphome you are using?
My experience:
esphome 1.13.6 (last version of 1.13 branch) with arduino_version dev - no disconnects. When i upgraded to esphome 1.14.3 (last) - a lot of disconnects. And it is not dependend on arduino_version. When i rolled back to 1.13.6 - no disconnects. So i’m now on 1.13.6.
1 Like
I’m going to roll back. I’ve actually moved some stuff onto Tasmota as it got so bad.