Core: Numpy missing, trend binary sensor doesn't function

[ohadbenita]

Home Assistant release: 0.62
Python release: 3.5.3
Component/platform:Trend Binary sensor
Description of problem:Numpy package is missing
Expected:All packages installed
Traceback (if applicable):

2018-01-28 13:37:39 ERROR (MainThread) [homeassistant.helpers.entity] Update for binary_sensor.mq_135_3_smoke_detected fails
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/core/__init__.py", line 16, in <module>
    from . import multiarray
ImportError: libf77blas.so.3: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 201, in async_update_ha_state
    yield from self.async_device_update()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 306, in async_device_update
    yield from self.async_update()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/binary_sensor/trend.py", line 177, in async_update
    yield from self.hass.async_add_job(self._calculate_gradient)
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/binary_sensor/trend.py", line 193, in _calculate_gradient
    import numpy as np
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/__init__.py", line 142, in <module>
    from . import add_newdocs
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/add_newdocs.py", line 13, in <module>
    from numpy.lib import add_newdoc
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/lib/__init__.py", line 8, in <module>
    from .type_check import *
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/lib/type_check.py", line 11, in <module>
    import numpy.core.numeric as _nx
  File "/srv/homeassistant/lib/python3.5/site-packages/numpy/core/__init__.py", line 26, in <module>
    raise ImportError(msg)
ImportError: 
Importing the multiarray numpy extension module failed.  Most
likely you are trying to import a failed build of numpy.
If you're working with a numpy git repo, try `git clean -xdf` (removes all
files not under version control).  Otherwise reinstall numpy.

Original error was: libf77blas.so.3: cannot open shared object file: No such file or directory

Additional info:
This started happening when I upgraded from 0.60.1 to 0.62

[fabaff]

The package is not missing, the installation on your system failed.

[ohadbenita]

I see no errors in the installation, also tried to manually install numpy from the venv

[fabaff]

ImportError: libf77blas.so.3: cannot open shared object file: No such file or directory

indicates that a devel package, probably the one of atlas or blas, is missing.

[Webserve]

Had the same error. fixed it with the command:

sudo apt-get install libatlas-base-dev

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

[starkillerOG]

I had the same issue with the binary trend sensor, installing libatlas-base-dev (apt-get install libatlas-base-dev) fixed it for me.
@fabaff maybe this pakkage schould be added to the requirements of the binary trend sensor?

[ohadbenita]

+1 for that

On Sat, 1 Sep 2018 at 23:30 starkillerOG [e-mail] wrote:

I had the same issue with the binary trend sensor, installing
libatlas-base-dev (apt-get install libatlas-base-dev) fixed it for me.
@fabaff https://github.com/fabaff maybe this pakkage schould be added
to the requirements of the binary trend sensor?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/11993#issuecomment-417888259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdL_vhui6owmztauwb1c1kFb906FGhKjks5uWvxcgaJpZM4RvqiX
.

>

אוהד בניטה
נייד - 0508246047

__/ # ##
(^=_ p _###_
c / ) | /
_____- //^---~ _c 3
/ ----^\ /^_\ / --,-
( | | O_| \_/ ,/
| | | / \| `-- /
(((G |-----|
//-----\
// \
/ | | ^|
| | | |
|____| |____|
/______) (_____\