no.
Also, it’s best to have DNS 2 set as well in case the first is unavailable. Use:
1.1.1.1 or
8.8.8.8
Ok. Added all three.
DNS is still at 0.0.0.0.
[23:10:04][I][wifi:235]: WiFi Connecting to '...searching'...
[23:10:04][I][wifi:498]: WiFi Connected!
[23:10:04][C][wifi:344]: SSID: '...searching'
[23:10:05][C][wifi:345]: IP Address: 192.168.86.100
[23:10:05][C][wifi:347]: BSSID: 44:07:0B:0F:DE:C4
[23:10:05][C][wifi:348]: Hostname: 'esp32'
[23:10:05][C][wifi:352]: Signal strength: -48 dB ▂▄▆█
[23:10:05][C][wifi:356]: Channel: 1
[23:10:05][C][wifi:357]: Subnet: 255.255.255.0
[23:10:06][C][wifi:358]: Gateway: 192.168.86.1
[23:10:06][C][wifi:359]: DNS1: 0.0.0.0
[23:10:06][C][wifi:360]: DNS2: 0.0.0.0
[23:10:06][D][wifi:507]: Disabling AP...
[23:10:06][C][ota:029]: Over-The-Air Updates:
[23:10:06][C][ota:030]: Address: 192.168.86.100:3232
[23:10:07][C][ota:032]: Using Password.
[23:10:07][C][api:022]: Setting up Home Assistant API server...
[23:10:07][I][app:059]: setup() finished successfully!
[23:10:07][I][app:105]: ESPHome version 1.19.4 compiled on Jul 7 2021, 22:28:16
[23:10:07][C][wifi:484]: WiFi:
[23:10:07][C][wifi:344]: SSID: '...searching'
[23:10:08][C][wifi:345]: IP Address: 192.168.86.100
[23:10:08][C][wifi:347]: BSSID: 44:07:0B:0F:DE:C4
[23:10:08][C][wifi:348]: Hostname: 'esp32'
[23:10:08][C][wifi:352]: Signal strength: -48 dB ▂▄▆█
[23:10:08][C][wifi:356]: Channel: 1
[23:10:09][C][wifi:357]: Subnet: 255.255.255.0
[23:10:09][C][wifi:358]: Gateway: 192.168.86.1
[23:10:09][C][wifi:359]: DNS1: 0.0.0.0
[23:10:09][C][wifi:360]: DNS2: 0.0.0.0
[23:10:09][C][logger:189]: Logger:
[23:10:09][C][logger:190]: Level: DEBUG
[23:10:09][C][logger:191]: Log Baud Rate: 115200
[23:10:10][C][logger:192]: Hardware UART: UART0
[23:10:10][C][captive_portal:148]: Captive Portal:
[23:10:10][C][ota:029]: Over-The-Air Updates:
[23:10:10][C][ota:030]: Address: 192.168.86.100:3232
[23:10:10][C][ota:032]: Using Password.
[23:10:10][C][api:095]: API Server:
[23:10:11][C][api:096]: Address: 192.168.86.100:605
Not sure why the device is not being sent the correct DNS values.
Another way to potentially fix this is to use the following in the add-on config.
"status_use_ping": true
I think we need to start over here. 
Right now it’s a little messy, and despite I read all your three threads, I’m still not sure what exactly is happening. 
As I already said in the other thread, we need to know, what exactly is your error. From this thread, it looks like your ESP is working and you just couldn’t get the green header bar.
If I put all the infos (from all your threads) together, it looks more like you could flash it, but it isn’t reachable in ESPHome dashboard as well as in HA. Is this your error?
If it’s the latter one, would you mind writing down exactly, what you’re doing? All steps, even the push of a button and every screen you get while working with this.
I’ll start the list, you expand on it.
- You have HomeAssistantOS running with the official ESPHome add-on.
- You open the webUI from ESPHome (aka the ESPHome dashboard).
- Delete the node you worked with as a test (your esp32 or 32)
- You click on the big plus sign, what happens next (screenshot is preffered, every pop-up you get here)?
You don’t need to work along, let’s just try it step by step. I’m quite sure, there is a solution for this.
The problem is, he’s using
manual_ip
without defining DNS1: and DNS2: values.
Try this:
manual_ip:
# Set this to the IP of the ESP
static_ip: 192.168.86.100
# Set this to the IP address of the router. Often ends with .1
gateway: 192.168.86.1
# The subnet of the network. 255.255.255.0 works for most home networks.
subnet: 255.255.255.0
#
dns1: 1.1.1.1
dns2: 8.8.8.8
On the router settings screenshot, the DHCP is set to 192.168.1.x, you are using 192.168.86.x is that correct ?
1 Like
Nope, that’s not necessary. I have all my ESPs running with manual_ip, neither of them has any DNS entries defined (as these are advertised through the router). They work without any problems. So this can’t be it.
Same here no DNS entries defined in my ESPHOME configs
My logs say:
[12:53:05][C][wifi:359]: DNS1: (IP unset)
[12:53:05][C][wifi:360]: DNS2: (IP unset)
It doesn’t look like I can change that.
Setting a DNS didn’t help.
Doesn’t seem to help.
Why can’t you set a manual ip with 192.168.1.x ?
I thought you were talking about the other way around. Does your IP match your router’s DHCP?
Also, I don’t know why I set it to .86. It should have been 192.168.1.1 for the gateway since that’s my router’s IP. Still didn’t work but thanks for that.
You seem to be on the right track!
As far as I can see, it should work. At least the flashing of the ESP is ok. It’s not the easiest way with downloading and pushing it manually, but it works.
The assigned IP address is x.x.x.100 as written in the firmware. The connection to your router seems ok as well. So this leaves us with a lot less possibilities for errors. 
After flashing and closing the ESPHome-Flasher, did you disconnect the ESP from your PC? Ideally you should power it with a seperate power supply, like a cell phone charger. Nonetheless you need to restart the ESP by disconnecting and connecting it again to a power supply.
Then go back to the ESPHome dashboard and press “LOG” under the node. What do you get there? Any response?
Just tried disconnecting it and plugging it directly to power. Didn’t end up working. Went into LOGS and got these messages:
INFO Reading configuration /config/esphome/32esp.yaml...
INFO Starting log output from 192.168.1.150 using esphome API
INFO Connecting to 192.168.1.150:6053 (192.168.1.150)
WARNING Initial connection failed. The ESP might not be connected to WiFi yet (Error connecting to 192.168.1.150: [Errno 113] No route to host). Re-Trying in 1 seconds
manual_ip:
# Set this to the IP of the ESP 192.168.86.130
static_ip: 192.168.1.150
# Set this to the IP address of the router. Often ends with .1
gateway: 192.168.1.1
# The subnet of the network. 255.255.255.0 works for most home networks.
subnet: 255.255.255.0
dns1: 8.8.8.8
dns2: 1.1.1.1
Using x.x.86.x, I used to be able to telnet to the device. Now I cannot.
Sorry to say, but my advise would be to roll back the changes you made to your IP settings in the router. Work with what you normally have. Just use an IP address that is in the range of your normal IP settings, eg. 192.168.178.x and that is not taken by the automatic DHCP lease in the router.
The router should have a setting, where you can set the IPs that are handed out automatically, eg. 192.168.178.100 to 192.168.178.200. Just take care, that the IP address you set in the ESP firmware is not in this “automatic” range, to stay with the example 192.168.178.201. You get the idea.
After that, we work our way up. The ESP should have an IP address, that is in your normal settings. If you need to change the firmware, do it as shown in your video and flash the ESP with these settings. You can safely leave out the DNS server in ESPHome. Just the three non optional settings (static_ip, gateway, subnet).
So let’s try again, connect the ESP to your power supply and let it boot.
Does it show up with the choosen IP address in your router?
If yes, go to the ESPHome dashboard and press “LOG”. What is the output?
Ok. I’ve changed the IPs back.
manual_ip:
static_ip: 192.168.86.200
gateway: 192.168.86.1
subnet: 255.255.255.0
Now that this has been brought up, I now see that my router is x.x.1.1 but my Google Nest wifi device is x.x.86.1. So now it makes sense to have it back to 86.1.
ESP8266:
- Shows up on Google Nest
- Can telnet to it over port 6053
- Doesn’t connect in ESPHome
ESP32:
- Doesn’t show up on Google Nest (though it did at one point in all of this)
- Can telnet to it over port 6053
- Doesn’t connect in ESPHome
Anyone able to help? I thought connecting an ESP device was supposed to be pretty easy. I really want to go further with all of this.