search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.89k stars 30.12k forks source link

Rollease Acmeda integration fails with "UnboundLocalError: cannot access local variable 'hubs' where it is not associated with a value" #124025

Open davros123 opened 1 month ago

davros123 commented 1 month ago

The problem

Integration fails to start with this error when trying to add a hub (v1). image - looking at the logs

I was running the HACS version of this integration however it was not reliably working (only updated after reboot then stopped responding after a day or so) so I decided to uninstall the HACS and move to the "official" supported integration.

When I tried to add the "official" integration, I revieve the above error. After experiencing the above error on my (fully configured) HA, I thought it might be my config...so I wiped the ssd and installed a completely fresh install with no other integrations or config. and got the same error.

(same error from my orginall (fully setup) HA) image

What version of Home Assistant Core has the issue?

core-2024.8.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

Rollease Acmeda Automate

Link to integration documentation on our website

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

Diagnostics information

Here is the error acmedaerror.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

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

Code owner commands Code owners of `acmeda` 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 acmeda` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

acmeda documentation acmeda source (message by IssueLinks)

AdamCavaliere commented 1 month ago

I got this to work by adding it as a custom integration through HACS: https://github.com/atmurray/ha-acmeda

parkglen commented 1 month ago

I got this to work by adding it as a custom integration through HACS: https://github.com/atmurray/ha-acmeda

Thanks @AdamCavaliere - That worked

atmurray commented 1 month ago

Hi all, I've got a pull request open that fixes this issue: https://github.com/home-assistant/core/pull/124960 Until that gets accepted/merged/released, this is the same as the v0.4.6 release of the custom integration you can add using HACS: https://github.com/atmurray/ha-acmeda

davros123 commented 1 month ago

Thanks I updated the HACS version and it resolved this issue. It "may" have also resolved an issue where the blinds stopped responding after a day or so...it's been 24 hours and still working 🤞

Thanks @atmurray for your continued support of this integration

papaavi commented 3 weeks ago

Hey @atmurray this solved for me too. I noticed when I did this solution last time for a different issue via HACs, the HASS version of the integration duplicated my blinds so I had 2x of the same (I deleted the integration so that's how I got in this current 500 error mess in the first place). Thank you so much for supporting this integration, it's the whole reason I got into HASS in the first place. It's brilliant.