Another missing piece on new app, history log is completely garbage and not able to track status precisely. I would see the most recent ones but after a while they disappeared out of nowhere and only thing left is yesterday’s partial log:
By the way, I migrated my not so complicated classic app routines to new app scenes, deleted all the routines in classic app, and… This is what happens :
What I found is that if you click on the 3 dots in the right corner of history, click on hide or unhide, then toggle the check next to other messages. It will repopulate your history and it appears to be complete. This is not a permanent fix. I have to do it each time I look at history on both Android 8 & Android 9 devices.
I guess I get excited too easily and did a silly move thankfully all my new scenes are working in new app. Only thing is my wife’s Google Assistant doesn’t see any scene created in new app…
My problem is it appears I am essentially barred access to the new Samsung developer tools and new documentation because I am a third party. I would have to be a employee or official representative of Xiaomi / Aqara in order to gain access.
So I do not have a clear idea of exactly what changes need to be made to all those DTHs I am maintaining to get them fully working in the new app.
I want to know: what options do I have?
If Samsung is not going to provide full support in the new SmartThings mobile app for community-created DTHs for devices of companies that aren’t interested in approaching Samsung directly, then I don’t want to be the one to make that announcement on the above-linked thread. You or another staff member of SmartThings should do that so users are well-informed to make whatever choices they need to make as a result.
Here is another example where the automation scripting is frustrating. I want a siren to sound for a very short burst when a trigger occurs. So I first add the action Alarm on with Delay this action not set. Next I want to add the action Alarm off, with a Delay of say 5 seconds. But because I already used the Siren device in one action I can’t use it again. I will try making two automations from the same trigger…
Later: That worked However, much neater to have either a) had it in the same automation or b) edit the Zwave Siren handler to allow shorter alarm durations
Scenes in the new V3 app have a lot of the functionality of Routines from the Classic app.
Back before Webcore, we used to change modes in the Classic app by triggering a Routine. Same idea. So while certainly somewhat convoluted, I think it is part of the traditional smartthings official feature way of working with modes.