I, for one, hope that MyNext Manager continues to work, even if Samsung kills the Groovy IDE and creates their own.
I was one of those dinosaurs who had a 1st generation SmartThings Hub, and was told last week that the 1st generation hubs were being phased out in June. Nice to them to do that. Anyway, I took advantage of the Aeotec replacement hub offer, and actually just migrated everything on my old hub to the new one this weekend. Everything, that is, except the NST Manager hooks into my Nest Protects.
I’ve elected to use the native ST/Google Nest hooks into the Thermostat and my 2 Outdoor Cameras, which all seem to work flawlessly with the new hub. However, of course ST didn’t build in support for my 2 Nest Protects. After banging my head against the wall for the last couple of days in trying to get NST Manager to work on the new hub (yeah, I know it hasn’t worked since 2019, but I figured I’d try), I just decided to break down and buy Yves’ application.
The code is almost 100% foolproof. I am not a developer, but I am somewhat familiar with the Groovy IDE, and the only issue I had was copying the cookie code from Chrome Dev Tools into the MNM text. Once I figured that out, though, and published and ran the app, it immediately saw my thermostat and my 2 Protects. I set the refresh interval to 1 minute, and everything worked flawlessly. I have to say that Yves’ code was very well done.
I just hope that the app still continues to work after ST changes their IDE UI. MyNextManager is really a nice solution, and while I really hoped to find a free solution, this wasn’t too expensive to get everything going in my home automation system.