#beta

18 messages · Page 1 of 1 (latest)

hazy mulch
crisp marsh
#

Also you can merge to dev and request a back port

glass bronze
#

Is there a way to determine how many HA installations have installed a beta release ?

hazy mulch
hazy mulch
crisp marsh
#

4m after startup and every 12hrs

crisp marsh
#

Its a bit faster than dhcp ptr scan (every 24h) but people likely want to find Bluetooth devices faster. Trade off is slightly more battery drain.

fair isle
#

Why not mention the reason for failed to connect right next to the dialogue box just like automation notes

#

I am running beta 2026.6 and adguard as separate LXC in proxmox. Exact reasons for failed to connect just like automation notes would make life easier for lot of us instead of looking into logs

hexed lily
fair isle
#

At least as a general guide or for official integrations. Adguard integration is maintained by our automaton the great @rancid crescent himself.

craggy quail
arctic cobalt
#

Also the text in the descriptions is no longer aligned 'centre' which was very difficult to read: just need to work out how to get new lines to work in that.

craggy sedge
#

guys, I have a suggestion... let the secondary info to display whatever you want, including values of other entities configurable from UI... currently I had to make a template card and there's a bunch of stuff to know to do that (or ask AI for help), it'd be easier on people who just want make stuff quickly and forget about it

pulsar merlin
#

For those of you running, or thinking of running, a beta release this is the channel for all beta-centric questions, problems, and other chatter. You can find details on the beta releases at https://rc.home-assistant.io/.

Oh, and thank you for helping make Home Assistant better for everybody 👍

rotund yoke
#

Happy to see this new channel! Anyone on the new beta yet?

paper portal
#

I am

#

since friday

rotund yoke
#

nice! hows it running so far?

paper portal
#

no issues so far

novel wedge
#

hi there. I created an issue that the Xiaomi Switches are not working again on the Beta.

barren timber
#

I've just released 0.66.0.beta1 with a bunch of fixes

novel wedge
#

does it fix the 2 issues I reported above?

barren timber
#

I don't know

novel wedge
#

i'm only seeing beta0 in the hass.io tab anyway... If it fixes above I'll update when I see it

barren timber
novel wedge
#

of course. no worries

#

i rolled back last night as I need my switch to work

barren timber
novel wedge
#

thanks. neither of the above is in there

fallen merlin
#

@novel wedge Yes I didn't put it in the hotfix milestones because it's part of the template sensors which many people rely on, so if there were a bug in that patch it wouldn't be good

#

But it should be in the beta though....

#

I tried the configuration that was shown in the GitHub issue when I did the fix and it worked for me :/

#

Can you link to the part of the config that's not working for you (the community thread has quite a lot of different ones and I don't know which to try with)

novel wedge
#

@fallen merlin I’m using the weather.yaml that’s linked to in the 7 day weather forecast thread. I’ll find a link to the exact post if you need it..

#

Are you saying the fix is in beta0?

novel wedge
#

That’s the link @fallen merlin

fallen merlin
#

Yes it should be in beta0

fallen merlin
#

ok apparently I can't figure out how to paste images in discord

paper portal
#

You cant 😉

fallen merlin
#

but.... the configuration you linked to works for me

#

@paper portal oh ok :)

paper portal
#

Upload it on imgur or similar and share the link

fallen merlin
ashen wind
#

Images on discord? Just drag and drop works perfectly fine.

pulsar merlin
#

I just enabled it for here a couple of hours ago, given that reporting weird bugs will be easier with images

#

As long as nobody abuses it ;P

paper portal
#

😮

fallen merlin
#

ah, had to restart my discord client

weary gate
#

Is there anywhere one can follow the development of home assistant cloud towards google home?

#

Just got my google home thats why im asking 😛

pulsar merlin
#

It's with Google for their own internal field tests

weary gate
#

Ah, so the code is already complete?

#

Just waiting for approval?

pulsar merlin
#

Yup

#

I think it was mentioned in #cloud-archived recently, but I may be mixing up channels

#

Yup, mentioned last Thursday

barren timber
#

Correct.

#

The code is already included in Home Assistant releases, just waiting for Google to make it publicly available

weary gate
#

Sweet, the current setup is kinda complicated 😛

stark roost
#

kinda 😄

snow lantern
stark roost
#

but it does work very well and it's pretty damn cool

barren timber
#

@snow lantern thanks, will check it out

snow lantern
#

but those errors look different....so will test more when I get home

barren timber
#

Your errors are about Hue not being able to connect

#

Which, we should catch more elegantly

snow lantern
#

yeah....but I am not sure why those errors are there. The hub is connected

snow lantern
#

BTW.....everything is working well for me here

#

the errors don't appear when I turned on the power to the hue bulb.

novel wedge
#

@fallen merlin if I use this in the developer tools template:

#

{%- set date = as_timestamp(now()) + (2 * 86400 ) -%}
{{ date | timestamp_custom("%A (%-d/%-m)") }}

#

I get a blank reply

#

but I did roll back from the beta as my Xiaomi switches also don't work

#

however I don't understand why the template isn't working

fallen merlin
#

the template is working for me with the beta :/

novel wedge
#

The python script for darksky is working

#

so if you put the above in the dev tools template you get a response?

fallen merlin
#
  • just checked with 0.65.6 too and works too
#

so I think there's something else going on with your setup

#

yes, I get a response

novel wedge
#

i put exactly what I pasted above in dev tools and no response

fallen merlin
novel wedge
#

i'm on hassio

fallen merlin
#

that is ... very weird 😳

novel wedge
#

0.65.6

#

yes it is lol!

#

but there's a few people with issues with this on hassio....

fallen merlin
#

I have no idea why that might be, there have been no major changes to the template engine recently ...

#

is it only on hassio?

novel wedge
#

all the people who can't get it to work have been on hassio

fallen merlin
#

(it would make even less sense to me if it was just on hassio... I think)

novel wedge
#

haha

queen axle
#

there is no reason why the template engine should be different using Hass.io

crude vortex
#

for me too, local dev works, hassio doesn't

fallen merlin
#

ok I don't have hass.io so I can't debug it

novel wedge
#

well I can't get local dev working either as per above screenshot

crude vortex
#

[Error] Failed to load resource: the server responded with a status of 400 (Bad Request) (template, line 0)

novel wedge
#

i don't see any error in the log

crude vortex
fallen merlin
#

that seems like a weird url...

pulsar merlin
#

Yeah, that "stray" colon after the port isn't normal

fallen merlin
#

is hassio using some reverse proxy that might do this sort of stuff?

crude vortex
#

oh. that's my fault

#

it was actually discord messing it yp

pulsar merlin
#

If you use code blocks, that won't happen

#

~format

split sinewBOT
#
:information_source:
Format Code:

To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks. Here's an example:
```yaml
code here
```

crude vortex
#

yeah, i know 😔

novel wedge
#

haha

crude vortex
#

but that error was expected, as I messed up a template. then the server will respond with a 400

#

so, no, I see no errors in the logs

#

the only thing I can think of is the date/time libraries are different and don't work nice with python on hassio

green fox
#

That's the dashes in %-d/%-m causing the issue (maybe that was mentioned?). I guess maybe Hassio uses a minimal libc without that supported?

fallen merlin
#

hassio uses docker

#

and I don't see it on my docker setup...

#

so it's probably not due to date/time libraries

crude vortex
#

yes, without the - they work

fallen merlin
#

oh ok

#

nevermind

snow lantern
#

@novel wedge The template has been working for a while now. There has to be something else wrong with your setup

queen axle
#

^it does not work with hassio

novel wedge
#

yes! without dashes it works

snow lantern
#

Ok....that is possible. I am not using venv

#

well, at least we know the cause 😃

novel wedge
#

@snow lantern it hasn't been working with hassio for more people than just me

fallen merlin
#

I guess it has to be fixed in the templates, not the home assistant core

queen axle
#

has someone created an issue?

fallen merlin
#

I don't think we can/should fix this issue ourselves (if it's due to python's internal datetime library)

novel wedge
#

