-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Automation shows "State Usage is Greater than 80%" #569
Comments
same issue here |
@PeteBoyRocket @jacobwtyler If you can then open it and press Done. That should call the stateCleanup() function and clear out the queues. If that doesn't work but you can get into the SmartApp still than go into Application Preferences > Logging > Toggle Reset Application Data > Press Done all the way out to the main smart apps list. |
I can open it, but I suspect thats because I still have the hacked |
Ok, removing all of the nest devices THEN uninstalling it is how to remove it! Obvious in hindsight. Next I'll try uninstalling it, then remove all the Nest Manager Smartapp and device handler code. Aka as clean as I can get it and start from scratch |
Good news! whatever the issue was doing this seems to have fixed it!
@jacobwtyler Can you try this? If this fixes your issue, I guess we can close this, unless @tonesto7 wants to do anything further with it. |
@tonesto7 I don't have any options when I click on the SmartApp. It only displays the message
and the only thing I can click is the back button in the top left or a Save button in the top right. (I'm on iOS). I did completely remove all Nest devices from SmartThings and then removed the SmartApp via the IDE and then reinstalled NST Manager and added all my devices back successfully and I thought everything was fixed so I went into WebCoRE and set my pistons back up the way I had them. Then I decided to click on the SmartApp again and the message was back. I'm going to try removing everything again. |
Removed all 12 cameras, 1 thermostat and 6 Protects again and uninstalled the SmartApp via IDE and created new OAuth and reinstalled. Once again, everything installed fine and I get everything set up. This time, I went right back into the SmartApp and it did allow me in. I looked for the
section that you referenced and found nothing of the sort. A few seconds after looking around in the SmartApp, ST pushed a notification which just read "Info: ". This looked familiar and it happened last time as well I believe. Anyhow, after that notification, I could no longer get into the SmartApp. It just gives me the 80% full message again. Any ideas? |
I got it to install if I didn’t add my 12 cameras and I was able to view the logging section. It was 78% without the cameras and I tried the reset application data. It it didn’t free up any space. As soon as I add the cameras back, it goes up to 84% and I had a quick chance to try the reset application data again but it did nothing again. Then it gives me an “info:” notification and I can no longer get into the SmartApp. Only the 80% message. |
Do you have the weather device enabled? |
@imnotbob, currently I do not have the weather device enabled but I did when this started. Total devices: In order to get my manager state down to 78%, I’ve eliminated the weather sensor and all 12 cameras. |
I created some changes to reduce state usage. Once tony has a look at them he can share them out. After that I would like to see you data in the web diagnostics (I don't need logging on) |
Likely this should move to private messages in the forum |
Your update got me down to 55% WITH the cameras added back. Thanks so much! |
Verify the following before opening an issue:
About Your Setup:
Expected Behavior
Tapping the NST Manager automation should allow me to configure it.
Current Behavior
Tapping the NST Manager automation shows this message:
I'm unable to do anything with the automation at this point. Including uninstalling it.
Hacking this line https://github.com/tonesto7/nest-manager/blob/master/smartapps/tonesto7/nest-manager.src/nest-manager.groovy#L152
to
(stateSz > 180)
Lets me use it again. seems to work ok. See this in the diagnostics page after doing that:And this:
Steps to Reproduce (for bugs)
1.Tap the NST Manager automation
Context
Please include a copy of your log under the IDE if possible
https://graph-eu01-euwest1.api.smartthings.com/api/smartapps/installations/a6832cdd-c230-4b51-8bef-0e501da8c70a/diagHome?access_token=70991a52-67b1-4b7f-b859-b6ab33635612
The text was updated successfully, but these errors were encountered: