What about opening up the STHM APIs to a whitelisted set of trusted partners?
I just use virtual switches to control sthm and the scenes control the switches. No problem
Please add feature to change the name of mobile presence sensor.
You can still do this through the IDE if you want to. What they really need to do it add the option to see the status of the mobile press sensors as a device in the new app.
@blake.arnold is engineering aware that Automation mode preconditions arenât working. For instance l just had the below automation run, even though my location is in âguestâ mode. Very frustrating. The migration was enough of a challenge, and after rebuilding manually my routines as automations not having them work properly is beyond frustrating.
They are aware and working on a fix
I believe historically they are in Korea, but there are some job postings on the SmartThings site for USA based openings.
Good to hear. This is where a public change log / open issues / caveats register would be helpful.
So true⊠So so true.
Im a huge fan of the open bug database om minecraft.net
Ok, so I play a lot of video games⊠Sue meâŠ
I agree. For now I created a Simulated presence sensor device to see it in my device list.
I have a custom DTH for the Whistle pet tracker, and that shows too. It is only mobile presence that is hidden for some reason.
Thanks. I agree with you about showing presence sensor as Device
Does anyone know the answer to this?
Really wish you could change the icons in the New App. I have no idea what device is what using my current naming structure.
The Contact and Motion are obvious (well although the Motion looks like a Contact ) but the other 3 SwitchesâŠ
These devices are paired to Hubitat but mirrored in ST using HubConnect so the icons are messed up.
Classic App:
Before someone suggest to just shorten the name, itâs not that simple. Everyone is trained to use: âName of Roomâ âDevice Nameâ
âDownstairs Bathroomâ âFanâ
âDownstairs Bathroomâ âLightâ
âUpstairs Bathroomâ âDoorâ
âMaster Bathroomâ âMotionâ
We have the same devices in multiple rooms so it just makes sense to name it that way for ease of use using Alexa.
+100
Device naming is INCREDIBLY important when integrating with Voice Assistants⊠Well that or spend literally HOURS renaming stuff in the voice assistant app - only to have it overwritten when someone say - updates the skill⊠Those tiles need a word wrap or SOMETHING. I was going to submit this feature request after some of the hotter issues were fixed, but since you brought it upâŠ
Just a heads-up⊠if you are using both apps, and have STHM in ST (v3), when you got to click the âmigrate this locationâ in ST Classic - it will fail when migrating your SHM. It happened to me. It moved all my Routines, but nothing in SHM. ST Classic told me that I already had STHM set up, so it couldnât migrate until I deleted STHM, and gave me the option to retry again. I did have STHM âinstalledâ in ST v3, but I think it was by default when the app was installed, and I never had anything set up to run in it. I was hesitant to delete STHM (b/c I wasnât sure if the migration tool would actually re-create it from SHM, and I didnât know if I could get STHM back safely/stabley), so I selected the ST Classic Migration Tool option to just delete SHM, and I manually re-created my setup in STHM. At least the migration tool thinks Iâm complete now.
FWIW⊠I debated on a soft migration vs using the migration bar/link, and opted for the latter⊠hoping that Iâd be âchecked off the listâ when they push that button for everyone in a month or two, and it wouldnât screw up the work Iâm doing now to get everything running as it did before. Who knows if I chose wisely or not.
If they are custom DTH, define ocfDeviceType
in the metadata:
FYR, OCF is doing to be depricated, VIDâs is the way to go.
They are still processing PRs with them getting updated, so it must not be any time soon.