there is an issue where I posted about it and then they closed the issue to non devs

fallen merlin
#

yes, because it wasn't related to the fix in the PR (and it wasn't an issue, it was a PR)

queen axle
#

the | seems to be the problem? nvm

novel wedge
#

if I remove the - it works and only displays slightly differently with a leading zero as in 29/03 instead of 29/3

#

(I have day before month)

crude vortex
#

Yes that’s expected. As the - is there to drop the leading zero

fallen merlin
#

I think this should just be a known limitation;

green fox
#
{%- set date = as_timestamp(now()) + (2 * 86400 ) -%}
{{ date | timestamp_custom("%A (%d/%m)") | replace("(0", "(") | replace("/0", "/") }}
``` There!
novel wedge
#

hahahha!!!! smartarse

#

hahaha

snow lantern
#

So, can someone summarize the issue please

queen axle
#

^see Otto's pic

green fox
#

Summary: %-d (with the minus) is optional for the operating system to support.

snow lantern
#

looks like it is the - that is causing the issue

barren timber
#

Yeah, that broke our Hass.io build once

snow lantern
#

Good to know

#

Just confirms that we should ALWAYS use the template editor before using things in the config.

novel wedge
#

i just edited my weather.yaml to use this instead of the python script. restarting now

#

WORKS!!!!

#

Yes!

#

thankyou guys

#

that has been so bloody frustrating when only a few have the problem and everyone else says 'it works for me' lol

snow lantern
#

I know....I am glad we got that sorted 😃

novel wedge
#

i think it's your script isn't it? @snow lantern (weather.yaml) do you want to post an amendment on the 7 day weather forecast thread on the forum?

snow lantern
#

Yes, I can.

queen axle
#

^thats a disadvantage of posting code in the forum btw: hard to keep it updated

novel wedge
#

agreed but it's linked to the github as well

snow lantern
#

@queen axle But, it is amazing how the whole thing has evolved. People get inspired by others code and add features

queen axle
#

indeed, a lot of people share code snippets 😃

snow lantern
#

some threads are few thousand posts

queen axle
#

yes, what makes it hard to pick out the good posts ^^

green fox
#

I have debugged so many slightly different Sonos TTS scripts in the forum lately 😢

barren timber
#

Anyone around that want to test some Hue fixes ?

queen axle
#

I can

barren timber
queen axle
#

let me turn on my bridge 😛

snow lantern
#

I can as well

barren timber
#

Okay, so I linked the PR above

#

It should solve one of your issues for sure @snow lantern 😃

snow lantern
#

the error logs?

novel wedge
#

has anyone seen @tidal mortar around? The beta broke the Xiaomi miio component again.... I was wondering if it's fixed in beta1?

tidal mortar
#

@novel wedge Huh?

novel wedge
#

i did log an issue

tidal mortar
#

What's the problem?

novel wedge
tidal mortar
#

Hmm... some other component upgraded construct.

snow lantern
novel wedge
#
Sun Mar 25 2018 20:34:33 GMT+1100 (AEDT)

Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/lib/python3.6/site-packages/homeassistant/components/switch/xiaomi_miio.py”, line 100, in async_setup_platform
from miio import Device, DeviceException
File “/usr/lib/python3.6/site-packages/miio/init.py”, line 2, in 
from miio.protocol import Message, Utils
File “/usr/lib/python3.6/site-packages/miio/protocol.py”, line 33, in 
assert construct.version_string == “2.9.31”
tidal mortar
#

Which construct version is installed?

novel wedge
#

how can I see?

tidal mortar
#

Do you still know how to SSH to your hassio host system and open a shell at your docker container (homeassistant).

novel wedge
#

yeah I have the shell open - just need the correct command

tidal mortar
#

cat /usr/lib/python3.6/site-packages/construct/version.py

queen axle
#

@barren timber I have this with beta 0 but I have no lamps connected yet (don't have any E27 lamp here atm)

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 222, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/usr/lib/python3.6/site-packages/homeassistant/components/light/__init__.py", line 494, in state_attributes
    value = getattr(self, prop)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/light/hue.py", line 244, in hs_color
    self.light.action.get('hue') / 65535 * 360,
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
barren timber
#

I have a fix for that one ready

queen axle
#

ok I will pick your PR

barren timber
tidal mortar
#

@novel wedge Thanks for pinging btw. 😃

barren timber
#

oh it has, I'll merge it

novel wedge
#

root@hassio:~# cat /usr/lib/python3.6/site-packages/construct/version.py
cat: /usr/lib/python3.6/site-packages/construct/version.py: No such file or directory
root@hassio:~#

barren timber
#

@queen axle will rebase my branch

#

alright, rebased. Fix is included in the upgrade-aiohue branch now

snow lantern
#

Where? we should close that issue then

tidal mortar
#

What's the output of cat /usr/lib/python3.6/site-packages/miio/version.py

novel wedge
#

root@hassio:~# cat /usr/lib/python3.6/site-packages/construct/version.py
cat: /usr/lib/python3.6/site-packages/construct/version.py: No such file or directory
root@hassio:~#

tidal mortar
#

Okay. This isn't the correct machine/container.

novel wedge
#

oh? i'm on hassio

tidal mortar
#

Did you execute something like "docker exec ...." ?

novel wedge
#

no I just connected on port 22222

tidal mortar
#

You must enter the home assistant container of hassio.

novel wedge
#

how do i do that?

#

i'm using the debug ssh thingy on port 22222 to hassio.local

tidal mortar
#

Wait a second. I search your issue of the pst 😉

#

Port 22222 is fine.

#

This is the host system.

novel wedge
#

right

tidal mortar
#

There should be a command called "docker".

novel wedge
#

do i just type docker?

#

that just gives me a list of switches for the command

tidal mortar
#

This first command executes a shell on/inside of the docker container.

#

You have access to another filesystem afterwards.

novel wedge
#

/bin/bash cat /usr/lib/python3.6/site-packages/miio/version.py cat

tidal mortar
#

cat /usr/lib/python3.6/site-packages/construct/version.py should output something this time.

novel wedge
#

is that it?

tidal mortar
#

If you want both in one command.

#

:

#

docker exec -it homeassistant /bin/cat /usr/lib/python3.6/site-packages/construct/version.py

novel wedge
#

2.9.39

#

2018.03.16

tidal mortar
#

Interesting.

queen axle
#

@barren timber I still have this error

barren timber
#

what error ?

queen axle
#
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/home/bs/home-assistant/homeassistant/helpers/entity_platform.py", line 260, in _async_add_entity
    await entity.async_update_ha_state()
  File "/home/bs/home-assistant/homeassistant/helpers/entity.py", line 222, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/home/bs/home-assistant/homeassistant/components/light/__init__.py", line 494, in state_attributes
    value = getattr(self, prop)
  File "/home/bs/home-assistant/homeassistant/components/light/hue.py", line 244, in hs_color
    self.light.action.get('hue') / 65535 * 360,
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
barren timber
#

You're not running the latest version

#

I rebased the upgrade-aiohue branch and it has the fix now

queen axle
#

Oh you did another push...

barren timber
#

Well that was to fix the tests. Your fix was achieved by rebasing on latest dev after I merged the fix

#

for the issue you had

tidal mortar
#

@novel wedge I assume beacontools broke the construct dependency again. 😦

novel wedge
#

yeah it's a pain for you I'm sure

#

i thought there was a permanent fix to stop this from happening - you're always having to clean up a mess someone else makes

queen axle
#

yeah you added tests. Well the issue is that my lamps are all offline atm. if I turn them on or change brightness I get this error

#

(still get it)

tidal mortar
barren timber
tidal mortar
#

The construct dependency of xiaomi_miio is pinned to 2.9.31 for safety.

#

I assume the beacontools requirement overrides the xioami_miio version. I will bootstrap a hassio build to verify my assumption.

novel wedge
#

ok. can I do what I did before and manually use the correct construct?

barren timber
#

@novel wedge please make sure that the deps folder in your config dir is empty

novel wedge
#

I don't have a deps folder

#

(hassio)

barren timber
#

ok, just checking

novel wedge
#

oh I do

#

oops

#

but it's empty

barren timber
#

okay, good

queen axle
#

light/hue.py was not part of the PR 🤔

barren timber
#

I know. Like I said, I rebased

queen axle
#

ok ok

#

^^

novel wedge
#

@tidal mortar can you give me the command to load the correct construct again from the docker ssh?

#

i know it's not persistent

tidal mortar
#

Yep. Wait a sec.

#

docker exec -it homeassistant pip3 install construct==2.9.31

novel wedge
#

ok I'll just upgrade to beta0 and then try that..... give me a few.....

#

still only beta0 here - I thought i'd have beta1 by now...

queen axle
#

@barren timber fixed ;D

novel wedge
#

bloody hell this is taking forever! our internet has gone to shit since yesterday

tidal mortar
#

@barren timber It's possible/allowed to pin a implicit dependency of a component/device library?

barren timber
#

Why wouldn't the device lib do that ?

tidal mortar
#

python-miio, python-eq3bt and beacontools are depending on "construct".

#

the construct api is very unstable.

#

So we pinned the construct version at python-miio.

#

The construct version of beacontools survives. 😦

#

beacontools allows a version range from 2.8 to <2.10.

#

python-eq3bt doesn't use pinning ATM.

#

python-miio is pinned to 2.9.31.

barren timber
#

Doesn't your pinned version fall in the range of beacontools ?

tidal mortar
#

In a fresh virtualenv the construct version 2.9.41 will be installed.

#

Yes. 2.8 < 2.9.31 < 2.9.41 < 2.10.

barren timber
#

So I am confused now. That is working as expected right ?

#

From the Docker logs of our x86 image: Collecting construct==2.9.31 (from python-miio==0.3.8->-r requirements_all.txt (line 951))

novel wedge
#

how big is the beta 0 update? (in mb)?

barren timber
#

I don't know

novel wedge
#

just trying to see how long it's going to take to update here

tidal mortar
#

@barren timber Are the logs public? Could you provide a url?

#

If I build a new image construct==2.9.41 (!= 2.9.31) is included.

paper portal
#

i think beta1 is ~8megs if that makes sense?

novel wedge
#

hmm. ok

barren timber
#

I don't think the logs are public because that's not how Docker works

#

Also note that this is not for Hass.io, but just normal Home Assistant

#

Pascal can give you the logs for hass.io builds

#

Ah, one difference between Hass.io and the normal Docker build is that normal Docker build does not uncomment the requirements that fail to install, like Hass.io does

tidal mortar
#

Correct.

barren timber
#

So we don't actually install beacontools etc

tidal mortar
#

The beacontools requirement overrules the python-miio somehow. although there is a intersection.

barren timber
#

So what about making your lib work with 2.9.41?

#

That would remove the problem

tidal mortar
#

No... last three times we made python-miio compatible with the recent version of construct.

#

A day later & a home assistant release later the maintainer of construct released a new version and broke the API again.

barren timber
#

did you raise an issue with the construct lib about semver ?

barren timber
#

okay, I get the point 😉

barren timber
#

Please wrap your urls with < and > to avoid expansion

tidal mortar
#

Sorry. 😃

barren timber
#

So yeah, I don't know why pip is doing what it does

#

I guess I'm fine with pinning it for now, although I obviously prefer if we just run 2.9.41

tidal mortar
#

😦

#

Sorry for the expansion again.

queen axle
#

you can edit your posts and add <>

barren timber
#

that dude sounds like an ass

tidal mortar
#

Yep.

barren timber
#

he should just do semantic versioning instead of this cowboy style.

tidal mortar
#

We are moving away from construct soon.

#

I will try to prepare a construct 2.9.41 compatible python-miio version.

#

The xiaomi_miio components will be broken in HA 0.66. 😦

novel wedge
#
Using username "root".
Authenticating with public key "rsa-key-20171114"
root@hassio:~# docker exec -it homeassistant pip3 install construct==2.9.31
Collecting construct==2.9.31
  Downloading construct-2.9.31.tar.gz (68kB)
    100% |████████████████████████████████| 71kB 105kB/s
Installing collected packages: construct
  Found existing installation: construct 2.9.40
    Uninstalling construct-2.9.40:
      Successfully uninstalled construct-2.9.40
  Running setup.py install for construct ... done
Successfully installed construct-2.9.31
You are using pip version 9.0.1, however version 9.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
root@hassio:~#

Finally on 0.66.0beta0 and downgraded construct. restarting now

split sinewBOT
#

Attention!: Please use https://www.hastebin.com to share code that is more than 10-15 lines. You have been warned, @novel wedge!
Please read rule #6 here #rules

barren timber
#

@tidal mortar good to hear you're moving away. That's a dependency one should depend on

novel wedge
#

@tidal mortar ok doing that brought my xiaomi switch back to life again

#

thanks

#

beta 0.66.0beta0

tidal mortar
#

You are welcome!

#

I'm working on a permanent solution but it will need some time.

novel wedge
#

you've had a nightmare with all these xiaomi miio devices. That's a full time job right there

barren timber
#

We should see the dependencies that use construct and see if we can ban it, like we did with pycrypto and enum34

tidal mortar
#

I need some sleep. Cya! 😃

novel wedge
#

nice

sleek whale
#

i switching to a beat release a bad idea?

novel wedge
#

depends.... there is an issue with miio devices....

sleek whale
#

Miio devices? Given that I don't know what they are I doubt I'd be affected

novel wedge
#

xiaomi

sleek whale
#

ahh, don't have any

#

although to be honest, i'm sure i'd be ok with sticking on 0.65.x for now

novel wedge
#

well that component is the only one I had trouble with on the beta. my setup is pretty uncomplicated though

sleek whale
#

as is mine.

novel wedge
#

check issues on github to be sure

#

testing betas before general release helps everyone

sleek whale
#

and how do yuo switch to the betas?

#

erm?????

Current Version: 0.66.0
Released: March 31, 2018
RELEASE NOTES```
novel wedge
#

