Installing AppDaemon on Ubuntu with virtualenv

emulated hue and alexa dont need open ports, so they are not effected by a proxyserver.
normal hue also not (i think, dont have it)

i dont know about ifttt or haaska, i dont use those.
its possible that you need to configure something in your proxy server when you use haaska.

same if you want to use hadashboard outside your network (allthough i dont advise that)

and dont worry about off topic in a topic that is 3 years old :wink:

your questions are somewhat related anyway.

and remember: open as little to the outside as possible.
think twice about if you really need to use it when you are not at home.

i stepped away from opening my network, i use VPN on my mobile only.
and because of that there is no need for proxy or SSL at all.

1 Like

Two more quick questions then.

  1. Will the app still support acting as a device tracker
  2. Will I still be able to access my HA instance from the outside without adding port 8123 at the end of I wanted to?

i cant tell you what an app can do or not, without knowing what app.
but normally an app works always as long as HA and AD are connected.

how and what you can access from the outside completely depends on the settings from your proxy server. but it can be a pain in the but to configure the proxy server to your needs.

nginx can do very much, but its not the easiest to configure.

you can connect any duckdns url with or without port to your HA, but if you want to access more then just HA you might need more addresses or use ports.

the proxy server works like this:

  • if a request for xx.xx.xx comes in then show A
  • if a request for xx.xx.xx:port comes in then show B
  • if a request for xx.xx.xx/api comes in then show C

Ha, sorry I meant the iOS HA app. I use it as a device tracker. Sounds like it should work fine

yeah that should work also with a proxy server.

I wanted to thank you again, I have not moved to nginx yet,but I did go ahead and move my instance to a private domain. No more duckdns. I had a domain sitting on the shelf for a while and wanted to see if I could do so. It was a bit of a pain to get the ssl certs, but now I have that figured out. That will be something Iโ€™ll need when I move to nginx. I have a router with merlin firmware, and it looks like I could install nginx on the router, which seems like a good idea. Iโ€™m enjoying working on something new.

your welcome. im glad that i could help.

I got sidetracked and still have not made the nginx plunge. Saw in HA .110 that there was support for an internal IP. I tried setting that up but had no success. Is this something that I should be able to configure with the new internal setting?

I tried to browse to my HA instance by https://IP:8123, but did not have any success. So maybe my HA instance needs some work

Thanks for your insight

i think the internal IP is without ssl so http and not https

at least that would be the logical thing.
and indeed that they made that possible should make it possible to talk between AD and HA without the need for a proxy server.

of course in that case you cant access AD (and dashboard from the outside, but that is also the advised way)

Sorry I wrote that backwards. When I try with http, it fails to connect, when I try with https I connect but with a cert error (which makes sense).

if both addresses have ssl then i dont see the point. (allthough its at least a little better)
but if you got ssl in HA you need cert verify in appdaemon.yaml (i believe, but i am not sure because i never used any of it)

Iโ€™d be happy to remove the SSL from internal. I dont even remember setting it. Must have been so long ago, I dont even know where to turn it off. haha. Iโ€™m reading through the posts now to see where I may have went wrong

i dont know if they made it possible to chose if you want SSL.
its possible that to get rid of the internal SSL you will need to remove it completely.
which is only advised when you dont access HA from outside your network, or through a proxy server.

1 Like

Thanks, got it , I understand now. Thanks. Cert verify did work though. Iโ€™m now able to use my internal IP vs expernal DNS. Baby steps, but itโ€™s a bit better, thanks again

1 Like