If you look under my thread, @tonesto7 posted many times and the posts are still there today…
I was offended by some posts in my thread from other NST team members (one of them has since left the forum ), which were offensive for the work I’ve done for the community …
Ask @tonesto7 if he’s offended… we just exchanged about our respective design…
I do see that Firebase has been experiencing high latency issues since last night. I’m not familiar with the NST architecture and how Firebase is used - or if there is any relationship between the issues at all.
We do use firebase but only to collect anonymous exception data if the user opts-in for it.
But it was disabled as soon as I seen the platform issues start
@tonesto7 I can take a look later tonight to verify but if brad is correct the way you could work around latency issues like that is by using asynchronous http instead of sync. Async will send the request and then continue execution of the function. Then when the http responses completes the handler will fire in a new sandbox with another 20 seconds (IIRC it has the same timeout).obviously if firebase is having issues and is timing out you won’t get your metrics but at least you can limit your exposure in ST.
Hey Everyone,
I have noticed over the last few days that my Set to ECO if Contact Open isn’t triggering ECO on my Thermostat. Also when I go into thermostat device on ST anything I do in ST sends the notification that it was complete but Nest isn’t changing. If I make changes on the nest app they update correctly on the ST app.
Any Idea why this would have stopped working in the last week? I updated NSTManager and devices yesterday to see if that would help but no change.
I removed the automations, rebuilt them and saved them. That still didn’t help. Haven’t reinstalled NST Manager but was wondering if that was the next step.