I’m asking because i need to debug my “MiLight Manager” as somehow since a recent update it’s not working anymore. So i need to know the packets smartthings sends to that thing (http calls) which used to show up nicely in the live logging.
I bought Smartthings to be in control of custom apps and have the ability to create one myself if i’d want to. The integration of other radios helps massively!
Now i bought it before samsung made it horrible.
Now i have to go on the research route again to find a solution that can do my milight lights + integrate with google home. While this is possible with Home Assistant, it’s a huge hassle to get it working… And that is even without the hassle of usb dongles for other radios (zigbee most notable).
Hence a “programmable hub” with integration in Google home out of the box was the most convenient and easiest way.
Yep, I agree. Replicating some of my SmartApps with Routines has been challenging. Doable, but challenging, especially since there are also limits on how many you can have (automations, devices, etc.).
I’ll likely stay with ST for several reasons, but I will miss the convenience of quickly developing SmartApps.
I’ll only keep the smartthings crap because another samsung device requires it to be configured in my house. Other then that i have no need for it anymore. Or rather, they killed my only other immediate need for it.
SmartThings was always cloud-based, hence our vulnerability when the company decides to change the cloud services.
For what you’re describing, your best bet will probably be hubitat or Homeseer, with Hubitat being the more familiar development environment. But with either you are insulated from corporate changes if you choose to keep what you had. Home Assistant is always possible as well, but is more work to run.
200 total of all devices regardless of protocol including virtual devices, per location (not per hub). It appears to mostly be a UI limit imposed by the app as it also affects users who do not have a hub.
The limit has been in place for about two years, but is enforced differently in different places so it’s kind of weird.
Correct, and anything over than that causes your hub to disconnect/reconnect due to hub resource issues. How do I know? I have an open incident on that. Hub events also show this issue, but not in a lot of detail but you can see a pattern: