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

[Bug]: Not full localkey value is used #226

Closed
3 tasks
Lurker00 opened this issue May 10, 2024 · 2 comments
Closed
3 tasks

[Bug]: Not full localkey value is used #226

Lurker00 opened this issue May 10, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Lurker00
Copy link

LocalTuya Version

3.2.5.2b7

Home Assistant Version

2024.4.4

Environment

  • Does the device work using the Home Assistant Tuya Cloud component?
  • Is this device connected to another local integration, including Home Assistant and any other tools?
  • The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

Today I've added a new Zigbee device (a relay with dimmer), and now I ofter see "Sub-device localkey doesn't match the gateway localkey" messages in the log, related to this device. I've modified the source code

            if gateway._local_key != self._local_key:
                self.warning(f"Sub-device localkey doesn't match the gateway localkey ('{gateway._local_key}'!='{self._local_key}')")
                self._local_key = gateway._local_key

and I see that the self._local_key is 'G3i...1UB', i.e. not full, but it matches the full localkey. The same in the diagnostics.

It seems there is a bug somewhere...

Steps to reproduce.

Don't know

Relevant log output

2024-05-10 11:28:11.028 WARNING (MainThread) [custom_components.localtuya.coordinator] [bff...ns9] Sub-device localkey doesn't match the gateway localkey ('G3iJ8V>%m7@7Z1UB'!='G3i...1UB')

Diagnostics information.

localtuya-944c1616039a1d1ec6b9745179bff74e-ПЛ_ Диммер-2b23e409000e04a36a10be91f6f812c2 (1).json

@Lurker00 Lurker00 added the bug Something isn't working label May 10, 2024
@xZetsubou
Copy link
Owner

I guess the bug is in diagnostics.py module.

@xZetsubou xZetsubou added the master/next-release Fixed in master branch, Will be ready in the next release label May 10, 2024
Copy link

This issue was closed because it was resolved on the release:

@github-actions github-actions bot added stale and removed master/next-release Fixed in master branch, Will be ready in the next release stale labels May 26, 2024
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