Let’s start with the acknowledge that I’m still fairly new to the whole HA environment, so my problems might be easy for some of you. But anyway, I’ve just come to a hold and can’t seem to figure out why it doesn’t work.
I have installed the system via hass.io on a NUC and I have to say I’m really impressed with the overall ease of things when you take the hass.io way. My only real problem at the moment is the dashboard.
I’ve tried to follow various guides and forum topics, but still no result.
For the ease of things I’ve attached an image with the different configurations that I have, in hopes that someone skilled can tell me where it goes wrong. I’m also really sorry for any rookie mistakes that i’ve made, but i’ve changed so many congigurations now, that I actually lost track of some of it. But hey, it’s a learning process.
As far as I can tell from my logs, AppDeamon is running, and it says that it has startet the dashboard, but I can’t seem to find it anywhere. Whenever I go to the IP it just wont connect.
I really hope some of you can help, and I truly appreciate the time you guys spend on helping out! Big thanks!
I’m not familiar with hass.io yet, but is appdaemon running in the same docker container as HA? Are you sure the IP address is correct for the dash_url setting?
Your screenshots don’t make sense. You should have a “hamburger menu” on the top left to access the dashbaord.
From a container perspective, every process has it’s own container.
Home assistant is one
AppDaemon (assuming you’re referring to the supervisor) should also be running in it’s own container. See below some screenshots showing the hamburger menu with the menu collapsed and how it should look expanded. “State” should be your main view.
whats in the logs at that time?
are you trying it from the same subnet?
have you set any certification?
and you could probably try the complete path to the dirs in your config.
like
@bager
I am not familiar with docker containers, but if it is a linux based something then it should be running ssh. And it can be managed through ssh. If you are running windows on your home computer Download putty from here: www.putty.org, and then start it. Type the IP of your HA machine and log in with your HA user account. After that just type sudo netstat -tpan
and you should get a list of services listening on different ports. And if you can’t see 3030 or 5050 in the list then appdaemon is not listening anywhere. If you can see localhost by the 3030 or 5050 port then you will need to make changes to make it listen on 0.0.0.0.
If you are using a mac, then you can use the command line (terminal) where you can type ssh Ip_Of_Ha_device and then login with the HA user account.
tom
Hey @towme ! Thanks a lot for that reply. I won’t say that it got ME closer, but it definetly showed that nothing is listening on the ports. So I guess that that is a step? How do I then make sure that it will begin listening to the port? And to @leighcurran, as you can see, I’m still having the same issue.
And then I put the port in the config in my hass.io setup, and then it actually worked!
Well. Almost. When I go to http://URL:5050 i get the dashboard welcome. Perfect
But from there, the link to the actual dashboard doesn’t work. I have it set in the config as:
dash_url: http://192.168.0.133
But that won’t make it go to the dashboard as it lacks the port. if I then manually type dash_url: http://192.168.0.133:5050/hello, it works fine. BUT. If I add the port in the config like this:
dash_url: http://192.168.0.133:5050
Nothing works. That seems weird.
Well, I can make it work as I just type the URL manually, and it is not an issue as the dashboards are static in my situation. so no problem. Just weird IMO.
So grateful for you guys help. Its extremely nice that this community is so helpful towards the less technical of us!
You shouldn’t add the port in the config, because the port shows what service it is so it gets assigned automatically (well sort of). For example ssh usually listens on port 22, http on port 80, https on 443 and so on. The first 1024 ports a reserved and already sorted out for different services, but from 1025 - 65535 you can almost freely choose your favourite port for your own app. Baloob chose 5050 when he wrote the Appdaemon 2.0, also 3030 for appdaemon v1.x.
All this is means is that if your service is not running on the default port number (which above 1024 is usually the case) then you will have to add it manually after the IP address separated with a colon.
So the correct way should be that you put your IP into the config, and then add :5050 to the links in your dashboard configs. Also keep in mind that the name of dashboard should be added to the link when you try to open it.
You probably will want to have different dashboards for the lightning and the heating, so your urls will look like this: http://IP:5050/lights and http://IP:5050/heat
don’t lose faith in this project, keep up with the trying thats the way to go!
Makes sense. And the same conclusion I came to.
No though, I have issues with the actual devices from HA not working in the dashboard. I came across a forum saying that it has something to do with nginx not being configured correctly. But when I install NGINX on hass.io it won’t start. So that makes it kind of hard to configure it. Do you happen to know anything about that?
@bagger
Appdaemon is not yet able to use the nginx reverse proxy. So you are not able to configure it like HA.
Anyways you should get it running first on your home network without any extra software getting in the way.
If you are trying to access http://192.168.0.133:5050/hello, then it suggests that you are at home on your own wired / wireless network. Then you do not need nginx in the middle.
You only need nginx if you want to “hide” your HA machine and port from the eyes of others.
Ha listens on 8123 port, nginx listens on 80 or 443.
So bad people know that port 8123 is HA, and then they know how to attack your system, and if you are controlling locks, then it is not a good thing to have your house hacked. But if you are using nginx, then it seems that it is listenting on port 80/443 which is standard http(s), and it does not tell you what is the software behind it.
