#Error occurred loading flow for integration tuya: No module named 'tuya_shared'
69 messages · Page 1 of 1 (latest)
When you say bare metal - exactly what does that mean?
That could mean pip install or flashing HAOS to the computer's drive
'Latest' is not a version number. Please provide the actual version number.
2024.12.4
You've got uv installed? You've tried activating the venv and installing the module to see the full error messages?
I use micromamba
uv is installed
and yes i tried to iunstall it
python3 -m pip install tuya_shared
ERROR: Could not find a version that satisfies the requirement tuya_shared (from versions: none)
ERROR: No matching distribution found for tuya_shared
python is 3.12.0
You should really be on 3.13 now
3.12 support will be dropped in the next few releases
as far as I understand is not mandated yet
Yet, but the docker images use it, so that's a good sign that it's time to move over already
is not tuya part of the core?
i mean the standard integration
on 3.13
File "/home/drfaustroll/micromamba/envs/homeassistant/lib/python3.13/site-packages/homeassistant/components/ffmpeg/__init__.py", line 8, in <module>
from haffmpeg.core import HAFFmpeg
ModuleNotFoundError: No module named 'haffmpeg'
2024-12-19 16:38:57.713 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of 'tts'. Setup failed for dependencies: ['ffmpeg']
2024-12-19 16:38:57.713 ERROR (MainThread) [homeassistant.setup] Setup failed for 'tts': Could not setup dependencies: ffmpeg
(homeassistant) drfaustroll@mefisto:~/homeauto/.homeassistant> python3 -m pip install ha-ffmepg
ERROR: Could not find a version that satisfies the requirement haffmpeg (from versions: none)
ERROR: No matching distribution found for haffmpeg
and so on... that is why I avoid 3.13
this is practically where I stopped, when tried last time 3.13
024-12-19 16:52:08.618 ERROR (MainThread) [homeassistant.config_entries] Error importing platform config_flow from integration wled to set up wled configuration entry: Platform wled.config_flow not found
2024-12-19 16:52:08.618 ERROR (MainThread) [homeassistant.config_entries] Error importing platform config_flow from integration wled to set up wled configuration entry: Platform wled.config_flow not found
2024-12-19 16:52:08.678 ERROR (SyncWorker_3) [homeassistant.components.camera.img_util] Error loading libturbojpeg; Camera snapshot performance will be sub-optimal
Traceback (most recent call last):
File "/home/drfaustroll/micromamba/envs/homeassistant/lib/python3.13/site-packages/homeassistant/components/camera/img_util.py", line 100, in __init__
TurboJPEGSingleton.__instance = TurboJPEG()
^^^^^^^^^
NameError: name 'TurboJPEG' is not defined
Any reason you're avoiding docker?
No I am using for testing and other things I do not think production stuff shall be run in docker... It just hides a lot of issues
I suspect in this case just shows bad practices on enforcing versions on packages...
What is odd I use 3 custom integrations that have no issues all the ones that create problems are the ones from "official" support
It's likely your problem is a lack of OS packages, which Docker avoids... and the whole magic of Docker is that in production it avoids issues, not that it hides them
not really is mainly lack of correct versions of various python packages
for example now i clean up all and from all on 13 esphome integration seems to be broken
2024-12-20 08:56:10.368 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration esphome: Platform esphome.config_flow not found
2024-12-20 08:56:10.374 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):````
when these things worked on python 3.12
is there a list of versions per release
?
I can extract them from docker but would be nice not to have to download it
Versions of what?
There's a requirements file, if that's what you mean
Check the core repo
yes I checked but that is for 2025 already not for 2024.12.4
now i realise since core i working but esphome integration is not is useless
since that will not have deps on esphome
Honestly, at this point I'd try HA in Docker to see whether the problem is with your install, or your config, or what
If it starts in Docker then the problem is with your install/environment
And then you can troubleshoot from there
if works on python3.12 on the same machine same config same base but not when i move to 3.13
to me looks quite simple
That doesn't mean it's not a problem with your install/environment
indeed the user is always an idiot
Or you're missing some dependency/build option
i am not using any exotic integration is esphome one
The Core method rather assumes that you're able to troubleshoot and diagnose install/build problems
less hubris may help in here... there is no need to be on a high horse
No high horse, I'm just telling you how it is
Most people are expected to run HAOS or Docker
If you want to run Core (and I used to), then it's on you to ensure that your system is suitable
for a reason in python 3.12 pull correctly a lot of deps but not in 3.13
so that tells me there is an issue with ha
thanks for help