0.74: Tuya, Cloudflare DNS, Push Camera and Users UI

It’s time for Home Assistant 0.74! 🎉

This week we heard that Guido van Rossum, the founder of Python, is taking a permanent vacation as the leader of Python after being at the helm for almost 30 years. Guido has not been directly involved with Home Assistant. However he created Python and was part of the team that built asyncio, technologies that power the foundation of Home Assistant and what makes us so fast and robust. Under Guido’s guidance, the Python community has grown out to be very friendly and open. A great inspiration for us and other tech communities out there. Thanks for all you have done Guido!

![](upload://ysY6w6IxzEhXDcOsrAT6tGMuKIt.jpeg) Paulus & Guido at PyCon US 2018

All right, back to Home Assistant. The last release introduced a tech preview of the new user system. The initial preview still required creating users via the command line. In the last two weeks, we’ve worked hard on adding support for an onboarding wizard and a user management interface. A walkthrough of the new features can be found below. Thanks to @awarecan and @jeradM for all their work!

To try it out today, read these instructions. The user system is still in tech preview. We’ve moved fast to get where we are today. The next step is that we need to take a step back and look at the system as a whole to make sure it’s robust and ready for prime time.

We keep seeing great examples of UIs built with Lovelace. Follow us on social media (FB, Twitter, G+) where we will keep sharing great examples.

For the Lovelace changes in this release, check out the changelog. To help our development and design teams, we’ve also introduced a Lovelace card gallery.

Thanks to @c727, @jeradM and @ciotlosm for leading this effort ❤️

I’m happy to announce that this release introduces support for Tuya thanks to @huangyupeng. Tuya produces cheap cloud-enabled devices that are sold under a wide variety of brand names across the globe, and now they work with Home Assistant too!

New Platforms

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Breaking Changes

Beta Fixes

All changes


This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2018/07/20/release-74/
3 Likes

thanks for this release.

I am trying to set up users on my Hassbian installation and cannot find the script which is in built Homeassistant. When I use the command hass --script auth --config /path/to/config on my configuration.yaml directory I get --bash: hass: command not found

Any help please?

Thanks.

You don’t need to use the script anymore with 0.74.

so all I need to do is to add the following in my configuration.yaml:

# Example configuration.yaml entry
homeassistant:
  auth_providers:
   - type: homeassistant
   # Uncomment next line if you want to enable legacy API password support
   # - type: legacy_api_password

# Enable the auth component
auth:

Because I have done that and I dont get a new login screen in my frontend after restarting HA.

Mine complains about “access_token” not being setup. I can’t find this in any of the docs posted. :frowning:

how did you set yours up?

Exactly what you posted, but it never serves the UI, so I’ve reverted the auth setup in my config to get it back online.

Do users work with iOS application?

Did you log out, after doing that?

Done that and it works fine now thank you

Man… I want to get home now. Tuya is going to be awesome!

Is the new python build / version included in the docker image for this release already? It was mentioned here: https://twitter.com/pvizeli/status/1017906821577805825. I am specifically interested in this image: https://hub.docker.com/r/homeassistant/raspberrypi3-homeassistant/tags/

I have a new user created when I look in Configuration>Users (in Hassio) I have the user I created that is the owner and also a homeassistant user that I didn’t create??

image

Can I delete this user? Where did it come from??

That was created by legacy_api_password auth provider. You can delete it if you don’t want to use legacy_api_password anymore, and if you are regret, legacy_api_password auth provider will recreate it.

1 Like

no worries… just wondered where it came from. @dale3h suggested it might be that.

After put in the configuration. There is popup for me to set Name, username and password. Then I cannot login to the page at all.

# Example configuration.yaml entry
homeassistant:
  auth_providers:
   - type: homeassistant
   # Uncomment next line if you want to enable legacy API password support
   # - type: legacy_api_password

# Enable the auth component
auth:

Any error log?

on frontend https://ip:port
error loading

Do I have to logout from current (normal before setting the new authorize). then restart?

Not necessary, but you can try. Any error in back end?