MTS150 not following HK ignore

[Marksi73]

What issue do you have? Please be as thorough and explicit as possible.

Homekit-native Devices (smart Thermostats) are doubled in Home because all Devices connected via Hub are Homekitnative AND visible through plugin). Example Device: https://www.amazon.de/gp/product/B09G9XKH3G/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS? 1

• Which version of Homebridge/HOOBS do you have? 1.6.0

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known. Raspbi 4, Node.js Version 16.17.1

• Which version of this plugin (homebridge-meross) do you have? Has the issue started since upgrading from a previous version? newest. The Thermostats are new and since then this effect occurs

• Which Meross devices do you have that are causing issues? Please include product models if applicable. Smart Thermostats connected via homekit hub

[bwp91]

Hi @Marksi73

please can you provide a model list of the hub subdevices that are homekit native? (that you own)

[Marksi73]

I have several „MTS150 Version 4“ here (so they are called in the app during setup). In the userguide and some internetsites they are called „MTS150H“.

[bwp91]

do you happen to know if there is a version of this model that is not homekit native?

[Marksi73]

I never found one, but I don‘t know it for sure

[bwp91]

Specifically ignoring the MTS150 is a bit of a pain for the plugin as the plugin does not seem to [need to confirm] be able to distinguish between the HK models and not.

What I shall do is add config options to be able to ignore sub devices of a meross hub

[therealsatera]

have this issue, too. an option to not transfer an device to Homekit, if its already there would be great.

Meross MTS150 v4 Homekit Edition

[Marksi73]

I bought an homekit-compatible switch meanwhile so I dont have this problem any longer. A config option to ignore devices under a hub would be very useful I think. Thanks for you efforts.

[bwp91]

For context on why I have been so "slow" on this...

For most devices I can ignore by homekit-native-ness by the model and hardware version.

In this case the 'device' is the MSH bridge, which exposes both homekit native and non-native devices. So a homekit native bridge can expose non-hk-native subdevices and conversely a non-homekit native bridge can potentially expose hk native subdevices.

So the answer is not as simple as ignoring or not the bridge device.

[Marksi73]

Hey, I never wanted to say that you are „too slow“ or anything similar. I believe that this is a tricky thing and not easy to solve. Many thanks for your good work!

[bwp91]

I never wanted to say that you are „too slow“ or anything similar.

Ah I did not mean to suggest that I thought anyone had thought this 👍

[bwp91]

@Marksi73 are you available on discord?

[bwp91]

By the way,

A config option to ignore devices under a hub would be very useful I think.

this already exists

[Marksi73]

@Marksi73 are you available on discord?

No sorry :)