Support for 433 MHz devices?

(N0ir) #1

I am thinking about making the switch from a Vera Lite to SmartThings (when it is avaliable in Sweden…) but was wondering if there is any way to also support 433 MHz devices?

I currently have a RFXtrx433 USB 433.92MHz Transceiver ( connected to my Vera and it makes it possible to use a wide array of cheap and avaliable sensors and switches in addition to Z-Wave. I also have a lot of built-in light switches and dimmers I do not want to replace.

The RFXtrx433 have also been ported to a lot of other smart home-systems and I hoped maybe the SmartThings also could use it? Any other way?

Support for 433/315 MHz Wireless Door & Window Sensors
(Duncan) #2

No, sorry. We currently don’t have any plans in progress to add support for that. It might be easy to make a bridge with Arduino or Raspberry Pi, though.

(Patrik) #3

+1 on support for 433MHz devices. I have the exact same setup and also thinking of switching.

How hard would it be to make a bridge for someone that thinking of choosing SmartThings for its ease of use?

(Barry Murphy) #4

Did you end up building a bridge to control your 433mhz devices?

( co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #5

A NinjaBlock is a possible option. They are out of business, but trying to keep their Cloud up for Cloud-Cloud integration, and it is ooen source.

The specs are also published to assemble your own.


+1 1 on support for 433MHz devices.

Plz add the support or at least enable connection to RFXtrx433 USB

(Dan) #7

I have added support for 433MHz devices via my ST_Anything project… Details can be found at

(Todd Wackford) #8

Here’s some cool stuff for the hackers in the community:

(hakem) #9

On this topic, I have a fundamental conceptual existential question :slight_smile:

I understand z-wave / zigbee bring lot of advantages in an open architecture smarthome open standard. But, price of a smoke detector or any other basic sensors such as :

Smoke detector 433 MHZ = 4 USD , z-wave or zigbee = minimum 29 USD
Door sensor 433 MHZ = 4 USD , z-wave or zigbee = minimum 19 USD

I understant that it is worth inveting in z-wave devices. However, if their functionality is classical and basic such as door sensing/ smoke . What would be driver to invest 5 times the price in z-wave and not use 433 MHZ. For a larage building, budget is easily 5 times as high.

I know you guys are pationate and also very smart, kindly enlighten me on reason to go with z-wave despite high price of its sensor

(Geko) #10

Z-Wave uses more advanced protocol than simple 433Mhz sensors. In a nutshell, it’s more secure and more robust. Does in justify higher cost? It depends on your specific situation and requirements.

(supa) #11

Cheap solution here.
It uses any android device + buying a $30 RF/IR transmitter.


I think the Wink Hub 2 also does 433. Am I allowed to say that here? :stuck_out_tongue:

(Geko) #13

There are many different protocols that use 433 MHz frequency band. Wink only supports two specific protocols - Kidde and Lurton. They are not the same as simple on/off RF switches that Broadlink is meant for.

(Fernando) #14

Hi! @n0ir, where you able to workaround this?

(Erik Karlsson) #15

+1 on this.
If you’re in Sweden (or rest of Europe I think also) there is another hub with 433, animus home.

@geko, yes z-wave is more robust but sometimes you’re just looking for cheaper alternatives to play around with

(Joylove) #16

I’d upgrade my Smartthings Hub for native 433MHz support. The RM2+Android bridge is unreliable.

(lehighkid) #17

@ogiewon I am attempting to replicate exactly what you have built out specifically for controlling etekcity sockets via 433mhz. That said, I have pulled your project into but it is throwing errors about secrets.h missing which makes sense. Would it be possible for you to drop the sensitive values and post that file with the variables so I can compile?

(Dan) #18

I think you’re using another user’s code, not mine. I never included a secrets.h file in any of my sketches. If you look at my ST_Anything example sketches, you’ll see plenty of examples of what those values should be.

Is this the post you’re getting the source code from by any chance? If so, you may want to ask @perivar for a sanitized copy of secrets.h. Or, just replace all of necessary constants with values.

(lehighkid) #19

@ogiewon sorry - I had multiple threads open. I pulled a fork from this thread/post: It appears there is a secrets.h file that stores the variables for the connection details for the network and hub. I was attempting to keep the values separate instead of updating the main.ino file but not sure of the data types for each variable - for instance:

I’ll look through the other examples… Apologies for the confusion.

(Per Ivar Nerseth) #20

Hi, I added a secrets.h file so passwords etc isn’t published on github when I publish the source. It only contains:

#define WIFI_SSID “**"

#define DEVICE_IP_ADDRESS { 192, 168, 0, 200 }
#define ROUTER_GATEWAY { 192, 168, 0, 1 }
#define LAN_SUBNET { 255, 255, 255, 0 }
#define DNS_SERVER { 192, 168, 0, 1 }
#define SERVER_PORT 8090
#define HUB_IP_ADDRESS { 192, 168, 0, 50 }
#define HUB_PORT 39500