Is my ESP32 rebooting itself? it disconnect from wifi few times a day

[Mahko_Mahko]

Is there a reason you have a core installation rather than an all-in-one?

Core is generally for advanced users with specific needs. Those users are generally comfortable navigating these kinds of things.

I have a core development HA instance but my main HA is all-in-one and I although I occasionally hit up against limitations of that installation method I much prefer it for its simplicity.

My dev instance runs in a VSCode devcontainer where I also manually installed ESPHome and the dashboard. But I find it a bit fiddly and at times confusing and so prefer the ease of use of the all-in-one set-up.

Installation

[kbrown01]

Is that really relevant? I have reasons for sure, noy sure they are all valid but that is what worked for me (now for years). Core is running … perfectly in most aspects. And that same box runs Kodi, databases, some other applications used in my software companies and many other things. It was a spare unit easy to add Core. Huge memory, lots of CPU and free.

But again, is the question relevant or better said … is the documentation lacking? Should it say, “forget it if you use Core. This will not work” … or “The standard installation does not enable the web server so if you want to change things, do not click here and install the “canned” version”.

Or can I go shell into the unit and manipulate things?

No where in any documentation describes this. If it does, I apologize. If it doesn’t, then it should state right up front what HA platform is required, what features are available should you choose quick install, what the canned parameters are, what limitations you will have … etc.

Like for instance, just take this as an example and take you mind and think like a novice user and not someone who wrote the code:

The ESPHome native API is used to communicate with clients directly, with a highly-optimized network protocol. Currently, only the ESPHome tool, Home Assistant and ioBroker use this native API.

After adding an api: line to your ESPHome configuration you can go to the Home Assistant web interface and navigate to the “Integrations” screen in the “Configuration” panel. Then wait for the ESPHome device to show up under the discovered section (can take up to 5 minutes) or add the device manually by choosing “ESPHome” from the integration overview and entering “<NODE_NAME>.local” or the IP address of the unit in the “Host” field.

The ESPHome native API is based on a custom TCP protocol using protocol buffers. You can find the protocol data structure definitions here: api.proto A Python library that implements this protocol is aioesphomeapi.

Example configuration entry api:

You naturally assume I guess that everyone in the world knows what a “ESPHome configuration” is and where to add the api: line.

[kbrown01]

So starting from the simplest description I can give.

I know I want a bluetooth_proxy to expand the are for connections,
I go to the link, see the Amazon link and order the boards.
I plugged in the USB to my PC and flashed, no issues really to here.
I put that ESP into a little box.
I have moved it to several locations in the house, used a block or not, have done many other things…

After one or two cycles, it completely drops and forgets the connection and after that they only way to get it back is to reboot HA.

I see no where to login to change anything.
There is no web interface.
There is no pre-compile interface if you click the button

So now I have a pretty little white box that does nothing that I thought it would do.

And just saying, I built a few of these too … DIY Milight Hub for Home Assistant using Sidoh NodeMCU ESP8266 – Jackson Raila: Straight To The Point

And they work perfect. So it isn’t I do not know what I am doing (so much). I just need directions to work with it.

[nickrout]

You can install esphome in other ways to using the addon. You’ll have to do that.

[parautenbach (Pieter Rautenbach)]

@kbrown01

You naturally assume I guess that everyone in the world knows what a “ESPHome configuration” is and where to add the api: line.

It’s your device YAML and the api: key goes in there. It really is the simplest of things.

@kbrown01

I see no where to login to change anything.
There is no web interface.
There is no pre-compile interface if you click the button

You seem to be all over the place. Since you’re running HA Core, and assuming you want to flash devices from the same machine, simply create a new Python venv for ESPHome. Then activate this venv and do pip install esphome. This is what you get: bare bones. You can edit YAML and flash it. That’s it.

[Edwin_D]

I see the firmware version is 2024.5.0

I read a topic on this forum that stated several people that had connection problems with wifi for this version of esphome. Those were solved by going to an earlier version. It could be you are facing the same problem. Unfortunately I cannot find the topic where I read it. Personally I also do not have witi problems. I use version 2024.5.3

Then again, it could be many things. I also personally know people that bought a batch of esp’s from Amazon that had very bad wifi. There are many imitation boards, some better, some worse. Or it could be a bad adapter.

If it is the first problem, downgrading to an earlier version of ESPHome could work. You could also specify an earlier version in the yaml, but it would require you to adopt the device in esphome, get the yaml file for it and edit it. It has been a while since I used a prebuilt image, but I seem to remember you get the option to edit the yaml when you adopt it in ESPHome.

I read you use core HA. You can do anything with Core that you can do with Supervised and addons, but it does require more experience and most tutorials are written for supervised. You will need a separate instance of ESPHome, but I assume you already have it because you have more ESP’s.