0.64: Over 1000 integrations! New: HomeKit, BMW, August

same zha issue here. Running the docker image

Edit: should add this is using the HUSBZB-1 stick

2018-02-26 19:51:46 ERROR (MainThread) [homeassistant.setup] Error during setup of component zha
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/setup.py", line 145, in _async_setup_component
    result = yield from component.async_setup(hass, processed_config)
  File "/usr/src/app/homeassistant/components/zha/__init__.py", line 96, in async_setup
    from bellows.zigbee.application import ControllerApplication
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 7, in <module>
    import zigpy.application
  File "/usr/local/lib/python3.6/site-packages/zigpy/application.py", line 6, in <module>
    import zigpy.appdb
  File "/usr/local/lib/python3.6/site-packages/zigpy/appdb.py", line 4, in <module>
    import zigpy.device
  File "/usr/local/lib/python3.6/site-packages/zigpy/device.py", line 5, in <module>
    import zigpy.endpoint
  File "/usr/local/lib/python3.6/site-packages/zigpy/endpoint.py", line 7, in <module>
    import zigpy.util
  File "/usr/local/lib/python3.6/site-packages/zigpy/util.py", line 6, in <module>
    from Crypto.Cipher import AES
  File "/usr/local/lib/python3.6/site-packages/Crypto/Cipher/__init__.py", line 3, in <module>
    from Crypto.Cipher._mode_ecb import _create_ecb_cipher
  File "/usr/local/lib/python3.6/site-packages/Crypto/Cipher/_mode_ecb.py", line 29, in <module>
    from Crypto.Util._raw_api import (load_pycryptodome_raw_lib,
  File "/usr/local/lib/python3.6/site-packages/Crypto/Util/_raw_api.py", line 32, in <module>
    from Crypto.Util.py3compat import byte_string
ImportError: cannot import name 'byte_string'

Getting an error with the coinbase sensor since updating to .64

2018-02-27 03:09:55 ERROR (MainThread) [homeassistant.setup] Error during setup of component coinbase
Traceback (most recent call last):
File “/usr/src/app/homeassistant/setup.py”, line 148, in _async_setup_component
component.setup, hass, processed_config)
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 327, in iter
yield self # This tells Task to wait for completion.
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 250, in _wakeup
future.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 243, in result
raise self._exception
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/coinbase.py”, line 51, in setup
api_key, api_secret)
File “/usr/src/app/homeassistant/components/coinbase.py”, line 77, in init
from coinbase.wallet.client import Client
File “/usr/local/lib/python3.6/site-packages/coinbase/wallet/client.py”, line 38, in
from Crypto.Hash import SHA256
File “/usr/local/lib/python3.6/site-packages/Crypto/Hash/SHA256.py”, line 23, in
from Crypto.Util._raw_api import (load_pycryptodome_raw_lib,
File “/usr/local/lib/python3.6/site-packages/Crypto/Util/_raw_api.py”, line 32, in
from Crypto.Util.py3compat import byte_string
ImportError: cannot import name ‘byte_string’

Not sure if this is still an issue - but when I briefly tried 0.64 I saw an error:

Error while setting up platform denonavr

And the Marantz network receiver I use stopped showing up as a media player. Unfortunately I rolled back to 0.63 because of the broad link issues and dont have further information on this issue.

From the SSH container:

curl -d '{"version": "0.63.3"}' http://hassio/homeassistant/update

(replace 0.63.3 with whatever version you want to roll back to)

4 Likes

I checked my Marantz (NR1605) after spotting someone with Denon losing their input selections in 0.64. My device and controls appear fine, so think this a more specific Marantz device issue.

I got this too…

1 Like

ohh ok - will try again to get some more details by updating to 0.64.

If its any help - my model is Marantz M-CR603 (Network CD Receiver)

a huge mess with entity_registry and xiaomi gateway/devices

Already rolled back. But I noticed at least 2 of my zigbee devices are now messed up. Going to have to fix them now.

Adding an activity line does not fix the problem for me. I still get the error.

The Pollen sensor is working for me on 0.64. What log entries related to it are you seeing?

Running 0.64.1 which was recently pushed out, broadlink and harmony fixed.

I couldn’t see it mentioned anywhere in the changelog but you appear to have fixed the GPIOs not returning to the inactive state on short pulses. Awesome! Thank you.
Better but not fixed. Short pulses do still hang the gpio binary sensor in the active state.

still waiting for the hass.io update. I’m thinking I may want to move to hassbian…have to think about that.

How to update to 0.64.1?, i must downgrade to 0.63.3. But since 0.64.1 fix my problem, i want to update but it not appear, even after i re-update to 0.64.0. I also try @Tinkerer suggest:

curl -d ‘{“version”: “0.64.1”}’ http://hassio/homeassistant/update

But it not work

Edit: opened an issue as it never seems to complete.
https://github.com/home-assistant/home-assistant/issues/12797

After updating my instance has been slow and unresponsive. I have found that a postgres query is running to try and clean up old records or purge anything older than 10 days. Just an FYI if anyone else is having issues.

datid | datname | pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | xact_start | query_start | state_change | waiting | state | backend_xid | backend_xmin | query
-------±---------±-----±---------±---------±-----------------±------------±----------------±------------±------------------------------±------------------------------±------------------------------±------------------------------±--------±-------±------------±-------------±----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
58038 | hass | 1555 | 16384 | hass | | | | -1 | 2018-02-28 00:58:01.164423+00 | 2018-02-28 01:28:01.162094+00 | 2018-02-28 01:29:39.773623+00 | 2018-02-28 01:29:39.773627+00 | f | active | 9907992 | 9907992 | DELETE FROM events WHERE events.time_fired < ‘2018-02-18T01:28:01.160835+00:00’::timestamptz AND events.event_id NOT IN (3216110, 3216111, 3216933, 3227885, 3227887, 3227888, 3227889, 3227891, 3227900, 3227911, 3227912, 3227913, 3227921, 3227922, 3227923, 3227924, 3227925, 3227926, 3227928, 3227929, 3227930, 3227950, 3227951, 3227953, 3227956, 3227963, 3227964, 3227969, 3227971, 3227974, 3227975, 3227976, 3227981, 3227987, 3227988, 3227989, 3227990, 3227991, 3227992, 3227993, 3227994, 3228007, 3228008, 3228012, 3228013, 3228014, 3228016, 3228017, 3228018, 3228024, 3228025, 3228026, 3228027, 3228029, 3228032, 3228033, 3228034, 3228035, 3228039, 3228058, 3228061, 3228075, 3228076, 3228080, 3228081, 3228082, 3228083, 3228102, 3228103, 3228107, 3228108, 3228109, 3228110, 3228126, 3228127, 3228135, 3228136, 3228146, 3228148, 3228149, 3228150, 3228151, 3228152, 3228154, 3228159, 3228166, 3228167, 3228169, 3228174, 3228179, 3228181, 3228182, 3228183, 3228185, 3228187, 3228194, 3228196, 3228202, 3228203, 3228210, 32

Hi, it’s great that we now render the charts 100% locally. Thank you for that, but here is my feedback on the Chat.js usability in HASS:

  • My light level sensor doesn’t always sent a value and it shows like this (before it showed an uninterrupted line):

  • One of my temperature sensors gets a new value every 1 hour and is plotted like this (before it showed a normal line - not “steps”):

  • The info window shows up ON TOP of the chart, hiding big chunks of the chart beneath it. The info window should show ABOVE the chart, so it doesn’t hide it: image

  • In the timelines, if we can’t specifically the colours we want (maybe in the future, right?) maybe it would be best to exclude the colour “white”:

  • Scrolling up/down the history page on a mobile phone needs some fixing. We end up scrolling and zooming each chart individually. I don’t have a suggestion on how to fix it, but it should be considered.

Keep up the good work!

2 Likes

My first expression of hte 0.64.1 - seems snappy and almost everything is ok!

I live in Europe and would like to have time stamps in 24hour format, it seems new version is in 12hour format and date is also showing in US-format:

image

2 Likes

If you have experience with programming and want more control over your system than hassbian is a better option indeed. I also used Hass.io at the first time but found it so restricting (because I want to have control over the pi) that I switched to the hassbian version :wink:

Another issue with the new charts:

  • The Y axis should start in 0:
    image