Shutter with Google Home

Hello, I added my shutters in Gladys, but I have 0 devices showing up in Home.
Is that normal?

They are not yet integrated into Google… it’s on the to-do list…

1 Like

Ah okay, at the moment, what’s available?
Light and outlet?
It’s a shame that the paid integration is only partially implemented :stuck_out_tongue:

Yes, I’d say the classic switches, and the colors of the lamps.
But not the rest…
It’s a pity, I admit, we’re doing our best :wink:

1 Like

Good evening @spenceur,

I’m not sure if you’re used to test images, but I’ve started the development of the integration of shutters and curtains with Google Home, so I’m generating an image: atrovato/gladys:google-home (it will be available within 2 hours).

So as usual, before deploying the new image, it’s recommended to make a backup of the database, or to use another Gladys instance so as not to risk corrupting the functional data (and avoid having to start from scratch).

If you’re not used to this mode, we can find interested people in the community.

I made the changes blindly, not having the means to test the devices at home; please be lenient :wink:

PS: I also have the thermostat on my to-do list for Google Home.

1 Like

I’ll take a look as soon as I have 10 min :slight_smile:

1 Like

This weekend I should have 15 min ^^’ @AlexTrovato I haven’t forgotten you

1 Like

@spenceur don’t hesitate to give feedback :wink:

Hmm short on time :smiley:
I was wondering, I mount the image on a PC,
I transfer the G+ account to the PC’s instance and try via Google ?!

Is the rollback a re-transfer of the G+ between the two instances?
Any risk of messing up the G+ production?

No worries, I just wanted to know.

For your test, in this version there are no modifications to the database, the risk of losing data is (normally) nonexistent.

But the test image is not up to date with enedis and the latest changes… so there may be a side effect.

I wouldn’t want to harm your installation through overzealousness… I’m invoking a special card :stuck_out_tongue:

@pierre-gilles any idea how to test an image through Gladys+ « without risk Â»?

Ahaha! Thanks :smiley:
I’ll take care of it one lunchtime at work.
I’m waiting for a reply from @pierre-gilles :slight_smile:

You can run your tests with the MQTT integration :slight_smile: That’s always what I do. You create MQTT roller shutters, and on the Google Home side you check that the action in Google Home is properly reflected on the front-end. If it works with MQTT, it will work with other integrations (this doesn’t preclude a final test)

For testing at @spenceur :

I assume these changes are relatively minor and do not touch the database; if that’s not the case this tutorial does not apply:

  1. @AlexTrovato: rebase your GitHub to be as close as possible to current production, and restart a build of the Docker image. A quick test via the MQTT integration on your side would be best to avoid the ping-pong for small development bugs :slight_smile:
  2. @spenceur: As soon as the image is ready, if Gladys hasn’t had an update by then (in which case, go back to 1.), stop your production Gladys, and restart a container with the same parameters as production, changing only the Docker image.
  3. @spenceur: To return to your normal production, stop Gladys, and do the reverse: restart Gladys in production with the production image (gladysassistant/gladys:v4)
1 Like

Perfect! I’m preparing an up-to-date image of the latest release published tonight, thanks :slight_smile:

And I will also test it on my side via MQTT.

Thanks again.

2 Likes

Thanks @pierre-gilles @AlexTrovato,
I’ll test between two meetings or at the lunch break if you’ve had time to update the image :slight_smile:
Thanks :slight_smile:

1 Like

Well, I tested with a fake MQTT device… and bam, it doesn’t work… so I looked at Google’s documentation, and there I came across a particular case that’s not handled at the moment:

Note: You must use the secondary user verification for this trait.

So uh… I’ll do some dev work to integrate that…
In the end the feature isn’t ready :confused:

Sorry for the wait and the inconvenience… I’m doing my best.

EDIT: it’s only for voice commands… to consider for prioritization
EDIT: but it still doesn’t work

Ahaha no worries, I’ll wait for your go :slight_smile:

So, I still have something, up to date on version v4.20.0 (apparently that helped it work properly with G+).

The image is available here :

Keep me posted :slight_smile:

1 Like

Were you able to test it via an MQTT device without any issues?

Yes, I did see the values update on my dashboard.

It’s OK with me, by the way :smiley:

1 Like