Great! Thank you!
1 Like
I still have custom rules in the old SHM to let me know if a door was left open for x minutes. When I migrated to the new app, there wasnât a way to do that in the new app. Has that changed?
4 Likes
Submitted form. Iâm having a really hard time understanding your logic at this pointâŚ
You are taking the self-proclaimed LARGEST USER BASE INSTALLED APP, Echo Speaks, and shutting it down without letting the dev know? Perhaps get your devs and him talking to have a PARITY replacement in the new app. Iâm talking Echo devices showing in ST when added to my account, full media control (play/pause/start/stop/volume, etc.), and incorporate into automations as an output device.
How many people are going to self-host this? Iâm guessing that about 5% of the user base actually have something on 24/7 in their home that could actually host this, and no one is going to want to buy more hardware for thisâŚ
I want to replicate my WebCore morning install where I ramp a set of lights, set Volume of echo dot, turn on a specific playlist, play for 900 seconds, then stop.
At a minimum.
2 Likes
I think samsung wants everyone to use Bixby for voice capabilities but the problem is Bixby is.nit available as of yetâŚwell in s. Korea I think. If thatâs the case then samsung needs to get the dam product out for sale. Iâve always said itâŚsamsung makes great hardware but when it comes to softwareâŚwell I think everyone knows the answer.
This is a big part of why weâre making all of these changes.
Right now 70% of our incidents are related to our legacy architecture.
We spend a ton of resources on keeping the old way of doing things going when we could put those resources toward building cool new stuff and give everyone a more stable, consistent experience in the process.
12 Likes
This doesnât have anything to do with BIxby. It has to do with keeping the platform stable and costing Samsung $. SmartThings hosts all Groovy SmartApps in their cloud, which they have to pay for. SmartThings has a lot of cloud computing AWS resources, but there is always a limit. If all those resources are used up by a large community smart app, they will run out of resources for other things to run properly. Iâd guess some of the recent outages are due to this.
6 Likes
To set the record straight, the install base on this smartapp is fairly small, but it generates the largest absolute load on our architecture. Thatâs why weâre doing this. Itâs enormously resource intensive on the entire platform for the benefit of a small group of users.
5 Likes
Just about everything is in the cloud. I hate the cloud. Personally. Yes I know platform issues equal $$$% but you would think they would have worked with Anthony to try & have a basic echo speaks app instead of pulling the rug out from under him.
3 Likes
To set the record straightâŚwhat is the userbase size of echo speaks???
That changes a lot of my perspective from the outside, but not my requests. Thanks for clarifying.
1 Like
I hope your right, support finally got back with me to answers to my original question. This is their response to custom device handlers.
â Question-1 If I have devices that use custom device handlers, and they work in the new app currently, will they continue to work after migration?
Ans: Customer device handlers are not supported in the new app.â
1 Like
Hereâs my most recent experience with the New App. About 20 second from open to display power in Classic. Double that time in the New App. Same StepsâŚHow is that possibly âfasterâ?..
7 Likes
Tagging @blake.arnold
Yes, although given the specific nature of certain issues lately, Iâd have stuffed some socks in the end of the trumpets before fanfaring the changes to device health. It was at best unfortunate timing âŚ
2 Likes
While they did add delays to actions in automations, you can, for example, lock a door after 10 minutes if left unlocked but donât believe they fixed it to where notifications are sent after 10 minutes yet.
3 Likes
I just tried the migration tool as instructed by the banner in the Classic app. I have a pretty basic setup. It crapped out. Android 9 (LG V35).
About a second into the migration I am now on a screen that is greyed out and unresponsive with a blue spinner , saying my migration did not complete - some of your features failed to migrate, please apply recommended solutions flagged for you back in the classic app".
Well sure, Iâll do that, except the app is hung. If I kill the app and re-try it does exactly the same thing.
So I reboot and re-run the app. It offers (as before) to âMigrate this location nowâ. Which then appears to get further - it says it migrated 6 routines, smart home monitor, and smart locks. Successful!
Except the screen is again greyed out, blue spinner, canât hit any of the buttons in the app (such as âGet the new SmartThingsâ) until I kill the app and re-rung it (no reboot needed this time, so thatâs an improvement).
The migration tool was tested, right?
Now on to see whether anything still works (via the new app).
Am I going to get the ability to enable Smart Home Monitor from a scene again? My migration kept failing because of that, so I had to remove it from the âIâm Backâ and âGoodbyeâ actions for the migration to work.
Really loved that feature!!!
1 Like
You can daisychain it.
Have the scene turn on a virtual switch.
Have that switch coming on change the STHM mode in an automation.
I use power allowance to have that kind of virtual switch turn itself off again so itâs ready for the next time, but there are also other ways to handle that.
So itâs more work to set up but you can get the same end result.
How come I donât have an âAlexaâ option under âVoice Assistantsâ? I only see Bixby and Google. Considering we have a whole host of Echoes around the house that ainât gonna flyâŚ
Is the new integration not live yet or is it somehow region locked meaning I cannot connect to my US Echo account from EU?!
When Echo Speaks is removed does it also remove functionality with webCoRE?