@daven @IcarusR @tonydt1g3r
It is clearly due to SmartThings cloud modifications.
Below is is the email notification I received on April 4th :
SmartThings Hub 2015 (v2) and 2018 (v3) Firmware Update
Maintenance complete
Firmware version 30.3 has been released to all Samsung SmartThings 2018 and 2015 model Hubs. Please contact us via support.smartthings.com if you have any questions.
Time posted
May 4, 20:28 EDT
Components Affected
Americas - Hubs, Devices, and Automations, Europe, Middle East, and Africa - Hubs, Devices, and Automations, Asia Pacific - Hubs, Devices, and Automations
What I can contribute to this debate is that curiously (for once !), my dozen of FGK-101 are STILL WORKING
They are all :
- pre-ZW5 FGK-101
- running pre-ZW5 custom handler : JJ’s Fibaro FGK-101 Handler v0.9.5.4
- all my Hubs are v1 Hubs (2014), which were not (supposed… to be) updated on April 4th
- located in France
=> Please confirm that you all have v2 or v3 Hubs.
Since I do not have a v2 or v3 Hub, I will not be able to help much, although there is clearly something in my custom handler to which the latest hub updates are allergic.
Usually, I find incompatibilities running “live logging” after a reload of my custom handler.
If somebody among you knows how to do that, I may try to work with him to isolate the problematic code.
Unfortunately, SmartThings support will be completely useless , as they have been since they decided “custom handlers” were anathema (and that after SmartThings promoting back in 2014/2015 these handlers as one more proof of SmartThings “open” solution superiority… ) .
Once we have a better idea from where comes this new incompatibility, we may try to post to the developers forum, but they will not help until we have more or less isolated the problem line(s).
Sorry I cannot help more, it would a nice change from corona-virus worries…