What happens if you navigatè to http://192.168.xx.xx:5050/api/appdaemon/state/default/light.kitchen_right in your browser?
Thanks @Burningstone, I’ll try to craft mine around yours and see if I get any better luck. Will keep you posted.
I did and the only thing that I have on the page was that : “404: Not Found”
Ok, so the Appdaemon rest api is not working for some reason.
Try adding the api: and admin: entries to your appdaemon.yaml. Restart Appdaemon and then goto http://192.168.xx.xx:5050 and click on entities and see if all your HA entities are listed there.
1 Like
Updated:
I was looking in the wrong place …
So under “hass” . I see all my entities
BTW, thanks to all for your assistance !!
OK … further more I was just able to load one of my dashboards without seeing any Java errors, so I am on the right path … now I just need to read the docs on skins (css) as what I have does not seem to work at this time, but this is minimal.
Thanks again to everyone for your help
1 Like
I figured out the issue. I commented it out following then AD worked.
logsize: 100000
log_generations: 3
great to hear you figured it out.
How do I use admin interface?
I added following to appdaemon.yaml file.
admin:
title: AppDaemon
stats_update: realtime
http:
url: http://192.168.86.226:5050
When I browse to 192.168.86.226:5050 I get the following error message. All the content in the admin GUI is empty.
Error getting state, check Java Console for details
From Chrome Dev Console:
Failed to load resource: the server responded with a status of 404 (Not Found)
:5050/api/appdaemon/state:1
Do you have the api: entry in your appdaemon.yaml?
2 Likes
Had the same problem. Api fixes it, thanks
1 Like
thx. for that correct answer @tjntomas
it wasnt intended, deshalb it isnt in the docs, but in AD 4 admin depends on api.
actually are admin: api: and hadashboard: all connected together, they all depend on http:
1 Like
Bingo! That solved the issue. 
1 Like
I’m still seeing issues on my config:
2020-02-05 17:06:42.733849 INFO AppDaemon: AppDaemon Version 4.0.1 starting
2020-02-05 17:06:42.734017 INFO AppDaemon: Python version is 3.8.1
2020-02-05 17:06:42.734176 INFO AppDaemon: Configuration read from: /conf/appdaemon.yaml
2020-02-05 17:06:42.734319 INFO AppDaemon: Added log: AppDaemon
2020-02-05 17:06:42.734477 INFO AppDaemon: Added log: Error
2020-02-05 17:06:42.734620 INFO AppDaemon: Added log: Access
2020-02-05 17:06:42.734756 INFO AppDaemon: Added log: Diag
2020-02-05 17:06:42.734906 ERROR AppDaemon: time_zone not specified in appdaemon.cfg
2020-02-05 17:06:42.735042 ERROR AppDaemon: latitude not specified in appdaemon.cfg
2020-02-05 17:06:42.735174 ERROR AppDaemon: longitude not specified in appdaemon.cfg
2020-02-05 17:06:42.735309 ERROR AppDaemon: elevation not specified in appdaemon.cfg
Here is my appdaeomon.yaml:
secrets: /conf/secrets.yaml
logs:
main_log:
filename: /conf/logs/appdaemon.log
error_log:
filename: /conf/logs/error.log
access_log:
filename: /conf/logs/access.log
appdaemon:
time_zone: 'America/Los_Angeles'
latitude: !secret lat
longitude: !secret long
elevation: 239
app_dir: /conf/apps
plugins:
HASS:
type: hass
namespace: hass
ha_url: !ha_url
token: !secret token
api:
http:
url: http://192.168.11.225:5050
hadashboard:
admin:
title: AppDaemon
stats_update: realtime
And my test docker script:
docker run --rm -it -p 5050:5050 acockburn/appdaemon:latest
Just to make sure, do you have a secrets.yaml file in the same directory?
Also this
ha_url: !ha_url
should be this:
ha_url: !secret ha_url
i think you are somehow editing the wrong appdaemon.yaml
because your appdaemon.yaml that you show here contains the right latitude, longtitude, etc.
but AD sees an appdaemon.yaml that doesnt contain those values.
I am assuming that you are not using hass.io.
You are not mapping the drive to your config directory in your docker run command. Try with:
docker run --rm -it -p 5050:5050 -v /path_to_your_config_folder:/conf acockburn/appdaemon:latest
If that fails, try a passing all environment parameters in the docker run command, i.e.
docker run --rm -it -p 5050:5050 -v /path_to_your_config_folder:/conf -e HA_URL="http://192.168.xx.xx:8123" -e TOKEN="YOUR_TOKEN" -e DASH_URL="http://192.168.11.225:5050" acockburn/appdaemon:latest
Thanks for catching this! Yes I have a secrets.yaml in the same directory.
aaah … I cannot believe I did that…! Thank you – it’s working now!
Really pleased with AD 4, but had a small request/question. Previously I was using: Fullscreen images (cameras, weather radars) on click for HADashboard to maximize/minimize my camera stream on keypress. AD 4 seems take the user to the actual stream on key press and then user is unable to easily move back. Is there anyway to mimic the functionality I had before?