how do you run HA?

#

current is 0.65.6 so I don't know where you see that

sleek whale
#

That was on the home page. I have it in a venv

novel wedge
#

in hassio you need to enable beta channel in hassio>system

sleek whale
#

Nope, venv install

novel wedge
sleek whale
novel wedge
#

yeah

sleek whale
#

would it be shell pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@beta

#

?

novel wedge
#

rc is for release candidate/beta releases

barren timber
#

@sleek whale read the blog post where we announced the betas

sleek whale
#

ahh, ty

#

now to figure out how to move my damn wemo switch to a different network name but not reset everything

novel wedge
sleek whale
#

My god, the systemd service restarts a lot faster on .66b1

novel wedge
#

you have beta 1?

#

lucky bastard

#

lol

barren timber
#

Beta 2 was just released

novel wedge
#

haha

#

still only beta0 on hassio

#

what are the changes in b2?

barren timber
#

you have to look at the same place as that I told you to look at yesterday when you asked about the changes in beta1 😉

sleek whale
#

and i just upraded to beta 2

barren timber
#

👍

novel wedge
#

hahaha Well i'd need to scroll a long way up to find it

paper portal
#

bah, just upgraded to beta1 - 1,5 hours ago 😛

barren timber
novel wedge
#

thanks - i'll bookmark it this time

sleek whale
#

@paper portal i did it 15 minutes ago

barren timber
#

Well, the bookmark will have to change for each milestone

#

In repo, click on pull requests -> milestone

queen axle
novel wedge
#

ok thanks. also b now not beta?

barren timber
#

yeah, beta was invalid identifier for version strings

sleek whale
#

Anyone else have HA take 1.5 minutes to restart?

pale oriole
#

@sleek whale pip3 install --upgrade --pre homeassistant

tidal mortar
#

@novel wedge You should catch some sleep, too. In which timezone do you life? 😉

novel wedge
#

hahaha!!! @tidal mortar! I was just going to ask if you ever slept!!

#

we are UTC+11 here so it's 5:39pm here now on Tuesday afternoon

#

where are you?

#

I was up earlish for me this morning

#

