0.91: More streaming, better Zigbee, cameras with ESPHome

Juliean_Galak · April 12, 2019, 9:58pm

Did you install Tensorflow as a docker container? Or with the pip method?

hunterjm · April 12, 2019, 10:12pm

TensorFlow is included in the official docker container or through pip for venv installs. You can not use a separate TensorFlow standalone container.

Juliean_Galak · April 12, 2019, 10:17pm

You mean it’s included in the Hass.io official container? Fantastic, didn’t realize that. One less thing to worry about

hunterjm · April 13, 2019, 4:06am

No, not Hass.io. Home Assistant container.

kirpat · April 13, 2019, 4:25am

Dear,
Do you mean downloading homeassistant as container on raspbian strech or any os?

Juliean_Galak · April 13, 2019, 8:51pm

I’m very new to docker, so didn’t even know there was a separate home assistant container as separate from the hass.io container (running on ubuntu under Docker). Regardless, I found your hass.io add-on fir installing tensorflow on hass.io, and it appears to be working, or at least not throwing errors. I set it up on one camera, but I need to have someone actually walk past that camera before I can tell if it’s on or not. (I set it up remotely, there’s noone home)

AZDane · April 15, 2019, 4:00am

For some reasion 0.91.3 is not showing up as available in my Hass.io. I’m presently at 0.91.2

Anything I can do to make it show?

nickrout · April 15, 2019, 4:25am

Wait for the hassio image to be built?

AZDane · April 15, 2019, 5:00am

But does it normally take this long? It was released the 10th. Is there a place I can see the latest Hass.io version?

aidbish · April 15, 2019, 7:10am

Try this
From ssh

hassio ha update --version=0.91.3

tom_l · April 15, 2019, 7:10am

I updated to 0.91.3 a few days ago so it should be available.

Klagio · April 15, 2019, 8:25am

No, I had it since some days, updated yesterday

AZDane · April 15, 2019, 1:07pm

Yes, I guess I could do that. Just curious what would cause it not to show up.

chri5tian · April 21, 2019, 10:17pm

Unfortunately I’ll have to go back to v89. This version broke my Xiaomi_aqara component. I tried regenerating the key a few times, nothing seems to work, it just says (MainThread) [homeassistant.config] Invalid config for [xiaomi_aqara]: required key not provided @ data[‘xiaomi_aqara’][‘gateways’][1][‘mac’]. Got None. (See /config/configuration.yaml, line 21). Please check the docs at https://home-assistant.io/components/xiaomi_aqara/
As far as I’m concerned, it is configured correctly and it worked perfectly before updating to this version. Anybody else with a Xiaomi Mi Gateway experiencing the same issue?

aidbish · April 21, 2019, 11:00pm

2 Xiaomi gateways working perfectly fine on 91.3 and also tested with latest beta without issue

chri5tian · April 21, 2019, 11:11pm

Thanks for confirming, I will try to play about with it, hopefully get it to work. Reverting back to v89.1 it works perfectly, when I update Home Assistant, it stops working. I have default config:
xiaomi_aqara:
discovery_retry: 5
gateways:
- mac: 7C:49:EB:xx:xx:xx
- key: **************
Not really sure what makes it break.

nickrout · April 21, 2019, 11:31pm

Xiaomi gateway works fine here on 0.91.x

Steven_Rollason · April 22, 2019, 8:27am

Try removing the colons from the MAC address, the description of the mac option says:

The MAC address of your gateway. Needs to be formatted without “:”.

I don’t know if this changed in this version.

nickrout · April 22, 2019, 8:29am

You don’t even need the MAC address unless you have more than one gateway.

crzg · April 24, 2019, 8:49pm

Is anyone else having persistent issues with Yeelight?

Have tried restarting multiple times, using discovery and not, config is all up to scratch.

0.91.0 works perfectly fine and have rolled back and forth - with 0.91.4 entities appear as unavailable and I see the following error consistently:

2019-04-24 20:32:58 ERROR (MainThread) [homeassistant.components.light] yeelight: Error on device update!
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 261, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 379, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result
    raise self._exception
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/yeelight/light.py", line 356, in update
    elif self.light_type == yeelight.enums.LightType.Ambient:
AttributeError: module 'yeelight' has no attribute 'enums'