I’m not sure - maybe someone who knows Docker better than me can answer? I am trying to set the hub up so it will build tagged builds which would presumably mean you could choose the one you want but I haven’t figured it out yet.
Thanks for the heads up - I’ll see if I can fix it.
I had that initially, so then I tried to roll back to the old version, which then didn’t work either (same issue), and so I started to think it was something else. Checked default pythons versions, etc, went forward again, trying installs/upgrades/etc and somehow it started working even though I don’t think I changed anything 
I checked the latest non dev version and that seems OK
What’s the best way to try this in hassio?
waiting for the moment that someone makes the efford to create an AD 3.0 addon 
I’ve got it installing just need to update my files
@matt2005 @ReneTode
I’m kinda holding back to publish the add-on with a beta version of AppDaemon.
Since Hass.io does not support beta versions/stability channels and the fact that Hass.io users simply “expect” things to work.
i already have more then enough problems helping people that install AD on hassio, so i am absolutely not sad about that
but if i remember correct there is also the option that others built addons because they like a certain thing to work.
and as soon as someone made one, and another asks for it, i will point to the made addon.
for now i dont know of any, so i say people that they have to wait till someone creates it.
That’s fine. I’m currently aware of 1 issue with my add-on, which will be fixed in the upcoming release. (Raspberry Pi 1/Zero).
If you run into other issues, please let me know. I’m actively developing and fixing issues on all Hassio Community Add-ons.
/off-topic. Back on track.
most of the time its not about issues but about people nwing how to work with the platform and with AD, combined with the fact that i really have never seen hassio, and only know about disadvantages
and even if there was an issue with an addon, i probably wouldnt recognise it as such
Because of breaking changes, wouldn’t it be safer to publish a new addon “AppDaemon 3”? Even when AD3 will be out of beta, someone will still need to install AD2 for compatibility.
@namadori… OK, so why did I not think about that? Thank you!
This is going to be a busy weekend
That will be followed by a couple of busy nights on my side 
BTW, thanks for your great work, HADashboard was a great improvement in my daily HA usage. 
then you better thank @aimc because he created it
all that frenck did was make a connection between hassio and appdaemon (not that its nothing but there are months of work from Andrew in AD)
I think a Goodyear blimp throwing “thank you” fliers over for each one of the contributors of HA and add-ons wouldn’t be enough for the time and effort they put in a project for free.
This said, even the smallest contributors like @frenck deserve a Thank You every now and then…
(I hope everyone gets this is a joke, I really appreciate frenck’s plugin )
i didnt mean HA i meant Appdaemon and the dashboard. thats from andrew.
but when i look at the addon on github, and even the logs i see come by, i can understand that people think that frenck did create the whole thing.
thats why i make that clear once in a while
After installing the Version 3.0.0b1 and reloading the HADashboard ther error “Error getting state, check Java Console for details” will be displayed for every widget on the dashboard.
All wigets are empty showing no state at all.
This does not happen with chrome. Since on iOS-Devices every browser has to use the apple-webkit there is no workoround for this problem.
There is a similar issue with HA Verion 0.60 and higher, regarding the display of the history graph.
For HA the fronend parameter, javascript_version: es5 has to be set in order to avoid this.
I opened also an issue on github for this
i think you have another problem.
Andrew uses IOS himself, so i cant imagine that he would create something that he couldnt use
did you:
RESOLVED. I had an app_dir: /opt/appdaemon_beta/ line in my appdaemon.yaml. This seems to have messed things up. Was setting the app_dir deprecated?
All of my apps are erroring out when loading.
2018-01-19 10:23:15.457858 INFO AppDaemon: App initialization complete
2018-01-19 10:23:27.558120 INFO AppDaemon: /opt/appdaemon_beta/apps.yaml modified
2018-01-19 10:23:28.186773 INFO AppDaemon Version 3.0.0b1 starting
2018-01-19 10:23:28.186986 INFO Configuration read from: /opt/appdaemon_beta/appdaemon.yaml
2018-01-19 10:23:28.187535 INFO AppDaemon: Starting Apps
2018-01-19 10:23:28.215330 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-01-19 10:23:28.254733 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-01-19 10:23:28.254897 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-01-19 10:23:28.255073 INFO Starting Dashboards
2018-01-19 10:23:28.258056 INFO API is disabled
2018-01-19 10:23:28.262405 INFO AppDaemon: HASS: Connected to Home Assistant 0.61.0
2018-01-19 10:23:28.280100 INFO AppDaemon: Got initial state from namespace default
2018-01-19 10:20:35.656815 INFO AppDaemon: Loading Module: /opt/appdaemon_beta/apps/occusim.py
2018-01-19 10:20:35.662228 WARNING AppDaemon: ------------------------------------------------------------
2018-01-19 10:20:35.662369 WARNING AppDaemon: Unexpected error during loading of outdoor:
2018-01-19 10:20:35.662448 WARNING AppDaemon: ------------------------------------------------------------
2018-01-19 10:20:35.663106 WARNING AppDaemon: Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/appdaemon/appdaemon.py", line 1466, in read_app
if module_name == self.app_config[name]["module"]:
TypeError: string indices must be integers
In this example below, “outdoor” refers to an item in my secrets.yaml:
outdoor: http://10.0.1.22:8123/api/camera_proxy_stream/camera.outdoor?token=A_TOKEN&api_password=A_PASSWORD
After chasing this, and putting " around the URL above, the error moves to a different item in secrets.yaml. After adding double quotes there, the error moves to:
2018-01-19 10:23:30.331075 WARNING AppDaemon: ------------------------------------------------------------
2018-01-19 10:23:30.331233 WARNING AppDaemon: Unexpected error during loading of log:
2018-01-19 10:23:30.331314 WARNING AppDaemon: ------------------------------------------------------------
2018-01-19 10:23:30.331968 WARNING AppDaemon: Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/appdaemon/appdaemon.py", line 1466, in read_app
if module_name == self.app_config[name]["module"]:
KeyError: 'module'