BUT… it’ still looks like a rough POC at this point. IMHO, it does not yet look like a robust enough solution to depend upon for home automation.
I’d humbly suggest if people want reliable, fast, local processing for home automation:
if you want Groovy support, buy a Hubitat hub. Most of your existing DTH and SmartApps already work, and run locally on the hub.
if you don’t care about or need Groovy support and don’t mind going the RaspPi route, look into Home Assistant. It’s already got a huge open source following.
Both of the above are already robust and ready for prime time.
Its nice - but… after using NodeRed / HA for a year. Not going back. Webcore was a nice solution while it lasted and it got me where I am today, but It’s now completely unsupportable in ST and I’m not going Hubitat just for WebCoRE. I’d be more likely to hang a Homeassistant instance on that Pi with the SmartThings integration and make it run Node Red just for automation purposes then port the pistons to Node Red.
Yeah - exactly, see previous…
I’m with @jlv - It’ is pretty cool, but no way I’m spinning up a Pi for a potentially neutered ‘maybe’ solution at this point. I’m either all in with my own app that makes calls to the api, or Hubitat if I actually care about groovy or HomeAssistant for pretty much all other reasons. That is - if I’m burning the money for a Pi and zwave / zigbee coordinators, or a hub.
How do we stop devices on boarding to the IDE ? I have 3 Ikea Tradfri LED GU10 bulbs, each time i reset them and re on board them they connect to the stock Smartthings ZLL white colour temperature bulb 5000k
Unless you’ve manually installed the driver from the beta channel, you wait for them to be supported in Edge on the production channel. Or you sit back, relax and let the migration move them for you.
Of course SmartThings could totally change the game if they would just let us implement SmartApps on the hub. All they need to do is make the API available to Lua apps and provide a way to subscribe to device states. Then we could have the same breadth of community-developed, locally running SmartApps, as is being developed now for Edge drivers. But if we can’t have that, then just doing it on your own Pi is the next best thing.
I’ve got an Edge driver I’ll be releasing soon that allows you to monitor the online/offline health status of any SmartThings device. It requires my edgebridge app to be running on an always- on computer on your network (Windows/Linux/Mac).
DM me if you are interested.
EDIT: The subject driver is now available; see this post.
Thank you - when I wrote this post there wasn’t an Edge Driver for the Nano Duo, in fact I wrote to Aeotec support to tell them - because I find it strange that a company selling Aeotec-branded Smartthings hubs but then not ensure compatibility with all their Zwave/Zigbee devices. I like to think that my little complaint helped push them into coming up with an Edge Driver, which I see now is added at the very bottom of the list
Honestly, given the direction that Samsung seems to be going in and kicking us in the teeth on their way, why not just shift to a friendlier platform like HA or Hubitat? They at least seem to care about their user base more than ST. With Hubitat at least groovy is supported and easily ported to.
Well, I’ve been checking my DTH devices every so often to see if they have been migrated to Edge drivers, but I can stop checking my DTH devices now since they changed the wording in the original announcement to ‘after’ 30 September is when the DTH drivers will be automatically migrated.
And they’ve added another one of their Groovy SmartApp besides Smart Lighting to the migration. I hope they add the logic of a few more of their SmartThings SmartApps like the Notification capabilities of their Notify Me When SmartApp (currently need to create an individual Automation notification for each device), and their Left It Open SmartApp (currently need advanced skills using two Automations per device with Virtual Switches as timers running in loops).
I see these Notify Me and Smart Lighting and Left it Open apps, and wonder why on earth Smartthings still have not resolved this after so many years for us in Europe - I have never seen any of these apps working because of some geographic restrictions they have in place.
And I wonder if any of those apps were to be ported over to the new Edge environment whether they will make them accessible to us on this side of the pond.
I have just installed and tested this new driver released by Aeotec for the Nano Duo. The device installed correctly as a dual-component device, so it is slightly better than the DTH which used to occupy 2 slots (of my 200-device limit). So far it seems to be working well albeit with significant delays, but I still need to rebuild the Zwave mesh as I have just excluded and re-included 5 Zwave devices on the same floor and relatively close to each other.
The only problem this driver has is that it shows in the UI as a single tile with one switch, which controls both switches together - but if you go into the detail page you can control each one individually. I personally prefer to see the individual components on the dashboard (though 2-component devices like this one end up using more real estate) - and @philh30 has recently been writing such a driver with such a UI for one different device that I also have, and in my opinion, it looks great and shows the individual detail of the components without having to go into the detail page.
Anyhow - at least it seems to work. so for now, it will do. and of course - thank you!
They mentioned there would be a new Smart lighting plugin to replace the current version. They are going to migrate the current SL rules over to the new version automatically. As far as region blocking goes … unknown
So started to check out IFTTT for Ecobee control today and had forgotten I already had my Blink cameras running through it. Also forgot I have to create applets for both on and off on the virtual switch, so definitely going to be tight in the free account. As suggested I know I could work around with multiple accounts.
The other thing I’m running into is away mode. Currently I use Webcore to set both thermostats to indefinite away when all phones leave the house, but in IFTTT I am finding you can’t set a comfort profile indefinite. Did you find a way around that? I thought I could just set an actual temperature set point instead, and change it as the seasons change, but for several months I have it set to auto so need actually a cooling and warming set point which I don’t think IFTTT can do. Have you run into this?
guess I will have to wait as they don’t reply to my queries here.