RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe

Question

RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe

pimw1 opened this issue 2 years ago · 50 comments

The problem

Since Home Assistant Core 2022.5.0b7, i receive the following error. This error was not present in Home Assistant Core 2022.5.0b6.

What version of Home Assistant Core has the issue?

core-2022.5.0b7

What was the last working version of Home Assistant Core?

core-2022.5.0b6

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: root
Source: /usr/src/homeassistant/homeassistant/bootstrap.py:326
First occurred: 23:50:50 (1 occurrences)
Last logged: 23:50:50

Uncaught exception
RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe

Additional information

No response

Answer 1 · 2022-05-04T05:54:22.000Z

I don't see any reason why this happens:

Our Numpy wheel is built on 6 Jan, and hasn't changed since then.
Our Python version and base image haven't changed in the past releases.
Nothing in b6 -> b7 is (or can be) NumPy related.

Questions:

What platform are you running? Could you provide the output of ha info (or alternatively, the data from the System Health menu)
Do you have custom integrations? Which ones?

Some things you can try:

Rebuilding Core using ha core rebuild
Disabling custom integration and running ha core rebuild after that

Answer 2 · 2022-05-04T07:45:20.000Z

ha info output:

Custom integrations:
hacs
local tuya
sonoff lan
ltss
adaptive_lighting
watchman
HyperHDR

ha core rebuild & disabling customr integration + ha core rebuild is something that i can do tonight / tomorrow.

Answer 3 · 2022-05-04T08:09:27.000Z

Hello, I have the same error message with the current beta. I use ha with a Docker container.

Answer 4 · 2022-05-04T08:43:38.000Z

Hello, I have the same error message with the current beta. I use ha with a Docker container.

Please follow #71270 (comment)

Answer 5 · 2022-05-04T09:24:00.000Z

My information from system health:

Version	core-2022.5.0b7
Installationstyp	Home Assistant Container
Entwicklung	false
Supervisor	false
Docker	true
Benutzer	root
Virtuelle Umgebung	false
Python-Version	3.9.9
Betriebssystemfamilie	Linux
Betriebssystem-Version	5.15.30-v7l+
CPU-Architektur	armv7l
Zeitzone	Europe/Berlin

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4884
Installed Version	1.24.5
Stage	running
Available Repositories	1026
Downloaded Repositories	18

Angemeldet	false
Zertifikatsserver erreichbar	ok
Authentifizierungsserver erreichbar	ok
Home Assistant Cloud erreichbar	ok

Dashboards	3
Ressourcen	11
Ansichten	21
Modus	storage

My custom integrations:

HACS
Miele Integration
Alarmo
Power calculation
Bosch Smart Home Controller (SHC) integration
Husqvarna Automower
Waste Collection Schedule

Answer 6 · 2022-05-04T09:41:14.000Z

We've rebuild our numpy wheels to be included in the final release

Answer 7 · 2022-05-04T18:29:21.000Z

I updated to 2022.5.0 but got it anyway 🤔 Was it supposed to be fixed or did it not get into .0?

Answer 8 · 2022-05-04T18:51:38.000Z

numpy/numpy#21036 (comment)

So is some other wheel compiled against the wrong numpy version? Any easy way to find out which one that could be? 🤔

Answer 9 · 2022-05-04T20:12:56.000Z

The issue is also present in 2022.5.0.

Answer 10 · 2022-05-04T20:17:47.000Z

I have the issue also on 2022.5.0

Answer 11 · 2022-05-04T20:20:25.000Z

I have the issue also on 2022.5.1

Let me know how you got 2022.5.1 😸 back to the future?

I tagged the issue for 2022.5.1 since it is still active, building wheels process did not finish, it is being worked on, I'll update here when it is fixed, no need for additional information.

Answer 12 · 2022-05-04T20:21:58.000Z

Oups :) Typo !

Answer 13 · 2022-05-04T20:27:15.000Z

Hello, I have the same error message with the latest 2022.5.0. I use ha with a Docker container

Answer 14 · 2022-05-04T20:28:21.000Z

I had the error too. My install:

Version	core-2022.5.0
Installation Type	Home Assistant Container
Development	false
Supervisor	false
Docker	true
User	root
Virtual Environment	false
Python Version	3.9.9
Operating System Family	Linux
Operating System Version	5.13.0-40-generic
CPU Architecture	x86_64
Timezone	America/New_York

I disabled all custom integrations and the error was still there, but normally run:
HACS
Alexa Media Player
Local Tuya
Meross Lan
NWS Alerts
TP Link Deco
Watchman
Node Red Companion

Debug logs seem to give a little more info:

2022-05-04 16:16:59 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [140095141387376] Sending {"id":83,"type":"result","success":true,"result":[{"name":"root","message":["Uncaught exception"],"level":"ERROR","source":["/usr/src/homeassistant/homeassistant/bootstrap.py",326],"timestamp":1651695415.7125967,"exception":"RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe\n","count":1,"first_occurred":1651695415.7125967}]}

Answer 15 · 2022-05-04T20:34:01.000Z

