Nobody in the community for a helping hint ?
„platform ultrasonic“ seems to be unknown …. but what does it mean ?
How to introduce a new platform to HA ?
Hi David ….
I changed the D1 mini to a new one and took care, that I didn’t overheated the pins …. same problem.
I also made a complete new installation, initializing the D1 and reinstalled a yaml file … everything along the guideline …. with a positive Log file.
The Log showes … everything is fine and I can read the distance measuring of the ultrasonic sensor in the log.
But there’s no way to have it implemented into HA.
[09:27:27][C][captive_portal:144]: Captive Portal:
[09:27:27][C][ota:082]: Over-The-Air Updates:
[09:27:27][C][ota:083]: Address: wasserstand.local:8266
[09:27:27][C][ota:086]: Using Password.
[09:27:27][C][api:134]: API Server:
[09:27:27][C][api:135]: Address: wasserstand.local:6053
[09:27:27][C][api:139]: Using noise encryption: NO
[09:27:27][C][mdns:084]: mDNS:
[09:27:27][C][mdns:085]: Hostname: wasserstand
[09:27:28][D][ultrasonic.sensor:040]: 'Wasserstand' - Got distance: 0.40 m
[09:27:28][D][sensor:125]: 'Wasserstand': Sending state 0.40080 m with 2 decimals of accuracy
[09:27:30][D][ultrasonic.sensor:040]: 'Wasserstand' - Got distance: 0.40 m
What happens if you throw a api: (see api docs and the getting started guide) in your esphome yaml (if you haven’t already)?
You might wanna add a new esphome integration in the ha configuration and add your nodes mDNS address (wasserstand.local) in case auto discovery doesn’t find your device. If mDNS is broken on your network you could try the normal hostname (wasserstand) or the ip of the device.
Plenty of people (me included) have no problems having esphome nodes connected to ha 
This probably won’t help, but I had to reload the yaml back onto the mini because I changed modems and hadn’t set a static ip. When I did, and then tried to use configuration-integration-esphome using the new ip, it gave me the “Can’t connect to ESP. Please make sure your YAML file contains an ‘api:’ line.” again. I tried several times before I gave up. It was giving temp and humidity readings in the log. I left it plugged in and 2 days later it appeared in integrations under esphome. It has been up for a few days and hopefully it won’t disappear.
I’m stuck in the same place.
Synology with ESPHome in docker.
When I try to add integration ESPHome in HA, it asks for host computer and there I write the IP to Synology.
Still: “Can’t connect to ESP. Please make sure your YAML file contains an ‘api:’ line.”
I have looked in numerus instructions but all left this part out.
What app are You referring to in Your first post?
I had the same problem (look here). I solved it by adding a passwort to the api section:
api:
password: "your-password-here"
What password is it?
Your password 
Have you ever solved the problem?
I had the same problem because I thought I had to enter the IP of my esphome (docker) instance with port 6052
But that was a fail. You have to enter the WLAN IP of the device. The port of the device will automatically be 6052 if you did not declare any other manually.
After connect you have to enter the api encryption key in home assistant that was installed on the device.
e.g. my device ir-receiver.yaml from esphome after i installed it on the d1_mini
esphome:
name: "ir-receiver"
platform: ESP8266
board: d1_mini
# Enable logging
logger:
level: VERBOSE
# Enable Home Assistant API
api:
encryption:
key: "2MeMPEGzET8U*******GCg1lFD1y+NkNI="
ota:
password: "bbe8d860***a6df8d2a5df0"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
manual_ip:
static_ip: 192.168.178.91
gateway: 192.168.178.1
subnet: 255.255.255.0
Its a little bit different thinkin of connecting if you are used to create a controller first…
It could be quite far-fetched that in the local network the communication between the devices must be allowed. I use a Fritzbox there is such a setting but have never tried it without. Therefore here only as additional info. If the device is pingable and no ports are blocked in the local firewall, this should work fine. Some esp devices also need a little longer until they are accessible.
I think many of this (fails) assumptions (and tries) presented in this thread wouldn’t be written here if users would just take a few minutes minutes to read the “Getting Started” guide: 
In detail: 
Connecting your device to Home Assistant
Once your configuration is installed on your ESP device and is online, it will be automatically discovered by Home Assistant and offered to set up on your integrations screen:
Alternatively, you can manually add the device on the Home Assistant Integrations page. Click on the “Add Integration” button (bottom right), search for esphome, and enter the host name, eg: “<NODE_NAME>.local” as the host. Use the same process to add multiple esphome devices.
Thank you for being so smart! 
1 Like
@ orange-assistant I read and installed using the “Getting Started” guides. ESP Home is installed and online however “HomeAssistant” detect the new device and when trying to add also get the silly message of
“Can’t connect to ESP. Please make sure your YAML file contains an ‘api:’ line.”
Have wasted hours on this and for now giving up as seems way too much hassle.and seems like many others have this issue with no answer on hand. So no, the “How To” provides zero instructions with dealing with this error.
2 Likes
What I really wonder - does your esphome YAML by accident or silliness doesn’t contain an api: line? 
1 Like
Yes, this is consistent issues , they keep updating and changing the interface and introducing new issies. The documentation is BS too.
Is it? For me it’s a constant non-issue 
Feel free to participate to make it better! It’s open source and everybody is invited to improve things like the documentation (specially users like you which having problems understanding the docs and therefor could make them better for everybody! 
)
There is even a guide how to contribute 
@orange-assistant: A stupid reply. How can one contribute to documents when one is learning . We come here asking for assistance. Your reply is totally unhelpful and puts one off asking for help.
1 Like
Exactly these people who have a hard time learning know what additional information in the docs would have helped than achieve their goal faster. Users and devs which regularly work with esphome and the docs (and have already some knowledge) typically have no problems with the “BS” docs (@ForxPorx) likes to call them.
It’s just a point of view and it’s really necessary for the people who have problems understanding the documentation to improve them 
That’s okay (and that’s what the forum is there for indeed) - but sadly many people have problems even providing the minimum information necessery so others can actually help them. 
Also people (like you @myhass140) get offers/question to narrow down the problems but often don’t even bother to reply back 
Not much humans can do when an individual doesn’t want to get help 
Wow, clueless and rude or what! All my (few) questions posted are followed up in detail with whoever has “kindly” assisted me. I where possible also make note of “My Solutions & mistakes” so others can learn.
No response required as have unlinked myself from this thread as nothing to learn here.
Not that I’m aware of Maybe you see a different thread than the rest of us? Check January 19th 2023 of this thread 
followed by no reply of you (the person who seeking for help)
Maybe you thought
