I have created a gateway transport for the SmartThings hub. It works for me but it's definitely a work in progress. There are two pieces to this:

• The MySensors gateway transport for SmartThings here.
• The SmartThings gateway device handler located here.

This is an Ethernet gateway transport that is designed to run on a Raspberry Pi 3 gateway. I have no plans right now to adapt to other platforms but feel free to contribute and add that support for other gateway devices.

SmartThings has an API that is called via an http POST method. Right now this is a one way transport and that's from MySensors to SmartThings. It doesn't handle an http request from SmartThings to the MySensors gateway. I have gotten http requests to work from SmartThings to an esp8266 and an arduino with a W5100 though, so I know it can be done. You have to host a webserver and I think it's not working on the pi because the ethernetclient.cpp/ethernetserver.cpp is custom for MySensors on linux.

You also have to install a SmartThings device handler for the MySensors gateway on SmartThings. The above repo contains the device handler and an example motion sensor device handler.

I learned a ton about the way that MySensors is working and also the way that SmartThings works. I'm happy to answer questions and share any of that knowledge as I'm able to.

@alex28 I think these are fair criticisms. I've spent a ton of time with mysensors and have backed away because of some of these same things. I love the idea and appreciate the effort that's went into the platform. You have to tinker a lot and you spend more time figuring out problems with the platform than you do actually building sensors. Spending time troubleshooting only to find out others have spent time on the same thing or info is outdated takes the fun out of the process for me.

However, having said that I keep coming back because I love the idea of this platform. Lots of really great ideas and great makers contributing here.

@mfalkvidd nrf24, 4.7uf, and it's powered at 3.3v, I put a meter on it. I'm using the MySensors board by sunberg.

I'll take a look at the guide, thanks.

@zboblamont Moved things around and that didn't work. I soldered up a new newbie pcb thinking maybe it was my solder job and tried that and I get the same result. I've swapped nrf24 radios out and still the same result.

I think I found the problem. I've been using an ESP32 for the gateway and hadn't had problems. For whatever reason I added this new node and I had the problems as described. I decided to try swapping the ESP32 out with an ESP8266 and things started working. I guess I'll stay with ESP8266 on the gateway.

I went to the last link you provided and looked where it makes the connection. I've tried to find the description of signature of the call when it makes the connection and I don't see a definition for the signature being used below. The signature I've used and seen is using the first two parameters, but what are the 3rd and 4th parameters?

(void)WiFi.begin(MY_WIFI_SSID, MY_WIFI_PASSWORD, 0, MY_WIFI_BSSID);

@mfalkvidd Thank you

@TRS-80 My point was you didn't add anything constructive to thread. You could have said hey you might have a radio propagation issue and here's how you could troubleshoot it. That's a helpful comment. What's not helpful is sitting on the sidelines until the problem was solved and then making a comment like: You didn't solve it you just got lucky. I did pinpoint the problem to be the gateway hardware. Could I have spent hours to figure out exactly what it was in the ESP32 that was failing? Possibly, but I have parts on hand, they are cheap, and I just swapped it out and it eliminated the issue. So my approach wasn't lucky it was measured and methodical. I tried the suggestions given in the thread then I replaced one radio and tested with a known working radio. I did the same with the other radio and so on. No coincidence there that I was able to isolate where the issue was. And your comment was not based on any evidence it was just a feeling you had and you offered no solutions.

I'm not trying to cause an issue here and I'm trying to be as polite as possible to what I felt was a very 'troll like' comment. Be helpful and supportive in your replies. I came asking for help and everyone else on the thread gave some things to try and added value to the conversation. Be the same way as I'm sure you have value to add.

Is the NodeMCU an ESP8266 or an ESP32? I've had trouble with the ESP32 and getting the communication to work but have no idea why. I did what you did and swapped out the NRF24's and it didn't help. Then I swapped out the microcontrollers and that's when I swapped the ESP32 (gateway in my case) with an ESP8266 and everything worked fine.

Sometimes what I'll do to troubleshoot is replace the gateway with an UNO just to eliminate issues and go with a known working piece of hardware. Sounds like you may have done some of that already. You could try moving them a little farther apart and see if that works.

What does the message, GWT:TIN:CONNECTING..., mean? Connecting to what? Sometimes mine will just repeat over and over and I have to reset it one or more times until it connects to whatever it is it's connecting to. Assuming it's my wifi it's trying to connect to? My gateway is a Node MCU ESP8266.

@TRS-80 I have no idea what you're talking about. I changed out pieces one at a time until I found the problem. That's not called luck that's called troubleshooting. Please provide constructive comments not sarcastic non-sense.

I think I found the problem. I've been using an ESP32 for the gateway and hadn't had problems. For whatever reason I added this new node and I had the problems as described. I decided to try swapping the ESP32 out with an ESP8266 and things started working. I guess I'll stay with ESP8266 on the gateway.

@zboblamont Moved things around and that didn't work. I soldered up a new newbie pcb thinking maybe it was my solder job and tried that and I get the same result. I've swapped nrf24 radios out and still the same result.

@mfalkvidd It's powered from an outlet and it reads 3.3v when I put my meter on it, I don't believe this is the problem.

@zboblamont Thank you. I will try and report back.