Closed rasssta closed 2 weeks ago
if that were true the integration wouldn't run at all. Oh also you should check that the base requirement for Mammotion is 2024.9.0 now due to the RETURNING type.
The integration won't load, figured it was due to the login issues I've seen mentioned so I upgraded the integration but still didn't work. Hence why I started to look into this issue. Do you want me to debug anything or should I just upgrade pymammotion manually?
Have you updated Home assistant to 2024.9.0 or above?
Same problem. I am on 2024.10.4. Worked previously.
Do the logs explicitly say it cannot find the newer versions of pymammotion? If so it's a cache issue with uv / pip and not something I can fix. Usually a reboot or two sorts it.
Updated to 2024.9.3 and got this in the log:
2024-10-28 09:51:03.015 ERROR (SyncWorker_10) [homeassistant.util.package] Unable to install package pymammotion==0.2.84: error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [47 lines of output]
+ /srv/homeassistant/bin/python3.12 /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458/vendored-meson/meson/meson.py setup /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458 /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458/.mesonpy-zej1de7m/build -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458/.mesonpy-zej1de7m/build/meson-python-native-file.ini
The Meson build system
Version: 1.2.99
Source dir: /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458
Build dir: /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458/.mesonpy-zej1de7m/build
Build type: native build
Project name: NumPy
Project version: 1.26.0
C compiler for the host machine: cc (gcc 12.2.0 "cc (Raspbian 12.2.0-14+rpi1) 12.2.0")
C linker for the host machine: cc ld.bfd 2.40
C++ compiler for the host machine: c++ (gcc 12.2.0 "c++ (Raspbian 12.2.0-14+rpi1) 12.2.0")
C++ linker for the host machine: c++ ld.bfd 2.40
Cython compiler for the host machine: cython (cython 3.0.11)
Host machine cpu family: arm
Host machine cpu: armv7l
Program python found: YES (/srv/homeassistant/bin/python3.12)
Found pkg-config: /usr/bin/pkg-config (1.8.1)
Run-time dependency python found: YES 3.12
Has header "Python.h" with dependency python-3.12: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Message: During parsing cpu-dispatch: The following CPU features were ignored due to platform incompatibility or lack of support:
"XOP FMA4"
Test features "NEON" : Supported
Test features "NEON_FP16" : Supported
Test features "NEON_VFPV4" : Supported
Test features "ASIMD" : Unsupported due to Compiler fails against the test code of "ASIMD"
Test features "ASIMDHP" : Unsupported due to Implied feature "ASIMD" is not supported
Test features "ASIMDFHM" : Unsupported due to Implied feature "ASIMD" is not supported
Configuring npy_cpu_dispatch_config.h using configuration
Message:
CPU Optimization Options
baseline:
Requested : min
Enabled :
dispatch:
Requested : max -xop -fma4
Enabled : NEON NEON_FP16 NEON_VFPV4
Library m found: YES
Found CMake: /usr/bin/cmake (3.25.1)
WARNING: CMake Toolchain: Failed to determine CMake compilers state
Run-time dependency openblas found: NO (tried pkgconfig and cmake)
Run-time dependency openblas found: NO (tried pkgconfig and cmake)
../../numpy/meson.build:207:4: ERROR: Problem encountered: No BLAS library detected! Install one, or use the `allow-noblas` build option (note, this may be up to 100x slower for some linear algebra operations).
A full log can be found at /tmp/pip-install-0uhz5lp9/numpy_1f5e0c6e61094aeb99f3a60356bff458/.mesonpy-zej1de7m/build/meson-logs/meson-log.txt
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
2024-10-28 09:51:53.138 ERROR (SyncWorker_10) [homeassistant.util.package] Unable to install package pymammotion==0.2.84: error: subprocess-exited-with-error
However, when running "pip install pymammotion==0.2.84" manually afterwards it worked fine.
UV which home assistant changed to messes up old versions, update to latest
The problem
Not sure if this is a "me problem" or an "integration problem". But I've seen it in the past with this integration as well that pymammotion isn't updated to the required version specified in manifest.json. Any idea what might cause this?
I'm running 0.1.81 and have verified that my manifest.json says:
"requirements": [ "pymammotion==0.2.84" ]
But my venv is running: $ pip list | grep mamm pymammotion 0.2.76
I have restarted HASS (multiple times) since upgrading to 0.1.81.
I'm running HASS core 2024.8.3. Not sure if there's something special to be done there? Can't recall having this kind of issue with any other integration and I've been running HASS core for 3-4 years. Have I just been lucky or ignorant? :D
What Mammotion mower are you using?
Yuka
What version of the Mammotion intergration are you using?
0.1.81
What version of Home Assistant Core are you running?
2024.8.3