so the auto-detect for yeelights (LED Bulbs) - is that permanent?

tidal mortar
#

In germany there is 8:43am.

#

Just posted an answer.

novel wedge
#

it seems to work fine and I hide them from the integration anyway as they have native GA support

#

hahaha!

tidal mortar
#

GA support?

novel wedge
#

google assistant

#

ok so i'll treat them like they have native support then.

tidal mortar
#

Correct.

#

I will try to implement the unique_id support for the yeelights. May be the change won't be accepted because of the cost (feature loss).

#

The background: A serial number / unique identifier is needed. Therefore the device must be available at the network and provide some information.

#

Some people likes to start Home Assistant while some lights aren't available (powered off).

novel wedge
#

oh ok.

tidal mortar
#

This devices cannot provide the unique identifier. In the past unavailable lights are showing up as "unavailable device" at the dashboard.

novel wedge
#

they always get auto detected here so I've been hiding them

tidal mortar
#

This isn't possible because the identifier must be known before the setup of the platform (light).

#

I will update the component and give it a try.

novel wedge
#

it could also be that the light isn't detected at the network level (wifi issue)

#

does that only mean it won't get a unique id or does it mean it won't ever be detected if it's unavailable?

#

well I made the changes and it looks good to me

tidal mortar
#

The auto-discovery checks the network traffic (mDNS announcements) all the time.

#

If a new device/yeelight appears it will be added immediately.

#

If you have disabled the discover method the light needs to be configured manually (the config you removed now).

novel wedge
#

well that's kinda cool. When HA restarted, it was slowish picking them up - like a few extra seconds but then they showed up on the right card in the right place

tidal mortar
#

In this case Home Assistant will retry every 30 seconds as long the component throws a "platform not ready" exception.

novel wedge
#

and google turned it off but the front end of HA took a while to register it was off

#

well I don't have the platform defined anymore (I removed yeelight from lights.yaml)

tidal mortar
#

Yes. You could increase the polling interval 😉

#

At the moment the light will be asked about the state every 30secs.

novel wedge
#

how would I increase the polling interval?

novel wedge
#

ah ok

tidal mortar
#

I don't know how to do it if discover does all the work for you 😉

novel wedge
#

so what interval won't kill my system? is 10 good?

tidal mortar
#

Just give it a try.

novel wedge
#

it will still be on a yeelight platform though won't it?

tidal mortar
#

I don't know the number of you devices.. power of your host system etc.

novel wedge
#

ah ok

tidal mortar
#

Correct.

#

The parameter must/can be defined per platform.

novel wedge
#

so I'd put it in light yaml file not config though

tidal mortar
#

The light.yaml is a include of the config. Isn't it?

#

In short: yes!

novel wedge
#

yeah it is

#

trying 10 now

#

depends where it's at in the 30 seconds how long it takes to poll anyway I guess

#

doesn't seem to work.... checking log (like 15 seconds)

#

more like 20

#

ah that's fun finding all the places you have to change things

#

lol

tidal mortar
#

😉 I need to do some real work now. Bye bye.

novel wedge
#

thanks!

crude vortex
#

syssi, why wouldn't it be able to get unique_id config upon discovery of a new light?

tidal mortar
#

No. That isn't the point.

#

Auto discovery is perfect and works fine.

crude vortex
#

oh, I see. It would not show lights as 'unavailable' like it does now, it just would not show them

#

right?

tidal mortar
#

In this case we have the most informations about the device, device id/mac, capabilities,...

#

Correct.

#

This is the problem.

#

Some people are depending on the "device unavailable feature" and are using a static configuration therefore.

#

The unique id feature requires a available device on startup.

crude vortex
#

It could setup an unavailable light based on the entry in the entity-registry? And when it is discovered make it a fucntiuonal light.

#

if that's is not a possibility now it could be a usefull addition to the entity registry (persistent state, persistent device)

tidal mortar
#

We aren't talking about the same thing.

#

Lets discuss the "static configuration" case.

#

If you setup the yeelight platform with a static host entry.

#

A light entity will be created (unavailable) and gets available as soon the light is reachable. This is the first time we can request a unique identifier.

#

That's too late.

#

