Hello,
I am using
Hass.io Add-on: AppDaemon v1.3.0 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant From: Community Hass.io Add-ons By: Franck Nijhof <[email protected]>
on Home Assistant 0.75.2 and HassOS 1.9
I edited dashboard and since that cannot open it at all.
Neither AppDaemon restart nor HomeAssistant reboot did not help.
Not even AppDaemon reinstall
There are several strange lines in the AppDaemon log:

Traceback (most recent call last): File "/usr/bin/appdaemon", line 7, in <module> from appdaemon.admain import main File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 2, in <module> from pkg_resources import parse_version File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 73, in <module> __import__('pkg_resources.extern.packaging.specifiers') File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 674, in exec_module File "<frozen importlib._bootstrap_external>", line 779, in get_code File "<frozen importlib._bootstrap_external>", line 487, in _compile_bytecode ValueError: bad marshal data (unknown type code)

Any idea how to recover functionality?

Problem/Motivation

I would like to use Pillow library in Hassio AppDaemon addon 4.0.3 but I'm not able to make it works.
I correctly added Pillow in my python_packages addon configuration

Expected behavior

AppDaemon start and load Pillow python package in order to use it in my MQTT app.

Actual behavior

`2019-09-18 14:51:46.848696 INFO AppDaemon Version 3.0.5 starting
2019-09-18 14:51:46.849731 INFO Configuration read from: /config/appdaemon/appdaemon.yaml
2019-09-18 14:51:46.854672 INFO AppDaemon: Starting Apps
2019-09-18 14:51:46.864382 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2019-09-18 14:51:47.389537 INFO AppDaemon: HASS: HASS Plugin Initializing
2019-09-18 14:51:47.390641 INFO AppDaemon: HASS: HASS Plugin initialization complete
2019-09-18 14:51:47.391383 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin
2019-09-18 14:51:47.409693 INFO AppDaemon: MQTT: MQTT Plugin Initializing
2019-09-18 14:51:47.410638 INFO AppDaemon: MQTT: Using 'mqtt client status' as Will Topic
2019-09-18 14:51:47.411503 INFO AppDaemon: MQTT: Using 'mqtt client status' as Birth Topic
2019-09-18 14:51:47.412366 INFO AppDaemon: MQTT: Using 'appdaemon_mqtt_client' as Client ID
2019-09-18 14:51:47.414851 INFO Starting Dashboards
2019-09-18 14:51:47.442681 INFO API is disabled
2019-09-18 14:51:47.477778 INFO AppDaemon: HASS: Connected to Home Assistant 0.98.5
2019-09-18 14:51:47.631615 INFO AppDaemon: Got initial state from namespace default
2019-09-18 14:51:49.898925 INFO AppDaemon: MQTT: Connected to Broker at URL 192.168.1.6:1883
2019-09-18 14:51:50.500191 INFO AppDaemon: Got initial state from namespace mqtt
2019-09-18 14:51:50.500992 INFO AppDaemon: MQTT: MQTT Plugin initialization complete
2019-09-18 14:51:51.703038 INFO AppDaemon: Reading config
2019-09-18 14:51:51.717754 INFO AppDaemon: /config/appdaemon/apps/apps.yaml added or modified
2019-09-18 14:51:51.719099 INFO AppDaemon: /config/appdaemon/apps/apps.yaml added or modified
2019-09-18 14:51:51.719546 INFO AppDaemon: App 'telegram_bot' added
2019-09-18 14:51:51.719928 INFO AppDaemon: App 'heating_bot' added
2019-09-18 14:51:51.720293 INFO AppDaemon: App 'ir_remote' added
2019-09-18 14:51:51.720641 INFO AppDaemon: App 'mqtt_handler' added
2019-09-18 14:51:51.721229 INFO AppDaemon: Adding /config/appdaemon/apps to module import path
2019-09-18 14:51:51.723176 INFO AppDaemon: Loading App Module: /config/appdaemon/apps/mqtt_handler.py
2019-09-18 14:51:51.765175 WARNING AppDaemon: ------------------------------------------------------------
2019-09-18 14:51:51.765832 WARNING AppDaemon: Unexpected error loading module: /config/appdaemon/apps/mqtt_handler.py:
2019-09-18 14:51:51.766395 WARNING AppDaemon: ------------------------------------------------------------
2019-09-18 14:51:51.773964 WARNING AppDaemon: Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/appdaemon/appdaemon.py", line 2026, in check_app_updates
self.read_app(mod["name"], mod["reload"])
File "/usr/lib/python3.7/site-packages/appdaemon/appdaemon.py", line 1809, in read_app
self.modules[module_name] = importlib.import_module(module_name)
File "/usr/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/config/appdaemon/apps/mqtt_handler.py", line 3, in
from PIL import Image, ImageDraw
File "/usr/lib/python3.7/site-packages/PIL/Image.py", line 95, in
from . import _imaging as core
ImportError: Error loading shared library libjpeg.so.8: No such file or directory (needed by /usr/lib/python3.7/site-packages/PIL/_imaging.cpython-37m-aarch64-linux-gnu.so)

2019-09-18 14:51:51.774566 WARNING AppDaemon: ------------------------------------------------------------
2019-09-18 14:51:51.775028 WARNING AppDaemon: Removing associated apps:
2019-09-18 14:51:51.775554 WARNING AppDaemon: mqtt_handler`

Steps to reproduce

My plugin configuration
{ "disable_auto_token": true, "system_packages": [], "python_packages": [ "transmissionrpc", "Pillow" ] }

Proposed changes

Could you please give me some hint about resolving this issue?

Problem/Motivation

Since the recent update in hass.io appdaemon does not seem to want to start.

Expected behavior

I even tried to uninstall it completely to do a fresh install of appdaemon, yet still with a fresh install it doesnt want to start.

Actual behavior

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
-----------------------------------------------------------
 Add-on version: 2.0.2
 You are running the latest version of this add-on.
 System: HassOS 1.13  (aarch64 / raspberrypi3-64)
 Home Assistant version: 0.91.0
 Supervisor version: 152
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in e.g, GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing... 
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-compiled-dir.sh: executing... 
[cont-init.d] 21-compiled-dir.sh: exited 0.
[cont-init.d] 30-auto-token.sh: executing... 
[14:21:30] INFO: Updating Hass.io API token in AppDaemon with the current one...
[cont-init.d] 30-auto-token.sh: exited 0.
[cont-init.d] 31-ha-url.sh: executing... 
[cont-init.d] 31-ha-url.sh: exited 0.
[cont-init.d] 50-compiled-symlink.sh: executing... 
[cont-init.d] 50-compiled-symlink.sh: exited 0.
[cont-init.d] 80-system-packages.sh: executing... 
[cont-init.d] 80-system-packages.sh: exited 0.
[cont-init.d] 81-python-packages.sh: executing... 
[cont-init.d] 81-python-packages.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:21:31] INFO: Starting AppDaemon...
[14:21:32] INFO: Starting AppDaemon...
[14:21:33] INFO: Starting AppDaemon...
[14:21:34] INFO: Starting AppDaemon...
[14:21:35] INFO: Starting AppDaemon...
[14:21:36] INFO: Starting AppDaemon...

Steps to reproduce

Simply update everything to the newest version and you probably will get the same issue.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Appdaemon supports api for remote requests but i think the api_port specified in the appdaemon.yaml is not working

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Developing a AppDaemon Plugin

(Why the issue was filed)
Trying to test the plugin I am working on, and so will need to be able to load it into the plugin folder, so I can test it

Expected behavior

(What you expected to happen)
Access to folder to upload plugin

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

I turned on log_thread_actions by setting to 1, after restart of AppDaemon logging starts, but I noticed that after the log cycled, I was no longer seeing the thread information in the new log

