Just remove them from any apps that they are being used with, and delete them from the IDE
I’m currently staging an update for the apps and devices. I would wait till after that happens today so you know you are using the latest code.
perfect - thanks
If it makes you feel better I had to do that too. I decided yesterday that I wanted to install fresh. Not sure why sometimes there is a cross dependency.
I always have a good experience with support. They get a bad rap sometimes for taking too long, but I don’t pay a monthly subscription so I can live with a little delay.
@desertblade that does make me feal better. I wanted to start fresh and setup nest manager from the repository instead of cut and pasting it into the IDE. Thought i did something stupid. I havent reinstalled it yet.
Thanks.
Wait for the update later today. I want to blame ST with all the changes they have been doing, but there could be situations where the app could get stuck this way. So far it has only happened a few times and in every case support fixed it.
@desertblade I will wait. I dont want to have to contact support again.
Thanks.
UPDATES [RELEASED]
[Updated]: Manager App v2.0.3
- Removed: ShowAwayAsAuto function has been removed from the SmartApp and Device Handler.
- Added: Support for Child App Notifications
[Updated]: Automations App v1.1.0
- Fixed: Contacts and Remote Temps not trigger Thermostat actions
-
Fixed: Legible logs entries in the IDE when automation events occur. This helps troubleshoot
- Added: Custom Notification Recipients of each individual Automation. (If their is a demand I will add custom quiet time settings as well)
- Updates: 100’s of UI tweaks
- Added: Use Switches to trigger Remote Sensor Rule evaluations.
- Updated: This was a major refactor of the app to allow better flow and consistency.
It is Highly recommended that you remove ANY existing automation’s before updating the code. I apologize for this inconvenience but this was a necessary change
I made every effort to test this the best I can but there is bound to be some residual bugs.
PLEASE Report any new issues using the github issues page. It is very difficult to perform troubleshooting via this thread post
[Updated]: Thermostat v2.0.2
- Removed: ShowAwayAsAuto feature because it caused to much confusion.
[Updated]: Presence v2.0.1
- Updated: Modified the way the data is sent from the Manager App to the presence device.
[Updated]: Weather v1.1.0
- Added: (Thanks to @desertblade) The weather device now Shows Forecast for the next 3 days as well as the local alerts.
- Added: (Thanks @E_sch) Now provides all of the same attributes as Smart Weather Tile for existing app compatibility.
Trying to use he automations to turn off my thermostat when any of my doors with open/close sensors are open. The system defaults the delay time to 300 and it says it’s in minutes. From my observations this time isn’t in minutes. Is this a typo and it’s actually being measured in seconds?
the selector shows options in minutes but the values returned for scheduling are in seconds.
@tonesto7. I have some good and bad news for you…
-
My contact sensor automation is now working. The push notification is NOT working however.
-
I get the below error when trying to install an automation based on external temperature:
method: script14617920985811583733466.getExtTmpWeatherRefreshVal() is applicable for argument types: () values: [] @ line 204
Will add to github bugs later on when I have time.
Sorry about that one I just pushed out the fix
Hmm, same issue. It saves the automation as Nest Automations but when I go to rename the automation, I get the “Failed to Save Page: namePage” error. This time, it doesn’t throw that error in IDE though.
i’m testing now
That’s a new one. Are you seeing anything in the logs
@tonesto7 I have contact and mode automation configured. Testing now the mode automation. Changing the ST Mideast to away, does not change the Nest mode tonaway. I see following in log…
4046f08b-b0c8-4ffb-b465-f9bfdb07ab25 11:25:31 PM EDT: warn No event handler found for mode event ‘Away’
My mode automation has stopped working
I’m sorry for the issues. Im exhausted and I will work through this in the morning. The more details on these errors the better please
No worries.
Here is what i get in the log when I change modes in ST
1:14:39 AM: warn No event handler found for mode event 'Night’
1:13:48 AM: warn No event handler found for mode event ‘Hold’
I’m really enjoying watching the progress made on this. I’ve installed it for a while now dating back to the previous version. Initially I had ZERO idea what in the heck I was doing, how to install, etc…etc… it’s only by lurking here and reading your posts did I teach myself what I was doing wrong and how much of an idiot I truly was!
The new app is a much better improvement. I’m not sure what any of it does yet, but I’ve got it on my ST App and I like the new layout. I need to keep reading and learning.
The one issue I have so far is that if my thermostat is shut “off” I can’t turn it on via the app or, vice-versa. Raising / lowering the heat has a slight delay, a few minutes or so from the time I press the button on the app to the time it actually “hits” the Nest but other then that, great work!
2 Likes