@bseal Thanks! ST_Anything sounds like a good stating point. I would need way more sensors in my gateway. DAN's scenario is an Arduino board with all sensors connected to it so I agree with him that doesn't make sense to support more sensors that ST_Anything does. The scenario with a MySensors gateway is different though. Good news is that looks like I'll just need to write a Device Type (no need for a smart app). I wonder if this device type can be made generic, if there is some way of the gateway to announce how many sensors and which types it has to the device type so it can dinamically build a list of sensors for ST.

@hek Yes, IFTT is a detour from a latency point of view but it's just the first step as I've mentioned. It's just so I have a quick win before I dive to tackle the ST integration (probably with Zibgee). This second phase will probably include not only coding on the Arduino side but also on the ST side. I'll probably need to write a device adapter (what they call a device type) for the gateway and a smart app to integrate that adaptter with other apps and devices.

I've just joined the community and have a Smartthings V2 hub. I'm no gifted engineer or coder (although I do have an engineering and coding background). I've just ordered components to build my first sensors and an Ethernet gateway. My plan is to integrate with ST through IFTTT as a first step as it seems it doesn't require HTTPS. Second step would be to connect to the hub locally. If I go for the LAN route looks like I'll need HTTPS to get oAuth authorization first. I'm not sure NodeMCU can handle that, so I'll probably use a Yun or a Raspberry Pi. I may just go the ZigBee way buying the SmartThings Shield for Arduino ($35).