Eatoff
That was quick for the raspberry pi 4 support! I just got it up and running on Raspbian Buster last night, might just move it all across anyway
Edit: actually, no USB boot support yet. I moved my raspbian to a USB SSD
That was quick for the raspberry pi 4 support! I just got it up and running on Raspbian Buster last night, might just move it all across anyway
Edit: actually, no USB boot support yet. I moved my raspbian to a USB SSD
Thanks for all your hard work! Regarding pi 4 support, is the 32 bit version recommended, or the 64 bit version?
2 repliesActually, no it doesn’t if you are on a tablet in landscape mode it shows the minimized sidebar.
1 replyre the sidebar, what about us poor souls who specifically asked during the original twitter thread started by JuanMTech mockup that we wanted to keep the ability to completely turn off the sidebar?
“The sidebar will now always be visible” feels like you just ignored us.
Please don’t take this the wrong way. I love the work you guys do, and appreciate the effort that is involved. But this feels like you just made a pretty big choice for all users about how their HA system is going to look.
How then do you unhide it to access say the dev-tools? (answer: you can’t easily)
1 replyIf it does operate that way then it sounds like an acceptable solution.
I have upgraded and it doesn’t
I will not be adding any more features related to the sidebar. Since CCH only operates inside of Lovelace I need to keep any interaction with the sidebar to a minimum. The sidebar is required for navigation outside of Lovelace, so any modification of it should be handled with an addon that is available across the entire frontend. Something like this doesn’t exist yet, but I’m sure it will in time.
Talked about it a bit here: Compact Custom Header
I’m seeing the same error with nmap_tracker and unifi. Unifi was giving the same error in 0.95.4 as well (but runs fine).
My ecobee climate objects have lost the ‘operation’ attribute in this release. I don’t see any documented change on that, though, so could this be a bug?
1 replyThanks! I overlooked to do that.
Kind of odd that if you don’t enable Advanced mode, you still get the menu to restart the server!
… and here we go again. My perfectly functional custom component from 0.94.2 isn’t loaded in 0.96.0. No complaints in the log during startup but no component created. Only when I run Config Check does it report: Platform not found: climate.my_mqtt
Looks like I have my work cut out for me.
I don’t know what exactly transpired on the discord channel but the new menu’s inability to be hidden is not to my liking.
6 repliesFirst stab of it, maybe get added in later release. I know they removed another part when not in advanced mode after feedback
I was monitoring the beta and didn’t see anything dramatically different in MQTT HVAC. Of course, all it takes is just one little change in just the right place …
Unrelated to my custom component but I just noticed i0.96.0 can’t find the toggle-lock-entity-row card. Weird. More digging to be done.
Ditto. Though using CCH to hide it on tablets and for users who I don’t want to access it at all is possible. So no drama.
Nor mine. All objections dismissed.
The ability of CCH to hide it isn’t adequate IMO.
I’m really looking forward to this update (cloud fix):
really happy that the HassIO version is out so quickly too! Awesome
I’m seeing 0.96 there
I stand corrected. my bad
whoooo buddy… I am not even sure where to start with this lol. This is what the config tester gives me.
I am currently running 95.4
copying cffi/_embedding.h -> build/lib.linux-armv7l-3.7/cffi
copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.7/cffi
running build_ext
building '_cffi_backend' extension
creating build/temp.linux-armv7l-3.7
creating build/temp.linux-armv7l-3.7/c
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include/python3.7m -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.7/c/_cffi_backend.o
unable to execute 'gcc': No such file or directory
error: command 'gcc' failed with exit status 1
----------------------------------------
ERROR: Failed building wheel for cffi
Running setup.py clean for cffi
Building wheel for pycparser (setup.py): started
Building wheel for pycparser (setup.py): finished with status 'done'
Stored in directory: /root/.cache/pip/wheels/f2/9a/90/de94f8556265ddc9d9c8b271b0f63e57b26fb1d67a45564511
Successfully built pycparser
Failed to build cffi
Installing collected packages: setuptools, wheel, pycparser, cffi
Running setup.py install for cffi: started
Running setup.py install for cffi: finished with status 'error'
ERROR: Complete output from command /usr/local/bin/python -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-728nqkv3/cffi/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-5sb4lqs2/install-record.txt --single-version-externally-managed --prefix /tmp/pip-build-env-gbqe3dil/overlay --compile:
ERROR: unable to execute 'gcc': No such file or directory
unable to execute 'gcc': No such file or directory
No working compiler found, or bogus compiler options passed to
the compiler from Python's standard "distutils" module. See
the error messages above. Likely, the problem is not related
to CFFI but generic to the setup.py of any Python package that
tries to compile C code. (Hints: on OS/X 10.8, for errors about
-mno-fused-madd see http://stackoverflow.com/questions/22313407/
Otherwise, see https://wiki.python.org/moin/CompLangPython or
the IRC channel #python on irc.freenode.net.)
Trying to continue anyway. If you are trying to install CFFI from
a build done in a different context, you can ignore this warning.
running install
running build
running build_py
creating build
creating build/lib.linux-armv7l-3.7
creating build/lib.linux-armv7l-3.7/cffi
copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/verifier.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/lock.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/api.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/model.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/recompiler.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/__init__.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/cparser.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/error.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/commontypes.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.7/cffi
copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.7/cffi
copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.7/cffi
copying cffi/_embedding.h -> build/lib.linux-armv7l-3.7/cffi
copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.7/cffi
running build_ext
building '_cffi_backend' extension
creating build/temp.linux-armv7l-3.7
creating build/temp.linux-armv7l-3.7/c
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include/python3.7m -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.7/c/_cffi_backend.o
unable to execute 'gcc': No such file or directory
error: command 'gcc' failed with exit status 1
----------------------------------------
ERROR: Command "/usr/local/bin/python -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-728nqkv3/cffi/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-5sb4lqs2/install-record.txt --single-version-externally-managed --prefix /tmp/pip-build-env-gbqe3dil/overlay --compile" failed with error code 1 in /tmp/pip-install-728nqkv3/cffi/
----------------------------------------
ERROR: Command "/usr/local/bin/python /usr/local/lib/python3.7/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-gbqe3dil/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple --find-links https://wheels.home-assistant.io/alpine-3.9/armv7/ -- 'setuptools>=40.6.0' wheel 'cffi>=1.8,!=1.11.3; python_implementation != '"'"'PyPy'"'"''" failed with error code 1 in None
[23:01:18] ERROR: An error occurred while installing Home Assistant:
Looking in links: https://wheels.home-assistant.io/alpine-3.9/armv7/
Collecting homeassistant
Downloading https://files.pythonhosted.org/packages/15/85/89cc12c8d9d6969bdc394e56aae8107cfc7112255b346ffa7fb6f575ce64/homeassistant-0.96.0-py3-none-any.whl (5.0MB)
Collecting python-slugify==3.0.2 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/c1/19/c3cf1dc65e89aa999f85a4a3a4924ccac765a6964b405d487b7b7c8bb39f/python-slugify-3.0.2.tar.gz
Collecting aiohttp==3.5.4 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/0f/58/c8b83f999da3b13e66249ea32f325be923791c0c10aee6cf16002a3effc1/aiohttp-3.5.4.tar.gz (1.1MB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Collecting attrs==19.1.0 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/23/96/d828354fa2dbdf216eaa7b7de0db692f12c234f7ef888cc14980ef40d1d2/attrs-19.1.0-py2.py3-none-any.whl
Collecting astral==1.10.1 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/ff/5d/261f49822b7f77c265197d46cdbaaaaf06f458734e9ac55a140dd75bdf29/astral-1.10.1-py2.py3-none-any.whl
Requirement already satisfied: pip>=8.0.3 in /usr/local/lib/python3.7/site-packages (from homeassistant) (19.1.1)
Collecting pytz>=2019.01 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/3d/73/fe30c2daaaa0713420d0382b16fbb761409f532c56bdcc514bf7b6262bb6/pytz-2019.1-py2.py3-none-any.whl (510kB)
Collecting pyyaml==5.1.1 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz (274kB)
Collecting cryptography==2.7 (from homeassistant)
Downloading https://files.pythonhosted.org/packages/c2/95/f43d02315f4ec074219c6e3124a87eba1d2d12196c2767fadfdc07a83884/cryptography-2.7.tar.gz (495kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'error'
6 replies
I haven’t updated yet as I suspect I am going to need to re-check all my climate stuff but I can’t think of ANY reason I would always want the sidebar visible even if it was more compact. It mostly contains functions the admin is considered with not a typical user.
And on mobile I have completely removed both menus with the compact header mode as most of the time they are BOTH not necessary since they are mostly edit functions.
1 replySounds like I should wait a few days for the custom lovelace components to update and I should be good to go.
Just hope the compact header can still allow the notification icon to be visible and not part of the side bar.
1 replyNot a big fan of UI items that stick out and can’t be hidden. This is kind of a step back from “clean” UI.
I don’t mind the new sidebar arrangement, but
I have only tried on my desktop so far; and
I agree you should be able to get rid of it.
The new Dev Tools are awesome.
Going back to them and seeing the same states/templates is realy great!
Thanks for this!
The Hue integration is broken after I updated to .96 - other that have this issue?
I see no errors in the logs, but every Hue light or sensor is unavailable.
Okay - after 5 restarts the Hue devices is back - strange that nothing is written to the log if the bridges (yes I have 2) were out of reach (which have never happend before)
I don’t think the config checker would be able to check if there would be issues with installing dependencies in this case.
Hue works here.
My enphase integration seems to be broken. No entities found following an update to 0.96 on hassio.
Log Details (ERROR)
Thu Jul 18 2019 00:30:30 GMT-0700 (Pacific Daylight Time)
Error while setting up platform enphase_envoy
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/src/homeassistant/homeassistant/components/enphase_envoy/sensor.py", line 45, in async_setup_platform
from envoy_reader.envoy_reader import EnvoyReader
File "/usr/local/lib/python3.7/site-packages/envoy_reader/envoy_reader.py", line 8, in <module>
import requests_async as requests
ModuleNotFoundError: No module named 'requests_async'
4 replies
I have No Lights they are all unavailable. I Am using Deconz Conbee it was working in 95.4.
The logs show no errors. And the config Configuration valid!
Will try and keep rebotting HA As @BlackChart has done.
2 repliesI am getting excactly the same when checking 0.95.4 -> 0.96 using: Check Home Assistant configuration Add-on
partial log:
copying cffi/pkgconfig.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/ffiplatform.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/cparser.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/vengine_cpy.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/setuptools_ext.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/lock.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/__init__.py -> build/lib.linux-x86_64-3.7/cffi
copying cffi/_cffi_include.h -> build/lib.linux-x86_64-3.7/cffi
copying cffi/parse_c_type.h -> build/lib.linux-x86_64-3.7/cffi
copying cffi/_embedding.h -> build/lib.linux-x86_64-3.7/cffi
copying cffi/_cffi_errors.h -> build/lib.linux-x86_64-3.7/cffi
running build_ext
building '_cffi_backend' extension
creating build/temp.linux-x86_64-3.7
creating build/temp.linux-x86_64-3.7/c
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include/python3.7m -c c/_cffi_backend.c -o build/temp.linux-x86_64-3.7/c/_cffi_backend.o
unable to execute 'gcc': No such file or directory
error: command 'gcc' failed with exit status 1
2 replies
How are you checking?
Hi @rendili
No i have not updated the Hive Component yet because the wife needs the lights back on.
I Found the probem it was a Custom Component Call Light Proxy by @OttoWinter
I have uninstalled it and now my lights are back…
2 repliesMe too (Same here and not upgrading yet).
I thought carefully about not adding to a flood of “me too” posts but then decided that it was probably the only way to get issues noticed on this forum. Although I suspect the issue is with the checker add-on rather than the latest version of HA).
That’s why I was asking… I don’t think that checker addon has worked for a while and I deleted it. There is a breaking-changes custom component but I have not used that either. I generally just check for the breaking changes in the release notes.
The new OpenTherm Gateway component does not create a climate device (see https://github.com/home-assistant/home-assistant/issues/25239) , but it does add a dozen sensors. Most of them are useless for me, as my central heater does not support all those features. Is there a way to limit that behaviour?
Seeing exactly the same. I’m on 0.94.4.
Hi all.
Unfortunately broadlink switch seems broken (was OK in 95):
2019-07-18 11:47:25 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform broadlink
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/broadlink/switch.py", line 80, in setup_platform
broadlink_device = broadlink.rm((ip_addr, 80), mac_addr, None)
File "/srv/homeassistant/lib/python3.7/site-packages/broadlink/__init__.py", line 529, in __init__
device.__init__(self, host, mac, devtype)
File "/srv/homeassistant/lib/python3.7/site-packages/broadlink/__init__.py", line 171, in __init__
self.update_aes(key)
File "/srv/homeassistant/lib/python3.7/site-packages/broadlink/__init__.py", line 184, in update_aes_crypto
backend=default_backend())
File "/srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/backends/__init__.py", line 15, in default_backend
from cryptography.hazmat.backends.openssl.backend import backend
Config:
- platform: broadlink
host: 192.168.1.222
mac: 'C8:F7:42:16:F3:73'
type: rm_mini
switches:
condizionatore_pwr1:
friendly_name: "condizionatore1"
command_on: 'JgBAAAABGYkVMhUPFQ8VDxUzFQ8VDxUPFQ8VDxUPFQ8VDxUPFQ8VDxUPFTMUEBQQFBAUMx$...'
command_off: 'JgBAAAABGYkVMxUPFQ8VDxUyFQ8VDxUPFTMVMxUPFQ8VDxUPFQ8VDxUPFBAUEBQQFBAUM$....'
Many thanks!!
3 repliessame after reboot
thanks…
I am 100% aware of it and have been following it from its early days in the GitHub architecture repo to the PR by pvizeli.
I’m having same issue, but I haven’t solved after few restarts
My config is
- platform: nmap_tracker
home_interval: 5
hosts: 192.168.1.0/24
# interval_seconds: 30
# consider_home: 180
before 0.96 I had also the two commented lines active, and no issue.
Looking at the integrations description I don’t see those two parameters.
Are these still active?
Where should I open the issue?
Thanks
1 replyI’m seeing similar on my iPad… it’s not snapping back properly (iOS app and chrome) but not 100% sure it’s HA and not the iOS 13 beta causing it…
1 replythey are part of the device_tracker
see link at the bottom of the page you referenced
Thanks, nice to know it’s not just happening to me. I guess this is ‘v1’ of the new sidebar, hopefully ‘v2’ will work out a few of these issues
I have the exact same log error using the enphase integration as well. Was looking forward to mapping out individual inverter numbers…
installed hassio on pi4, but getting “… add-on is not available on your system.” for all add-ons? Any ideas?
1 replyDitto.
I don’t see why there has to be a tradeoff. You want icons? Then you gotta lose the ability to hide the menu!
Eh?
I’m not fond of the workaround which is install and configure a completely different menu.
Car Customer: I don’t like this new triangular steering wheel. I prefer the round one.
Car Dealer: It’s the latest thing. It’s better. Trust me.
Car Customer: Can I get a round one?
Car Dealer: Sure. Just replace it yourself.
Yep you are not alone:
Same here. Got similar error, but there are some differences.
Also I’ve tried to:
Any suggestion!?
2 repliesHaving similar issues on my xiaomi vacuum cleaner here too, with the same ImportError about OPENSSL_1_1_1.
xiaomi_miio: Error on device update!
...
ImportError: /usr/lib/arm-linux-gnueabihf/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so)
Anyone else got issues trying to update?
My hassio log spits out something along the lines:
19-07-18 11:49:41 INFO (SyncWorker_9) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.95.4 to homeassistant/qemux86-64-homeassistant:0.96.0
19-07-18 11:49:41 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.96.0.
19-07-18 11:50:33 ERROR (SyncWorker_9) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.96.0 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.96.0: No such image: homeassistant/qemux86-64-homeassistant:0.96.0").
19-07-18 11:50:33 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
Reading the “404 - not found” error I thought the image might be taken down, so I tried pulling the image locally (docker pull homeassistant/qemux86-64-homeassistant:0.96.0
) but this works just fine.
ASUSWRT stopped working.
Error during setup of component asuswrt
13:51 components/asuswrt/init.py (ERROR)
Thu Jul 18 2019 13:51:35 GMT+0200 (centraleuropeisk sommartid)
Error during setup of component asuswrt
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py”, line 153, in _async_setup_component
hass, processed_config)
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/asuswrt/init.py”, line 45, in async_setup
from aioasuswrt.asuswrt import AsusWrt
File “/srv/homeassistant/lib/python3.7/site-packages/aioasuswrt/asuswrt.py”, line 9, in
from aioasuswrt.connection import SshConnection, TelnetConnection
File “/srv/homeassistant/lib/python3.7/site-packages/aioasuswrt/connection.py”, line 6, in
import asyncssh
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/init.py”, line 31, in
from .agent import SSHAgentClient, SSHAgentKeyPair, connect_agent
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/agent.py”, line 35, in
from .public_key import SSHKeyPair, load_default_keypairs
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/public_key.py”, line 43, in
from .encryption import get_encryption_params, get_encryption
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/encryption.py”, line 23, in
from .crypto import BasicCipher, GCMCipher, ChachaCipher, get_cipher_params
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/crypto/init.py”, line 27, in
from .ec import ECDSAPrivateKey, ECDSAPublicKey, ECDH
File “/srv/homeassistant/lib/python3.7/site-packages/asyncssh/crypto/ec.py”, line 24, in
from cryptography.hazmat.backends.openssl import backend
File “/srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/backends/openssl/init.py”, line 7, in
from cryptography.hazmat.backends.openssl.backend import backend
File “/srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/backends/openssl/backend.py”, line 74, in
from cryptography.hazmat.bindings.openssl import binding
File “/srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py”, line 15, in
from cryptography.hazmat.bindings._openssl import ffi, lib
ImportError: /usr/lib/arm-linux-gnueabihf/libssl.so.1.1: version `OPENSSL_1_1_1’ not found (required by /srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so)
have you find a solution?
still looking for it, since I get error during “Check Home Assistant configuration”
Failed config
General Errors:
- Platform not found: device_tracker.nmap_tracker
Thanks
I’ve never installed or updated numpy, is this something I should attempt to fix or is this something the developers of the IQVIA platform need to address?
IQVIA Platform Error
2019-07-18 06:06:12 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform iqvia.sensor: Platform not found (
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the multiarray numpy extension module failed. Most
likely you are trying to import a failed build of numpy.
Here is how to proceed:
git clean -xdf
Check that you are using the Python you expect (you’re using /srv/homeassistant/bin/python),
and that you have no directories in your PATH or PYTHONPATH that can
interfere with the Python and numpy versions you’re trying to use.
If (1) looks fine, you can open a new issue at
https://github.com/numpy/numpy/issues. Please include details on:
Note: this error has many possible causes, so please don’t comment on
an existing issue about this - open a new one instead.
Original error was: libf77blas.so.3: cannot open shared object file: No such file or directory
).
Replying to my own problem here.
In case anyone gets this issue, check your disk usage %, after running docker pull homeassistant/qemux86-64-homeassistant:0.96.0
ssh’d onto hassio it told me there is no disk space left.
Sadly the error output from hassio is a bit misleading here.
eq3btsmart error also in 0.96…
2019-07-18 13:56:17 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform eq3btsmart
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/eq3btsmart/climate.py", line 69, in setup_platform
devices.append(EQ3BTSmartThermostat(mac, name), True)
TypeError: append() takes exactly one argument (2 given)
In config:
climate:
- platform: eq3btsmart
devices:
salotto:
mac: !secret salotto_mac
I’m also having the same issue. chrome seems to be doing it as well but only randomly
You guys using a browser for this or the iOS app? I’ve noticed that the app fully hides the sidebar. I’ll be honest. I like the way the iOS app does it over this new shrinking side bar.
Not a fan of the never hiding sidebar on desktop.
For all those people with OPENSSL issues, please follow the discussion here.
Sorry - what is CCH?
I’ve had a play with the new menu and I am not a fan at all.
It takes up screen real-estate for little benefit. 95% of the time I have the sidebar closed and only open it for config tasks. Why have something taking up screen space when I hardly use it?
Nothing should interact on mouse-over. It’s not a design paradigm anywhere else in home-assistant. I’m a bit shakey on a mouse - and the first thing I did when messing about on the demo screen is try to open the top left camera - overshot a bit and suddenly the sidebar is open. Then over to the right to let it close - and then I did it again!
At the most - if we have to have a slidey sidebar - why can’t it just slide in when you hover over the hamburger top left? Why take up all that space on the main screen?
It really looks like they thought it looked cool and just did it. Is this something somebody could make a custom component for like they did to de-clutter the top banner?
1 replySo not really related to the new version (haven’t updated yet)
But on the demo how do you get the weather map? is it just linking to an external site or is it a component I’m not aware of?
@DavidFW1960 It is same on IOS12 on iPad. I have raised a bug report on it on github today
Can someone try and open HA 0.96 in Edge?
On the computer I have access to here at work NOTHING is displayed other than a blue bar.
I do not normally use Edge so I do not know how it worked in 0.95. I tried because I noticed issues with the new left bar in Google Chrome on Linux. The Google Chrome issue went away after a yum update on that Centos machine
But when I look at my Home Assistant in Edge in Windows 10 I cannot get the browser to display anything. I never get to the login prompt. Nothing. Can someone here confirm that problem?
Hi everyone, Great Work that you all do with Home Assistant, Love it!
Love Updates and all the changes, but this time after updating to 0.96, Cloud Component broke… And the problem seems to be the same as other people posted above for other broke components.
2019-07-18 12:00:28 ERROR (MainThread) [homeassistant.setup] Error during setup of component cloud
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 153, in _async_setup_component
hass, processed_config)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/cloud/__init__.py", line 142, in async_setup
from hass_nabucasa import Cloud
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 16, in <module>
from .remote import RemoteUI
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/remote.py", line 16, in <module>
from .acme import AcmeClientError, AcmeHandler
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/acme.py", line 9, in <module>
import OpenSSL
File "/srv/homeassistant/lib/python3.7/site-packages/OpenSSL/__init__.py", line 8, in <module>
from OpenSSL import crypto, SSL
File "/srv/homeassistant/lib/python3.7/site-packages/OpenSSL/crypto.py", line 16, in <module>
from OpenSSL._util import (
File "/srv/homeassistant/lib/python3.7/site-packages/OpenSSL/_util.py", line 6, in <module>
from cryptography.hazmat.bindings.openssl.binding import Binding
File "/srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 15, in <module>
from cryptography.hazmat.bindings._openssl import ffi, lib
ImportError: /usr/lib/arm-linux-gnueabihf/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /srv/homeassistant/lib/python3.7/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so)
Tried to update and upgrade de OS, I’m running Hassbian Strech instillation, didn’t work.
Keep the good work, thanks.
Edge stopped working for me awhile back.
Recently I installed the new Canary Version and with 96 it works perfectly
I have just checked and I have the same issue with edge.
With 0.94.2 it works in Edge (no so snappy in performance compared to Chrome), but with 0.96.0 I get just the bar at the top (Orange for me with this server ) , no menu options / text