Expected behavior:

continue to see thread messages after log switch

Actual behavior

thread messages stopped on log cycle

Steps to reproduce

turn on log_thread_actions and se if messages are still being delivered to log after log switch

I am running AppDaemon version 3.0.5 in Hass.io

Problem/Motivation

I'm unable to install the Appdaemon addon under hassos.

core-ssh:~# hassio addons install a0d7b954_appdaemon3
Processing... Done.

Error: Unknown Error, see logs
core-ssh:~# hassio info
arch: armv7
channel: stable
hassos: "2.12"
homeassistant: 0.100.3
hostname: hassio
logging: info
machine: raspberrypi3
supervisor: "192"
supported_arch:
- armv7
- armhf
timezone: Europe/Oslo

Expected behavior

Expected addon to be installed

Actual behavior

Addon fails to install

Steps to reproduce

core-ssh:~# hassio addons install a0d7b954_appdaemon3
Processing... Done.

Error: Unknown Error, see logs

Proposed changes

Sorry, no ideas... :)

#Problem/Motivation

Cannot load this add -on for some reason. Below is what the log shows:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon3 v1.0.1
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 03-version-requirements.sh: executing... 
Version 103 is not a valid version.Error: "No Major.Minor.Patch elements found"FATAL: You Supervisor version is: 103
FATAL: This add-on requires: >=0.85.0
FATAL: Please consider upgrading.
[cont-init.d] 03-version-requirements.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 50-compiled-symlink.sh: executing... 
[cont-finish.d] 50-compiled-symlink.sh: exited 0.
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

No idea what happened it just stopped working out of no where. Any thoughts guys? Getting a similar issue with the terminal add on. Other addons are working fine.

Problem/Motivation

When trying to style the value of a sensor widget, where the value is text, it doesn't apply the style.

Expected behavior

value_style should be applied for text-value sensor widgets

Actual behavior

value_style isn't applied

Steps to reproduce

• Create a sensor widget with a sensor that has a textual value.
• Add value_style: 'font-weight: 200:' to the widget
• Observe that the style is not replied, as the text is still bold (font-weight: 400).

Proposed changes

Make the value_style work for text value sensors.

Problem/Motivation

I use a custom component which uses emoji

this would be the fix

https://github.com/home-assistant/appdaemon/pull/417/files

this is my issue for my custom component:

https://github.com/benleb/ad-batterycheck/issues/1

Would be nice if someone could take care of this :)

Thanks in advance guys.. You are the best!

(Why the issue was filed)

Expected behavior

Emoji support

(What you expected to happen)

Actual behavior

nemoji support

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

GitHub

Gimme back the emoji! by benleb · Pull Request #417 · home-assistant/appdaemon

Just kidding... This adds a switch to disable the encoding of every log message to ascii. As someone (a german for example) might want to log "Umlaute" (äöü). Also useful if you want to p...

Problem/Motivation

2018-11-04 17:24:11.829047 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-11-04 17:24:16.842162 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-11-04 17:24:21.854504 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-11-04 17:24:26.867869 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-11-04 17:24:31.881642 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I upgraded to 3 and I cant get it to work, I thought I did all the right add and replace from https://appdaemon.readthedocs.io/en/latest/#upgrading-from-2-x , now Im getting more errors. Can I re-download or downgrade reset it? I'm at a loss trying to figure it out??

HA 0.80.0
appdaemon3 1.5.0

Expected behavior

(What you expected to happen)

Actual behavior

LOG
WAS GETTING THIS ERROR BE FOR I MADE THE CHANGES

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon v1.5.0
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / Resin OS 2.3.0+rev1 / HA 0.80.0 / SU 136 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing... 
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-compiled-dir.sh: executing... 
[cont-init.d] 21-compiled-dir.sh: exited 0.
[cont-init.d] 30-auto-password.sh: executing... 
[cont-init.d] 30-auto-password.sh: exited 0.
[cont-init.d] 31-ha-url.sh: executing... 
WARNING: You are using an non-recommended Home Assistant URL!
WARNING: Setting the "ha_url http://hassio/homeassistant" option in your AppDaemon config to
WARNING: "" is recommended!
[cont-init.d] 31-ha-url.sh: exited 0.
[cont-init.d] 50-compiled-symlink.sh: executing... 
[cont-init.d] 50-compiled-symlink.sh: exited 0.
[cont-init.d] 80-system-packages.sh: executing... 
[cont-init.d] 80-system-packages.sh: exited 0.
[cont-init.d] 81-python-packages.sh: executing... 
[cont-init.d] 81-python-packages.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml
ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml
ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml
ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml

**NOW I'M GETTING THIS**

> data = constructor(self, node)
  File "/usr/lib/python3.6/site-packages/appdaemon/utils.py", line 101, in _secret_yaml
    raise ValueError("!secret used but no secrets file found")