The unique identifier must be known before adding the device: add_devices(lights

crude vortex
#

You can get the unique_id from the entity-registry

tidal mortar
#

Good point.

#

Is it accepted to lookup a unique_id by the entity name?

crude vortex
#

so you can set up a 'mock/unavailable' light with the known unique_id, and replace it to a functional light when it is discoverd.

#

I don't know. I think this functionality/use case is not currently part of the entity registry, but it would be very usefull.

tidal mortar
#

Hmm, okay. This exceeds my python skills probably. 😉

#

There are more problems. The developer api of the yeelight doesn't provide a unique identifier. There is another protocol which exposes some details. 😦

crude vortex
#

the entity_registry currently has no method to query it for all entities that are registered for a platform.

#

Oh, that is a bigger problem 😉

#

isn't the mac-address known in discovery info? The mac-address is uniuqe

tidal mortar
#

I will talk to the yeelight staff. They are chatty.

#

Yes. The discovery is the best case.

#

Static configuration is the worst-case.

crude vortex
#

static = IP-address?

#

then you should be able to get the mac-address too, look at _arp() in nmap_tracker.py

#

feels a bit hacky, but should work.
Could be quite useful as a util function to enable unique_id's for statically configured hosts (as long as discovered devices on the same platform use the mac-address of course)

tidal mortar
#

@crude vortex It's hacky and your assumption isn't correct.

#

If you have a local network with multiple subnets/complex architecture there is no mac address/the reported mac address is one of the gateways.

crude vortex
#

yeah, that's right

#

best thing then would be to get them (Yeelight) to return the mac-address (or another id) in thier api. (that's always the best solution 😃 )

#

Complex networks are of course one of the reasons to define static config....

#

@tidal mortar in the Yeelight docs i see this: "ID": The ID of a Yeelight WiFi LED device, 3rd party device should use this value to uniquely identified a Yeelight WiFi LED device.

tidal mortar
#

Yes. This is the discovery api.

#

(of the yeelight)

crude vortex
#

can't you send a search request to the specific IP addres instead of broadcast to trigger a search response from the bulb?

tidal mortar
#

I will give it a try.

green fox
#

Still no beta1 for Hassio?

crude vortex
#

updating now

green fox
#

Can I force update when the UI still shows beta0 (that I know is broken for me) as latest?

#

Or rather, I know how to force a version but I do not know where to check if a beta is available for Hass.io ...

#

nvm, b2 was just pushed a little while ago and beta1 was indeed skipped. So I do know, I just happend to hit a race :)

crude vortex
#

you can reload the supervisor under system, that will force a check of the latest version.

fallen merlin
#

@tidal mortar I don't think we should be querying the entity registry, but your problem is exactly what config entries are trying to solve; maybe have a look at them at some point, I think they should fix your problem

tidal mortar
#

What do you mean by "config entries"?

tidal mortar
#

Interesting. Thanks for the hint! 😃

fallen merlin
#

It's some very fancy stuff :P

#

No problemo

stark steeple
#

are there release notes for each of the betas?

#

I went to release page and dont see them under each beta version

queen axle
#

Only total changes in blog post afaik

barren timber
#

If someone wants to automate it for me, please

indigo hatch
#

@tidal mortar maybe overriding the unique id (for yeelights) based on autodiscovery data is fine?

#

it's unfortunate that this info (mac addr) is not afaik available over the api. it would be over miio api (iirc) tho, but that'd complicate things needlessly

#

anyway, very unfortunate that those are again broken due to construct

#

I have tried to explain it now multiple times to the developer that for such a library (binary parsing & building) it makes no sense to break the api as much as possible, as the users of such libraries probably expect stability for the sake of usefulness

#

alas to no avail

#

then he wonders elsewhere why his lib does not have so much hype around as kaitai struct (which doesn't offer building so it is not usable in our case :/)

#

unfortunately I'm very busy nowadays with other stuff, so haven't had any time to look into converting it to use our own parsing impl. that'd require to have a robust test-suite for the protocol itself first, and that was where I was before getting busy

#

pinning the version higher may also break other components (eq3btsmart comes to my mind), also the custom_component for yeelight's bt devices may be broken.. it's quite sad to try to play whack'a'mole on those api changes

barren timber
#

@indigo hatch fork it under another name

#

@indigo hatch for unique ID, we can store that in config entries

indigo hatch
#

@barren timber I have no intention to get more libs to maintain 😃 but yeah, a fork could be an option indeed, I just feel that it's not a great way either...

#

@barren timber unique id collected by the discovery process? or having an ability to define it in the config?

barren timber
#

collected in discovery process but then stored in config entry so it is persisted between restarts.

#

I feel ya on the lib maintenance. You could just fork, rename and not evolve. If the lib does all you need?

novel wedge
#

is the construct fix going to make it into 0.66.0 release?

tidal mortar
#

@novel wedge I will try to get it into today.

tidal mortar
mortal wyvern
#

Does anyone know if Google Home can be used as media_player ?

#

I'd like to play a file or announce something when I come home

#

Unfortunately Amazon Alexa can't do that

queen axle
#

this channel is for beta testers

mortal wyvern
#

Google Home has some other nice features and I was thinking about switching

royal shale
#

@mortal wyvern wrong channel for this question, but yes

mortal wyvern
#

@royal shale 👍 and sorry

novel wedge
#

@tidal mortar Excellent work again. Thanks for that.

barren timber
#

Published beta 3

fierce notch
#

Can't update to beta 3 yet (from b2 on hassio). Update button colors red but nothing seems to happen. Message 'Update Available' stays on screen. ??

crude vortex
#

On trying to update Hass.io to beta3:[hassio.docker.interface] Can't install homeassistant/raspberrypi2-homeassistant:0.66.0.b3 -> 404 Client Error: Not Found ("manifest for homeassistant/raspberrypi2-homeassistant:0.66.0.b3 not found").

sharp citrus
#

Same here!

#

@idle wraith @barren timber

snow lantern
#

@sharp citrus Please don't tag people, if not required

idle wraith
#

Diskspace? Or maby it need more time until docker sync the repository over the world

#

Oh wrong tag

#

I update it

#

You can use hassio ha update -o version=0.66.0b3

sharp citrus
queen axle
#

update again to the image with correct tags....

tidal mortar
#

@novel wedge Could you test the beta3?

fierce notch
#

Hassio update (from b2) b3 works now! Thanks. Also noticed that Xiaomi vacuum cleaner and air quality monitor are working now (for me for the first time). But... xiaomi miflora stopped working.

tidal mortar
#

@fierce notch Could you provide a screenshot of the air quality monitor?

fierce notch
tidal mortar
#

Thanks!

barren timber
#

@tidal mortar does that need fixing ?

#

Planning to make release official soon

tidal mortar
#

@barren timber Nope. The xiaomi miio stuff is fine!

barren timber
#

perfect

tidal mortar
#

Thanks for asking! :-)

fierce notch
#

Any suggestion to get Mi Flora working again? Log: Updating miflora sensor took longer than the scheduled update interval 0:00:30

vivid plank
#

any know issues with hue platform?

barren timber
#

delete your Hue custom component

vivid plank
#

thats all?

barren timber
#

Yeah, the custom component is not compatible

vivid plank
#

ehh where it wa .. sensors?

barren timber
#

I don't know.

vivid plank
#

ok.. let me restart

#

nope

#

let me see log at startup again

#

2018-03-31 00:03:27 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform hue
Traceback (most recent call last):
File "/home/hass/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/home/hass/homeassistant/lib/python3.6/site-packages/homeassistant/components/light/hue.py", line 56, in async_setup_platform
bridge = hass.data[hue.DOMAIN][discovery_info['host']]
KeyError: 'host'

#

still same

barren timber
#

because you did not delete your custom component 😢

vivid plank
#

i did ..

#

ait

#

pycache was inside ..

#

still the same

#

i deleted sensor folder in custom_components

snow lantern
#

It should be under light sub-folder under

barren timber
#

You also have a Hue custom component for the main one

#

Called hue.py or hue/__init__.py

vivid plank
#

strange

novel wedge
#

@tidal mortar working out-of-the-box with Beta 3. Thanks

tidal mortar
#

@fierce notch Did you solve the miflora issue? Do you use the miflora component or mqtt? Could you describe your setup (hassio?)? Is your sensor in range?

earnest ruin
#

do the betas get changelogs??

fierce notch
#

@syssi#5175 Thanks for asking ! No it's not solved yet. I use the miflora component. My set up (in hassio): see pictures. Also notice that it seems stop working from b3, from b3 air quality monitoring and the vacuum cleaner start working. In the Mi Home app Mi Flora is still working.

tidal mortar
#

@fierce notch Could you enable the debug log for the miflora component and provide the output?

barren timber
#

I've just tagged the first beta of 0.66.1

#

It includes frontend fixes for thermostats

fierce notch
#

@tidal mortar Issue with miflora was fixed (for me) since release 0.66.0. Thanks for your great support!

tidal mortar
#

Perfect!

modest dirge
#

im Russian im but not very well English

pulsar merlin
#

@modest dirge Please do not cross post

modest dirge
#

!what

#

im Russian im but not very well English

pulsar merlin
#

Пожалуйста, не перекрестите пост - не отправляйте одно и то же сообщение в нескольких каналах

modest dirge
#

ok

rare sail
#

🤦

steep kelp
#

Hi hi

fast aspen
#

Hi in the last version Version: 0.66.1

#

the login password does not work

#

in the http: the api_password

#

doesn't work

#

I had my password, and now I can access to my HA without using password or putting in the login any randorm word

#

is there any BUG reported ?

pale oriole
#

@fast aspen ^

#

@fast aspen I cannot reproduce on 0.66.1 (public release)

#

But I did manage to lock myself trying to! lol

fast aspen
#

yes I have trusted_networks

pale oriole
#

~share

split sinewBOT
pale oriole
#

trusted_networks allows you to access without a password.

#

(if you are part of the trusted network)

#

Straight from the documentation: "List of trusted networks, consisting of IP addresses or networks, that are allowed to bypass password protection when accessing Home Assistant."

fast aspen
#

omg... thats a big missunderstanding from my side

#

I m very sorry, thank you for the clarification

#

I m going to try removing trusted_networks

pale oriole
#

I believe we have proper tests in place to ensure that this specific security vulnerability does not happen.

fast aspen
#

I understood completlly different the trusted_networks parameter

pale oriole
#

Also, please note that this channel is for beta versions (i.e. 0.66.0b0, 0.66.0b1, 0.66.1b0, 0.67.0b0) of Home Assistant and Hass.io, not releases or point releases (i.e. 0.66.0, 0.66.1, 0.66.2, 0.67.0)

fast aspen
#

definitely, today is not my day @pale oriole mindblown

barren timber
#

I just pushed out 0.67.0b0

#

release notes will be on the site as linked in the topic

pale oriole
#

👍 Thank you sir!

snow lantern
#

Thanks...that fixed Abode 😃

modest dirge
#

Hello. This might be a stupid question but I'm trying to find out the easiest way to see what PRs are included in the next release (ie. the latest beta build). When the release schedule changed, I could see this here, https://rc.home-assistant.io, but as of the now this page just shows the released version.

paper portal
modest dirge
#

Right now it is of course. Been testing this link for days with no luck. Disregard my request... 😃

barren timber
#

@paper portal good point, let me remove the domain prefix 🤔

#

That was on my to do list to fix

#

my bad

supple quail
#

i can see numeric_state 'above' or 'below' commands , what is the command for equals? cant seem to find it in the docs - can someone help?

dense tendon
#

@supple quail you could use either the state or template trigger.

supple quail
#

thanks @dense tendon also not sure why i posted in beta - half asleep

modest dirge
#

If I think I've found a bug in the bluetooth_tracker component (using hassio addon for RPi3), where do I report this?

#

BTW: Running 0.67b0

snow lantern
modest dirge
rotund yoke
#

@modest dirge you should comment on it letting others know you have the same issue, helps developers see how widespread things are, hopefully that bug gets fixed since I use BT lol

modest dirge
#

I will report it, just want to test some more before I do.

median dove
#

hello, i got a little problem with my xiaomi vacuum bot, it worked perfectly in version 0.65, but it stopped working since 0.66. Homeassistant can't setup the componnent anymore, it fails with "Unable to install package python-miio==0.3.9: homeassistant 0.67.0b0 has requirement pip>=8.0.3, but you'll have pip 10.0.0b2 which is incompatible.
pyatv 0.3.9 has requirement aiohttp<3,>=2.3.0, but you'll have aiohttp 3.1.1 which is incompatible.
Consider using the --user option or check the permissions

#

has anyone got the same problem, or even better, a fix for that problem?

#

if i install aiohttp==2.3.0, homeassistant fails to start, because it requires 3.1.1

wanton furnace
#

@median dove sounds like a bug, probably worth opening a ticket on github if none exsist already.

#

I also see aiohttp related issues, but another bug.

barren timber
#

@median dove you should never manually install any package besides Home Assistant

#

Clear your <config>/deps folder

#

And install Home Assistant again, preferably in a new clean virtual environment

barren timber
#

I published beta 1

rare sail
#

seems to be working good

#

no issues so far

ashen wind
#

@barren timber is that 0.67 blog article containing the changelog generated/updated automatically?

barren timber
#

No

#

Well yes, I generate it using the hass-release package, but I have to run the command

ashen wind
#

Ok, thanks.

snow lantern
barren timber
#

I will totally add that if someone automates it for me 😉

#

For now, you will have to look at the 0.67 milestone on GitHub

snow lantern
#

I totally get it 👍

torn heart
#

Is it a known bug that the Node config options drop-down menu in the zwave config panel is not working? I´ve tried Chrome, Safari and Firefox, but I get nothing...

#

This applies to all devices, regardless of current state.
Running 0.67.0b1

pulsar merlin
#

cough You need to remember to mention the version of HA 😉

maiden pine
#

I installed the beta 0.67.0 .dev0 using the command " pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@dev", right after the fix to the Amcrest component was committed. I see that 0.67.0b1 is out there, but when I run that same pip3 upgrade all I get is the same 0.67.0.dev that I already have. How do I upgrade to the newest beta release?

rotund yoke
#

hmm looks like we need the correct command pinned in teh chat

#

you need to specify the beta version instead of teh dev branch

#

pip3 install --upgrade --pre homeassistant

maiden pine
#

@rotund yoke Thanks!

#

Hmmmm ... that had exactly the same result.

earnest ruin
#

is there a changelog for the beta versions anywhere? something more than a list of commits

maiden pine
#

@rotund yoke Wait, I see that did help, but now there's a dependency issue with my virtual env. I think I can handle that. Thanks again.

nova aspen
earnest ruin
#

hmm.. I don't think that exists for the beta releases.. didn't last 2 releases.. seems to catch up at the full release

nova aspen
#

It was there for both 0.66 and 0.67 when them where in beta (rc)

split sinewBOT
serene cairn
#

The automation I wrote under packages in version 0.67.0 was not working properly. However, the version of 0.66.1b0 does work correctly. How can I solve this problem?
Here is my automated code.

barren timber
#

I've just released 0.68.0b0

queen axle
#

pre-release not listed on GitHub

barren timber
#

oh my bad

#

doing so now

thin crater
#

https://rc.home-assistant.io/ -> TOO_MANY_REDIRECTS

Home Assistant

Open-source home automation platform running on Python 3. Track and control all devices at home and automate control. Installation in less than a minute.

barren timber
#

works here

#

It's kinda random, sometimes happens, sometimes not

#

Also, I forgot to publish the release notes…

thin crater
#

😦

snow lantern
barren timber
#

Should go away with a refresh of your browser

#

generating release notes now

barren timber
#

Just pushed release notes to rc branch, should up on the website in a bit

snow lantern
#

Loving this beta/rc release cycle. At least we are not fighting fires

barren timber
#

yeah, it's easy for me too

snow lantern
barren timber
#

oh nice

rotund yoke
#

I like that we are seeing issues get detected earlier, I think one improvement I would like to see is to maybe include a known issues section in the stable release notes. I saw quite a few duplicates pour in for issues that were caught during the beta and fixed in the first point release.

barren timber
#

We had a PR for the release note generator that will now list the PRs that were made during the beta release

royal shale
rotund yoke
#

Aren't those fixes already in 67.1 too?

barren timber
#

Yep

stiff linden
#

Can wait to see my name in 0.68 😁✌🏻

#

Can’t

snow lantern
barren timber
#

Well my issue is that we then have to duplicate it like 5 times

#

Making that page completely unscrollable

vivid plank
barren timber
#

If you can figure it out, would love to solve it

#

Something with cloudflare flexible ssl and netlify

neat lily
rancid crescent
#

@neat lily Do you have discovery enabled?

neat lily
#

No, I disabled that actually

rancid crescent
#

there you go 😃

#

add hassio: to the config

#

the discovery module adds that for you, in case you disable discovery... well... you'll have to add it manually

neat lily
#

oooohh... thanks!

barren timber
#

0.68.0b1 has been released

keen gazelle
#

Where do we find a list of what's included in the new beta?

dense tendon
sleek whale
#

Anyone else have their web cams reverse colors in .68.0b0?

snow lantern
#

My cams appear fine

barren timber
#

Released 0.68.0b2 with the Sonos fix

novel wedge
#

Beta 2? But 0.68 is up now and neither are available in Hassio? Am I missing something here?

#

That’s a massive delay even for Hassio

#

Hahaha! Literally I just asked that and I get a notification that 0.68.0 is available. Hahahaha. Maybe tomorrow......

rare sail
#

at least you got to complain

barren timber
#

New rc has been released

paper portal
#

@barren timber will the rc. website be update later today with the release notes?

barren timber
#

Yeah

#

Want to do it?

paper portal
#

have no clue how to 😦

dusk spindle
#

just tried to install 0.69 beta and it's failing to install the frontend:

2018-05-05 12:27:25 ERROR (Thread-2) [homeassistant.util.package] Unable to install package home-assistant-frontend==20180505.0: Could not find a version that satisfies the requirement home-assistant-frontend==20180505.0 (from versions: 0.1, <snipped>, 20180322.0, 20180326.0, 20180330.0, 20180401.0, 20180404.0, 20180414.0, 20180417.0, 20180418.0, 20180420.0, 20180425.0, 20180426.0)
No matching distribution found for home-assistant-frontend==20180505.0
#

should I try to manually install home-assistant-frontend==20180505.0 from pip?

#

or has the new frontend build not made it to pypi yet

queen axle
#

Go to pypi and check it...

dusk spindle
#

looks like that's the case, 20180505.0 isn't on pypi

queen axle
#

Congratulations

barren timber
#

Yeah I messed up

#

I ran the build command and not the release command

#

Just came back from my walk, fixing it now

#

fixed

dusk spindle
#

Looks like the custom_components PR #14211 broke the lutron caseta pro custom component that a handful of people use from the forums:

File "/home/hass/custom_components/lutron_caseta_pro.py", line 24, in <module>
    from . import casetify
SystemError: Parent module '' not loaded, cannot perform relative import

It's trying to do a relative import of casetify.py which is also in the custom_components directory. Is there a different way this import should be done now?

split sinewBOT
snow lantern
#

not sure what am I missing.... hassctl update-hass 0.69.0b0 is not working

#

same error with pip3 install --upgrade homeassistant

#

ImportError: cannot import name 'dist'

barren timber
#

maybe hassctl is not compatible with pip 10 ?

snow lantern
#

I tried pip3 install --upgrade homeassistant and get the same error

queen axle
#

also this is not the command to install pre-releases....

#

--pre

rotund yoke
#

hmm we should have that command pinned to this room

snow lantern
#

even with that same error 😦

queen axle
snow lantern
#

hmm....wondering what am I missing

green fox
novel wedge
#

So I just installed 0.69.0b0. In the absence of any release notes, is there any reason why the Yeelights picked up by discovery have changed their names to add another 20 or so characters in the device light. Name???????

#

If there’s a reason np but I had t edit groups and customise and my google assistant configuration and also when I tried to sync my devices it failed, unlinked and then my app wasn’t in the list to link anymore - had to go and test simulation again before it was back up and then could sync and it used the rooms so it wasn’t that much of an issue.

#

Anyway, just thought you’d like to know for the release notes.

barren timber
#

release notes finally up, somebody committed wrong docs

#

that's what you get when people don't test locally

#

bah

errant storm
#

Cool, thank you:)

