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

Blog
2

thanks for new release!

very minor issue, but is “activity” supposed to be required now for the harmony component? with this config:

platform: harmony
name: living room
host: X.X.X.X

i get this new error in 0.64:

2018-02-25 21:02:23 ERROR (MainThread) [homeassistant.config] Invalid config for
 [remote.harmony]: required key not provided @ data['activity']. Got None. (See 
?, line ?). Please check the docs at https://home-assistant.io/components/remote
.harmony/

adding an activity line fixes it, but it’s listed as optional in the docs and it worked fine without it prior to 0.64.

1 Like
3

Thank you so much. Better and Better. ^^

I will try the update this evening.

4

Got this error with 0.64. This was fine in 0.63.3. This is for the Broadlink RM Mini3.

Error while setting up platform broadlink
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/broadlink/init.py”, line 5, in
from Crypto.Cipher import AES
File “/usr/local/lib/python3.6/site-packages/Crypto/Cipher/init.py”, line 3, in
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
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’

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.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/switch/broadlink.py”, line 74, in setup_platform
import broadlink
File “/usr/local/lib/python3.6/site-packages/broadlink/init.py”, line 7, in
import pyaes
ModuleNotFoundError: No module named ‘pyaes’

5

Will make a fix for 0.64.1.

1 Like
6

Congrats for the 1000 milestone!!

I did notice that Harmony remote now requires “activity” but the docs don’t make mention of any breaking change.

7

All my MQTT motion sensors and switches lag for a second.
Seems like HA needs some time to react on the mqtt payloads.
Back on 0.63.3 everthing is fast again and reacts in milliseconds.
Can someone confirm this?

8

Did you figure this out? I do have many broadlink devices. Worry update then something goes wrong.

9

Probably due to https://github.com/home-assistant/home-assistant/pull/12004. However I can’t confirm this :confused: I’ve been using this MQTT patch on my personal server for quite some time now and have not seen something like that happen. Could you post some information about your setup (mosquitto, …) and whether those sensors have topics that have many subscriptions? Thx

10

Thanks for posting this. I was just about to post the same.

11

I’ve had similar problem before. Stop HASS and then install pyaes with:

pip install pyaes
pip show pycryptodome
pip uninstall pycryptodome
pip install --upgrade pycryptodome

If there is no pycryptodome on your system try with pycrypto.

12

@OttoWinter, thanks for your responce.
I’m running HA in a venv on ubuntu, , python 3.6.3, eclipse-mosquitto in a docker container.
There are just a view Sonoffs and NodeMCU’s as motion sensors/switches that send ‘ON’ to different topics. I will test further when i’m at home in the evening and file a new topic/issue if necessary.

13

MySenors component stoped working:

Testing configuration at /config
ERROR:homeassistant.config:Invalid config for [mysensors]: length of value must be at least 1 for dictionary value @ data['mysensors']['gateways'][0]['topic_in_prefix']. Got None
length of value must be at least 1 for dictionary value @ data['mysensors']['gateways'][0]['topic_out_prefix']. Got None. (See /config/configuration.yaml, line 90). Please check the docs at https://home-assistant.io/components/mysensors/
ERROR:homeassistant.setup:Setup failed for mysensors: Invalid config.
Failed config
  mysensors: 
    gateways: [source /config/configuration.yaml:91]
      - device: 192.168.1.186
        tcp_port: 5003
    optimistic: True
    persistence: True
    retain: True
    version: 2.0

  General Errors: 
    - Setup failed for mysensors: Invalid config.

Successful config (partial)
  mysensors:
14

Hi,
what is the ETA for 0.64.1?

Thanks,
Klaus

15

Thanks for the report. Will be fixed in 0.64.1

1 Like
16

Thank you for the new release. However for MySensors I get:

ERROR:homeassistant.config:Invalid config for [mysensors]: length of value must be at least 1 for dictionary value @ data['mysensors']['gateways'][0]['topic_in_prefix']. Got None
length of value must be at least 1 for dictionary value @ data['mysensors']['gateways'][0]['topic_out_prefix']. Got None. (See /home/pi/.homeassistant/configuration.yaml, line 61). Please check the docs at https://home-assistant.io/components/mysensors/
ERROR:homeassistant.setup:Setup failed for mysensors: Invalid config.
Failed config
  mysensors: 
    gateways: [source /home/pi/.homeassistant/hubs/mysensors.yaml:1]
      - baud_rate: 115200
        device: /dev/ttyUSB0
        persistence_file: /home/pi/.homeassistant/mysensors.json
    optimistic: False
    persistence: True
    version: 1.5

  General Errors: 
    - Setup failed for mysensors: Invalid config.
17

I had the same problem with Mysensors, as a workaround I added this to my gateway config:

topic_in_prefix: 'mygateway1-out'
topic_out_prefix: 'mygateway1-in'

I don’t use the topics but mysensors works again.

18

Its great, no doubt, but still no BlueTooth support for NUC. I bet Rolls Royce component will be sooner than BT for NUC LOL :rofl:

19

I had a problem with platform: broadlink, lost all switches.

20

Super! Thanks.

21

Can confirm this works in Docker. Users need to execute this via SSH inside their container e.g. docker exec -it home-assistant bash, followed by a restart

1 Like