Reboot devices esphome

ESPHome
1

Hello everyone. Today I was without internet for a long time. Once I got internet again I found that no device was able to connect to the router. Is there a mechanical way to restart the devices?
Thanks

2

Only by a hard reset I think (ie remove power)

3

It’s the only one that occurs to me too. I’m going to try that tomorrow. Thank you very much

4

If they couldn’t connect they may have dropped back to being an AP. You could try that.

5

No. That didn’t happen. I checked it. So it only remains to cut the power and restore it again.
Thanks

6

Odd that stopping the internet caused them to stop working. Your AP and DHCP server usually don’t need the internet to operate.

7

Cut the power and reset it again but they still do not connect. There are many devices and none take IP. It’s very weird

8

Have you tried a restart of the router?

9

Yes. Reboot the router. Cut the power, put static IP, dynamic. The only thing I didn’t do is rewrite the devices. Everything connected except the esphome devices

10

How, if you didn’t reflash the ESP devices?
For what it’s worth, the only devices in my home with static addresses are my servers. All of my ESPHome devices get their IP from DHCP.

And, as @nickrout said, the ESP device could simply be reverting to the AP mode. Use your phone to connect to http://192.168.4.1

11

I don’t have any device as ap, the ssid of that device should be seen right? Can I force a device to be set as ap?

12

Show us your yaml file.
Unless you specifically removed
captive_portal:
from your yaml file, you have a fallback AP. Normally on 192.168.4.1

If the ESP device can’t connect to the WiFi for (I don’t recall how long the timeout is), then it becomes an Access Point at 192.168.4.1
You connect to the network at 192.168.4.1 on your phone and from there you can set your WiFi credentials.

13

@stevemann Sorry. But I don’t understand what captive portal is?

I don’t know what happened but I think there was a problem with the router. I reset it and some devices appeared in ap mode, but all sockets are still not visible. Does anyone know how I can put them in ap mode? thanks

14

SHOW US YOUR YAML FILE of one of the failing devices. Normally after a couple of minutes of no connection, the AP mode is automatic.

15 
esphome:
  name: enchufe-wifi-aire-comedor

esp8266:
  board: esp8285
  
# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "55500ac401870baa67c63a7f980920bb"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
#  manual_ip:
#    static_ip: 192.168.0.61
#    gateway: 192.168.0.1
#    subnet: 255.255.255.0
#    dns1: 8.8.8.8
#    dns2: 8.8.4.4

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  #ap:
  #  ssid: !secret wifi_ssid_2
 #   password: !secret wifi_password

# Example configuration entry
dallas:
  - pin: 03

# Individual sensors
sensor:
  - platform: dallas
    address: 0xb2031644035dff28
    name: "Temperatura Reposicion"
    id: temp_aire_comedor

# Example configuration entry
switch:
  - platform: gpio
    name: "aire_comedor"
    pin: GPIO12
    id: relay


binary_sensor:
  - platform: gpio
    pin:
      number: GPIO0
      mode:
        input: true
        pullup: true
      inverted: true
    name: "aire_comedor"
    on_press:
      - switch.toggle: relay    
    
    
  - platform: status
    name: "enchufe-aire_comedor-estado"
  - platform: gpio
    pin: GPIO3
    name: "enchufe-aire_comedor-sensor"
16

So you have captive portal commented out. The device should still have done into ap mode though.

Unknown why yours aren’t working, just one of those things perhaps.

17

An ap appears that gives me an ip 192.168.4.4 but it does not allow me to access 192.168.4.1

18

There will be nothing to access unless you have captive portal configured, and you don’t.

See Captive Portal — ESPHome

19

So, what happens when you log on to the network at 192.168.4.4?

20

This computer gets 192.168.4.4