No need for additional I have it too (btw I have it too) 😃 , I tagged the issue for 2022.5.1 since it is still active, building wheels process did not finish, it is being worked on, I'll update here when it is fixed.

Answer 16 · 2022-05-05T11:12:36.000Z

Fix with: #71325

Answer 17 · 2022-05-06T01:22:30.000Z

I'm still seeing this on 2022.5.1. Just installed it 30 minutes ago.

System Health

version	core-2022.5.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.9
os_name	Linux
os_version	5.10.103-v8
arch	aarch64
timezone	America/Los_Angeles

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4934
Installed Version	1.24.5
Stage	running
Available Repositories	1035
Downloaded Repositories	10

Home Assistant Supervisor

host_os	Home Assistant OS 7.6
update_channel	stable
supervisor_version	supervisor-2022.05.0
docker_version	20.10.9
disk_total	111.1 GB
disk_used	8.1 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	Check Home Assistant configuration (3.10.0), Duck DNS (1.14.0), File editor (5.3.3), NGINX Home Assistant SSL proxy (3.1.1), Samba share (9.6.1), Terminal & SSH (9.4.0), ESPHome (2022.3.1), Samba Backup (5.0.0)

Dashboards

dashboards	2
resources	5
views	6
mode	yaml

Answer 18 · 2022-05-06T01:53:31.000Z

Also seeing this on 2022.5.1, unfortunately

System Health

version	core-2022.5.1
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.9.9
os_name	Linux
os_version	5.10.28-Unraid
arch	x86_64
timezone	America/Los_Angeles

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.24.5
Stage	running
Available Repositories	1039
Downloaded Repositories	31

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	1
resources	24
views	7
mode	storage

Sonoff

version	3.0.3
cloud_online	6 / 6
local_online	6 / 6

Answer 19 · 2022-05-06T02:41:40.000Z

I just updated to 2022.5.1 and still have this error in my logs.

Answer 20 · 2022-05-06T03:22:17.000Z

I just updated to 2022.5.1 and still have this error in my logs.

Same for me, just curious why this is "closed"

Answer 21 · 2022-05-06T04:20:23.000Z

2022.5.1 it's still there

Answer 22 · 2022-05-06T04:53:11.000Z

Also seeing this on 2022.5.1

Answer 23 · 2022-05-06T05:37:16.000Z

I just updated to 2022.5.1 and still have this error in my logs.

Answer 24 · 2022-05-06T05:55:53.000Z

I am on 2022.5.1 and this error brakes initial setup from fresh install.

It gets stuck here:

Answer 25 · 2022-05-06T06:33:13.000Z

I also still have the error message in .1

Answer 26 · 2022-05-06T06:51:17.000Z

Same got it in 5.0 and in 5.1

Answer 27 · 2022-05-06T07:10:30.000Z

+1 from me

Answer 28 · 2022-05-06T07:13:21.000Z

Ran into this same issue working on something completely unrelated.
This is caused by a version mismatch, updating numpy to 1.22 fixed the error in my case.

pip install --upgrade numpy

Answer 29 · 2022-05-06T07:35:37.000Z

@pvizeli was there a reason why we bumped to v1.21.6 and not to the latest v1.22.3 in #71325 ?
https://github.com/numpy/numpy/releases/tag/v1.22.3

Answer 30 · 2022-05-06T07:45:12.000Z

@pvizeli was there a reason why we bumped to v1.21.6 and not to the latest v1.22.3 in #71325 ? https://github.com/numpy/numpy/releases/tag/v1.22.3

It was bumped vs an existing wheel that was already built:
https://wheels.home-assistant.io/alpine-3.14/amd64/numpy-1.21.6-cp39-none-any.whl

v1.22.3 does not have a wheel build on the wheels repo.

Answer 31 · 2022-05-06T08:29:07.000Z

Not sure if that helps, but dependency tree on my machine:

numpy
Required-by: imageio, matplotlib, noaa-coops, pandas, pyairvisual, PyTurboJPEG

imageio
Required-by: env-canada

pandas
Required-by: noaa-coops, pyezviz, pykrakenapi

matplotlib
Required-by: pycocotools

Versions

numpy 1.21.6
imageio 2.19.0 (released on 2nd May)
pandas 1.4.2
matplotlib 3.5.2 (released on 3rd May)
env-canada 0.5.22
noaa-coops 0.1.8
pyezviz 0.2.0.6 (released on 27th April)
pykrakenapi 0.1.8
pycocotools 2.0.1

Answer 32 · 2022-05-06T08:45:40.000Z

I am also getting this error.

This is after a fresh installed with no changes or addons installed

I used has ova 7.6 for my image to install into VM. I also tried has_ova 8.0 RC3. Get the same error using that image to install

Answer 33 · 2022-05-06T08:46:58.000Z

Yes count me in as well!

Answer 34 · 2022-05-06T08:50:01.000Z

As I previously wrote here: #71270 (comment) no need for extra confirmations, it doesn't make handling this faster, it is being worked on, Thanks for your patience.

Answer 35 · 2022-05-06T10:58:49.000Z

