@nayelyz any update on this?
The team didn’t find any 500 errors in the logs so you will have to recreate the scenario directly on your side because as this tool is from @TAustin we cannot see what happens on that side, for example, in which request the error occurred to see which device was involved and if it’s the same every time. Or, he can add more logging to his server and see what happens when it makes the call.
They also mentioned that using the call mentioned by @orangebucket would be more efficient than a separate call for each device.
So using an undocumented, 6 year old API is the recommendation. Got it.
I have two devices I have a feeling may be a problem. I’ll report back shortly.
I had two Minimotes still on a DTH but the DTH had been removed. I’ve excluded the two devices and now I only get one 500 error when filtering to offline. I’ll find the third device.
I’m fairly sure this last problem device is a weather device also still on a DTH. Now, the DTH for this is still in place (I think) and this device is updating (I’m seeing updates in SharpTools) but it cannot be selected in the SmartThings app (I had the same issue with those two Minimotes).
I will kill this weather device soon as it’s obviously going away but for now, as it’s updating I am going to wait. But I do believe that’s the last device throwing that 500 error.
I finally deleted this legacy weather device and it has not stopped the remaining 500 error when I filter for offline devices.
However … I did just find the remaining culprit.
I have three Life360 devices hanging around. Useless now I know but I’ve kept them there to remind me to find an alternative. Anyway, just one of the three was showing the same issue I had noted above with the Minimotes - I could not open it in the ST app. The difference between that one and the other two Life360 devices is that at some point it had had a parent of the hub set and the others did not. Deleting that one device has cleared up the 500 error.
Glad you finally tracked it down.
For future reference for anyone following this, you can use the API Browser+ to display an individual device’s status (Devices->Devices>Status button) and it also shows the online/offline status for the individual device. With your number of devices, it wasn’t a very practical way to find it, but is IS an option…