Was very excited with the Connect Home announcement, thought I can solve two problems (wifi and Home automation at once)
Bought the Samsung Connect Home (imported from US), set up yesterday. And very surprised to find out that can’t find the option for the Smartthing hub. Asked the question to webchat, and was told that it is because smartthing hub not available in Australia.
Very annoyed because it means that have just bought very expensive mesh wifi system.
Anyone knows anyway to get around it to enable the smartthing hub function? use VPN?
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
3
Have you been able to download the SmartThings App itself (perhaps by finding an APK if it is not in Play store…)?
What happens when you try to “claim” the Hub after creating an account in the SmartThings App?
Besides being in Australia, there are known conflicts between using a Samsung Account vs a SmartThings Account. To focus on getting the SmartThings Hub portion working, I would personally concentrate on using the SmartThings App and creating a login / Account in it first, etc. …
But I am not familiar enough with the Samsung Connect Home to know what specific problem you are encountering or what solution is best…
With samsung connect home…supposed to use samsung connect app. And in the samsung connect app supposed to be option of switching on the smartthings hub, but in my samsung connect app…no option like that available.
If i use smartthings hub…the samsung connect home does not come witg tge welcome code like smartthing hub does…so cant get it connected through smartthing hub.
That is why i am thinking there is either different samsung connect app for us here in australia…as the hardware itself is from the US…
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
5
There are definitely differences and/or location detection. Since the Hub has Z-Wave, Samsung is legally forbidden to let it run in countries of the wrong frequency.
But, I would attempt
Reset everything.
Disable location services on your phone.
If possible, get the Samsung Connect App from a USA source.
Regardless; create a new Account and say your location is USA. Indeed, you may end up having to use a VPN if the setup process uses IP GeoLocation even though you disabled location services on your phone.
Also remember that the US and UK versions run on different frequencies. All this really means for you is that when you buy z-wave and zigbee devices you MUST get them from the US sources. If you get the UK ones, they will not connect.
Im from South Africa and I had a few of those issues myself.
Do you know if the Samsung connect Home is also illegal in Australia as is the case with the Smart Hub? I have several sensors coming from the States to use with a US platform and they are meant to work with the Smart Hub. I thought by buying the new Connect Home I could bypass this issue. I would appreciate any help or advice.
did you confirm with where’s my ip? I would start there. If you have your “lowest point” of web access on vpn, you should be good.
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
15
If the Hub uses non-Australia permitted Z-Wave frequency, then it would be illegal to operate.
I don’t there are variable frequency Z-Wave chipsets (?) at this time; so this means custom hardware for each Z-Wave Region. Regardless, all RF devices need national certification in most countries to be legally operated.
I’ve been reading a lot into SmartThings and Connect Home as I find it all interesting.
I noticed in a post above it mentioned ZigBee to only get from US or UK (Depending on the Hub). Note that ZigBee is internationally on the same frequency so your ZigBee devices, that are SmartThings approved, will work on any hub.
The Z-Wave is the big issue. In Australia we use two Z-Wave frequencies. 921.4MHz and 919.8MHz. It is ILLEGAL to use any Z-Wave device that uses frequencies other than those in Australia.
Take the American and UK frequencies as an example. The UK (EU Countries) Use 868.4, 868.42 and 869.85. These are very close to the Telstra 3G frequency of 850MHz and as such could potentially interfere with Mobile Networks and as such are illegal to use in Australia.
The US use 908.4, 908.42 and 916MHz. The lower end of that is very close to the Optus Mobile frequency of 900MHz and as such could interfere with Mobile communications and are illegal to use in Australia.
That is aside to any other devices, such as RADAR, that may operate in the bands, which the devices would have no knowledge of.
This is why the Samsung Connect Home will not activate in Australia without pretending to be in the USA.
If you disable the Z-Wave, then you are legal again. There are a stack of Zigbee and WiFi devices that work with SmartThings and Connect.
It is a pity they do not release an Australian version as there is a very strong community of Home Automation enthusiasts here and the Hue lights have really taken off.
If anyone from SmartThings reads this, maybe they can give us an idea when an official Australian launch may take place.
Note: Australian Launch could also include New Zealand, Malaysia, Hong Kong and a few other places that use the same frequencies.
1 Like
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
21
I’m not “from SmartThings”, but I can share my impression (based on Samsung Developer Conference) that Samsung absolutely intends to take SmartThings global… well, at least to everyplace that is a Samsung market.
But the timeline isn’t specified. There’s bits of evidence of “globalization” going on, such as language translation efforts. And the expansion of the concept of the Hub into other products like ADT Panel, NVIDIA Shield, etc., already makes it easier to offer multiple Z-Wave SKUs.
Samsung is playing this as a long-term “no rush” strategy. Even in North America, there’s barely any marketing and retail push. I seriously doubt that sales are growing at any significant rate. One major inflection point can occur once the SmartThings Classic App is deprecated (followed by the deprecation of the “Groovy API”).