Recent Posts

Pages: 1 [2] 3 4 ... 10
11
WeatherCat iOS Clients / WeatherCatRCP 1.1 (180619) for iOS Beta
« Last post by The Grand Poohbah on June 19, 2018, 07:48:12 PM »
WeatherCatRCP version 1.1 is available for Beta testing.

What's new
When awakened, the App will detect if the Gateway has changed and provide an alert.
The alert gives you the option of continuing with the new Gateway or changing the server.
This alert is an option on the Options screen. The default is OFF.

The Gateway changes when your device switches to a different WiFi network,
switches from WiFi to a cellular network, switches from a celluar network to WiFi,
looses the network connection (cellular or WiFi) entirely, or re-connects after loosing a connection.

This option is helpful if your WeatherCat 3 server is on the "Local network" (WiFi),
but not accessible from the Internet. It lets you deal with those instances when you
are away from your local network and inadvertently open WeatherCatRCP, causing
WeatherCatRCP to spend what seems like an eternity searching for the non-existant "Local network".
Instead, you can select "Change Server" in the Gateway Changed Alert and either
switch to an Internet connection or quit the App.

Tip
If you get "No network connection" or cannot connect on the "WeatherCat Servers" screen.
Tap the Radio Button next to the Local or Internet URL to try again.

Specific changes
- Added a "Gateway change Alert" switch on the Options screen (default is OFF).
- If the Gateway alert switch is ON, show an alert when the App becomes active and the Gateway has changed.
- Show an error message (instead of error number) when there is no network connection.
- Show the Gateway IP address on the Settings Manage WeatherCat Servers screen.

Notes to Beta Testers
Use TestFlight to install WeatherCatRCP Version 1.1. If you want to revert to the original 1.0 release,
you can delete 1.1 on your device and re-install 1.0 from the Apple App Store.

Please share your insights and experiences on the ways you found the "Gateway Changed" feature useful.

Members of the original v1.0 Beta test group will be automatically invited.

See the iOS Clients topic "About the WeatherCatRCP Beta" for information on joining the Beta test group and using TestFlight.
12
General Weather Discussion / Re: Weatherlink API
« Last post by Blicj11 on June 19, 2018, 05:09:37 AM »
Thanks for posting.

The last time I checked, WeatherLink 2.0 has some pros, offset by some cons. It will be interesting to see how it plays out, especially given the slow and painful death of Weather Undergound. WU is likely already dead, but may unaware, as it appears unaware of so many other things. Haha.
13
General Weather Discussion / Weatherlink API
« Last post by Weatheraardvark on June 18, 2018, 10:50:50 PM »
As our move to WeatherLink 2.0 proceeds, we are approaching an important update that will affect anyone using the WeatherLink 1.0 API. This may affect you if you use the current API to:
Display data on a personal or community web page.
Share data with a 3rd party service that is dependent on the API.
Access your weather data from our servers.

The current www.weatherlink.com/xml.php API is scheduled to be decommissioned at the end of July, 2018. The new api.weatherlink.com/v1, available in JSON and XML formats, will be the ONLY functioning API after July 2018. This API works for WeatherLink 1.0 and 2.0 and can be used immediately, but it requires the use of a unique API token.

To generate a unique API token: Watch the Generate API Token video
 
Log in to WeatherLink 2.0 using existing WeatherLink user credentials.
Access the account information in the right sidebar, under the username and account picture.
On the account information page, click Generate API Token.
Fill in the required fields and click the Generate button.
The unique API token will display in the API Token field.

These important changes will help us make continual improvements to the API so that you can access your personal weather station data or share it with 3rd party services faster and with maximum reliability.

If you are aware of any person or 3rd party that may use the WeatherLink 1.0 API, please help us spread the news of the upcoming changes.

Thank you,

All of us at Davis Instruments
14
WeatherCat iOS Clients / Re: iOS Client unable to connect after weak WiFi
« Last post by David on June 16, 2018, 06:06:21 PM »
Greatly appreciated!
15
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.
16
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
17
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.
18
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.
19
    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?
    20
    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
    Pages: 1 [2] 3 4 ... 10