On my cell phone I get 192.168.4.4 but on 4.1 it doesn’t find any page. With some devices I managed to get it in but the latter I don’t know what the problem is
I’m already trying anything. “Micronet_2.4” appears and it is the one that gives me the ip 4.4 but I don’t know if this code is correct. What remains for me is to disassemble the sockets and re-record with UART
This tells us absolutely nothing. We don’t know when you flashed which yaml file to the device.
Also, don’t post fragments unless asked to. We need to see the whole yaml file that you flashed to the device.
Your yaml file in post#15 does not have captive_portal:. If that is what you flashed to the device, then you do not have automatic AP fallback. Period.
However, if it worked before you had an internet outage, it should still be working now.
I would first do an IP scan of your network. I recommend the free Advanced IP Scanner tool. Run this to see if your devices have an IP address.
Next, I would recycle the power to one of the failing devices. NOT THE ROUTER.
If Home Assistant doesn’t see the device, run IP scan again to see if it got an IP address.
If no luck here, it’s time for disassembly and reflash. Don’t forget to add captive_portal:
Test the connection to Home Assistant before you reassemble the device in the wall.
The problem is that I don’t know how to speak English and the translations sometimes don’t say what I want to say. I also interpret eg “don’t publish a snippet of your code unless we ask you to” as an imperative. But I imagine that the translation also seems aggressive. The device is a sonoff s20. I already flashed the devices that no longer took ip. At this moment all the devices (plugs, touch switches, and sonoff basic are all working but nevertheless all the devices for esphome appear offline. I appreciate all the help. Surely I did something wrong and that is why all this happened. Thanks
Have you tried deleting the integration for the suspect device then let Home Assistant discover it again? If this doesn’t work then re-flashing the device is still the only solution.