No sensor data in dashboard

Running Hassio and Appdaemon3. Suddenly not getting any sensor data in dashboard.
When opening dashboard, I am getting several errors: Error getting state, check Java Console for details

Apart from empty widgets, dashboard is loading ok.

Systemlog:

18-03-03 09:01:51 ERROR (MainThread) [hassio.addons.addon] Addon core_configurator have wrong options: Missing required option ‘password’. Got {‘username’: ‘admin’, ‘password’: None, ‘certfile’: ‘fullchain.pem’, ‘keyfile’: ‘privkey.pem’, ‘ssl’: False, ‘allowed_networks’: [‘192.168.0.0/16’], ‘banned_ips’: [‘8.8.8.8’], ‘ignore_pattern’: [‘pycache’]}
18-03-03 09:01:51 INFO (SyncWorker_0) [hassio.docker.interface] Clean hassioaddons/appdaemon3-armhf docker application
18-03-03 09:01:54 INFO (SyncWorker_0) [hassio.docker.addon] Start docker addon hassioaddons/appdaemon3-armhf with version 0.1.0
18-03-03 09:01:55 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons/a0d7b954_appdaemon3/info
18-03-03 09:01:55 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons/a0d7b954_appdaemon3/info
18-03-03 09:01:56 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons/a0d7b954_appdaemon3/info
18-03-03 09:01:56 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons/a0d7b954_appdaemon3/info
18-03-03 09:01:56 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons
18-03-03 09:01:56 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons/a0d7b954_appdaemon3/info
18-03-03 09:01:57 WARNING (MainThread) [hassio.api.security] Invalid token for access /addons
18-03-03 09:01:57 INFO (MainThread) [hassio.api.security] /addons/a0d7b954_appdaemon3/info access from a0d7b954_appdaemon3
18-03-03 09:01:58 INFO (MainThread) [hassio.api.security] /addons/a0d7b954_appdaemon3/info access from a0d7b954_appdaemon3
18-03-03 09:01:58 INFO (MainThread) [hassio.api.security] /supervisor/info access from a0d7b954_appdaemon3

did you change anything?

Nope, however,itstarted working again. Might have been someting on the browser-side.