Local keys are now random letters/symbols

[uzlonewolf]

Just added a new bulb and it got a local key of =fU{R=MA^tC%>>zH. I don't think this will affect anything as long as they don't include " or \ in their character set, but it is interesting that they're moving away from hex digits.

So far I've seen the characters

' * # . = { } ^ < > % ( ) - _ / ` + [ ] ~ ; ? : @ & $ | !

[jasonacox]

Oh wow... No issues with tinytuya?

[uzlonewolf]

If they're on a different network you can also do python3 -m tinytuya scan -force 192.168.2.0/24 192.168.3.0/24 etc.

So far I've seen the characters

'*#.={^>%()-_/`+]-~;

[johnnykang]

alright.

It turned out to be the LocalTuya is the trouble.

I've sorted out the bug on that library locally, and I am able to use the new key format without issue with HomeAssistant.

Thank you guys for helping me to identify the root cause.

🙏

[uzlonewolf]

That's great!

What did you have to change to make it work?

[johnnykang]

with HA 2023.5, async_get_registry method is removed and LocalTuya has not updated the code to use async_get instead.

I was getting could not decrypt data: wrong local_key? error. Apparently that error was not obvious in the log and it was misleading. it was actually caused by the above exception and it has nothing to do with the actual device key.

[stu531]

Hi, I'd had a problem with this - but followed the update and got it solved. Thanks so much @johnnykang.

[szupi-ipuzs]

I've got this key:
?:vSi=XBXH<e(o@0

And now i have another that apart from letters (both capital and not) and numbers contains these chars: /`$:[&(