last release doesnt allow other plugins the hass and mqtt

[ReneTode]

What happened?

i updated AD to latest release and now the AD-AD plugin i use causes that AD doesnt start anymore because of a configuration error.

Version

4.2.3

Installation type

Home Assistant add-on

Relevant log output

[15:28:10] INFO: Starting AppDaemon...
Configuration error in: /config/appdaemon.yaml
1 validation error for MainConfig
appdaemon.plugins.ADENTITIES
  Input tag 'ad' found using plugin_discriminator() does not match any of the expected tags: 'hass', 'mqtt' [type=union_tag_invalid, input_value={'type': 'ad', 'url': 'ht...}, 'name': 'ADENTITIES'},

Relevant code in the app or config file that caused the issue

Anything else?

No response

[ReneTode]

version is most likely 4.5.11

i couldnt see it because there is no log about it, and github did suggest an older version.

[acockburn]

Hi Rene - nice to Hear form you!

This is the new config validation in action. Since the error occurs on AppDaemon.yaml, we can't rely on the logging section being set up so we log these errors to stdout immediately. We are looking at ways around this.

The actual issue here is an oversight with the validation setup, it should allow other values than "mass" and "mutt" precisely for custom plugins like you are using. We will fix this in the next release.

[ReneTode]

i hope that doesnt take to long, because i did mistake HA backup for a full backup, and have no option to return to an older version at the moment. i do use the addon because i need alexa media player in HA to connect to alexa. (it was to much work to keep doing that in AD myself)
so now my connection to my alexa devices is broken. if it takes to long ill need to find a workaround somehow.

[ReneTode]

just as a sidenote:
im trying to create some workarounds, and adding a new dict to an apps yaml file makes that the app crashes and it can only be recovered by restarting AD

2025-07-06 22:32:59.276578 INFO notify: {'entity_id': 'sensor.notify_message', 'new_state': {'attributes': {}, 'state': ' ', 'entity_id': 'sensor.notify_message', 'last_changed': '2025-07-06T22:32:59+02:00'}, 'old_state': {'state': None, 'attributes': {}}}
2025-07-06 22:34:53.494202 WARNING AppDaemon: ------------------------------------------------------------
2025-07-06 22:34:53.515050 WARNING AppDaemon: Unexpected error during utility()
2025-07-06 22:34:53.517160 WARNING AppDaemon: ------------------------------------------------------------
2025-07-06 22:34:53.552368 WARNING AppDaemon: Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/appdaemon/utility_loop.py", line 177, in loop
    await self.AD.app_management.check_app_updates()
  File "/usr/lib/python3.12/site-packages/appdaemon/app_management.py", line 814, in check_app_updates
    await self.check_app_config_files(update_actions)
  File "/usr/lib/python3.12/site-packages/appdaemon/app_management.py", line 655, in check_app_config_files
    if not utils.deep_compare(current_app, prev_app):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/appdaemon/utils.py", line 403, in deep_compare
    if isinstance(v, dict) and isinstance(data[k], dict):
                                          ~~~~^^^
KeyError: 'mutes'

[acockburn]

Hi Rene,

The dev branch now has a fix for the original issue if you want to give it a try.