-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
Weird encrypted response from tuya bulb ? #626
Comments
It may have been assigned a new local key when the device updated to 3.3. Have you tried reprovisioning? |
May I ask, how can I do that? Do you mean it changed its ID? |
I've removed the device like ten times now with no luck... keys change but I'm getting local keys with special characters that doesn't works, i get the following on the homebridge terminal: mhF]f;xT*}n]****, key for Foco Fachada (eb0c78be1146023769xlky), is not a valid key. Thanks for the help anywways. I truly appreciate any suggestions. |
Maybe the homebridge plugin has added checked for allowed characters? Seems more like a message from there then from the library here. Maybe this check need to be adjusted? |
I have two indentic bulbs that have been working flawlessly for a couple of months. Just recently one of them stopped working and looking at their responses I found the following.
First response is from the working bulb, second one is the one that isn't working. Is somebody experiencing this issue?
I tried setting the Tuya Protocol Version to 3.3 to no avail.
The second bulb has stopped reacting to any request.
The text was updated successfully, but these errors were encountered: