2023.5: Let's talk!

[Tokyo]

Interesting, it seems I was offered the Tapo C-200 camera firmware through the HA Systems menu: Version: 1.3.6 Build 230424 Rel. 77225(4A50)

Is that possible?

[AleXSR700 (Alex)]

I tried adding ssl support

Certificate Authority and self-signed certificate for SSL/TLS

but I just get that the server is not trusted. Both by the companion app and chrome.

Any new method available that actually works?

[nickrout]

It may be. Integrations can do that.

[armin-gh (ArminH)]

You did import your self signed certificate as trusted certificate into chrome?
The guide doesn’t seem to cover the client part of using self signed certificates

Armin

[boheme61]

@Tokyo

Is that possible?

Yes, a feature that was recently(months ago) added to Tapo(camera) controller.

If you click on Tapo(camera) controller in HACS, you can click the 3 dots in top-right corner, then click Redownload, there you see which versions are available, latest are 5.2.2(and you seems to have 5.1.7, so thats why), choose that 5.2.2 and redownload

1.6.1 is for tapo-controller, integration mainly made for Tapo-Plugs

[AleXSR700 (Alex)]

No, I did not.
But my main issue is the companion app anyway and that does not seem to allow importing or trusting.

I openes a thread for this here:

How to create ssl certificates for a purely local system?

Hey everyone, so the new voice Assist requires https/ssl to work. Unfortunately, HA does not come with built-in support. I tried creating my own certificates as described here Self-signed certificate for SSL/TLS - Home Assistant 中文网 but that seems to be outdated because it does not work with the Companion app. I am running a purely local server, so I cannot supply an external url to register. I won’t be running any VPN etc. (especially since they don’t work with DS Lite). So is there a way t…

[templeton_nash]

For what it’s worth I thought I’d contribute my experience of updating to 2023.5. This is because there have been a number of problems reported and I thought I’d share my findings.

Firstly, I didn’t rush in. I always wait and see what others report. I was particularly concerned about the bug where devices are no longer exposed to Alexa. So, I waited until this bug was fixed in 2023.5.1. I then waited some more because I had family stuff to do and I wanted to wait until I had sufficient time to deal with any issues.

I then made some screenshots of all my exposed entities and Alexa routines - just to be on the safe side!

I then updated to 2023.5.2. The experience was flawless. I quickly dealt with the 2 repair issues I had - a webhook and the workday sensors.

I then had a play with a voice assiatant.

I was concerned that I needed to set up DuckDNS, DNSMasq and all that stuff. What I’d overlooked was that I already have HTTPS access to HA via Nabu Casa. I just connected to the URL provided in Settings > Home Assistant Cloud > Remote Control. I’m not sure if this is super efficient because of the round trip to Nabu Casa servers that this introduces. However, at the moment I see this as something for play only. I think we’ll need wake word cabability before it is really useful.

EDIT: For me, the most significant benefit from the voice assistant work is the much improved way that devices and entities are exposed to voice assistants. To be able to do this directly from a device or entity is great, as is the ability to bulk expose and unexpose.

[Tokyo]

Thanks for the information.

There is no menu on the Tapo integration on the main Integration screen. However, if I select one of the cameras, I do get the menu and it has a Reload option. Is this what I am after?

[boheme61]

@Tokyo

Is this what I am after?

Nope, In Hacs, click on the Integration … Then click on the 3 dots

[AleXSR700 (Alex)]

What I don’t understand is that HA is proud to allow users to have safe, local, non-third-party systems yet the year of the voice requires the user to use third-party services and exposing the system via VPN to even use the microphone.

So what is the solution that allows users to profit from Assist without having to use third-party services and exposing their system?

If there is one, great, please add it to the description so users can use Assist

[petro]

You’ve been told multiple times that it’s browsers that enforce SSL for microphones, so there’s not much to ‘not understand’.

[Tokyo]

Thanks ! Found it, but didn’t need it.

After I got these errors, I went back to 2023.5.1. When I tried to redownload the Tapo integration, it wouldn’t let me requiring HA 2023.5.2. Once I reinstalled 2023.5.2, HACS offered the latest Tapo integration as an update.

Back to running 2023.5.2 without errors thanks to everyone giving me more insight on HA.

Thanks !

[AleXSR700 (Alex)]

So you are saying that no one in the team thought of that and no one knew that no browser will support this years’ features nor the HA own companion app because WebView does not support this either?

I am not even looking to use a browser. The companion app itself doesn’t even work with Assist.

So this year’s great voice features will not work for anyone who actually wants to have a secure system, closed system? It will only work for systems that are exposed via DuckDNS/VPN services?

[petro]

The companion app is a browser.

[AleXSR700 (Alex)]

It is an app that uses Webview. It is not a standalone and full feature browser.

You can call it browser but whatever you call it, did nobody in the team consider that basically 99 % of the “tools” that users would use to access their HA will not work with Assist?

[petro]

Both mobile apps extend safari or chrome, which have this limitation.

[Kertz1954]

I am not even looking to use a browser. The companion app itself doesn’t even work with Assist

.

My android companion app works very well with Assist.

What’s your problem ?

[nickrout]

You know most people won’t use voice assist via a browser. If you are at your browser, click a button.

Esphome based devices won’t require ssl. Voip doesn’t either.

[AleXSR700 (Alex)]

@Kertz1954 : please read. no ssl, no assist

@petro: So I repeat, no one thought of this? Btw, as per the devs, Companion app does not have the same abilities as chrome, which does allow for insecure mic usage. But companion app uses Webview which does not. So again, not thought through.

@nickrout: ESPHome is a new child of HA and that’s fine, but maaaany people dislike it because it is not as useful as other integrations. It is nice, but too limited and not intuitive. So what is the solution for everyone else? And who wants to use ESPHome to use a mic? 0.x % of the people?

There is a companion app and that is the main entry point for most people with a mobile device. And it is the mic that everyone has. And it does not work with Assist.

So, I’m sorry, but what good is a year of the voice if the most obvious approaches are all not supported and nobody thought of a workaround?
Tablets, mobile phones, computers… they all use browsers/companion app. And all are available and used by most users. None will work.

Just saying: year of the voice was never a good idea but if it doesn’t even work with the “stock” app, it makes even less sense.

[nickrout]

Have patience you angry man. Voice assist only started this month.