Where should error reports be made - here, on Github, or elsewhere?
After updating the Device Handler & SmartApp 5.3.0 beta code over my perfectly working existing install, I tried the web tile view feature for my thermostat, got the error {“error”:true,“type”:“SmartAppException”,“message”:“Not Found”} in my phone’s browser, and then when I went back to the SmartApp to turn on logging to be more helpful in reporting this got “unable to save settings” messages and now can’t access the NST Manager SmartApp at all (though viewing my thermostat in My Home tab still works and it displays the Device Info, etc. tiles fine there.)
Whatever you do, don’t try and uninstall or delete anything until you here back from @tonesto7.
If you can’t wait, I would revert your repository back to the master branch and update the SmartApps and Device Handlers back to 5.23. That should put you back exactly where you were before updating all the code to the Beta version.
And store any logs you did retrieve successfully from Live Logging so they can be sent later.
I am going to update to the 5.3 version tonight to see what my results are.
Edit: Can you provide a screenshot from IDE of the SmartApps and Device Handlers? If you updated thru the Repository, it’s possible that your Device Handlers (even when you select Publish), might be in Edited Mode (Magnifying glass) and your ST app is still reflecting previous version. This may not be your issue, but want to rule it out.
I took a brief look in Live Logging and I’m guessing it records nothing because it’s an external call to present data in a browser. I haven’t turned on logging from within NST Manager as Ryan did just so it doesn’t break my install.
I also noticed that when I open NST Manager for the first time, it shows all the previous versions on the first page and then after pressing Save, it then shows the v5.3 page. I’m sure this has something to do with being beta and the version notes still needing to be updated, but I thought I would mention anyway:
I will leave things on v5.3 if you want me to perform any tests later. All other functionality appears to be ok, outside of trying to turn logging on within NST Manager as Ryan did above that resulted in NST Manager being hung up.
I was playing around with logging to see if I could reproduce his error. I couldn’t. However, I enabled the web diagnostics logging and from the Diagnostics page I can access all the Device Web Tiles just fine. So I just went back into Modify Devices and selected the Web Device Tiles from there and they no longer receive the error message in the browser window. I have done nothing since my last post after updating all code.
Yes, I updated all of the device handlers in addition to the smart app, and double checked that all the code was v5.3.0 before opening the SmartApp on my iPhone.
I didn’t previously have web diagnostics turned on, and after getting the browser error on trying to view the Thermostat Device Web Tile, the first thing I did was to turn on web diagnostics. That didn’t give me an error, but rather turning on logging in IDE was what started the red bar notification error appearing at the top of the iPhone screen. After backing out to the main SmartApps tab of the ST app, I wasn’t able to go back into the NST Manager SmartApp.
I have to admit that although I had set up NST Manager as linked to the GitHub repository, when I added the nest-manager (beta) repository in settings and then changed to the beta repository in the properties for the smart app / device handlers, I could not get the new beta version to list in Update from Repo. So I just manually copied the beta code for everything. I think that ma just be an issue when switching from the normal repository to the beta, because right now I checked Update from Repo and I can there’s an update from Anthony (on the 5.3.0 beta), which has today’s date (when I click the magnifying glass to compare versions.)
Not having access to the SmartApp is fine right now; viewing the device in the ST iPhone App works fine, and the automations are still working (I had to go home at lunchtime and home/away modes worked fine.) So I’ll just sit tight until I hear back whether it’s better to roll back to the release version code or try updating the beta code.
If you just modify your existing repository from master to beta and back to master, then you don’t have to worry about updating each of the SmartApps or device handlers manually to reflect the repository. Much simpler this way. That’s what I did. Yes when adding the beta repository and already having the existing master repository I experienced the same thing. That is why I just modified the existing repo to beta and updated and that works perfect.
Actually that’s what I did. In IDE / My SmartApps → Settings, I added the nest-manager/beta GitHub branch. Then in the App Settings → Source Code Options for the already installed SmartApp and in the Device Properties for the already installed Device Handlers, I changed from nest-manager (master) to nest-manager (beta):
But even after that and then saving the code and publishing again, doing an Update from Repo for nest-manager (beta) didn’t list anything as updated in GitHub. So when I manually copied the code from the beta repo it was copied over my existing install.
Maybe I should have replaced “master” with “beta” instead of adding nest-manager/beta in Settings?
I’m hoping someone can solve this mystery for me: I have this installed, and it seems to be working alright, reporting the temp on things tab in Android app, but I can’t go into the thermostat and see all the settings. The presence and weather work fine and I can tap on them. But the thermostat just shows endless thinking icon. This doesn’t happen in iOS, as I can readily see all settings in thermostat. Is this a known issue if so, is there a fix?
Known issue. Posted about 100x in this thread alone
Issue with HTML being displayed on Android after the first viewing.
Big giant paragraph in the last 3 releases of NST Manager when you open a device in Things for the first time stating Android Issue in big letters.
The latest Beta release gives you access to this data via web browser from within NST Manager, instead of viewing the HTML Content in the device itself.
For Android, when you open the Device under things, simply swipe down on your screen and the content that can be displayed for the device will show at the top. To see the HTML data on tour Android, goto Settings/Apps/SmartThings/Clear Cache/Force Stop App. Go back into ST mobile app, open a device (TStat) and swipe down. You will see ALL data about the Thermostat, including the paragraph about Android and the HTML Content. After you exit things for that device, you will no longer see the content until you Force close the app again.
The fix is to either install the new beta version (you need to be able to know how to update repository to beta and update all code on your own), or to wait until the Beta is released into Production. Then you can access the HTML Content and graphs and extra goodies from within the NST Manager app where the urls can be used on their own.
question on automations, I use NST manager to change the modes depending on the home states but i have just decided to using webcore if im 3 miles from home and its cold out to set my status to home (so that it starts to warms up the house). So the plan was to remove the away change from NST manager and just have the home modes tigering it but you cant do this. so the question is does it only fire when the mode changes or if i change the mode to nest home wile its away will the manager change it back?
So, I reverted my existing install back to the 5.2.3 code, and the SmartApp is still borked, and I can’t open it. I’m not sure how helpful the diagnostic logs are, because although it’s turned on and showing logs, almost every entry is cut off with “[TRUNCATED].”
Partial NST Diagnostics log when I try to open the 5.2.3 SmartApp:
You have a leading or trailing space in the oauth call back field in Nest Developer. Please provide a screenshot of the overview page from Nest Developer. Do not include the bottom section that contains your product id or secret.
When you copy/pasted the product id and secret into clientID and clientSecret, you have a leading or trailing space in there.