neat lily
#

Installed 0.69.0b0 on hassio and now it seems like everything is broken. I can't log in to the frontend, the logs show nothing. I tried to SSH and downgrade but nothing is happening. What can I do?

thin crater
#

@neat lily you can downgrade back to 0.68.1

#

pip install home-assistant==0.68.1

neat lily
#

Thanks, trying

vivid plank
#

Good evening

green fox
#

Indeed it is.

novel wedge
#

@tidal mortar when you get a chance, can you advise re- the yeelights auto discovery in 0.69.0b0 - they came up with a different name to previously - a much longer string and meant I had to edit groups, customize, google assistant configuration and scenes - not an issue but if this is expected behaviour I don't see it in the now published release notes....

novel wedge
#

I saw that but it doesn't seem to be relevant....

blissful cloud
#

well that has the code in it which generates the name:
name = "yeelight_%s_%s" % (device_type,discovery_info['properties']['mac'])

#

ie, giving you yeelight_light1_hhhhhhhhh

#

Can you use the new rename feature to rename it back to what you had before?

#

(the cog on the popup in the frontend)

novel wedge
#

oh...... My name is now light.yeelight_mono1_miio56757126_miio_34ce00882e27 instead of light.yeelight_34ce00882e27

#

or something like that.

#

Only using discovery as I got sick of the duplication a while back

