search

codetheweb / tuyapi

🌧 An easy-to-use API for devices that use Tuya's cloud services. Documentation: https://codetheweb.github.io/tuyapi.
MIT License
2.04k stars 332 forks source link

Weird encrypted response from tuya bulb ? #626

Closed obaldius closed 1 year ago

obaldius commented 1 year ago

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.

Sin título

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.

kueblc commented 1 year ago

It may have been assigned a new local key when the device updated to 3.3. Have you tried reprovisioning?

obaldius commented 1 year ago

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?

weromemuero commented 1 year ago

I have the same exact issue, didn't change anything but one of my smartbulbs stop working and send a similar weird response. I removed the device from the app and re add but no luck. Also the device key is special characters instead of just alpha numeric. Bulb Key Does anyone have a solution for this?

obaldius commented 1 year ago

I have the same exact issue, didn't change anything but one of my smartbulbs stop working and send a similar weird response. I removed the device from the app and re add but no luck. Also the device key is special characters instead of just alpha numeric. Bulb Key Does anyone have a solution for this?

In fact I managed to solve it. Remove the device, add it again and get again its deviceID and key. At least one of them will be different once you remove and readd the device. With the new serials the device works as expected

weromemuero commented 1 year ago

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.

Apollon77 commented 1 year ago

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?