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

'lock' from integration bold has a non string unique_id '17307' #117773

Closed
jamespreedy opened this issue May 20, 2024 · 9 comments
Closed

'lock' from integration bold has a non string unique_id '17307' #117773

jamespreedy opened this issue May 20, 2024 · 9 comments

Comments

@jamespreedy
Copy link

The problem

Hiya folks, thanks for your support and hard work.

FYI only - I noticed the below in the logs, it asked that I raise a bug report, so just dropping it in here.

2024-05-20 07:46:25.087 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'lock' from integration bold has a non string unique_id '17307', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+bold%22
2024-05-20 07:46:25.087 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'lock' from integration bold has a non string unique_id '61324', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+bold%22

If there's any additional information needed, please let me know and I'll be happy to help.

What version of Home Assistant Core has the issue?

core-2024.5.4

What was the last working version of Home Assistant Core?

n/a

What type of installation are you running?

Home Assistant OS

Integration causing the issue

helpers?

Link to integration documentation on our website

No response

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

@jamespreedy
Copy link
Author

Not quite sure why it wants a bug in core, rather than in the custom component that created the lock entity.
As I say, if you need any additional information, please let me know.

@joostlek
Copy link
Member

This should have been reported in the custom component issue tracker instead.

@jamespreedy
Copy link
Author

@joostlek - no worries, I'll report it there.

Is there a better place to get some feedback to the HASS folks - the error specifically said to report the issue at this URL - https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+bold%22 - in this case under HASS core rather than the custom integration?

Thank you!

@emontnemery
Copy link
Contributor

emontnemery commented May 23, 2024

@jamespreedy is the lock from this custom integration: https://github.com/lwestenberg/homeassistant_bold ? If it is, how have you installed the custom integration?

@jamespreedy
Copy link
Author

@emontnemery - correct, https://github.com/lwestenberg/homeassistant_bold. It was installed using HACS. 👍🏻

Screenshot 2024-05-23 at 7 36 27 AM

@emontnemery
Copy link
Contributor

emontnemery commented May 23, 2024

I can't reproduce the issue, I get:

[homeassistant.helpers.entity_registry] 'lock' from integration bold has a non string unique_id '12345', please report it to the author of the 'bold' custom integration

Edit: I can indeed reproduce it.

@tim427
Copy link
Contributor

tim427 commented May 23, 2024

Probably something changed on the "lock" integration. I'll have a look ;)

Thanks for reporting @jamespreedy !

@jamespreedy
Copy link
Author

@tim427 - thanks mate! Appreciate I can't help with the PR, but happy to help test / debug logs / anything I can do to help.
Have a great week. 😀

@emontnemery
Copy link
Contributor

The incorrect issue tracker link is fixed by PR #118016

With that PR:

2024-05-24 08:42:03.990 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'lock' from integration bold has a non string unique_id '12345', please report it to the author of the 'bold' custom integration

I'm closing this issue now since the problem is in a custom integration and the wrong issue tracker link has been fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants