Recent Posts

Pages: [1] 2 3 ... 10
1
WeatherCat iOS Clients / Re: iOS Client unable to connect after weak WiFi
« Last post by David on Yesterday at 06:06:21 PM »
Greatly appreciated!
2
Quote
Following a successful connection to a RCP server (RCP_server_current), App polls and stores the device's current gateway IP address (gIP_sucess)
Upon open/wake from sleep, App polls the device's current gateway IP address (gIP_current) and compares gIP_current with gIP_sucess
If match
      connect to RCP_server_current.
else
      ask user for RCP server

I've spent some time looking into this and found some examples of how to get the router IP address in objective c. It's not pretty. I'll keep investigating.
3
Dear Jenna and WeatherCat frustrated sys-admins,

I am seriously considering cutting all ties with WU and going to personal website only...and so it goes.

I certainly won't disagree with your frustrations, but if you are considering creating a personal website, you could simply let WU "twist in the wind" and concentrate instead on that website.  If WU is no longer your primary web access to your data, then it doesn't matter as much what happens to WU.  There are some really nice templates out there so putting up your own website isn't as much of a chore as it used to be.  These days it is always better to focus on what positive steps we can make and let what is wrong wallow in it own futility.  Life is too short to let failings of services like WU get you down.

Cheers, Edouard
4
WeatherCat iOS Clients / Re: iOS Client unable to connect after weak WiFi
« Last post by Blicj11 on June 13, 2018, 07:45:46 PM »
My 2 for what it's worth, I think David's suggestion would be a major improvement if it is possible to implement. The few minutes waiting for a timeout seems like forever, even though it's not, and one has to keep fiddling with the iPhone to keep it from going to sleep whilst waiting for the timeout to occur.
5
WeatherCat iOS Clients / Re: iOS Client unable to connect after weak WiFi
« Last post by David on June 13, 2018, 07:07:38 PM »
That makes a lot of sense. Thanks for the detail.

The App doesn't know if you have left the network unless it attempts a connection. But you don't want it to automatically check for a connection, like it does now. For example, you leave the app open and the iPhone goes to sleep (the screen goes black). The App will ask you which server to use when it awakens. Another example is when you switch from the App to another app and then go back to the App. Again, the App will ask you which server to use when it awakens. This would have to be an option since many users would prefer the automatic connection. Are we on the right track?

YES, EXACTLY! I agree; it would have to be an option, for the exact reason you stated.

//break//

Would it be possible to add this logic before the app asks which server to connect to:

Following a successful connection to a RCP server (RCP_server_current), App polls and stores the device's current gateway IP address (gIP_sucess)
Upon open/wake from sleep, App polls the device's current gateway IP address (gIP_current) and compares gIP_current with gIP_sucess
If match
      connect to RCP_server_current.
else
      ask user for RCP server


