Hi. I still have the old code ( before they forced us to have a Google account ) from the other Nest smart app , this obviously isn’t working within the new v3 ST app. I can still see the smart app within ST and I can actually control it through another smart app called SmartRules but I like the idea of this app. What do I have to do? Completely remove anything to do with that within ST app?
Hi, you’d need to contribute to the MyNextManager V3 at my store.
The code has been rewritten to use the Nest Web APIs (less throttling, more features exposed) and I’ve revamped the UI to follow the ST standards & custom capabilities.
In order to use the new code, I’d recommend creating the new devices with MyNextManagerV3, substitute the old for the new devices in all your automations & scenes (including SmartRules) , and then, after remove the old devices
I have a problem downloading the Version 3 code. I’ve used both my original Sellfy download link (from Summer 2020) and when that didn’t work I re-purchased, but with the same result.
The Sellfy link looks fine on its face, but when I open the Zip it includes files labelled as V2.
To note, when I look inside the files themselves, MyNextTstatV2 and MyNextAlarmV2 include comments that they are Version 3 code, but MyNextManagerV2 and MyNextSensor V2 include comments that they are Version 2 code.
FYI: I’m in the USA if that is useful for troubleshooting the Sellfy distribution:
Don’t worry: you have the latest versions of the smartapps & DTHs. The name of the smartapp or the DTHs is different from the version numbers. For backward compatibility (for the instantiation process), the name of the smartapps or DTHs stays the same, but not the version in the header.
The version number of any of my smartapps is located in the header under a global method called ‘get_APP_VERSION’ in the header, and it appears in the 1st page when you execute the smartapp.
private def get_APP_VERSION() {
return “3.3.1”
}
The version number of all DTH (Device Type Handlers) is also located in the header as indicated in your image.
Hi @mattrix, if you mean by google home integration and TTS that your Nest tstat would be integrated to Google Home for automation purposes & voice integration through Google Home Assistant, then the answer is yes.
Greetings, I just installed your handler yesterday and it went smoothly without a hitch. Great app!
One thing I noticed is in the IDE, everything seems to be doubled, which seems odd.
Hi, this seems to be due to the ST custom capabilities that sometimes duplicate some thermostat capabilities… This is a ST platform issue, and there is nothing I can do on my side of things (for the moment) to fix this.
One other thing I’m wondering about. When I look at “MOTION” for my Protects, I notice anywhere from 9min to 13min goes by before it shows inactive. Is there an adjustment I can do so it’s only 1 min?
The fact your handler does motion is a huge bonus.
Hi, the only thing you have control over is the polling interval set in MyNextManager (last page). You can set it up to a 1-minute polling if you want faster responses from the APIs.
However, you’re still dependent on the Nest Cloud and there may be some other delays involved…
Yes what you need to do is plug a usb back there and charge the thermostat as time goes on you will see it wont lite or quick wake cause the battery is low ive only jump startee on the beging cause thats what nest told me
Just want to inform my contributors and all Nest users that a new version of MyNextTstat(v3.2) can be downloaded at my e-commerce solution provider (sellfy) using the original download link.
All you need to do is to copy &paste the new code over the existing one for the DTH (Device Handler Type)
Prior to the code upload, you’d just need to save the tokens info and restore it after the copy & paste.
You’d probably need to refresh the Samsung connect app’s cache in order to see the UI changes for the Next devices since V3. There are some instructions to do so in the release notes.
Since V3 of MyNextDevices, the new UI presentation adds the following commands for controlling your HVAC:
setTargetHumidity: to control your humidity inside your home via your dehumidifier/humidifier connected to Nest
Nest Home or Away: to set your Nest structure to Home or Away.
You can also call the following custom commands for more control over your Nest Tstat. MyNextTstat (v3.2) introduces new dual fuel commands for dualFuel/alt/emergency heating.
setThermostatFanSchedule: to create fan schedules at your tstat
setThermostatFanTimer: to set the fan timer in minute
setHotWaterBoost: to set a boiler’s hotWaterBoost timer in minutes (Europe)
setDualFuelBreakpointTemp: if you have dualFuel/alt/emergency heating, you can set the breakpoint temperature for switching to dualFuel/alt/emergency heating
setDualFuelBreakpointMode: You can set the following mode for alt/emergency/dual heating: “DUALFUEL_BREAKPOINT_ALWAYS_ALT” or “DUALFUEL_BREAKPOINT_ALWAYS_PRIMARY”. This allows finer control of your dualFuel/alt/emergency heating.