D1 mini Error 113 WARNING Couldn't connect to API

K-Glasius commented 5 years ago

Hi i have a D1 mini whit this yamel

esphomeyaml:
  name: pool
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: '*****'
  password: '******'

  manual_ip:
    static_ip: 192.168.1.75
    gateway: 192.168.1.1
    subnet: 255.255.255.0
# Enable logging
logger:

# Enable Home Assistant API
api:
  password: '******'

ota:
  password: '******'

i am getting erros on the API

LOG


INFO Reading configuration...
INFO Starting log output from 192.168.1.75 using esphomelib API
INFO Connecting to 192.168.1.75:6053 (192.168.1.75)
WARNING Couldn't connect to API (Error connecting to 192.168.1.75: [Errno 113] No route to host). Trying to reconnect in 1 seconds
INFO Connecting to 192.168.1.75:6053 (192.168.1.75)
WARNING Couldn't connect to API (Error connecting to 192.168.1.75: [Errno 113] No route to host). Trying to reconnect in 2 seconds
INFO Connecting to 192.168.1.75:6053 (192.168.1.75)
WARNING Couldn't connect to API (Error connecting to 192.168.1.75: [Errno 113] No route to host). Trying to reconnect in 4 seconds
INFO Connecting to 192.168.1.75:6053 (192.168.1.75)
WARNING Couldn't connect to API (Error connecting to 192.168.1.75: [Errno 113] No route to host). Trying to reconnect in 8 seconds
INFO Connecting to 192.168.1.75:6053 (192.168.1.75)
WARNING Couldn't connect to API (Error connecting to 192.168.1.75: [Errno 113] No route to host). Trying to reconnect in 16 seconds```

plz help

meijerwynand commented 5 years ago

Greetings,

Formatting please

Please try to post your config and logs by enclosing them in 3 backticks before and after the log / config you post, see here.

``` log file here ```

For yaml files, after the first 3 backticks, type the word yaml to enable syntax highlighting.

