No apps can connect, any suggestions

1

Newbie here. I installed hass.io on a rpi3. Got z wave, zigbee, and amazon alexa connected. For SSL, I used DuckDNS and NGINX addons, and I am able to log onto the system via “https://nunyabusiness.duckdns.org.”

My issue is that I cannot get any outside integrations to install or communicate. I have tried honeywell, wink, and MyQ, but I keep getting errors. Even the yr sensor gives me the error in the info developers tool:

Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Try again]

Also, in my system log, I have 2 error messages.

19-07-02 01:17:14 INFO (SyncWorker_1) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-deconz with version 3.1
19-07-02 01:17:18 WARNING (MainThread) [hassio.api.security] No API token provided for /api/config

19-07-02 01:21:04 INFO (SyncWorker_3) [hassio.docker.interface] Start homeassistant/raspberrypi3-homeassistant
19-07-02 01:21:07 WARNING (MainThread) [hassio.api.security] No API token provided for /api/config

I assume that I have some sort of authorization issue, but I cannot figure it out.

Any suggestions from the geniuses here?

2

I do not see related error for wink,Honeywell, etc.
They do not connect into HA. HA retrieve data or send data to those services. Are you sure host.is able to connect to them.

What is associated errors for those services?

3

Thanks for the reply. I removed those entries from the configuration.yaml since it wasnt working. I just rebooted with those entries, and these are the messages in the info section:

There was an error while logging in: 22:08:50.255624 Client Error while requesting data from api/v4/User/Validate: Cannot connect to host myqexternal.myqdevice.com:443 ssl:None [Try again]

10:08 PM components/myq/cover.py (ERROR)

Retrying in 17 minutes: Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Try again]

10:08 PM components/yr/sensor.py (ERROR)

Failed to initialize honeywell client:

10:08 PM components/honeywell/climate.py (ERROR)

After doing some more digging, it might be a DNS issue. Not sure how to fix it, but at least its another clue that will keep me up later then intended.