-
Notifications
You must be signed in to change notification settings - Fork 188
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
Can't get .status() from switch #3
Comments
It is having trouble with the JSON payload coming back from the switch. It could be an encryption problem or just a bad JSON format. Try updating to TinyTuya v1.0.4:
and then run the network scan function to see if the switch shows up:
|
I updated from v1.0.3 to v.1.0.4, but still the same problem.
It's my only device which has 22 chars as ID. Maybe that's the problem? |
There seems to be some strange behavior with some devices that have a 22 character IDs. Try adding
|
I tried adding
|
Oops! Try sending a DPS requested value:
Some of the device22 types have different lists of available dps values. I need to add a feature to scan these for us. If the above works, your device is the most common. If not, it will require a bit more work to figure it out. |
Now it works! |
Hi,
i can get the status from my 10 lamps, but when I try to get a status from a switch, i get the following error. This is my code:
And this error occurs:
The text was updated successfully, but these errors were encountered: