Allow apex local network name instead of ip

[brettonw]

I haven't looked at why this fails, but the Apex registers itself on the local network as "apex". In my configuration, I can access the device using "http://apex.local".

When setting up the integration, I was not able to use the name, and had to use the IP. This is fine, but if the DHCP reservation ever changes my integration will drop. I'd prefer to use the registered name "apex.local".

[itchannel]

I'll have to look into this as don't know if the .local dns namespace would be resolvable inside the HA container. I'll have a play on my dev instance.

[brettonw]

I run HA in a container and set the resolver to my local router in the docker compose file. I refer to other local integrations using names, so I was surprised this one failed.

On Aug 24, 2022, at 6:15 PM, itchannel @.***> wrote:

 I'll have to look into this as don't know if the .local dns namespace would be resolvable inside the HA container. I'll have a play on my dev instance.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[itchannel]

Ok if that's the case then I'll see what I can do 👍

[itchannel]

Works for me OK using the DNS name "apex.local"

[brettonw]

I tried again and it still doesn't work for me. I'll see if I can track down why.

[brettonw]

I suspect this is a local network issue for me. Looking at the code there is no reason this shouldn't work.

[brettonw]

How do you run HA? In a container?

[itchannel]

My main instance is HA OS and my dev instance is a container in docker.