The irony of this is, yes, GE link is not officially supported device, yet, as you rightfully pointed out its handler is local. However Osram bulbs which ARE officially supported devices don’t have handlers on the hub nor does Fibaro motion sensor (another official device that is not running locally). So, is NOT a support issue here, but a disconnect between various people involved in maintaining this platform.
Ohh, so here is a bright idea, we need to use the handler of an unofficial device to force an official supported device to run local. What sense does this make? You tell me!!!
FYI, thought I’d let folks know that during my migration from one v2 hub to another, I just had an smartsense motion sensor freeze up on “motion”. It happened soon after I rebooted my hub. I have no, zero, zippo smartapps deployed using motion sensors. @slagle tagging you as an FYI as well, including updating my open ticket on this issue.
I had 3 motion sensors that froze up on me last night. So this morning I rolled up my sleeves to migrate to Wink, because this is getting ridiculous. Unfortunately, that doesn’t work…so I am back at biting my fingers every time a device fails…
I have a Smartthings Outlet which refuses to be controlled on/off since last week, yet when I manually turn it on/off (at the outlet…little button on it), it will livelog as turning on/off, so I know the Hub (v1) sees it and is communicating with it. I’ve tried renaming the device handler, switching to v1 outlet handler, etc…nothing works. All other devices I have are working.
Since I got my ST system back in December, I’ve lost 3 ST motion sensors. Like, locked up on motion/ no motion, still reporting temps and battery. No amount of fussing has brought them back.
Just happened to one over the weekend. Don’t know if it’s the sensor or the system, and the way things are … I don’t know how to know that! But I’ve reset that little thing probably 200 times over the weekend. No luck