[Matter] Differentiate shutters/blinds/doors with the endProductType

Being able to differentiate the type of openings

As seen in the discussion Différenciation des volets/stores/portes - #12 par pierre-gilles, the goal is to be able to differentiate the openings coming from Matter (and matterbridge via the current somfy/tahoma plugin):

  • roller shutter
  • garage door
  • awning
  • patio awning
  • interior blind
  • etc.

Commands could then be differentiated later (retract/extend for a patio awning, instead of open/close for example) and have dedicated icons (gate, garage, shutter e.g.).

The different elements will come from the Matter 1.4.1 documentation :


Some links to the Matter APIs if that helps:

Good evening everyone,

I’m bringing this topic up again… I have 5 roller shutters and a motorized Somfy sliding glass door. If I ask to close all the shutters (which were open) => the 5 shutters close

…and the sliding glass door (which was closed) opens…

Could we choose the type of opening at the Matter integration level in Gladys rather than wait for updates to the Tahoma plugin? A simple drop-down list…

Hervé

Hi @Herve, I’ve reread the discussions, and there’s no point waiting for a Tahoma plugin update; the ball is more in our court :slight_smile:

In this

Hello Pierre-Gilles

Yes, I use Google Home for voice commands.

At first, I had connected the Tahoma box directly to Google; it worked well.

Then I migrated Gladys to the mini PC and configured Matterbridge with the Tahoma plugin.

Because I then had all the Tahoma devices duplicated in Google Home, I removed the direct link to the Tahoma box in Google to keep only the link to Gladys.

Since then it’s a mess!!! :joy:

1/ they’re all « shutters »

2/ with Tahoma directly, Google seemed to know the state/position of the shutters; now that’s no longer the case. However, I created scenes in Gladys for opening/closing (Velux), and that works.

3/ but when I ask for opening or closing by voice, it works one time out of two… I need to dig into it…

Otherwise, yes regarding the Tahoma plugin, I haven’t had much feedback…

Hervé

Thanks for your feedback @Herve :slight_smile:

In that case, to address your issue, I think you can create a « routine » that just closes your shutters (and not your sliding glass doors), and then have a special voice trigger for that routine. (Search online for how to create a Google Home routine; there are plenty of tutorials)

Is the problem between Tahoma and Gladys or between Gladys and Google? Do you see the position in Gladys or not?

Whose feedback are you talking about? Mine or the matterbridge-somfy-tahoma plugin?

Pierre-Gilles,

Ah yes, sorry the wording was ambiguous! It is indeed the feedback from the plugin matterbridge-somfy-tahoma following the bug related to an unsupported device.

As for the rest, I’ll run tests and checks and will keep you informed.

You will only see the position in Gladys if the openings were controlled by Gladys.
You’ll need to make sure to set the up/down timing in the matterbridge-tahoma plugin settings to get a roughly correct position.
And currently the plugin does not retrieve the states of the shutters if they are controlled by a tahoma switch or a remote control.

Good evening @mutmut,

I don’t see where to enter this info in the plugin? Do I need to go into a file?

@Herve here’s where to enter the info :



You add your shutter/blind, you set the time in seconds it needs to raise or lower (I think I set the longest time when I had differences of 1 to 2s).
And once you’ve added all your shutters/blinds, the percentage given by the plugin becomes proportional to the time.
It’s not ideal yet but it helps compensate for the lack of state retrieval by having an « approximate » position.

@mutmut

Thanks for the feedback!

But oddly the plugin’s settings icon is inactive…

I just saw the docs on GitHub — I’ll edit the configuration file…

Weird :flushed_face: … but how did you manage to enter your credentials then?

EDIT: is your matterbridge up to date (3.3.3 currently)?

There we go, it’s good — actually Matterbridge needed a restart…

I’ll be able to record the ascent/descent times.