Batch Update for Routine Devices
Replacing a device is now easier than ever. Previously, you had to update every routine manually when a device was replaced. Now, you can swap an old device with a new one (of the same functionality) across all your routines simultaneously. For example, when you replace a living room bulb with a new one, you can update all routines containing that bulb at once, significantly reducing setup time.
How to use: Go to the Automation tab > Menu (âŻ) > Routine update.
Detailed Routine History
Gain full transparency into your homeâs automation with detailed execution records. You can now review exactly when a routine ran, the specific conditions that triggered it, the actions performed, and the final results. This makes it easier to troubleshoot routines that may not be working as intended. Additionally, long-pressing a routine allows you to view a full week of execution history at once.
How to use: Go to the Menu tab > History > select the â>â button.
Here are some entries that Claude.Ai was able to detect from Crash Log generated by my mobile.
[ATM]AutomationLocalPresetRepository.loadFromDb - com.google.gson.JsonIOException: Interfaces canât be instantiated! Interface name: com.samsung.android.smartthings.automation.data.action.Action
DeviceEphemeralCapabilityStatusResource.subscribeSse - java.lang.NullPointerException: Attempt to invoke virtual method âint java.lang.String.hashCode()â on a null object reference
I currently see that for one of my lights. It is perhaps worth noting that âSmartThingsâ is a hub name in your example.
In the Health Diagnostics the device ID is not a typical ST ID. It is has the format of a UUID but has lots of leading zeroes in it. I have seen it before with another device in the fairly recent past, but not before that.
My network has three TBRs on it. I donât know how you know which is active but all mine are V3 hubs so there shouldnât be anything unknown about any of them as far as SmartThings is concerned.
My thought was that the routing might have been via an inactive TBR over ethernet to the active TBR. I forget what they call that but I know it was enabled on ST relatively recently.
I suppose it could just be the inactive TBR acting as a thread router but I thought it recognised the device when that happened (though I could be thinking of the Zigbee routing which Iâve seen a lot more of).
It appears that âManage Hubsâ has finally been fixed. Thatâs been broken for the best part of four months. Good job I donât use Hub Groups.
I tapped on Map View to see what is going on there. It has been messed around with a bit. It seems you can now specify the size of the room but I couldnât seem to resize the interiors any more. However you could scale them up as a whole, which was a bit weird. The flow was so messed up I just lost interest. I do wish theyâd offer a way to disable it completely. A 292 Mb download without a cancel button is a bit ridiculous.
Good to see some sensible improvements to Routines, not that I normally use them.
The notice mentioned some other crud Iâm not interested in. I with theyâd take all that stuff elsewhere instead of bloating the app with it.
I thought perhaps they might have made Sleep Environment usable by now, but no. It still only recognises one model of T/H sensor, one model of motion sensor, and most bizarrely a single smart plug despite my having many more of the same smart plug also powering lights. Not that Iâm particularly interested.
I could accept that if it didnât claim that it couldnât show the history for a Rule activation because the Routine has been deleted (or so I assume as it got truncated to âdeleteâŚâ). That is quite pathetic.