ValueError: !secret used but no secrets file found
Traceback (most recent call last):
  File "/usr/bin/appdaemon", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 375, in main
    admain.main()
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 194, in main
    config = yaml.load(config_file_contents)
  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 72, in load
    return loader.get_single_data()
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 37, in get_single_data
    return self.construct_document(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 46, in construct_document
    for dummy in generator:
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 398, in construct_yaml_map
    value = self.construct_mapping(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 204, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 129, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 86, in construct_object
    data = constructor(self, node)
  File "/usr/lib/python3.6/site-packages/appdaemon/utils.py", line 101, in _secret_yaml
    raise ValueError("!secret used but no secrets file found")
ValueError: !secret used but no secrets file found
Traceback (most recent call last):
  File "/usr/bin/appdaemon", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 375, in main
    admain.main()
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 194, in main
    config = yaml.load(config_file_contents)
  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 72, in load
    return loader.get_single_data()
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 37, in get_single_data
    return self.construct_document(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 46, in construct_document
    for dummy in generator:
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 398, in construct_yaml_map
    value = self.construct_mapping(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 204, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 129, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 86, in construct_object
    data = constructor(self, node)
  File "/usr/lib/python3.6/site-packages/appdaemon/utils.py", line 101, in _secret_yaml
    raise ValueError("!secret used but no secrets file found")
ValueError: !secret used but no secrets file found
Traceback (most recent call last):
  File "/usr/bin/appdaemon", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 375, in main
    admain.main()
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 194, in main
    config = yaml.load(config_file_contents)
  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 72, in load
    return loader.get_single_data()
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 37, in get_single_data
    return self.construct_document(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 46, in construct_document
    for dummy in generator:
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 398, in construct_yaml_map
    value = self.construct_mapping(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 204, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 129, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 86, in construct_object
    data = constructor(self, node)
  File "/usr/lib/python3.6/site-packages/appdaemon/utils.py", line 101, in _secret_yaml
    raise ValueError("!secret used but no secrets file found")
ValueError: !secret used but no secrets file found
Traceback (most recent call last):
  File "/usr/bin/appdaemon", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 375, in main
    admain.main()
  File "/usr/lib/python3.6/site-packages/appdaemon/admain.py", line 194, in main
    config = yaml.load(config_file_contents)
  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 72, in load
    return loader.get_single_data()
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 37, in get_single_data
    return self.construct_document(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 46, in construct_document
    for dummy in generator:
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 398, in construct_yaml_map
    value = self.construct_mapping(node)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 204, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 129, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 86, in construct_object
    data = constructor(self, node)
  File "/usr/lib/python3.6/site-packages/appdaemon/utils.py", line 101, in _secret_yaml
    raise ValueError("!secret used but no secrets file found")
ValueError: !secret used but no secrets file found

before and after screen shot

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml
I had it working and not sure what happened I tried to uninstall then reinstall and nothing.

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

New install on HASS.IO with HASS 0.84.3, does not connect to home assistant

Expected behavior

Connect to Home Assistant

Actual behavior

errors in add-on log:
2018-12-18 10:25:25.332573 INFO AppDaemon Version 3.0.2 starting
2018-12-18 10:25:25.333208 INFO Configuration read from: /config/appdaemon/appdaemon.yaml
2018-12-18 10:25:25.335767 INFO AppDaemon: Starting Apps
2018-12-18 10:25:25.343033 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-12-18 10:25:25.443029 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-12-18 10:25:25.443995 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-12-18 10:25:25.444447 INFO Starting Dashboards
2018-12-18 10:25:25.454124 INFO API is disabled
2018-12-18 10:25:25.485412 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds

Errors in HASS log:
Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/handles/stream.pyx", line 609, in uvloop.loop.UVStream._on_eof
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:841)

Error doing job: SSL error errno:1 reason: TLSV1_ALERT_UNKNOWN_CA
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:841)

Steps to reproduce

Start App Daemon Add-on inside Hass.io installation. I do have a custom URL with Duckdns as well as https through letsencrypt, and looking at the appdaemon.yaml in config/appdaemon, it is pointed to the correct url, but the cert_path is pointed to an old version of my cert, which isnt fixed when I try to replace that old cert (they are pointed to /config/appdaemon/fullchain.pem, instead of /ssl/fullchain.pem which I thought was standard for add ons?)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I had a working app that relied on pycurl, which relies on curl-dev and python3-dev, as configured below.

{
  "disable_auto_token": false,
  "system_packages": [
    "libcurl",
    "python3-dev",
    "curl-dev",
    "g++"
  ],
  "python_packages": [
    "pycurl"
  ],
  "log_level": "info"
}

Expected behavior

python3-dev and other packages install successfully and appdaemon addon starts

Actual behavior

Recently the appdaemon addon started failing on startup with an error message, even with a fresh install:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
-----------------------------------------------------------
 Add-on version: 4.1.0
 You are running the latest version of this add-on.
 System: null  (armv7 / raspberrypi3)
 Home Assistant version: 0.99.3
 Supervisor version: 192
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] appdaemon.sh: executing... 
[21:43:39] INFO: Updating Hass.io API token in AppDaemon with the current one...
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/armv7/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/community/armv7/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/armv7/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/armv7/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/armv7/APKINDEX.tar.gz
v3.10.3-19-g7f993019c4 [http://dl-cdn.alpinelinux.org/alpine/v3.10/main]
v3.10.3-13-g8068beb776 [http://dl-cdn.alpinelinux.org/alpine/v3.10/community]
v20190925-2928-ge246b4559e [http://dl-cdn.alpinelinux.org/alpine/edge/main]
v20190925-2928-ge246b4559e [http://dl-cdn.alpinelinux.org/alpine/edge/community]
v20190925-1761-g0908eb7459 [http://dl-cdn.alpinelinux.org/alpine/edge/testing]
OK: 24377 distinct packages available
OK: 71 MiB in 34 packages
ERROR: unsatisfiable constraints:
  python3-3.7.3-r0:
    breaks: python3-dev-3.7.5-r1[python3=3.7.5-r1]
    satisfies: world[python3=3.7.3-r0]
[21:43:47] FATAL: Failed installing package python3-dev
[cont-init.d] appdaemon.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] appdaemon.sh: executing... 
[cont-finish.d] appdaemon.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Steps to reproduce

Install the current version of the addon (4.1.0) and start it with the above configuration

Proposed changes

I'm guessing a version bump is needed somewhere (Dockerfile), but I'm unsure how this is all wired up,

Problem/Motivation

I would like to use an app that requires AD 4.

Expected behavior

Update the hassio addon to AD v4.

Actual behavior

AD v3.0.5 is used.

Edit: I'll keep and update the instructions here.

Problem/Motivation

Keeps removing !secret from my appdaemon config file when updating the addon or hassio

Expected behavior

the !secret annotation stays in the config

Actual behavior

it removes !secret from !secret token

Problem/Motivation

There are several reasons for this:

• Not all log messages are consistent across all add-ons.
• Some messages are unclear to the novice user.

http://appdaemon.readthedocs.io/en/latest/HISTORY.html#b3-2018-02-11

Problem/Motivation

The addon seems to overwrite the ha_key when it restarts. I tried to replace it with:

ha_key: !secret home_assistant_key

But it is replaced by the actual key whenever the plugin starts.

I don’t really understand the consequences of this, I’m just trying to clean up my repo before publishing it on GitHub (I have some custom widgets to share).

This behavior only occurs when the internal hassio URL is used, as recommended by the add-on manual.

Expected behavior

The manual set ha_key: !secret home_assistant_key to be persistent between add-on restarts

Actual behavior

The value gets replaced by the API token.

Steps to reproduce

See above

Proposed changes

Don't change the ha_key in case it is being fetched from the secrets file.

Ref

https://community.home-assistant.io/t/community-hass-io-add-on-appdaemon/41261/113?u=frenck
AppDaemon/appdaemon#280

Problem/Motivation

Hi, I am facing a cache issue with HA Dashboards using AppDaemon. I make changes to the dashboard file with new switches and they dont get reflected as all my browsers cache the previous copy. I have tried 2 desktops and mobile phone , they all show cached data. When I switch to private browsing , I am able to see new changes. Can anyone advise how to avoid this behavior?

Expected behavior

Any changes to the dashboard file should be visible on the browser after a restart of App Daemon.

Actual behavior

The browsers keep on showing cached view, I havent cleared the browser cache but I do believe that clearing will solve the issue but that's not the solution I am looking for.

Steps to reproduce

Make changes to a dashboard file , say add a new switch. Refresh the dashboard on your browser, it shows a cached view. I am able to reproduce this on my iPhone, desktop chrome & Firefox.

Proposed changes

As a workaround , view the same in private mode and you will be able to see the changes.
describe the rationale behind it)

I’m trying to get it to start up but I only get a error
I have made a screenshot of the log and in the picture you can also see system information

Problem/Motivation

having !secret in apps.yaml no longer works

Expected behavior

!secret is parsed in apps.yaml as was the case prior to last release

Actual behavior

2019-04-02 22:19:17.599568 INFO API is disabled
2019-04-02 22:19:17.629602 INFO AppDaemon: HASS: Connected to Home Assistant 0.90.2
2019-04-02 22:19:18.014390 INFO AppDaemon: Got initial state from namespace default
2019-04-02 22:19:22.822573 INFO AppDaemon: Reading config
2019-04-02 22:19:23.217004 WARNING AppDaemon: Error loading configuration
2019-04-02 22:19:23.217780 WARNING AppDaemon: parser says
2019-04-02 22:19:23.218490 WARNING AppDaemon:   in "<unicode string>", line 79, column 15:
          gw_mac: !secret xiaomi_mac
                  ^
2019-04-02 22:19:23.218930 WARNING AppDaemon: could not determine a constructor for the tag '!secret'
2019-04-02 22:19:23.220558 WARNING AppDaemon: File '/config/appdaemon/apps/apps.yaml' invalid structure - ignoring

Steps to reproduce

have a !secret reference in apps.yaml

Proposed changes

Problem/Motivation

Add-on does not start correctly, throws error ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml

Expected behavior

Add-on to start without error

Actual behavior

Add-on starts with error even after uninstall and reinstall, I did configure the appdaemon.yaml file and it error'd with both with and without the updated config.

Hi,
I have HASSIO 0.91.4 with appdaemon addon 3.0.0 and duckduns using SSL access to HTTP GUI with this config:

{
  "disable_auto_token": false,
  "system_packages": [],
  "python_packages": []
}

but when I push on open UI WEB I obtain HTTP URL, but I would obtain HTTPS URL....

19-04-22 16:43:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3
19-04-22 16:43:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-04-22 16:43:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

what I have to change?

regards

Problem/Motivation

System packages are not being installed on addon startup.
Even when I tried to install package inside running image it didn't do it.

Expected behavior

On command apk add py3-psycopg2 system wants to add package

Actual behavior

System do update instead of add packages

Steps to reproduce

root@a0d7b954-appdaemon3:/$ apk add py3-psycopg2
fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
OK: 122 MiB in 54 packages

root@a0d7b954-appdaemon3:/$ apk add py3-psycopg2
OK: 122 MiB in 54 packages

PS: I have x86_64 instances

root@a0d7b954-appdaemon3:/$ uname -a
Linux a0d7b954-appdaemon3 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 Linux

Problem/Motivation

someone wants to use my snmp printer monitor

Expected behavior

pysnmp to be available

Actual behavior

error module pysnmp not found

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

Can you please include pysnmp on the next appdaemon3 and subsequent plugins for hassio?

Problem/Motivation

(Why the issue was filed)
Using system package curl-dev causing Appdaemon not to start

Expected behavior

(What you expected to happen)
Appdaemon to start normally.

Actual behavior

(What actually happened)
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] appdaemon.sh: executing...
[06:55:52] INFO: Updating Hass.io API token in AppDaemon with the current one...
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
v3.10.2-46-gbb3e7ac09b [http://dl-cdn.alpinelinux.org/alpine/v3.10/main]
v3.10.2-42-g95d37f7648 [http://dl-cdn.alpinelinux.org/alpine/v3.10/community]
v20190809-2683-gfa1dd17543 [http://dl-cdn.alpinelinux.org/alpine/edge/main]
v20190809-2698-g6ac0abb933 [http://dl-cdn.alpinelinux.org/alpine/edge/community]
v20190809-2697-g10ebdda859 [http://dl-cdn.alpinelinux.org/alpine/edge/testing]
OK: 25342 distinct packages available
ERROR: unsatisfiable constraints:
libcrypto1.1-1.1.1c-r0:
breaks: openssl-dev-1.1.1d-r0[libcrypto1.1=1.1.1d-r0]
satisfies: world[libcrypto1.1=1.1.1c-r0]
ca-certificates-20190108-r0[so:libcrypto.so.1.1]
python3-3.7.3-r0[so:libcrypto.so.1.1]
libcurl-7.65.1-r0[so:libcrypto.so.1.1]
apk-tools-2.10.4-r2[so:libcrypto.so.1.1]
libssl1.1-1.1.1c-r0[so:libcrypto.so.1.1]
libtls-standalone-2.9.1-r0[so:libcrypto.so.1.1]
libssl1.1-1.1.1c-r0:
breaks: openssl-dev-1.1.1d-r0[libssl1.1=1.1.1d-r0]
satisfies: world[libssl1.1=1.1.1c-r0]
python3-3.7.3-r0[so:libssl.so.1.1]
libcurl-7.65.1-r0[so:libssl.so.1.1]
apk-tools-2.10.4-r2[so:libssl.so.1.1]
libtls-standalone-2.9.1-r0[so:libssl.so.1.1]
[06:55:55] FATAL: Failed installing package curl-dev
[cont-init.d] appdaemon.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

Steps to reproduce

(How can someone else make/see it happen)
Adding curl-dev in system package.
{
"disable_auto_token": false,
"system_packages": [
"curl-dev"
],
"python_packages": [],
"log_level": "info"
}

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

One of my functions that used to work under appdaemon2 returns the following error:

his2 = self.get_state("appdaemon.last_motion", 'history_1')
TypeError: get_state() takes from 1 to 2 positional arguments but 3 were given

Expected behavior

return the value of attribute "history_2"

Actual behavior

TypeError is thrown

Steps to reproduce

invoke a get_state() for an attribute value

Problem/Motivation

My setup is a tablet running AppDaemon in a Fully Kiosk Browser. It sleeps after 30 seconds and wakes up if anything walks in front of the camera. Any setup with sleeping will show the same issues, such as a phone.

Expected behavior

When the device wakes up, the dashboard should refresh all widgets from states immediately.

Actual behavior

Nothing happens until the relevant state changes. The clock updates are a few seconds, but other data
that changes less frequently shows whatever state it had prior to sleeping, regardless of any changes
that have happened in the mean time. For example, data that only updates every minute will show
the old data, possibly hours old, for up to 60 seconds.

Steps to reproduce

Create a hassio sensor that updates every 60 seconds:

  - platform: rest
    resource: http://now.httpbin.org/
    name: "HttpBinTime"
    scan_interval: 60
    value_template: '{{ value_json.now.iso8601 }}'

and a corresponding dashboard element:

layout:
    - test

test:
    widget_type: sensor
    entity: sensor.httpbintime

Observe that it works if you keep watching it. Now open it on a phone (so that you can trust it to sleep). Wait 10 minutes, turn on phone, see that time is out of date. It helps to view it on another device so you can easily switch to it just after it changes and so see that it does indeed take 60 seconds to refresh.

Proposed changes

Have some javascript in the outer wrapper that observes the time every 0.5 seconds and
refreshes all widgets if the amount of clock time that passes between checks is more than 10
seconds.

Problem/Motivation

(Why the issue was filed)

My dashboards correctly display current state from home assistant so I know they are communicating. However if I try to control anything from the dashboard it doesn't do anything. Upon inspection of home assistant logs I see : [homeassistant.components] homeassistant/turn_on cannot be called without entity_id

appdaemon addon v1.3.0
Home Assistant v0.73.2

(10 hrs later)(I posted this in the appdaemon git incorrectly)
AppDaemon/appdaemon#346

I finally got it working again, and have narrowed it down to the ha_key in the configuration being auto set. :
[cont-init.d] 30-auto-password.sh: executing...
INFO: ha_key is missing in the AppDaemon configuration, fixing...
After which the key is set in the conf file, but my HA instance has no key. If I change the ha_url from http://hassio/homeassistant to http://172.17.0.1:8123 (which I got from the HAdashboard v2 addon which worked) and delete ha_key it works again!

Expected behavior

(What you expected to happen)

Blank key kept instead of replacing with a key that does not exist

Actual behavior

(What actually happened)

ha_key is created/replaced with some random key.

Steps to reproduce

(How can someone else make/see it happen)

Have no key in homeassistant.
delete ha_key from appdaemon.yaml or leave it empty
Restart appdaemon addon.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Running add-on 1.2.0 with Hassio 0.73.1 on RPI3

Problem

Yesterday everything was running fine and this morning the add-on is indicating it is running in the Home Assistant interface but the 192.168.....:5050 is not loading anymore (HA Dashboard)

Expected behavior

Loading the dashboards page

Actual behavior

Nothing is loading : ERR_CONNECTION_REFUSED

Steps to reproduce

Saddly I don't know!

What I did

1. Restart add-on
2. Uninstal / Re-install
3. Restart Hassio
4. Reboot RP3
5. Restart Network (router)
6. Restore an older snaphot from HomeAssistant (including the Add-On)
7. Wipe, than restore an even older snap shot from HomeAssistant (EXcluding the Add-On)

AppDaemon log (Debug level) :

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon v1.2.0
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
DEBUG: Requested API resource: http://hassio/supervisor/ping
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {}}
DEBUG: Requested API resource: http://hassio/addons/a0d7b954_appdaemon3/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "AppDaemon", "slug": "a0d7b954_appdaemon3", "description": "Python Apps and HADashboard using AppDaemon 3.x for Home Assistant", "long_description": "# Community Hass.io Add-ons: AppDaemon\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\nPython Apps and HADashboard for Home Assistant\n\n## About\n\nAppDaemon is a loosely coupled, multithreaded, sandboxed python execution\nenvironment for writing automation apps for Home Assistant home automation\nsoftware. It also provides a configurable dashboard (HADashboard) suitable\nfor wall mounted tablets.\n\n[Click here for the full documentation][docs]\n\n![HADashboard screenshot][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/330944238910963714.svg\n[discord]: https://discord.gg/c5DvZ4e\n[docs]: https://github.com/hassio-addons/addon-appdaemon3/blob/v1.2.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-appdaemon3/41261?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2018.svg\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-production%20ready-brightgreen.svg\n[release-shield]: https://img.shields.io/badge/version-v1.2.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-appdaemon3/tree/v1.2.0\n[screenshot]: https://github.com/hassio-addons/addon-appdaemon3/raw/master/images/screenshot.png", "version": "1.2.0", "auto_update": true, "repository": "a0d7b954", "last_version": "1.2.0", "state": "started", "boot": "auto", "options": {"log_level": "debug", "system_packages": [], "python_packages": []}, "url": "https://community.home-assistant.io/t/community-hass-io-add-on-appdaemon3/41261?u=frenck", "detached": false, "build": false, "network": {"5000/tcp": 5000, "5050/tcp": 5050}, "host_network": false, "host_ipc": false, "host_dbus": false, "privileged": null, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "http://[HOST]:5050", "stdin": false, "hassio_api": true, "homeassistant_api": true, "gpio": false, "devicetree": false, "audio": false, "audio_input": null, "audio_output": null, "services": null, "discovery": null}}
DEBUG: Filtering response using: .version
DEBUG: Requested API resource: http://hassio/addons/a0d7b954_appdaemon3/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "AppDaemon", "slug": "a0d7b954_appdaemon3", "description": "Python Apps and HADashboard using AppDaemon 3.x for Home Assistant", "long_description": "# Community Hass.io Add-ons: AppDaemon\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\nPython Apps and HADashboard for Home Assistant\n\n## About\n\nAppDaemon is a loosely coupled, multithreaded, sandboxed python execution\nenvironment for writing automation apps for Home Assistant home automation\nsoftware. It also provides a configurable dashboard (HADashboard) suitable\nfor wall mounted tablets.\n\n[Click here for the full documentation][docs]\n\n![HADashboard screenshot][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: https://img.shields.io/discord/330944238910963714.svg\n[discord]: https://discord.gg/c5DvZ4e\n[docs]: https://github.com/hassio-addons/addon-appdaemon3/blob/v1.2.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: https://community.home-assistant.io/t/community-hass-io-add-on-appdaemon3/41261?u=frenck\n[maintenance-shield]: https://img.shields.io/maintenance/yes/2018.svg\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-production%20ready-brightgreen.svg\n[release-shield]: https://img.shields.io/badge/version-v1.2.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-appdaemon3/tree/v1.2.0\n[screenshot]: https://github.com/hassio-addons/addon-appdaemon3/raw/master/images/screenshot.png", "version": "1.2.0", "auto_update": true, "repository": "a0d7b954", "last_version": "1.2.0", "state": "started", "boot": "auto", "options": {"log_level": "debug", "system_packages": [], "python_packages": []}, "url": "https://community.home-assistant.io/t/community-hass-io-add-on-appdaemon3/41261?u=frenck", "detached": false, "build": false, "network": {"5000/tcp": 5000, "5050/tcp": 5050}, "host_network": false, "host_ipc": false, "host_dbus": false, "privileged": null, "apparmor": "default", "devices": null, "icon": true, "logo": true, "changelog": true, "webui": "http://[HOST]:5050", "stdin": false, "hassio_api": true, "homeassistant_api": true, "gpio": false, "devicetree": false, "audio": false, "audio_input": null, "audio_output": null, "services": null, "discovery": null}}
DEBUG: Filtering response using: .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing... 
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-compiled-dir.sh: executing... 
[cont-init.d] 21-compiled-dir.sh: exited 0.
[cont-init.d] 30-auto-password.sh: executing... 
[cont-init.d] 30-auto-password.sh: exited 0.
[cont-init.d] 31-ha-url.sh: executing... 
WARNING: You are using an non-recommended Home Assistant URL!
WARNING: Setting the "ha_url" option in your AppDaemon config to
WARNING: "http://hassio/homeassistant" is recommended!
[cont-init.d] 31-ha-url.sh: exited 0.
[cont-init.d] 50-compiled-symlink.sh: executing... 
[cont-init.d] 50-compiled-symlink.sh: exited 0.
[cont-init.d] 80-system-packages.sh: executing... 
[cont-init.d] 80-system-packages.sh: exited 0.
[cont-init.d] 81-python-packages.sh: executing... 
[cont-init.d] 81-python-packages.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

The only thing i'm seeing in those lines is that :

WARNING: You are using an non-recommended Home Assistant URL!
WARNING: Setting the "ha_url" option in your AppDaemon config to
WARNING: "http://hassio/homeassistant" is recommended!

But my config file for app daemon is showing that exact URL

secrets: /config/secrets.yaml
log:
  logfile: STDOUT
  errorfile: STDERR
appdaemon:
  threads: 10
  app_dir: /config/appdaemon/apps
  plugins:
    HASS:
      type: hass
      ha_url: http://hassio/homeassistant
      ha_key: MY_KEY!
hadashboard:
  dash_url: http://127.0.0.1:5050
  dash_dir: /config/appdaemon/dashboards

And now I'm out of idea :(

Problem/Motivation

The following snippet used to work. I think prior to 0.67 of HASSIO

sample code snippet

def run_rainfall_callback(self, kwargs):
  self.Target = kwargs["Target"]
  self.Source= kwargs["Source"]
  self.log("Run rainfall update {} with {}".format(self.Target,self.Source))
  TargetValue=float(self.get_state(self.Target))
  SourceValue=float(self.get_state(self.Source))
  self.log("Target = {}".format(TargetValue))	
  self.log("Source = {}".format(SourceValue))
  TargetValue=TargetValue+SourceValue
  if TargetValue <= 2.0 :
    TargetValue=0.0
  else :
    TargetValue=TargetValue - 2.0
  self.log("Target = {}".format(TargetValue))
  self.call_service("input_number/set_value", entity_id = self.Target, value = str(self.get_state(self.Target)))	
  # or just self.set_value(self.Target,TargetValue)
  self.log("New Target = {}".format(float(self.get_state(self.Target))))

Expected behavior

(What you expected to happen)

2018-04-25 03:24:30.210216 INFO UpdateRainfall: Run rainfall set to execute
2018-04-25 03:25:00.012018 INFO UpdateRainfall: Run rainfall update input_number.pws_accumulated_rainfall with sensor.bom_melbourne_rain_today
2018-04-25 03:25:00.019711 INFO UpdateRainfall: Target = 5.2
2018-04-25 03:25:00.026737 INFO UpdateRainfall: Source = 0.6
2018-04-25 03:25:00.033686 INFO UpdateRainfall: Target = 3.8
2018-04-25 03:25:00.920099 INFO UpdateRainfall: New Target = 3.8

(What actually happened)

2018-04-25 03:24:30.210216 INFO UpdateRainfall: Run rainfall set to execute
2018-04-25 03:25:00.012018 INFO UpdateRainfall: Run rainfall update input_number.pws_accumulated_rainfall with sensor.bom_melbourne_rain_today
2018-04-25 03:25:00.019711 INFO UpdateRainfall: Target = 5.2
2018-04-25 03:25:00.026737 INFO UpdateRainfall: Source = 0.6
2018-04-25 03:25:00.033686 INFO UpdateRainfall: Target = 3.8
2018-04-25 03:25:00.920099 INFO UpdateRainfall: New Target = 5.2

Steps to reproduce

Run the code snippet.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Other information.
home-assistant.log records no error. However, if I do not have any 'input_text' entities defined (I have created a dummy to try to work around the issue) and call set_value then home-assistant.log records an error similar to 'no such service input_text/set_value'

Note: calling input_number.set value from home assistant works as expected.

Expected behavior

For AppDaemon to start and connect to HA

Actual behavior

AppDemon disconnects from HA as soon as it connects

Versions

HassOS 1.7
Supervisor 127
HA 0.76.0
AppDaemon Addon 1.4.1

appdaemon.yaml

log:
  logfile: STDOUT
  errorfile: STDERR
appdaemon:
  threads: 10
  app_dir: /config/appdaemon/apps
  time_zone: Pacific/Auckland
  plugins:
    HASS:
      type: hass
      ha_url: http://hassio/homeassistant
      ha_key: **REMOVED**
hadashboard:
  dash_url: **REMOVED**
  dash_dir: /config/appdaemon/dashboards

Logs

2018-08-21 20:21:06.640902 INFO AppDaemon: HASS: Connected to Home Assistant 0.76.0 
2018-08-21 20:21:06.693647 DEBUG AppDaemon: Event type:ha_disconnected: 
2018-08-21 20:21:06.695088 DEBUG AppDaemon: {} 
2018-08-21 20:21:06.697026 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds 
2018-08-21 20:21:06.698592 WARNING AppDaemon: HASS: ------------------------------------------------------------ 
2018-08-21 20:21:06.700339 WARNING AppDaemon: HASS: Unexpected error: 
2018-08-21 20:21:06.701800 WARNING AppDaemon: HASS: ------------------------------------------------------------ 
2018-08-21 20:21:06.705131 WARNING AppDaemon: HASS: Traceback (most recent call last): 
File "/usr/lib/python3.6/site-packages/appdaemon/plugins/hass/hassplugin.py", line 223, in get_updates 
  result = json.loads(self.ws.recv()) 
File "/usr/lib/python3.6/site-packages/websocket/_core.py", line 302, in recv 
  opcode, data = self.recv_data() 
File "/usr/lib/python3.6/site-packages/websocket/_core.py", line 319, in recv_data 
  opcode, frame = self.recv_data_frame(control_frame) 
File "/usr/lib/python3.6/site-packages/websocket/_core.py", line 332, in recv_data_frame 
  frame = self.recv_frame() 
File "/usr/lib/python3.6/site-packages/websocket/_core.py", line 366, in recv_frame 
  return self.frame_buffer.recv_frame() 
File "/usr/lib/python3.6/site-packages/websocket/_abnf.py", line 383, in recv_frame 
  frame.validate(self.skip_utf8_validation) 
File "/usr/lib/python3.6/site-packages/websocket/_abnf.py", line 162, in validate 
  raise WebSocketProtocolException("rsv is not implemented, yet") 
websocket._exceptions.WebSocketProtocolException: rsv is not implemented, yet 
2018-08-21 20:21:06.706616 WARNING AppDaemon: HASS: ------------------------------------------------------------

Problem/Motivation

I try to navigate to a 2nd dash with a separate skin and then return after an amount of time, for test purposes I've set 3 seconds for now.

in may main dashboard Home.dash I added:
verlichting:
widget_type: navigate
title2: Verlichting
dashboard: Verlichting
skin: Verlichting
args:
timeout: 3
return: Home
skin: Home

Expected behavior

I expected to go to verlichting.dash with skin Verliching and after 3 seconds to return to Home.dash with Home skin

Actual behavior

It returned to Home.dash but with Verlichting skin.

Steps to reproduce

see above

Proposed changes

I see it takes the arguments into the adressline when navigating to the other dash.
/Verlichting?timeout=3&return=Home&skin=Home&skin=Verlichting
after 3 seconds it returned to:
/Home?skin=Verlichting

somehow the &skin=Home got lost.

When I do not add the skin argument (/Verlichting?timeout=3&return=Home&skin=Verlichting) it still comes back with the verlichting skin to home: /Home?skin=Verlichting

I think this is behaviour is good for keeping the selected skin, but for me every dash needs his own skin.

Maybe it's possible to add a skin variable in the .dash file so it loads with the assigned skin and not with the skin passed in the address bar?

Thanks,

Dennis

Problem/Motivation

After update to 3.0.1 my Dash will NOT show GIF's but still shows JPG

(Why the issue was filed)

Expected behavior

Prev to upgrade my dashboard has a 7 day weather (JPG) and a Weather Radar (GIF) that would jump between

(What you expected to happen)

Actual behavior

7 Day weather shows, but Radar now just shows blank, testing url and is working

(What actually happened)

Steps to reproduce

weather2_frame:
widget_type: iframe
title: Weather
refresh: 15
img_list:
- https://icons.wxug.com/data/weather-maps/radar/united-states/cadillac-michigan-region-current-radar-animation.gif
- https://media.fox2detroit.com/media.fox2detroit.com/weather/images/7day_forecast.jpg

(How can someone else make/see it happen)

Proposed changes

not sure

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I run hassio as a VM, alongside the firewall. This means that there's no internet connection when hassio boots up and the add-ons are started. Because I use the python_packages config variable to install third-party packages, the add-on doesn't start at all.

Expected behavior

The add-on waits until internet connection is available.

Actual behavior

Package installation is retried 5 times, after which the add-on terminates.

Steps to reproduce

Add something to python_packages, block the internet connection and start the add-on.

Proposed changes

Maybe the add-on could be configured in such a way that package installs are retried until there is a working internet connection.

Problem/Motivation

AppDaemon doesn't have the same version mdi icons as Home Assistant.
MDI icons version currently in 4.4.95 for HA 0.99.2.

Expected behavior

Show the same icons as configured in HA.

Actual behavior

It shows blank.

Steps to reproduce

Cover device class shutter in HA the default icon is mdi-window-shutter
It doesn't exist in AppDaemon.

Proposed changes

Update the mdi icons to 4.4.95.

Hi! Great job with the version 3 of Appdaemon but I still have the same problem than version 2.

Problem/Motivation

The dashboard is not updated when an entity state changes.

Expected behavior

The state on the dashboard should be updated live when a state change occurs.

Actual behavior

You don't see the new state until a reload page is done on the browser.

Steps to reproduce

Changing the state of a switch through the homeassistant interface and then looking to the dashboard state that it's not updated.

Proposed changes

It's unknown the cause of the problem.

Problem/Motivation

Can't install the addon on Rasbperry Pi3, latest HassOS, latest Hass.io

Expected behavior

Installation :)

Actual behavior

First time HA crashed (required pulling the plug).
Second time it gave an error in HassOS log.

19-03-29 08:44:18 INFO (SyncWorker_4) [hassio.docker.interface] Pull image hassioaddons/appdaemon3-armhf tag 1.7.0. 19-03-29 08:45:06 ERROR (SyncWorker_4) [hassio.docker.interface] Can't install hassioaddons/appdaemon3-armhf:1.7.0 -> 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument").

Steps to reproduce

Simply installing the addon.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Installed the addon and there is error in the logs and dashboard does not show

(Why the issue was filed)

Expected behavior

See the dashboard

(What you expected to happen)

Actual behavior

(What actually happened)
Nothing .. Appdaemon not found

"description": "Python Apps and HADashboard using AppDaemon 3.x for Home Assistant",
"state": "started",
"version": "0.1.0",
"installed": "0.1.0",
"repository": "a0d7b954",
"icon": true,
"logo": true
}
],
"addons_repositories": [
"https://github.com/hassio-addons/repository"
]
} .version
DEBUG: Current Supervisor version: 0.85
DEBUG: Supervisor version condition: >=0.85.0
INFO: Supervisor version requirements checks passed.
[cont-init.d] 03-version-requirements.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing...
TRACE: hass.directory_exists: /config/appdaemon
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-compiled-dir.sh: executing...
[cont-init.d] 21-compiled-dir.sh: exited 0.
[cont-init.d] 50-compiled-symlink.sh: executing...
TRACE: hass.directory_exists: /config/appdaemon/compiled
[cont-init.d] 50-compiled-symlink.sh: exited 0.
[cont-init.d] 80-system-packages.sh: executing...
TRACE: hass.config.has_value: system_packages
TRACE: hass.jq.has_value: /data/options.json .system_packages
TRACE: hass.jq: /data/options.json .system_packages | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value:
[cont-init.d] 80-system-packages.sh: exited 0.
[cont-init.d] 81-python-packages.sh: executing...
TRACE: hass.config.has_value: python_packages
TRACE: hass.jq.has_value: /data/options.json .python_packages
TRACE: hass.jq: /data/options.json .python_packages | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value:
[cont-init.d] 81-python-packages.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
starting version 3.2.4
[services.d] done.
TRACE: hass.config.get: log_level
TRACE: hass.config.exists: log_level
TRACE: hass.jq.exists: /data/options.json .log_level
TRACE: hass.jq: /data/options.json .log_level
TRACE: hass.jq.is_string: /data/options.json .log_level
TRACE: hass.jq.is: /data/options.json .log_level string
TRACE: hass.jq: /data/options.json .log_level | if type=="string" then true else false end
TRACE: hass.jq: /data/options.json .log_level // empty
TRACE: hass.string.lower: trace
ERROR no 'appdaemon' section in /config/appdaemon/appdaemon.yaml
TRACE: hass.config.get: log_level
TRACE: hass.config.exists: log_level
TRACE: hass.jq.exists: /data/options.json .log_level
TRACE: hass.jq: /data/options.json .log_level

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Using system package curl-dev causing Appdaemon not to start

(Why the issue was filed)
to get it started

Expected behavior

start normal

(What you expected to happen)
would be very nice to get a hint / a solution

Actual behavior

my config

{
"disable_auto_token": false,
"system_packages": [
"libcurl",
"python3",
"python3-dev",
"curl-dev",
"gcc",
"g++"
],
"python_packages": [
"hass-apps",
"pip==19.2.3",
"pycurl",
"bluepy==1.3.0"
]
}

(What actually happened)
LOG:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...

Hass.io Add-on: AppDaemon
Python Apps and HADashboard using AppDaemon 3.x for Home Assistant

Add-on version: 4.1.0
You are running the latest version of this add-on.
System: Ubuntu 18.04.3 LTS (amd64 / qemux86-64)
Home Assistant version: 0.103.3
Supervisor version: 193

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] appdaemon.sh: executing...
[22:16:06] INFO: Updating Hass.io API token in AppDaemon with the current one...
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
v3.10.3-114-ga27739f065 [http://dl-cdn.alpinelinux.org/alpine/v3.10/main]
v3.10.3-110-g913c88060d [http://dl-cdn.alpinelinux.org/alpine/v3.10/community]
v20191219-394-ge993a59437 [http://dl-cdn.alpinelinux.org/alpine/edge/main]
v20191219-398-g4846b3fec5 [http://dl-cdn.alpinelinux.org/alpine/edge/community]
v20191219-390-gb1607cc1ff [http://dl-cdn.alpinelinux.org/alpine/edge/testing]
OK: 25705 distinct packages available
OK: 76 MiB in 33 packages
OK: 76 MiB in 33 packages
(1/3) Upgrading python3 (3.7.3-r0 -> 3.7.5-r1)
(2/3) Installing pkgconf (1.6.1-r1)
(3/3) Installing python3-dev (3.7.5-r1)
Executing busybox-1.30.1-r2.trigger
OK: 122 MiB in 35 packages
ERROR: unsatisfiable constraints:
libcrypto1.1-1.1.1d-r0:
breaks: openssl-dev-1.1.1d-r2[libcrypto1.1=1.1.1d-r2]
satisfies: world[libcrypto1.1=1.1.1d-r0]
ca-certificates-20190108-r0[so:libcrypto.so.1.1]
python3-3.7.5-r1[so:libcrypto.so.1.1]
libcurl-7.66.0-r0[so:libcrypto.so.1.1]
apk-tools-2.10.4-r2[so:libcrypto.so.1.1]
libssl1.1-1.1.1d-r0[so:libcrypto.so.1.1]
libtls-standalone-2.9.1-r0[so:libcrypto.so.1.1]
libssl1.1-1.1.1d-r0:
breaks: openssl-dev-1.1.1d-r2[libssl1.1=1.1.1d-r2]
satisfies: world[libssl1.1=1.1.1d-r0]
python3-3.7.5-r1[so:libssl.so.1.1]
libcurl-7.66.0-r0[so:libssl.so.1.1]
apk-tools-2.10.4-r2[so:libssl.so.1.1]
libtls-standalone-2.9.1-r0[so:libssl.so.1.1]
[22:16:15] FATAL: Failed installing package curl-dev
[cont-init.d] appdaemon.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

            Oops! Something went wrong.

We are so sorry, but something went terribly wrong when
starting or running this add-on.

Be sure to check the log above, line by line, for hints.

[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] appdaemon.sh: executing...
[cont-finish.d] appdaemon.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Steps to reproduce

maybe similar config as mine

(How can someone else make/see it happen)
see above

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

The :latest tag still points to the image with version 3.0.1. Possibly because the pipeline failed for the commit bumping to 3.0.2?

The 3.0.2 should really have been 3.1.0, at least if you subscribe to SemVer - it brings MQTT support for apps, which I'd consider a pretty significant addition.

Problem/Motivation

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AppDaemon
 Python Apps and HADashboard using AppDaemon 3.x for Home Assistant
-----------------------------------------------------------
 Add-on version: 2.0.0
 You are running the latest version of this add-on.
 System: HassOS 2.10  (armv7 / raspberrypi3)
 Home Assistant version: 0.90.2
 Supervisor version: 150
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in e.g, GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing... 
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-compiled-dir.sh: executing... 
[cont-init.d] 21-compiled-dir.sh: exited 0.
[cont-init.d] 30-auto-token.sh: executing... 
[00:22:14] INFO: Automatic update of Home Assistant token is disabled.
/var/run/s6/etc/cont-init.d/30-auto-token.sh: line 11: EX_OK: unbound variable
[cont-init.d] 30-auto-token.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 50-compiled-symlink.sh: executing... 
[cont-finish.d] 50-compiled-symlink.sh: exited 0.
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

(Why the issue was filed)

Expected behavior

30-auto-token.sh exit with 0

(What you expected to happen)

Actual behavior

30-auto-token.sh exit with 1

(What actually happened)

Steps to reproduce

config.json

{
  "disable_auto_token": true,
  "system_packages": [],
  "python_packages": [],
  "log_level": "info"
}

start the addon

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

while chasing a problem with hadasboard , i have identified that the problem was related to overlapping ports between traccar and appdaemon .
by changing apdaemon host port to 6050 didnt solve the problem , so started to scan my ports and realize that appdaemon was not opening 6050 , it seams that changing the port on the config interface is not changing the port internally (?).

if first starting traccar , appdaemon wont even start.

when stopping traccar and then first starting appdaemon , the dashboards returned to work as normal, and also traccar seams to work fine .

So starting order of these two addons seams to matter in my case.

so in the end what i did was to load appdaemon on start , and leave traccar for manual start later .

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

tnx for the answer in #58; for some reason pycurl does not start; pip does not get last release

(Why the issue was filed)
to get appdaemon started

Expected behavior

to start with these parameters

(What you expected to happen)

Actual behavior

my config:

{
"disable_auto_token": false,
"system_packages": [
"libcurl",
"libcrypto1.1",
"libssl1.1",
"python3",
"python3-dev",
"gcc",
"g++"
],
"python_packages": [
"hass-apps",
"pycurl",
"pip==19.3.1",
"bluepy==1.3.0"
]
}

(What actually happened)
my log:

(8/10) Installing mpc1 (1.1.0-r0)
(9/10) Installing libstdc++ (8.3.0-r0)
(10/10) Installing gcc (8.3.0-r0)
Executing busybox-1.30.1-r2.trigger
OK: 208 MiB in 45 packages
(1/3) Installing musl-dev (1.1.22-r3)
(2/3) Installing libc-dev (0.7.1-r0)
(3/3) Installing g++ (8.3.0-r0)
Executing busybox-1.30.1-r2.trigger
OK: 274 MiB in 48 packages
Looking in links: https://wheels.hass.io/alpine-3.10/amd64/
Collecting hass-apps
Downloading https://files.pythonhosted.org/packages/08/23/dd092b2144366057d0ec069ab6bc2c005c5daf546460b300a290f0ba4648/hass_apps-0.20191210.0-py3-none-any.whl (52kB)
Collecting observable>=1.0 (from hass-apps)
Downloading https://files.pythonhosted.org/packages/45/7c/b4b63f447378e8a0ebcd338d90f9389f57fb23253127425beacf0129edcb/observable-1.0.3-py2.py3-none-any.whl
Requirement already satisfied: voluptuous>=0.11 in /usr/lib/python3.7/site-packages (from hass-apps) (0.11.7)
Requirement already satisfied: appdaemon>=3.0 in /usr/lib/python3.7/site-packages (from hass-apps) (3.0.5)
Collecting cached-property>=1.5.1 (from hass-apps)
Downloading https://files.pythonhosted.org/packages/3b/86/85c1be2e8db9e13ef9a350aecd6dea292bd612fa288c2f40d035bb750ded/cached_property-1.5.1-py2.py3-none-any.whl
Requirement already satisfied: aiohttp-jinja2==0.15.0 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (0.15.0)
Requirement already satisfied: pyyaml==5.1 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (5.1)
Requirement already satisfied: Jinja2==2.10.1 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (2.10.1)
Requirement already satisfied: daemonize in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (2.5.0)
Requirement already satisfied: sseclient in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (0.0.24)
Requirement already satisfied: bcrypt in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (3.1.7)
Requirement already satisfied: websocket-client in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (0.56.0)
Requirement already satisfied: requests>=2.6.0 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (2.22.0)
Requirement already satisfied: astral in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (1.10.1)
Requirement already satisfied: aiohttp==2.3.10 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (2.3.10)
Requirement already satisfied: feedparser in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (5.2.1)
Requirement already satisfied: yarl==1.1.0 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (1.1.0)
Requirement already satisfied: paho-mqtt in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (1.4.0)
Requirement already satisfied: iso8601 in /usr/lib/python3.7/site-packages (from appdaemon>=3.0->hass-apps) (0.1.12)
Requirement already satisfied: MarkupSafe>=0.23 in /usr/lib/python3.7/site-packages (from Jinja2==2.10.1->appdaemon>=3.0->hass-apps) (1.1.1)
Requirement already satisfied: six in /usr/lib/python3.7/site-packages (from sseclient->appdaemon>=3.0->hass-apps) (1.12.0)
Requirement already satisfied: cffi>=1.1 in /usr/lib/python3.7/site-packages (from bcrypt->appdaemon>=3.0->hass-apps) (1.12.3)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/lib/python3.7/site-packages (from requests>=2.6.0->appdaemon>=3.0->hass-apps) (3.0.4)
Requirement already satisfied: idna<2.9,>=2.5 in /usr/lib/python3.7/site-packages (from requests>=2.6.0->appdaemon>=3.0->hass-apps) (2.8)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.7/site-packages (from requests>=2.6.0->appdaemon>=3.0->hass-apps) (2019.9.11)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/lib/python3.7/site-packages (from requests>=2.6.0->appdaemon>=3.0->hass-apps) (1.25.4)
Requirement already satisfied: pytz in /usr/lib/python3.7/site-packages (from astral->appdaemon>=3.0->hass-apps) (2019.2)
Requirement already satisfied: multidict>=4.0.0 in /usr/lib/python3.7/site-packages (from aiohttp==2.3.10->appdaemon>=3.0->hass-apps) (4.5.2)
Requirement already satisfied: async-timeout>=1.2.0 in /usr/lib/python3.7/site-packages (from aiohttp==2.3.10->appdaemon>=3.0->hass-apps) (3.0.1)
Requirement already satisfied: idna-ssl>=1.0.0 in /usr/lib/python3.7/site-packages (from aiohttp==2.3.10->appdaemon>=3.0->hass-apps) (1.1.0)
Requirement already satisfied: pycparser in /usr/lib/python3.7/site-packages (from cffi>=1.1->bcrypt->appdaemon>=3.0->hass-apps) (2.19)
Installing collected packages: observable, cached-property, hass-apps
Successfully installed cached-property-1.5.1 hass-apps-0.20191210.0 observable-1.0.3
WARNING: You are using pip version 19.2.3, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Looking in links: https://wheels.hass.io/alpine-3.10/amd64/
Collecting pycurl==7.43.0.3
Downloading https://files.pythonhosted.org/packages/ac/b3/0f3979633b7890bab6098d84c84467030b807a1e2b31f5d30103af5a71ca/pycurl-7.43.0.3.tar.gz (215kB)
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3.7 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-_v1e_5ub/pycurl/setup.py'"'"'; file='"'"'/tmp/pip-install-_v1e_5ub/pycurl/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base pip-egg-info
cwd: /tmp/pip-install-_v1e_5ub/pycurl/
Complete output (22 lines):
Traceback (most recent call last):
File "/tmp/pip-install-_v1e_5ub/pycurl/setup.py", line 229, in configure_unix
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/usr/lib/python3.7/subprocess.py", line 800, in init
restore_signals, start_new_session)
File "/usr/lib/python3.7/subprocess.py", line 1551, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'curl-config': 'curl-config'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-install-_v1e_5ub/pycurl/setup.py", line 944, in <module>
    ext = get_extension(sys.argv, split_extension_source=split_extension_source)
  File "/tmp/pip-install-_v1e_5ub/pycurl/setup.py", line 606, in get_extension
    ext_config = ExtensionConfiguration(argv)
  File "/tmp/pip-install-_v1e_5ub/pycurl/setup.py", line 101, in __init__
    self.configure()
  File "/tmp/pip-install-_v1e_5ub/pycurl/setup.py", line 233, in configure_unix
    raise ConfigurationError(msg)
__main__.ConfigurationError: Could not run curl-config: [Errno 2] No such file or directory: 'curl-config': 'curl-config'
----------------------------------------

ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
WARNING: You are using pip version 19.2.3, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[21:13:11] FATAL: Failed installing package pycurl==7.43.0.3
[cont-init.d] appdaemon.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

            Oops! Something went wrong.

We are so sorry, but something went terribly wrong when
starting or running this add-on.

Be sure to check the log above, line by line, for hints.

[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] appdaemon.sh: executing...
[cont-finish.d] appdaemon.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Index of /alpine-3.10/amd64/

Index of /alpine-3.10/amd64/

Problem

The AD service is running, but the Dashboard is not running anymore
No errors
In the appdeamon.yaml I have added the long-lived token generated by the HA

plugins:
HASS:
type: hass
ha_url: http://hassio/homeassistant
app_dir: /config/appdaemon/apps
Token: eyJ0eXAiOiJKV1QiLCJhbGciOiJ........

No other error is shown in any of the other log files.
I already checked everything, I don't know what else more I can do.

Thanks
Rui