#

no there's no cog for those lights

blissful cloud
#

Hmm

#

so mono1 is definitely part of that naming change

novel wedge
#

I've already edited my files for the new entity just didn't see it in the release notes and when 0.69 drops people might be unhappy lol

blissful cloud
#

This was added:

+LEGACY_DEVICE_TYPE_MAP = {

  • 'color1': 'rgb',
  • 'mono1': 'white',
  • 'strip1': 'strip',
  • 'bslamp1': 'bedside',
  • 'ceiling1': 'ceiling',
    +}
novel wedge
#

hmm... well that's ok if it's not going to change again. It needs to get into the release notes otherwise the Whineing will have no end....

blissful cloud
#

I'm sure it'll make it into the release notes before it's generally available.

#

Got to expect inconsistency when running the beta 😃

novel wedge
#

oh yeah.... I'm not complaining at all - this was only a heads up

tidal mortar
#

@novel wedge This wasn't intendet.

#

I will care about a fix.

novel wedge
#

hahaha

#

ok

#

well it's not really an issue - just something to be pointed out if it does this in the release

tidal mortar
#

I tried to avoid a change.

#

I'm unsure what I missed.

novel wedge
#

i was surprised when I loaded the Beta and my scene didn't work and the lights were in another group etc. Just a minor annoyance really

#

i don't mind if it stays like it is now (as I changed everything already) lol

#

OLD:
light.yeelight_white_34ce00887db6
light.yeelight_white_34ce00882e27
NEW
light.yeelight_mono1_miio56777493_miio_34ce00887db6
light.yeelight_mono1_miio56757126_miio_34ce00882e27

So it's added a chunk of text in the middle

tidal mortar
#

Do you own some colored yeelights, too?

#

Or does it apply to the monos only.

novel wedge
#

no only those 2 and I have some Xiaomi switches that use miio as well but they aren't affected

tidal mortar
#

Alright.

novel wedge
#

chuangmi.plug.m1

#

switches

#

I have limitlessled as well but they are ok

#

different platform obviously

tidal mortar
#

It's a yeelight/netdisco related problem.

#

I will try to reproduce it with my yeelight color.

novel wedge
#

ok. i only updated to 0.69.0b0

tidal mortar
#

I don't know how I could miss that.

novel wedge
#

lol

#

so it's going to change back again?

tidal mortar
#

Yes!

novel wedge
#

for 0.69.0 release I suppose?

tidal mortar
#

I hope so. The breaking change of the entity should/must be avoided.

novel wedge
#

I'll need to make sure I change it back in my config before it comes out then

#

yes - as I said if that just happened even if it was documented - you'd never hear the end of it

tidal mortar
#

Thanks for the ping again! 😃

novel wedge
#

hahaha

#

well that's the point of beta testing

tidal mortar
#

I'm very happy about the beta channel & support! 😃

novel wedge
#

it seems to have lead to more stable releases and less dot releases

tidal mortar
#

Definitely!

barren timber
#

@tidal mortar will include it in next beta today

tidal mortar
#

@balloob#6041 Awesome!

barren timber
#

New beta has been released

rare sail
#

🎉

barren timber
tidal mortar
#

@novel wedge I just tested the beta1. The issue is fixed! 😃

barren timber
#

Put out another beta release that will silent the exception introduced in 0.69.0b1

snow lantern
#

Could not find a version that satisfies the requirement homeassistant==0.69.0b2

#

Weird....as I can see it on PyPi

barren timber
#

PyPi was seeing some hiccups today

snow lantern
#

That may explain

novel wedge
#

@tidal mortar Thanks for that..

novel wedge
#

miraculously, 0.69.0b2 is showing in Hassio now. I'm updating and I already reverted back to previous config for Yeelight so lets see if it's working as before again now

#

11 hours.... pretty quick

novel wedge
#

@tidal mortar Yep all working again now!

barren timber
#

New beta released

snow lantern
barren timber
#

Oh

#

Let me quickly push it

#

Done

fierce notch
#

On Hass.io: Home Assistant 0.68.1 is available
You are currently running version 0.69.0b2 ??

queen axle
#

Have you left beta channel?

#

Nvm, the version file is incorrect for rc. @idle wraith

fierce notch
#

No, Channel still shows: beta

queen axle
#

Yes, as I said the version file for the beta branch is not correct atm

fierce notch
#

Ok, thanks!

idle wraith
#

@fierce notch @queen axle fix

#

version.json make merged between branch a bit heavy XD

#

strange, my beta changes was lost ugly

#

maybe it forget to press save ...

#

I should use the git cli for this work and not with the UI

barren timber
#

You should automate it 😉

novel wedge
#

I just had the same thing and didn't see it before pressing upgrade so I'm back on 0.68.1 now. I'm not being offered any update so I guess I'll need to wait for 0.69.0b3

#

on Hassio so I suppose there is no way to force an update to b3?

queen axle
#

Go to System and press reload supervisor

novel wedge
#

Thanks. Just went in there to do that but now it's offering me b3 anyway.... @queen axle

queen axle
#

yeah, it's auto updating every 6 or 8 hours

novel wedge
#

fair enough. I need to remember to try that in future

snow lantern
#

Weird....I don't even have deConz and Hue is already configured. Only started seeing this today (I updated to 0.69.0b3 yesterday).

gentle sigil
#

@snow lantern i have had the same but no zone

#

and i dont have deconz but it says confiure

snow lantern
#

There was one deConz PR merged in the last beta...must be related

gentle sigil
#

prolly

snow lantern
#

same here...when I click on configure, it says No deCONZ bridges discovered

gentle sigil
#

hmm i hadnt clicked on it.... let me see

barren timber
#

So available doesn't mean discovered

#

Should probably be something like "Add new integration"

gentle sigil
#

yep it aborted none discovered LOL

barren timber
#

Hue is imported based on your configuration.yaml setting

#

We should also call it Philips Hue, without "bridge"

#

who is in control of this shit?

gentle sigil
#

yea makes sense but good to me either way

snow lantern
#

Available sounds like it discovered something

barren timber
#

Yeah, but actually the "In progress" section is for discovered ones

#

I've been adding a lot of features lately, I should be focusing a bit more on polishing it up

