Unifi - Handle unsupported event key EVT_AP_UpgradeFailed

[stefanroelofs]

The problem

I see the following log messages from the Unifi integration:

2023-07-13 04:00:04.591 WARNING (MainThread) [aiounifi.models.event] Unsupported event key EVT_AP_UpgradeFailed
2023-07-13 04:00:04.592 WARNING (MainThread) [aiounifi.models.event] Unsupported event {'key': 'EVT_AP_UpgradeFailed', 'ap': 'xx:xx:xx:xx:xx:xx', 'ap_name': 'Upstairs (AC Lite)', 'ap_model': 'U7LT', 'ap_displayName': 'Upstairs (AC Lite)', 'subsystem': 'wlan', 'is_negative': True, 'site_id': 'xxxxxxxxxxxxxxxx', 'time': 1689213600044, 'datetime': '2023-07-13T02:00:00Z', 'msg': 'AP[xx:xx:xx:xx:xx:xx] upgrade failed', '_id': 'xxxxxxxxxxxxxxxx'}

I think it is only a matter of adding a handler to handle these events correctly. Like done previously here: https://github.com/home-assistant/core/issues/79325

The event itself is harmless I think, and can be safely ignored?

Thank you!

What version of Home Assistant Core has the issue?

core-2023.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Unifi

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifi

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @kane610, mind taking a look at this issue as it has been labeled with an integration (unifi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `unifi` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign unifi` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

unifi documentation unifi source _{^{(message by IssueLinks)}}

[stefanroelofs]

I actually have another unhandled message:

2023-07-13 09:06:33.745 WARNING (MainThread) [aiounifi.models.message] Unsupported message key scheduletask:add
2023-07-13 09:06:33.746 WARNING (MainThread) [aiounifi.models.message] Unsupported message {'meta': {'rc': 'ok', 'message': 'scheduletask:add'}, 'data': {'action': 'radio-ai', 'cron_expr': '0 3 * * *', 'name': 'radio-ai', 'execute_only_once': False, 'timezone': 'UTC', 'site_id': 'xxxxxxxxxxxxxxxxxxx', 'default': True, 'radios': ['ng', 'na'], 'optimize': ['channel'], 'channels_ng': [1, 6, 11], 'channels_na': [36, 40, 44, 48], 'ht_modes_ng': [20], 'ht_modes_na': [20, 40], 'useXY': False, 'exclude_devices': [], '_id': 'xxxxxxxxxxxxxxxxxxxxxxx'}}

Again, this is not an issue really. Just informing you. Thanks!

[tankdeer]

I actually have another unhandled message:

2023-07-13 09:06:33.745 WARNING (MainThread) [aiounifi.models.message] Unsupported message key scheduletask:add
2023-07-13 09:06:33.746 WARNING (MainThread) [aiounifi.models.message] Unsupported message {'meta': {'rc': 'ok', 'message': 'scheduletask:add'}, 'data': {'action': 'radio-ai', 'cron_expr': '0 3 * * *', 'name': 'radio-ai', 'execute_only_once': False, 'timezone': 'UTC', 'site_id': 'xxxxxxxxxxxxxxxxxxx', 'default': True, 'radios': ['ng', 'na'], 'optimize': ['channel'], 'channels_ng': [1, 6, 11], 'channels_na': [36, 40, 44, 48], 'ht_modes_ng': [20], 'ht_modes_na': [20, 40], 'useXY': False, 'exclude_devices': [], '_id': 'xxxxxxxxxxxxxxxxxxxxxxx'}}

Again, this is not an issue really. Just informing you. Thanks!

This message is similar to one I am receiving an opened an issue for.

https://github.com/home-assistant/core/issues/95652

The issue was closed as supposedly fixed, however it's still an issue. Seems as though there might have been more underlying changes causing these warnings.