Weird encrypted response from tuya bulb ? about tuyapi HOT 6 CLOSED

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

from tuyapi.

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?

from tuyapi.

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.

Does anyone have a solution for this?

from tuyapi.

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. 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

from tuyapi.

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.

from tuyapi.

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?

from tuyapi.