Android TV integration

What do you mean by Google Home remote? Is it via the Google Home app on your phone or via a Google Home speaker?

Ok maybe we should improve the UI so it’s clearer

Are you able to turn it off/on with this Chromecast or is it like your other Google TV, and it doesn’t work?

In the Google Home app:


I have this:

The circle doesn’t change the volume but if I click on ‹ ouvrir la telecommande ›:

I can change the volume (of the Google TV).

However, via the Chromecast HD:
Power on+off OK
Changing the volume is impossible but that’s a technical limitation because the volume is not controlled via the Chromecast but via IR (the supplied remote is universal)

Edit: wouldn’t there be a way to detect the Chromecasts present on the local network rather than entering the IP address manually?
It’s inconvenient because IPs are dynamic by default for me (and many people…)…

Good idea, I need to see how it’s done in the other integrations.

2 Likes

For Google Home, I already have a PR to integrate TV devices

1 Like

@AlexTrovato is this PR ready for review? :slight_smile:

Maybe re-run the tests, Codecov failed on the upload

This is a PR on my repo, codecov is acting up on my account.
But yes, the PR is ready — I need to generate an up-to-date test image to have it approved by our seasoned testers :wink:

2 Likes

So I created a PR on the Gladys repo:

And the test Docker image atrovato/gladys:google-home-tv is being built — it should take about 1 hour from now before it’s ready!

Thanks :slight_smile:

1 Like

Despite several attempts:

Unable to find image 'atrovato:google-home-tv' locally
docker: Error response from daemon: pull access denied for atrovato, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

Is there an issue with the sharing? Or is it just me?

Indeed, I made a mistake in the image name atrovato/gladys:google-home-tv, I am correcting my other comment.
Sorry for the inconvenience :confused:

1 Like

Hello!
I’m a bit stuck on how I should test @AlexT

Hi,

indeed, testing Google Home features isn’t the easiest.

First, you’ll have a problem because you won’t be able to test the Android TV integration and the TV functionality of Google Home at the same time, since each development is separate.

Regarding Google Home, today only Gladys Plus allows interacting with Google, and I advise against connecting a test instance to your main Gladys Plus account. You risk creating inconsistent backups.

It is possible to swap your production image for the test image, but I also discourage this procedure for the same risk of inconsistent backups.

(even if normally the risk of inconsistent backups is almost « impossible » with the Google Home test image, you can never be completely safe from a hidden bug)

One possibility would be to install a test Gladys Plus to which you would connect your test instance, but you would also need to configure the entire Google environment…

So it becomes complicated to test.

I think we still need to define a way to make testing with external services easier…

I can provide Gladys test accounts if needed!

@AlexTrovato did you test the feature for real or not?

Yes, I set up a Gladys Plus at home with all the Google configuration :wink:\n\nEDIT: via the Broadlink integration and a real TV.

1 Like

Ok great!!

@GBoulvin if you want a « secondary » Gladys Plus test account so as not to pollute your production, tell me :slight_smile:

What I find annoying when using the production Gladys Plus is that you’ll still have to « interrupt » production via Google Home by disconnecting from the Gladys service on Google to sign in with your test account, and vice-versa once the test is finished.
The devices will be deleted, and if the user has created triggers from Google Home (or other custom configuration), I don’t know what will happen. The user might lose everything.

I’m not sure I understand the scenario you’re describing… ^^

@AlexTrovato I did a test with the Docker image and a « virtual » MQTT device :

But the device appears as « offline » in Google Home:

Any idea ?

Uh no, that’s weird. Unless Gladys is unreachable. Or maybe because there are no values for the features.
Is the other « online » device from the same Gladys instance?

Indeed I have never used this TV (virtual).

Are you setting the attribute « online »: true correctly?

Yes

The device is « online: true » by default:

However, I’ve just re-run some tests, and indeed, it doesn’t work anymore… according to Google’s tests, some required configurations for the TV are missing.

I’m revising my copy…

2 Likes