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

Tuyadebug does not accept ampersand in tuya local key #1926

Open
RobbiTobbi1955 opened this issue Feb 4, 2025 · 1 comment
Open

Tuyadebug does not accept ampersand in tuya local key #1926

RobbiTobbi1955 opened this issue Feb 4, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@RobbiTobbi1955
Copy link

The problem

Not possible to retrieve the dps with a device that has an ampersand ('&') in its local key

Environment

  • Localtuya version: doesnt' apply.

Steps to reproduce

  1. call tuyadebug the like:
  2. python test.py 377552852462ab01b8b5 192.168.178.29 $1y.1a50`p3h!&l2
  3. NOTE the '&' before 'I2'

DP dump

does not apply

Provide Home Assistant traceback/logs

Copy of output to screen:

K:\Bluestacks\tuyadebug>python test.py 377552852462ab01b8b5 192.168.178.29 $1y.1a50`p3h!&l2
INFO:localtuya:localtuya version 1.0.0
INFO:localtuya:Python 3.11.1 (tags/v3.11.1:a7a450f, Dec  6 2022, 19:58:39) [MSC v.1934 64 bit (AMD64)] on win32
INFO:localtuya:Using pytuya version '10.0.0'
INFO:localtuya:TIMEOUT: No response from device 377552852462ab01b8b5 [192.168.178.29] after 2 attempts.
←]9001;CmdNotFound;l2←\Der Befehl "l2" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

[ translation: command  "l2"  is either a typoo or could not be found. ]

K:\Bluestacks\tuyadebug>

Additional information

Tuya allows crazy chars like ':', '.', '?', '*', '&', '^' in local keys.

@RobbiTobbi1955 RobbiTobbi1955 added the bug Something isn't working label Feb 4, 2025
@RobbiTobbi1955
Copy link
Author

After trying to fix the problem with PyCharm I found that running the same commandline resulted in successful retrieving the dps values. So maybe something else (windows?) must be blamed.

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

1 participant