gentle sigil
#

yea there are 5 million dollar homes available LOL

barren timber
#

I'll put it on my list somewhere

snow lantern
#

It is confusing....that is it. There are so many other things that are not discovered 😉

#

If it is the expected behavior...then it is perfect

barren timber
#

Want to see something cool? Remove your Hue integration and see all entities disappear without requiring a restart 😃

snow lantern
#

you mean the one on top?

barren timber
#

yeah

snow lantern
#

Oh...I see. All the hue entities are gone 😃

gentle sigil
#

ha ha ... you cant get that back

snow lantern
#

yes....it is one click

#

Just added them back

gentle sigil
#

damn .... your no fun

snow lantern
#

Also, did we add 4 columns in this beta?

barren timber
#

what do you mean ?

snow lantern
#

I always saw only 3 columns....this is the first for me

gentle sigil
#

yea usually only 4 when menu is minimized

barren timber
#

So eh, I am not sure 😛

snow lantern
#

something funny is going on....I get 3 columns when I refresh (F5). But, when I use the restore the browser (the button between minimize and close) and maximize it again, I get 4 columns

#

I can reproduce it reliably

barren timber
#

We're going to overhaul the frontend machinery so no need to write up a bug report

snow lantern
#

cool

barren timber
#

Talking about overhaul of things, I just updated the frontend in the dev branch so you can now enable auth providers 😃

#

and try it out

#

it still won't be persisted so every reboot you need to login again

snow lantern
#

will try it as soon as it part of the beta....this is my production machine

barren timber
#

And you will be able to manage users for now just from the command line with the new auth script

#

hass --script auth -c /path/to/config add arsaboo secretpass

snow lantern
#

Yeah....I saw that and I really need it now. My kid figured out that he can now enable TV time using HA 😂

gentle sigil
#

poor kid

barren timber
#

haha

#

ok, I'm off. PyCon is starting 😃

snow lantern
#

may not not right now....but over time may be we expose certain functions to users

#

enjoy!!

barren timber
#

Yeah permissions will come eventually

tame maple
#

Great feature @barren timber

fast aspen
#

Hi, when I use the command pip3 install homeassistant==0.69.0 , and I reboot the system, I am still having the old version instead of the .69(edited)
Do I have to do something more?

barren timber
#

pip3 install --upgrade homeassistant

dusk spindle
#

also if you used a venv make sure you activate it before running the pip3 command

rotund yoke
jolly mason
#

I literally just got my hub yesterday and this confused the hell out of me lol

barren timber
#

0.70.0b0 has been pushed to PyPi

#

generating release notes as we speak

barren timber
austere sundial
#

I found a problem on 0.70.0b0 beta, i am unable to navigate trough tabs on the hass.io page. Getting the following error in my browser console: Uncaught TypeError: this.hassioPanel.navigate is not a function

#

I am now unable to upgrade or downgrade because the hass.io pages do not render. Is there any other way to upgrade / downgrade using hass.io?

#

I also get: https://{url}/api/hassio/build-temp/util.js 401 (Unauthorized)

royal shale
#

@mervin#6093 do you have the ssh add-on?

barren timber
#

util.js error can be ignored

#

I'll look into the hassio one

#

found it, pushing a fix

#

Published 0.70.0b1

onyx glacier
#

restore via ssh hassio sn restore -slug xxxxxxxx

royal shale
#

or use hassio ha update -o version=0.69.1 (or whatever version)

austere sundial
#

@royal shale unfortunately i do not have ssh on 😦 is there any other way? for example calling a javascript function?

royal shale
#

I'd add that the ssh addon is important to have. Not that the host ssh is difficult, but having access to the hassio cli makes things simple

#

Especially if you're running beta

onyx glacier
#

i agree, if you want to beta test, you really need ssh enabled.

modest dirge
#

docker pull home-assistant:rc here we go

queen axle
#

You can enter /hassio/dashboard and click the update button for home assistant

novel wedge
#

so from ssh I should be able to issue:
hassio ha update
to update to 0.70.0b1?
I can't see the Hassio tab in any browser here either. No error just blank

#

I'm not seeing an update yet anyway

#

the whole frontend does not seem to be as snappy as it was on 0.69.1 either...

barren timber
#

any errors in your logs when not seeing the frontend ?

#

the runtime of the frontend should be exactly the same. The only difference is how the code is put together

novel wedge
#

i don't see any errors related to frontend at all

#

i get a task destroyed, timer got out of sync, duckdns error and config taking over 10 seconds

#

but I've pretty much always seen those

#

actuall I lie

#

looking in log I see:

#

2018-05-20 13:43:38 ERROR (MainThread) [frontend.js.latest.201805181] :0:0 Script error.

ivory quartz
#

@novel wedge @barren timber I am getting the same issues.

2018-05-20 08:32:56 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

2018-05-20 08:33:57 ERROR (MainThread) [frontend.js.latest.201805181] followed by a massive blob of data ending with "Script error." This happens when I click on the Hassio option on the left. The Hassio page is blank. My HA journey is in a very early stage, so no other complications that could have affected Hassio.

ivory quartz
#

I suspect that due to this, I'll have to re-etch Hassio on the SD card of the Pi and pop all my config back in as I cannot remember the password that I assigned for my SSH addon in the hope to downgrade HA, lol. Yep, that's the price one pays for living on the bleeding edge. 😃

novel wedge
#

Just wait for 0.70.0.b.1!

visual sorrel
#

Just for info as I don't seem to be alone but hass.io tab has stopped loading since updating to 0.70 beta.

royal shale
#

@novel wedge I haven't installed the beta. Can you reach it by adding /hassio/dashboard to the url?

#

I saw crusader727 mention it

#

or @visual sorrel have you tried

visual sorrel
#

Great that worked thanks.

royal shale
#

and @ivory quartz if you're still around

cinder wind
#

On my setup, I have noticed this is not limited to the Hass.io pages as my FloorPlan pages no longer load either (which this could be a change that will need to be addressed in FloorPlan?).

barren timber
#

@cinder wind I think it has to be addressed in floorplan… I have tried to get in touch with custom UI and custom panel devs via Twitter, #devs_frontend-archived and opening issues in the frontend repo. There is only so much I can do

novel wedge
#

yes that works. @royal shale

#

still not seeing b1 yet. I did reload supervisor from the ssh command line

barren timber
#

Weird

novel wedge
#

some times it takes a day with hassio

fierce notch
#

Indeed, still no b1. Also tried reloading the supervisor. This time the wait is much longer 😉

novel wedge
#

yes. I thought I'd see it by now for sure

fierce notch
#

Haha, me too. Checking was second thing (coffee first) this morning.

novel wedge
#

lol

#

it's been over a day

#

i bet I shut down my computer and then it will be there.... (It's almost dinner time here)

barren timber
#

No b1 yet because Pascal's wife is giving birth

#

So I'll update the JSON and see if that does the trick

#

I think the building is happening automatically but the releasing is not

#

ok what about this ?

#

can you check for updates again ?

barren timber
royal shale
#

@barren timber I see 0b1 now

barren timber
#

And can you upgrade to it ?

royal shale
#

just hit the update button

#

seems to be working

#

waiting to reconnect

#

ok hassio panel is back and navigable

#

icons are still an issue, but not related to the panel

royal shale
#

I can't figure it out. This is only happening in Chrome. If I crtl-f5 all the icons come back. I can click around and they remain. As soon as I hit my bookmark for my HA page, a majority of the icons disappear. I've cleared cache completely as well. Same behavior. The icons that remain are always the same.

#

and this is something that happens in chrome, ff, and edge for every light:

queen axle
#

the issue with the sliders is fixed already

barren timber
#

Yeah I'm pushing another update right now

#

The icon issue, it's weird 😦

#

I've published another beta that solves the double slider issue

royal shale
#

@barren timber did we hit another "built but not released" with beta release for hassio?

queen axle
#

It's not automated

novel wedge
#

i confirm the hassio panel is back

#

i don't have any icons in the hassio panel even if I ctrl+F5 in chrome as well