```yaml ...

Use the 'Preview' tab at the top of the editor to see how your post will look.

That will help immensely in being able to ready the configs.

Your issue

The error you are getting ...No route to host... generally indicates a networking issue. It says/means "I have no way (route) to get there (host)"

Is the IP you are assigning to the D1 mini in the same network IP range/subnet as the Home Assistant (HA) server? -- IP range: If the HA server is on 192.168.0.10 and the D1 mini is on 192.168.1.75 they will not be able to see each other* (given it's a simple network with no routing) -- Subnet/Netmask: Check if your subnet is the same as where your HA server -- IP Conflict: As you are manually assigning an IP, it could also be an IP conflict. Test from the PC you are running the esphomeyaml commands and do a few pings. --- ping the gateway (as per your example) : ping 192.168.1.1 --- ping any other node you know is on the network: ping 192.168.1.<whatever> --- ping the D1 ping 192.168.1.75

Thanks

OttoWinter commented 5 years ago

Please post USB/serial logs please, otherwise this cannot be debugged.

DavidDeSloovere commented 5 years ago

I have many wemos D1 minis, no problem with OTA updates or API connections or HTTP server for me. This looks more like a network or config issue to me.

K-Glasius commented 5 years ago

[1B][0;35m[C][ota:461]: There have been 9 suspected unsuccessful boot attempts.[1B][0m
[1B][0;32m[I][application:053]: Running through setup()...[1B][0m
[1B][0;36m[D][binary_sensor:027]: 'pool': Sending state OFF[1B][0m
[1B][0;35m[C][wifi:029]: Setting up WiFi...[1B][0m
[1B][0;36m[D][wifi:260]: Starting scan...[1B][0m

 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
[1B][0;32m[I][logger:071]: Log initialized[1B][0m
[1B][0;35m[C][ota:461]: There have been 10 suspected unsuccessful boot attempts.[1B][0m
[1B][1;31m[E][ota:466]: Boot loop detected. Proceeding to safe mode.[1B][0m
[1B][0;35m[C][wifi:029]: Setting up WiFi...[1B][0m
[1B][0;36m[D][wifi:260]: Starting scan...[1B][0m
[1B][0;36m[D][wifi:275]: Found networks:[1B][0m
[1B][0;32m[I][wifi:308]: - '******' (F2:9F:C2:7A:86:0B) [1B][0;33mâ–‚â–„â–†[1B][0;37mâ–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:309]:     Channel: 11[1B][0m
[1B][0;36m[D][wifi:310]:     RSSI: -62 dB[1B][0m
[1B][0;32m[I][wifi:308]: - '******' (F2:9F:C2:81:90:E9) [1B][0;31mâ–‚[1B][0;37mâ–„â–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:309]:     Channel: 5[1B][0m
[1B][0;36m[D][wifi:310]:     RSSI: -87 dB[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (F0:9F:C2:7A:86:0B) [1B][0;33mâ–‚â–„â–†[1B][0;37mâ–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '' (12:9F:C2:7A:86:0B) [1B][0;33mâ–‚â–„â–†[1B][0;37mâ–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (02:9F:C2:7A:86:0B) [1B][0;33mâ–‚â–„â–†[1B][0;37mâ–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (A2:20:A6:1B:9A:A4) [1B][0;33mâ–‚â–„[1B][0;37mâ–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '' (12:9F:C2:81:90:E9) [1B][0;33mâ–‚â–„[1B][0;37mâ–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (F0:9F:C2:81:90:E9) [1B][0;33mâ–‚â–„[1B][0;37mâ–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (6C:B0:CE:B3:45:74) [1B][0;31mâ–‚[1B][0;37mâ–„â–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (02:9F:C2:81:90:E9) [1B][0;31mâ–‚[1B][0;37mâ–„â–†â–ˆ[1B][0m[1B][0m
[1B][0;36m[D][wifi:312]: - '******' (6C:B0:CE:B6:CD:A0) [1B][0;31mâ–‚[1B][0;37mâ–„â–†â–ˆ[1B][0m[1B][0m
[1B][0;32m[I][wifi:179]: WiFi Connecting to 'E-G2.4'...[1B][0m
[1B][0;32m[I][wifi:349]: WiFi connected![1B][0m
[1B][0;35m[C][wifi:240]:   SSID: 'E-G2.4'[1B][0m
[1B][0;35m[C][wifi:241]:   IP Address: 192.168.1.75[1B][0m
[1B][0;35m[C][wifi:243]:   BSSID: F2:9F:C2:7A:86:0B[1B][0m
[1B][0;35m[C][wifi:245]:   Hostname: 'pool'[1B][0m
[1B][0;35m[C][wifi:250]:   Signal strength: -66 dB [1B][0;33mâ–‚â–„[1B][0;37mâ–†â–ˆ[1B][0m[1B][0m
[1B][0;35m[C][wifi:251]:   Channel: 11[1B][0m
[1B][0;35m[C][wifi:252]:   Subnet: 255.255.255.0[1B][0m
[1B][0;35m[C][wifi:253]:   Gateway: 192.168.1.1[1B][0m
[1B][0;35m[C][wifi:254]:   DNS1: 0.0.0.0[1B][0m
[1B][0;35m[C][wifi:255]:   DNS2: 0.0.0.0[1B][0m
[1B][0;35m[C][ota:129]: Over-The-Air Updates:[1B][0m
[1B][0;35m[C][ota:130]:   Address: 192.168.1.75:8266[1B][0m
[1B][0;35m[C][ota:132]:   Using Password.[1B][0m
[1B][0;33m[W][ota:136]: Last Boot was an unhandled reset, will proceed to safe mode in 0 restarts[1B][0m
[1B][0;32m[I][ota:477]: Waiting for OTA attempt.[1B][0m
[1B][0;32m[I][ota:154]: Boot seems successful, resetting boot loop counter.[1B][0m
[1B][1;31m[E][ota:485]: No OTA attempt made, restarting.[1B][0m
[1B][0;32m[I][helpers:277]: Forcing a reboot... Reason: 'ota-safe-mode'[1B][0m
[1B][0;33m[W][wifi:727]: Event: Disconnected ssid='E-G2.4' bssid=F2:9F:C2:7A:86:0B reason='Association Leave'[1B][0m

 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
[1B][0;32m[I][logger:071]: Log initialized[1B][0m
[1B][0;35m[C][ota:461]: There have been 0 suspected unsuccessful boot attempts.[1B][0m
[1B][0;32m[I][application:053]: Running through setup()...[1B][0m
[1B][0;36m[D][binary_sensor:027]: 'pool': Sending state OFF[1B][0m
[1B][0;35m[C][wifi:029]: Setting up WiFi...[1B][0m
[1B][0;36m[D][wifi:260]: Starting scan...[1B][0m

 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
[1B][0;32m[I][logger:071]: Log initialized[1B][0m
[1B][0;35m[C][ota:461]: There have been 1 suspected unsuccessful boot attempts.[1B][0m
[1B][0;32m[I][application:053]: Running through setup()...[1B][0m
[1B][0;36m[D][binary_sensor:027]: 'pool': Sending state OFF[1B][0m
[1B][0;35m[C][wifi:029]: Setting up WiFi...[1B][0m
[1B][0;36m[D][wifi:260]: Starting scan...[1B][0m

from terminte

OttoWinter commented 5 years ago

Closing due to inactivity

esphome / issues

D1 mini Error 113 WARNING Couldn't connect to API #14

Formatting please

Your issue