If that's not possible, I'd still be thrilled with the option to have the app ask me every time which server to connect to.
6
    Why select a server without initiating a connection? I don't understand. Please give me more detail about what you would like to do.

    Right now, when the user is on a network that does not have a WC RCP server:
    • Start the App
    • App immediately attempts to connect to the last server.
    • The App is locked up "in the bowels of iOS" for about 2-3 minutes (in my experience), before it times out. (In order for this to work, the app must be left open, in the foreground, and the phone must be prevented from locking.)
    • After the connection attempt has timed out, the App asks the user to try to connect again or to connect to a different server.
    • User selects correct server
    • App connects to the server
    [li]
    [/li][/list]

    The above takes 2-3 minutes and requires the user to keep WC RCP for iOS in the foreground while ensuring the phone doesn't lock until the connection attempt times out.

    What I'm proposing:
    • Start the App
    • App asks which server to connect to
    • User selects the appropriate I.P. address/network/ddns
    • App connects to server

    The above would take 1-2 seconds.

    Having the app ask which server to connect to on startup (prior to attempting to connect to a server from a network the user is no longer on), could be a preference that the user could turn on or off. If a user only uses the app on one network they would likely turn this feature off. Users, such as myself, who use their app on multiple networks (local, Internet) would not have to leave the app open for 2-3 minutes every time they switch networks before being able to tell the app which I.P. address (local, Internet) to connect to.

    If this explanation doesn't make sense, let me know and I'll create a video demonstrating the issue.

    That makes a lot of sense. Thanks for the detail.

    The App doesn't know if you have left the network unless it attempts a connection. But you don't want it to automatically check for a connection, like it does now. For example, you leave the app open and the iPhone goes to sleep (the screen goes black). The App will ask you which server to use when it awakens. Another example is when you switch from the App to another app and then go back to the App. Again, the App will ask you which server to use when it awakens. This would have to be an option since many users would prefer the automatic connection. Are we on the right track?
    7
    WeatherCat General Discussion / Re: Coping with Weather Underground "issuez"
    « Last post by jennajon on June 13, 2018, 01:52:14 PM »
    Blicj11:

    Totally agree. The new app simply does not offer as much information as the old, and therefore is worthless to me personally.

    However, the link I posted (http://stats.pingdom.com/zw9vxjhrr9ze/1850219) may not be reliable information since it still shows
    the Rapid Fire network to be completely offline. I am uploading information once again using the Rapid Fire option with no issues whatsoever.

    I am seriously considering cutting all ties with WU and going to personal website only...and so it goes.

    jenna
    8
    General Weather Discussion / Re: First Atlantic named storm of the season.
    « Last post by Blicj11 on June 13, 2018, 03:45:33 AM »
    Thanks for taking time out from worrying about the Buick to post this.
    9
    General Weather Discussion / Bud is no buddy of mine! (Re: Storm of the season.)
    « Last post by elagache on June 12, 2018, 11:49:45 PM »
    Dear WeatherCat observers of extreme weather (preferably from a safe distance!)

    The Atlantic is calm for the moment, but Eastern Pacific has suddenly become active.   Hurricane Bud was a category 4 storm for while.  That's a very energetic storm for the Eastern Pacific and especially so early in the season.  Here is the Eastern Pacific Hurricane Outlook:

    http://www.cpc.ncep.noaa.gov/products/Epac_hurr/Epac_hurricane.html

    The summary can be found on this slide:



    If this year lives up to billing, it could be an "interesting" year for cyclonic storms. 

    Edouard
    10
    WeatherCat iOS Clients / Re: iOS Client unable to connect after weak WiFi
    « Last post by David on June 12, 2018, 08:29:07 PM »
    Why select a server without initiating a connection? I don't understand. Please give me more detail about what you would like to do.

    Right now, when the user is on a network that does not have a WC RCP server:
    • Start the App
    • App immediately attempts to connect to the last server.
    • The App is locked up "in the bowels of iOS" for about 2-3 minutes (in my experience), before it times out. (In order for this to work, the app must be left open, in the foreground, and the phone must be prevented from locking.)
    • After the connection attempt has timed out, the App asks the user to try to connect again or to connect to a different server.
    • User selects correct server
    • App connects to the server
    [li]
    [/li][/list]

    The above takes 2-3 minutes and requires the user to keep WC RCP for iOS in the foreground while ensuring the phone doesn't lock until the connection attempt times out.

    What I'm proposing:
    • Start the App
    • App asks which server to connect to
    • User selects the appropriate I.P. address/network/ddns
    • App connects to server

    The above would take 1-2 seconds.

    Having the app ask which server to connect to on startup (prior to attempting to connect to a server from a network the user is no longer on), could be a preference that the user could turn on or off. If a user only uses the app on one network they would likely turn this feature off. Users, such as myself, who use their app on multiple networks (local, Internet) would not have to leave the app open for 2-3 minutes every time they switch networks before being able to tell the app which I.P. address (local, Internet) to connect to.

    If this explanation doesn't make sense, let me know and I'll create a video demonstrating the issue.
    Pages: [1] 2 3 ... 10