SmartThings Community

Moving from SmartThings to HASS, anyone else?

(Ron) #1

Any SmartThings users transitioning to HASS?
I tried over 1 year ago but decided it was too difficult.
I have started trying again and so far it is going much more smoothly.
In fact I have my Fibaro Motion Sensor online on HASS in about 20min. I spent a few days trying to get it to work on Hubitat but couldn’t get it to work. So maybe HASS is the right move.

Anyone interested in sharing the process my Home Assistant community username is “smart” since Ron was already taken. See you there…

(Andrew Caudle) #2

Before you decided on HASS, did you look at Hubitat?

(Ron) #3

Yes, I even mentioned it in my first post. People are loving Hubitat but unfortunately I had a lot of issues with mine. I am still watching them, it seems like a nice platform

That said in about 4hrs effort on HASS I now have the following working
-Hue Lights installed Out of the box
-Apple TV installed Out of the box
-Googe Home Media player and speech capability autodetected
-Foscam camera with 4 lines of config (never got these to work on SmartThings
-Link to Amazon Alexa
-Z-Wave configured with 2 lines and a little shell command line effort
-fibaro motion sensor included 100% configurable in HASS
-ge dimmer switch included, configuration fully supported
-aeotec minimote included

It’s pretty rock solid.

(Eddy) #4

I actually already moved to hassio, i just like to use it just because of the wider variety of device that i am able to integrate.
However i still uses smarthings, especially webcore for rule creation.
From there, i get to trigger devices from my home assistant.

(Ron) #5

Interesting approach. So do you just have virtual devices on SmartThings for your rules that then trigger HASS? Are you integrating with MQTT?

(Eddy) #6

Yep for the most part, so instead of using hassio to control smarthings, i do it the opposite way (smarthings controlling hassio devices)

reason is because i freaking hate the way rules creation are done on home assistant.
Yes i know theres Node red and others but i believe webcore is the easiest to use

I have MQTT setup with smarthings, it works fine but i dont use it alot. Hence why im using webcore instead
I dont have all my smarthing devices on HASS

(Ben Flux) #7

@GGexe, I’m keen to know how you’re using webcore to control HASS devices. I’ve got a device that works with HASS and it won’t work with ST so how do I go about it?

I have the Smartthings mqtt bridge already working and I too prefer the webcore rule builder over Hass automation but can’t see how to make in work in the opposite direction to the norm?

(Bill S.) #8

The ONLY thing that kept me from going 100% HASS was the problems with Zigbee/ZHA. Most of my devices are Zigbee devices and with the issues that kept coming up with the HUSBZB-1, it was just too unreliable for me.

(Bill S.) #9

@benflux HASS has a full API that you can call from webCoRE using standard HTTP GET/POST/PUT requests ( Using that, it’s pretty simple to push device commands to HASS from webCoRE (using the Location.makeWebRequest() method). HASS can also push commands to webCoRE’s http endpoints as well.

In fact, it’s how I used webCoRE to publish MQTT commands (http://localhost:8123/api/services/mqtt/publish)

(Eddy) #10

Yep its actually not that bad
i got a couple of example that might help you out

This is to activate a script in Home assistant

This is for when you want to pass on extra parameters:

Hopefully this helps you.

I wanted to know now is whether or not its possible to pass something like a variable from HA > to webcore global variable
If anyone did it, please let me know

(Bill S.) #11

You can call a piston (along with passing arguments) by using the execute URL (found in Settings>Integrations>Executing Pistons) in webCoRE and using the rest command in HA.

You replace :piston_id: with the piston you want to call and in the piston itself, process the args and set your variables.