I just ordered $100 worth of eWeLink ZigBee sockets and have discovered that these do not work with the SmartThings Hub. I’m wondering now, after looking into various posts about this…why doesn’t this work?
I don’t see, or can’t find, the protocol used by eWeLink. But if this works with Amazon Echo, then wouldn’t this have to be HA1.2 also ?
In the SmartThings App when I find the device, the device is found but doesn’t ever become recognized. It just remains as a “Thing” and I will never be able to get a status from it. It “should” be recognized as a socket. Why is this the case? Is there a way for me to see the raw logs of the communication that are happening?
“Thing” says to me that ST recognized something but it’s not sure what it is, so do what @Automated_House recommends and manually change the device type. More than likely ST doesn’t know the “fingerprint” of your device, hence the “Thing” thing… Send us a link to the product too please.
They only work for some people. It just depends on which “Shard” of the SmartThings cloud system your particular account is located on.
This has been a frequent issue over the years since 2015. One person will post a link to graph.api, Which is the original shard, and then someone else will post that when they go there either their account is blank or they can’t get into the IDE at all.
If it works for your account, it will work whether you put in the universal address that I listed or whether you put in the graph.API address.
But there are lots of other people that it will not work for, more and more each year as the customer-base grows and new people are put on different shards.
You can find many threads discussing this existing in the forum. Please just read the FAQ already linked to. It explains the details and, again, asks everyone to use the account.Samsung URL when posting to the forum to prevent frustration for other members.