HI Deano, I see the error which is a null pointer exception which is almost certainly the cause. Note: You cannot consider the logging output to be in sequential order, just a Smartthings quirk.
I was gone for a few months and reading up on the new Smartthings app and found out that when they switch to the new app (and shutdown classic) the only supported communications will Zigbee and Zwave. That means any and all HTTP connected devices will no longer be supported. So there will be no integration
Because of this discouraging situation I don’t see any future in finishing this device handler for Smartthings (it was only a Beta), only for it to become redundant later this year.
So I’m going to put my energy into finding a different platform that supports MQTT.
They don’t have a specific date yet but there is a lot of messaging regarding the migration in this thread. Get ready to make the switch!
Even if it is a year out it still means developing for Classic is a dead end.
I bought a Hubitat Elevation because of its similarity to the SmartThings hub and local execution. I haven’t yet switched over to it because it doesn’t yet have Github integration for DTH & SmartApp updates. Maybe check it out.
Without HTTP I cannot do anything. The fact that they are going to orphan 50% of my devices when Classic goes away and can’t even tell me if it will ever be supported has caused me to abandon SmartThings.
Their communication has been terrible on this and almost everything else.
No, I did not. Mainly because it does not support the UI mechanism on the same way as SmartThings. However, if you look on the Hubitat community website you will find a great Tasmota solution that works with a broad range of Tasmota devices and been very solid.