We have to find the library which was build on around May 3 which use numpy and is used by all of this people. Then we can remove this and rebuild the wheel with the pin numpy version (#71408).

Maybe it's matplotlib-3.5.2-cp39-none-any.whl ?

Answer 36 · 2022-05-06T11:03:50.000Z

We have to find the library which was build on around May 3 which use numpy and is used by all of this people. Then we can remove this and rebuild the wheel with the pin numpy version (#71408).

Maybe it's matplotlib-3.5.2-cp39-none-any.whl ?

I have a clean HA OS instance which also has this problem and users already experience it during fresh install, wrote you on discord

Answer 37 · 2022-05-06T15:35:38.000Z

I can't reproduce it on my dev systems.

Is there any integration that can't loaded? What is the future issue after that? Maybe if we know this, we could find the integration/pip module that have an issue

Answer 38 · 2022-05-06T16:03:21.000Z

I have the same issue in a clean installation.

Let me know if you need me to debug something.

I am running the supervised version.

Answer 39 · 2022-05-06T16:32:05.000Z

Is there a way to do a supervised install with an older version?

Answer 40 · 2022-05-06T16:50:53.000Z

I've been digging in. My findings:

dhcp -> scapy -> matplotlib -> numpy.
Matplotlib was updated on May 2
We created wheel for it on May 3 which could mean it got compiled against a newer version with numpy.

Answer 41 · 2022-05-06T16:55:54.000Z

What is the effect of this error? Can I still carry on with my fresh install or should I wait for a fix?

…

On Fri, May 6, 2022 at 6:51 PM Paulus Schoutsen ***@***.***> wrote: I've been digging in. My findings: - dhcp -> scapy -> matplotlib -> numpy. - Matplotlib was updated on May 2 <https://pypi.org/project/matplotlib/#history> - We created wheel for it on May 3 <https://wheels.home-assistant.io/alpine-3.14/aarch64/#:~:text=matplotlib%2D3.5.2%2Dcp39%2Dnone%2Dany.whl> which could mean it got compiled against a newer version with numpy. — Reply to this email directly, view it on GitHub <#71270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXZ774I4SSW5Z4554CHYN6TVIVEXZANCNFSM5VAGDTRQ> . You are receiving this because you commented.Message ID: ***@***.***>

Answer 42 · 2022-05-06T16:57:32.000Z

It's fine. It just means that DHCP discovery is not currently available. It's not required for Home Assistant to work.

Pascal pinned numpy on wheels builder
I've removed the Matplotlib 3.5.2 wheels from wheels index for Alpine 3.14
Triggered build wheels action

Answer 43 · 2022-05-06T17:04:53.000Z

Just updated to 2022.5.1 still getting the error - I'm just running container (not supervised). Deleted the container, removed all old docker images, and re-downloaded fresh still getting the error unfortunately. Install info above - #71270 (comment)

Everything seems to be working fine just getting the error. Let me know if you need anything else to try and help troubleshoot or test

Answer 44 · 2022-05-06T17:07:32.000Z

Just updated to 2022.5.1 still getting the error - I'm just running container (not supervised). Deleted the container, removed all old docker images, and re-downloaded fresh still getting the error unfortunately. Install info above - #71270 (comment)

Everything seems to be working fine just getting the error. Let me know if you need anything else to try and help troubleshoot or test

It should be resolved soon, I can reproduce it and a new numpy wheel is being built right now, I'll update when it is fixed

Answer 45 · 2022-05-06T17:13:02.000Z

It's fine. It just means that DHCP discovery is not currently available. It's not required for Home Assistant to work.

Pascal pinned numpy on wheels builder

I've removed the Matplotlib 3.5.2 wheels from wheels index for Alpine 3.14

Triggered build wheels action

Thanks for reply. Glad I can carry one with my setup

Answer 46 · 2022-05-06T18:23:53.000Z

@thecode tested it and the new wheels work. This is fixed in 2022.5.2.

Thanks everybody that chimed in!

Answer 47 · 2022-05-06T19:39:41.000Z

Thank you all for your efforts to resolve the issue.

Answer 48 · 2022-05-07T16:12:01.000Z

Thanks, it is working great for me too now!

Answer 49 · 2022-05-07T19:12:32.000Z

I'm (still?) seeing this on .2:

Logger: root
Source: /usr/lib/python3.9/site-packages/homeassistant/bootstrap.py:326
First occurred: 3:04:09 PM (1 occurrences)
Last logged: 3:04:09 PM

Uncaught exception
RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe

I'm running linuxserver/homeassistant though, looks like it might be their problem?

Answer 50 · 2022-05-07T19:55:43.000Z

I'm (still?) seeing this on .2:

I'm running linuxserver/homeassistant though, looks like it might be their problem?

You will need to wait for linuxserver to fix their wheels, I don't know if they build their own wheels or copy the ones from Home Assistant, but the following wheels should be fixed:
https://wheels.linuxserver.io/homeassistant/matplotlib-3.5.2-cp39-cp39-linux_aarch64.whl
https://wheels.linuxserver.io/homeassistant/matplotlib-3.5.2-cp39-cp39-linux_armv7l.whl
https://wheels.linuxserver.io/homeassistant/matplotlib-3.5.2-cp39-cp39-linux_x86_64.whl