[ESPHome] How to get a "Ready-Made Project" copy to a local HA ESPHome (for editing)?

Hi 2UAll!

I have a, kind of, noob question…

As an example to use I will refer to:
RMP = Ready-Made Projects — ESPHomeVoice assistantESP32-S3-BOX-3
RMP Git = firmware/voice-assistant/esp32-s3-box-3.yaml at 448c9eb48b64e4b08d21f3f022384fa0c5264c7a · esphome/firmware · GitHub

The goal is to the get RMP Git version copied, with all additional files, to my local Home Assistant ESPHome add-on, to change settings and experiment with it.

Does anyone know how to do this?

Any help will be highly appreciated!

When you adopt a rmp device into esphome the yaml will be downloaded.

Or you can download files from GitHub as usual.

Thank you for responding @nickrout
That is the problem I have, when a RMP-Device is added it is not showing in my local ESPHome add-on. It is only added here:
afbeelding
and not added here:
afbeelding
nor can I find any files here:
afbeelding

How can I do that?

Okay, I’m dit some testing. This are my findings, so far…

1 - I made a new HA Instance (in a Virtual Machine using ova) :white_check_mark :white_check_mark:
2 - Installed Studio Code Servers add-on. :white_check_mark:
3 - Installed Advanced SSH & Web Terminal :white_check_mark:
4 - Installed ESPHome add-on. :white_check_mark:
5 - Configure a M5Stack Atom Echom (white one) with RMP Voice Assistant connecting to the same network subnet. :white_check_mark:

5 REMARK -Now I noticed something strange. On the new HA-instance it is adoptable, on my existing it is not!
I will get back on this… This is the main problem, I think.

6 - Changed the M5Stack to connect on a different WiFi Network (with another subnet), now it is not adoptable by both HA-instances. I checked my firewall/network configuration this should be allright.
7 - Changing back to the same subnet to be adoptable again in my new HA-Instance.
I will keep you informed…

Regarding point 6 & 7 from the previous post:

6/7 - From the RMP website (ESP-Home), when using the Add to Home Assistant I could put the right IP-Address for connecting and it is disvored by both HA-Instances.

But in the test VM-instance it could adopt to the local ESPHome add-on but in my existing it is not!

5 - So the problem is my existing setup. I have a reasonable guess it has something to do with my custom self-signed SSL Encryption keys/certificate on my existing HA-instance.
The new/test HA-instance is not using custom certificates and, for encrypted communication, it is using a http(s) proxy.

How to solve that, I have no idea, but I think to have to investigate and start a new topic.

One question remains open:

How do I do that? Please help…

You can’t download a file from the internet?

Click on the file, then click on download raw file.

1 Like

Also, stop shifting it to a different subnet.

OK, got that working. Thanks.

I use several separate (secured) subnets, for example one for ESP, one for IoT, one for domotica controllers and so on. I manage them by a network firewall and Intrusion prevention. I got it working now, even with several subnets.

Only point 5 I have to work on, but that is an other story…