ModuleNotFoundError: No module named 'Cryptodome'

[ndfred]

When flashing a new device with

Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Traceback (most recent call last):
  File "./smartconfig/main.py", line 15, in <module>
    from smartconfig import smartconfig
  File "/home/fred/tuya-convert/scripts/smartconfig/smartconfig.py", line 43, in <module>
    from multicast import multicast_head, encode_multicast_body
  File "/home/fred/tuya-convert/scripts/smartconfig/multicast.py", line 12, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'

This is with the latest checkout (release v2.4.3) on my Raspberry Pi 4. I'll try and fix the issue and report back.

[ndfred]

It looks like install_prereq.sh is installing pycryptodomex but not pycryptodome, I'll try and install that and re-run the process:

$ sudo -H python3 -m pip install --upgrade pycryptodome
$ ./start_flash.sh

Edit: still not working, same message as before plus running the tests manually fails import, I'll keep digging:

$ python -m Cryptodome.SelfTest
/usr/bin/python: No module named Cryptodome
$ python3 -m Cryptodome.SelfTest
Skipping AESNI tests
Skipping test of PCLMULDQD in AES GCM
[...]

Suspecting the script is running python expecting python 3, but on my system it is python 2.

Very odd, if I run main.py directly it also fails to import:

$ ./scripts/smartconfig/main.py
Traceback (most recent call last):
  File "./scripts/smartconfig/main.py", line 15, in <module>
    from smartconfig import smartconfig
  File "/home/fred/tuya-convert/scripts/smartconfig/smartconfig.py", line 43, in <module>
    from multicast import multicast_head, encode_multicast_body
  File "/home/fred/tuya-convert/scripts/smartconfig/multicast.py", line 12, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'
$ python3 ./scripts/smartconfig/main.py
Traceback (most recent call last):
  File "./scripts/smartconfig/main.py", line 15, in <module>
    from smartconfig import smartconfig
  File "/home/fred/tuya-convert/scripts/smartconfig/smartconfig.py", line 43, in <module>
    from multicast import multicast_head, encode_multicast_body
  File "/home/fred/tuya-convert/scripts/smartconfig/multicast.py", line 12, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'

[ndfred]

I was actually in a python virtual env which is why python wasn't seeing the packages 🤦‍♂️

It might be best to install the tuya-convert python packages in a virtual env to make it cleaner, and that may avoid issues like this in the future. I'll close this as this was really my mistake.

[kueblc]

It looks like install_prereq.sh is installing pycryptodomex but not pycryptodome

pycryptodomex is intentional. pycryptodomex and pycryptodome have an important distinction, while pycryptodome strives to be a drop in replacement for the old Crypto package, pycryptodomex uses the Cryptodome name. This ensures that if you have the deprecated Crypto package installed, we use the correct package.

Might your issues be at all related to #575? Or rather that the issue presented in #575 is related to the python virtual env?

It might be best to install the tuya-convert python packages in a virtual env to make it cleaner, and that may avoid issues like this in the future. I'll close this as this was really my mistake.

Feel free to submit a PR :)

[ministryofsillywalks]

I'm having the same issue however I didn't use any virtual environment to install tuya-convert.
Sadly I have no clue what the hell is going on with python and whatnot ;)
Any nudge in the right direction would be great.

[micooke]

I had this same issue, which was a result of installing the prerequisites as sudo - and then running start_flash.sh without sudo.

So to reword this - manually installing the prerequisites from install_prereq.sh without sudo fixed my issue (or running start_flash.sh with sudo).

[RolandTalstra]

I'm experiencing the same problem, however sudo ./start_flash.sh doesn't work for me, the error remains the same

I ran the prereq's again, and re-installed tuya_convert, but to no avail.

Any more tips?

[abdalians]

getting the same error, any idea how to fix this?

[JohannCR]

Same error. Any news ?

[KDMcMullan]

Oooh, this is odd. I've not had this error before, but I have it now. I haven't used tuya-convert in a few months and I can't imagine what I might've done in the meantime!

[KDMcMullan]

I've just done a complete fresh install on a "virgin" Raspberry Pi and got the same error message. Are there any clues what might be going on? There are still a remarkable number of devices (and users) around which can really benefit from this method, if it's still supported. Thanks.

[TungstenE2]

same here, using Pi 3+ running Buster

1. Connect any other device (a smartphone or something) to the WIFI vtrust-flash
   This step is IMPORTANT otherwise the smartconfig may not work!
2. Put your IoT device in autoconfig/smartconfig/pairing mode (LED will blink fast). This is usually done by pressing and holding the primary button of the device
   Make sure nothing else is plugged into your IoT device while attempting to flash.
3. Press ENTER to continue


======================================================
Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Traceback (most recent call last):
  File "./smartconfig/main.py", line 15, in <module>
    from smartconfig import smartconfig
  File "/home/pi/tuya-convert/scripts/smartconfig/smartconfig.py", line 43, in <module>
    from multicast import multicast_head, encode_multicast_body
  File "/home/pi/tuya-convert/scripts/smartconfig/multicast.py", line 12, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'
........................................................................................................................
Timed out while waiting for the device to (re)connect
======================================================
Attempting to diagnose the issue...
No ESP82xx based devices connected according to your wifi log.
Here is a list of all the MAC addresses that connected:
0c:8f:ff:4xxxxxxxxxxx

If you see your IoT device in this list, it is not an ESP82xx based device.
Otherwise, another issue may be preventing it from connecting.
For additional information, check the *.log files inside the scripts folder.
Please include these logs when opening a new issue on our GitHub issue tracker.
======================================================
Do you want to try flashing another device? [y/N] N
======================================================
Cleaning up...
No screen session found.
No screen session found.
No screen session found.
Closing AP
Exiting...
pi@raspberrypi:~/tuya-convert $ 

[TungstenE2]

why is this ticket closed with no solution?

also this ticket is closed: fashberg/WThermostatBeca#39