How to Use a Meross or Matter Plug to Use HomeKit Presence to Trigger ST Routines

The Homekit idea is great for someone who has Apple TV, etc.
I quickly created virtual presence sensors in smartthings to test.
I have Hue lightbulbs. Homekit dims 2 lightbulbs to 2 specific percentages when a specific person leave/home. In smartthings, have automation with the condition of the 2 specific percentages to set the target presence sensor. Also dim the 2 lightbulbs to 50% and auto turn off in 10 sec to avoid the matching percentages happened.

Did a quick test and did look working well for now.
Thank you for sharing this great idea!

1 Like

It is utterly shameful that in 2024 Samsung cannot reliably do presence sensing. Its very obvious what this bug is and I find it shocking that Samsung do not fix it. Anyhow I thought this work around was a great idea. So I bought a Homepod and a Meross power strip (homekit compatible),. I set it all up but the only problem is that Smartthings does not recognise the switch change if I make the change in apple home. I can turn any of the sockets on and off from Smartthings and I see the change in Apple home, however if in do it the other way round and turn a socket on or off from Apple home the socket does indeed turn on but the status change is not registered in Smartthings. Any thoughts?

I’m sure that’s frustrating. It’s working fine for me. If you turn the socket off from the SmartThings app, does it show the change in apple home?

And did you use the custom integration to both platforms or did you use matter if that’s available for your device? (I’m not using matter for this.)

Tagging @jkp because I believe he also has some Meross devices and might be able to check if the state change is working for him. :thinking:

working fine here

how does the strip appear in Apple Home? one tile or separate tiles for each outlet?

1 Like

Mine appears as 5 devices, for what that’s worth. :thinking:

This is exactly how it appears in mine. When I turn off the powerbar manually they turn off in Apple home but do not turn off in Smartthings. However i can turn them off an on from the smartthings app. If it works for everyone else it must be a setting somewhere?

I just added the device and it shows as a linked services. The meross devices are under meros-c2c-pro. I have tried hitting refresh but this makes no difference

There was a user who reported a similar issue with their new Meross Garage door opener last night (status not updating in ST when managed in the Meross app). Best recommendation is to report the issue to Support for both ST and Meross.

2 Likes

I’m finding ST presence, at least from an ‘arrival’ standpoint, very reliable over the past many weeks. My iPhone is working perfectly, and the old ST arrival sensors are functioning well. I have one that occasionally drops off, but its issue is remedied via a Mode and via time conditions. If it is heard from within X time of dropping off, the system considers that it never left - and therefore does not unlock the door.

1 Like

FYI the fix for this was to unlink Smartthings from Meross then to relink it.

The problem was nothing to do with homekit as I could see non-homekit Meross devices exhibiting the same fault (whereby manual changes of state were not reflected in Smartthings).

All working now.

1 Like

I find the problems with presence using Iphones is not for me but other family members who do not routinely use the Smartthings app. Whenever they reboot or there is an IOS upgrade their phone needs to have smartthings restarted and logged into. They don’t think to do this until the sirens go off. I’m sure Samsung could fix this as I never had these problems when I used the life360 integration before this was killed.

1 Like

Wasn’t Life360 a totally separate cloud-based system, and the integration between it and SmartThings cloud-to-cloud? And didn’t Life360 have security AND data usage concerns?

Yes, to all of the above. It turned out. Life360 was selling location data to third-party brokers. Yes, even of kids. It wasn’t supposed to be individually identifiable, but that’s a whole other discussion.

2 Likes

Is anyone having issues with Meross/Homekit/Smartthings automations? My automations are triggering in HomeKit but not syncing into SmartThings recently after working flawlessly pretty much for several months.

I am. I’m using the 3 socket outdoor Meross plug as “presence sensors”. The automations are running, but the status does not sync to SmartThings when a person returns home/the outlet turns off. I’ve tested it via automations in Homekit, manually turning on/off in Homekit app and Meross app. The status syncs properly/automatically when a person leaves/the outlet turns on, but not when they return. I need to swipe down several times in SmartThings for the status to eventually update.

For me, my ST/Meross c2c devices that should be mirroring my Meross Homekit devices and the Meross App devices, do not update in ST when turning off, therefore any automations in ST based on the off status do not run until manually switched off in ST. They do show to be correctly switching off in Meross and HK.

Once manually turned it off in ST, they will all turn on in HK, Meross, and ST at the appropriate proximity and all required automations run.

Tried unlinking Meross from ST, as I saw that suggested on the Meross forum for previous instances of this behavior, and rebuilding my routines and sharptools panels that displayed those Meross devices but still the same effect. Switch “off” in Meross and HK won’t switch off in Smartthings. Switch “on” in Meross and Homekit DOES switch on in Smartthings.

Same. Only when Off and only in ST. On works fine. And seems to be only the HomeKit Meross power strip based on @JDRoberts recommended presence work around. I do have the MSG200HK garage opener but no related ST automations so haven’t checked to see if it updates correctly. All non HK Meross automations seem to be reliable, best I can tell.

I am experiencing the same problem. It was working fine for a while but now I have the same problem as the above 2 posts. Does anyone have this working ok still? Is it a new bug in the ST-Meross integration.