Uninstalled and reinstalled, entered my station ID, and it tells me not found. I have double checked my ID #.
Can you give me your station number and I’ll try to see what happens ?
I had the same problem as @txprairie.
I had to reboot the Roku box twice and then it took my ID
I have entered my # and one other # and they both work. Reinstalled app, also rebooted roku, prior to entering the #'s.
Will check what happens for a couple days
Thank you !
Funny observation.
Being from Florida I don’t see your Avatar as a radar map of Texas, I see a dolphin 
1 Like
Well i entered 5 ws numbers including my own and for a few days I was able to scroll through the list and see the data.
Today, I get to the 3rd ws down and the app crashes.
I’m gonna give it a rest
I know the cause . . . . Some things have changed regarding Tempest data-access.
If my application only ingested data from your own 1 station, there would be no issue.
The fact that my application is accessing other stations causes the issue.
The API call is taking an extended period of time to return data. That latency is not tolerated by ROKU and it closes the application.
The Tech Support and Management at Tempest is being VERY helpful with me and I expect a more robust solution this week.
This is the short version; I will elaborate more as progress and/or changes are made.
Thanks !!
1 Like
Just curious: why would the app work for a few days with 5 ws #'s, and then suddenly work for just 2?
In this case the number of weather stations is irrelevant.
The response time from the API call has increased and become more variable coinciding with the initial data-access problem that stopped the application from working at all.
It’s important to say Tempest has done nothing wrong and their APIs are working as designed.
I will know a lot more about a permanent solution later this week and will summarize what I know then.
Mine is working right now . . . . !
Thanks
1 Like