Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: 'WhereBucketValue' object is not subscriptable #401

Open
spockster1985 opened this issue Jan 7, 2025 · 2 comments
Open

TypeError: 'WhereBucketValue' object is not subscriptable #401

spockster1985 opened this issue Jan 7, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@spockster1985
Copy link

The problem

I installed 3 nest protects battery and added this integration to home assistant. It gives this error every 5 minutes.

What version of this integration (ha-nest-protect) has the issue?

0.4.0

What version of Home Assistant Core has the issue?

core-2024.12.5

Device / Model

Nest Protect (Battery) Topaz-234

Diagnostics information

config_entry-nest_protect-01JGXJ3V9Z0XN4GDY8JVFNEFFD.json

Home Assistant log

Logs ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 193, in _async_subscribe_for_data for area in bucket_value["wheres"]: ~~~~~~~~~~~~^^^^^^^^^^ TypeError: 'WhereBucketValue' object is not subscriptable

Additional information

No response

@spockster1985 spockster1985 added the bug Something isn't working label Jan 7, 2025
@GSzabados
Copy link
Contributor

@iMicknl, we likely need to set up the integration from scratch to be able to fully debug this. 🙄 Or somehow change the WhereBucket to make the integration to subscribe for it again.

@iMicknl iMicknl marked this as a duplicate of #411 Jan 27, 2025
GSzabados added a commit to GSzabados/ha-nest-protect that referenced this issue Feb 17, 2025
…knl#401

This should handle the error, as it is already handled a few lines above the same way.
@GSzabados
Copy link
Contributor

@spockster1985 and @alexsaare

if you want to fix this for now, you can implement this change manually:

8d352ab

After doing the changes in the file you need to restart Home Assistant, and the integration should work normally.

iMicknl pushed a commit that referenced this issue Feb 18, 2025
…#429)

This should handle the error, as it is already handled a few lines above the same way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants