Trixology
WeatherCat => WeatherCat iOS Clients => Topic started by: Marozsan on September 29, 2019, 05:30:45 PM
-
Following grade to os 10.14.6 on my mac, I am unable to connect WeathercatRCP on my iPad to my local network. Am able to connect to trilogy-eng.com server but not my home server. It has been working fine for the past year, but the upgrade seemed to do something?
Any suggestions?
-
Following grade to os 10.14.6 on my mac, I am unable to connect WeathercatRCP on my iPad to my local network. Am able to connect to trilogy-eng.com server but not my home server. It has been working fine for the past year, but the upgrade seemed to do something?
Any suggestions?
You did the right thing - attempt to connect to trilogy-eng.com - to verify that your copy of WeatherCatPad is working properly. I'll have to leave it to one of my fellow members whose server is running 10.14.6 to verify that WeatherCatPad will connect to their local network. (My WeatherCat server is running on an old iMac which is not supported by 10.14)
-
Dear Marozsan, Grand, and WeatherCat troubleshooters,
Following grade to os 10.14.6 on my mac, I am unable to connect WeathercatRCP on my iPad to my local network. . . . . .
. . . . I'll have to leave it to one of my fellow members whose server is running 10.14.6 to verify that WeatherCatPad will connect to their local network.
My Mac is running macOS 10.14.6 and I am able to connect my WeatherCatPad to the WeatherCat server using our local area network. In the past, I've found that in such cases simply switching to trixology-eng.com and then switching back to local is enough to get things working again. Have you tried that?
Cheers, Edouard [cheers1]
-
Yes, that was the first thing I tried tried and again several times with no results. I am running the WeathercatRCP app, not the WeathercatPad app. Not sure that makes a difference. I should also add that I upgraded my iPad software to 13.1 perhaps this contributes to the problem.
-
Dear Marozsan and WeatherCat troubleshooters,
Yes, that was the first thing I tried tried and again several times with no results. I am running the WeathercatRCP app, not the WeathercatPad app. Not sure that makes a difference.
WeathercatRCP works fine for me as well. Have you tried rebooting the Mac and iPhone? These days, these devices require rebooting much more frequently than in the past. It is probably prudent to reboot every week but I can't get into the habit of it.
Cheers, Edouard [cheers1]
-
Yes, tries rebooting as well, still get ?cannot verify server ? response.
-
I am running macOS 10.14.6 and WeatherCatRCP works on my iPad, but I have not upgraded my iPad to the new iPadOS yet so maybe that is the culprit. I am running iOS 12.4.1 on my iPad. I am running iOS 13.1.1 on my phone and WeatherCatRCP runs fine there.
-
I tried running it in my iPhone and no go there as well. Upgraded to the most recent iOS software issued last week. I also noticed after upgrading Mojave that my station communication information needed to be re-entered. All clues I think, but no solution yet.
-
I am now running iOS 13.1.2 and RCP is still working.I have two suggestions.
1. Make sure you are running the most recent version of WeatherCatClient, which is 2.0.0
2. Try deleting WeatherCatRCP from your phone and reinstalling it from scratch
-
I have deleted the app and reinstalled it to no avail.
What is WeatherCat Client 2.0 and where do I download it?
-
Dear Marozsan, Blick, and WeatherCat troubleshooters,
. . .
What is WeatherCat Client 2.0 and where do I download it?
WeatherCat Client is a version of the client running on a Mac instead of iOS. It will allow to you see if the problem is with the WeatherCat server or if the problem is in iOS. You can download it at the bottom of this webpage:
https://trixology.com/weathercat/ (https://trixology.com/weathercat/)
It is the download called: WeatherCat Miscellaneous Files.
Let us know what you discover.
Cheers, Edouard [cheers1]
-
One other thought. Reboot your Mac and make sure that Port 49255 is properly bound to whatever internal IP address you reserved for it. That port is required for WeatherCatRCP to function.
-
Ok, got it fixed. It seems when I restart the computer both my WeatherLink app and Weathercat lose the station config information. They were both running fine prior to the re start. So, I first needed to enter the proper start comm information by selecting the proper Usb-Usart driver and restarted Weathercat. My desktop Weathercat was then up and running. Secondly, Weathercat client indicated no IP information in the internet panel. So, I entered my ip address and it identified port 49250, so I hit connect. I then launched WeathercatRCP and it connected.
Thank you for your help. I am 78 years old, so working through the computer details takes me time.
-
I love it when a fellow Weather-Catter figures something out. Good for you for riding this one to the ground!
I thought that RCP requires 49255, but if you have it connected on 49250, don't fix what ain't broke.
-
Now the question is, why did both Weathercat and Weatherlink lose the station comm information when I restarted my mac?
It happened again today, but now I have the fix.
-
Mac info: macOS 10.14.6, WeatherCat 3.04 Build 91, WeatherCatRCP 1.2 (190618)
Finally decided to join the crowd displaying their prior months data trends. Downloaded the latest versions of the Misc Files, just in case. Started up the WeatherCat Client. Up came the standard Gauge display.
Deleted and Reinstalled WeatherCatRCP. Opened in Settings, showing default Metric values, changed to the minority "English" set. Noted "Local" showing just below "WeatherCat Server".
Tapped "Manage WeatherCat Servers" link and found three text boxes and "Local network".
Tapped the "Local network" radio button and nothing happened. Tapped again with same result. Tapped a third time and put the iPhone down as I was bored. Some time latter, the radio button indicated it had become selected and the Server Status showed "Verifying...". BTW, "10.0.1.3" was also showing under URL even though I had not yet entered anything in any text box. That is the correct IP for the mini on my network. Alas, the final indication was that the app was "Unable to verify server".
RCP Prefs shows Status: "Connected (Local)" or "Server details: 10.0.1.3 on port 49250" depending on radio button selection and after entering the URL.
Trying to select the middle text box indicates the device is frozen: it does not change the selected button for about 60 seconds. It then me to enter the same url above and Status shows "Connecting...". Gateway IP Address shows the WiFi router address, of course. Strangely, even though the text reads "Connecting...", there is no spinning gear in the status line of the iPhone for well over 2 minutes, although it does finally appear. Status now says "Verifying..." after another 3 minutes, fortunately, the spinning gear shows no sign of wearing out! [lol]
Final result (after at least 5 minutes): "Unable to verify server".
Selecting "Local network" has the same results.
Selecting "trixology-eng.com" seems to work and is handy in determining the local time in most of Great Britain.
Question of the Day: What step(s) did I forget?
Any other info I can offer?
-
Dear X-Air and WeatherCat iOS troubleshooters,
Finally decided to join the crowd displaying their prior months data trends.
[wink] . . . . Well, what kept ya'? . . . . . [biggrin]
. . . . . .
Alas, the final indication was that the app was "Unable to verify server".
. . . . . . .
The only suggestion that I don't see listed in your troubleshooting steps is rebooting the iPhone. If it isn't too much of a hassle, rebooting the Mac running WeatherCat is also a prudent thing to do. Alas, iOS isn't nearly as bullet-proof as a UNIX-based operating system, and rebooting does seem to be required regular maintenance.
Cheers, Edouard [cheers1]
-
rebooting the Mac running WeatherCat
WHAT?!!! And ruin my continuously running record attempt! I'm already at 6 days 6 hours and 17 minutes!!! [rolleyes2]
I did reboot the phone. Might as well reboot the mini.
I'm not sure how this app could show me anything "no matter where I might be" however. I don't have a static IP nor do I want to use a dynamic IP app. As long as I can access the web, I can always access my website. The only reason I've even attempted to get the app to work is to contribute to the end-o-month summary reports. [blush] And I enjoy many puzzles... :)
-
When we were testing the pre-release of RCP we had to port forward 49255. The WC Client can use 49250 through 49254, but I believe RCP requires 49255. Try adding that to the port forwarding instructions for your router and see if that is your issue. I mean your RCP issue; nobody on this forum has time to help with all your issues. :)
-
...nobody on this forum has time to help with all your issues.
Don't beat around the bush Blick, tell me how really feel! cmu:-)
-
I am having a similar problem with Weathercat app on my iPhone and iPad. It has worked fine for a couple of years and connected locally and remotely using a dyn dns address (internet 1), now it will not connect with either option but connects to the Trixology option (Internet 2) on all three settings.
-
Dear Blick, X-Air, Terry and WeatherCat "troubleshooters" (computer troubles only!) [biggrin]
. . . .
. . . . I mean your RCP issue; nobody on this forum has time to help with all your issues. :)
[wink] . . . . I'm not touching that one with a 12 foot pole! . . . . [biggrin]
I am having a similar problem with Weathercat app on my iPhone and iPad. It has worked fine for a couple of years and connected locally and remotely using a dyn dns address (internet 1), now it will not connect with either option but connects to the Trixology option (Internet 2) on all three settings.
I just double-checked WeatherCatRCP on my iPhone and WeatherCat-iPad on my iPad, both are working fine. I suspect you have something that is interfering with the normal operations of these applications. Did you change anything at the time they stopped working? Any new piece of networking hardware could be the cause.
Cheers, Edouard [cheers1]
-
Thanks for the reply Edouard.
Nothing changed at all. It is driving me nuts!! ???
-
Dear Terry and WeatherCat troubleshooters,
Nothing changed at all. It is driving me nuts!! ???
Unfortunately very strange. Is there any way you could create a simplified network with only the Mac running WeatherCat and one of your iOS devices? Sometimes the only way to troubleshoot these sorts of problems is try to eliminate as many intermediate components as possible.
Best advice I can come up with, . . . .
Cheers, Edouard
-
Terry:
Grand will have some advice the next time he logs in so do not give up yet. The same thing happened to me when we were testing the pre-release version of RCP but for the life of me I can't remember what he told me to do.
I assume you have already done the following:
- Verified you are still forwarding Port 49255 on your router
- Delete RCP app from your phone and and reinstalled it from scratch (you won't lose any data doing this but you will have to re-enter your settings.
-
Thanks both for responding. Much appreciated.
I need an "idiots guide" for these sort of problems!! How I set it up and had it working for the past few years I do not know!
Yes I have checked my router and port forwarding is still set up 49250 to 49255. Is there any more I can do to check this? When I log in to the router I am faced with a bewildering load of abbreviations, settings and numbers which mean nothing to me. I am afraid to change anything in case everything stops working.
I am using the original iPhone app, v 1.6 not the RCP version. I have deleted and reinstalled it (and the iPad app) and then entered my dyndns address in "internet 1" but no improvement.
-
Terry:
If you can connect to Trixology from the iOS app that means the app is working properly. Please tell us the following:
- macOS version under which your computer is running
- iOS version running on your phone
- iPadOS version
- WeatherCat version
- WeatherCatClient version - this is an app in your WeatherCat folder in applications on your Mac(
This will allow us to see if anyone else running the iOS app is using the same versions.
Also, if you have more than one Mac (iMac and a laptop, two iMacs, etc) there is an easy way to test port forwarding. If you only have one Mac I'll tell you a different way to test the port forwarding but need to know your macOS version.
-
Many thanks Blick
Here are the answers to your questions
macOS version under which your computer is running. - 10.15.3
iOS version running on your phone. - 13.3.1
iPadOS version. - 10.3.3
WeatherCat version. - 3.05
WeatherCatClient version - this is an app in your WeatherCat folder in applications on your Mac. - This is greyed out as not being compatible with the current OS
I do have a MacBook as well as the Mac Mini that WeatherCat is on.
many thanks in advance for your help
-
Hi again Blick
I have just checked the System Information and the WeatherCatClient version is 1.6.1 32 bit (unsupported)
I upgraded to Catalina back in December and the iPhone app has worked fine up until the past week or so.
-
Before I was so politely lol(1)reprimanded for having too "many issues", I checked to see if I had the correct app/files. Re-visit to the WeatherCat home page (https://trixology.com/weathercat/), scroll all the way to the bottom and look for the link to "WeatherCat Miscellaneous Files". It's under the heading of "Other Downloads". In that download is the newest version of WeatherCatClient (2.0). It is 64-bit, Catalina macOS 10.15 compliant. Hope that helps!
Of course, that doesn't explain why your setup continued to work after updating to Catalina...
-
Yes. Use version 2.0 of the WeatherCat client. Install (copy) it on your MacBook. If your port forwarding is setup correctly, the Client will pull up your WeatherCat data on your MacBook.
I'm not sure about running the old version of the WeatherCat iOS app on your setup. I deleted mine when I upgraded to the RCP version.
However, I do have an idea (which doesn't happen very often). On your router, make sure you are forwarding ports 49250-49255 to the internal IP address of your Mac Mini. It is much simpler if you assign an internal static IP address to your Mini so that it doesn't have the ability to grab a new IP address every time you reboot it. Then in the iOS app, enter your DYNDNS address for Internet 1. It doesn't really matter whether you enter it in Internet 1 or 2 but leave the Trixology address in one of them and put your's in the other one. You want Trixology so you can test to make sure the app works correctly. If it does, that narrows your issue down to something on your end.
I suspect that if your Mini does not have a static internal address, the reason your iOS app isn't working is because you rebooted your Mini at some point and it grabbed a different IP address from your router. So either give it a static internal IP by assigning the MAC address of the Mini to one of the addresses in your internal range, or find out what internal IP address the Mini is currently using, and forward the ports to that address and it should work, until you have to reboot.
If you are not using a static IP address on your Mini, it won't necessarily grab a new one on every reboot, but it can, if something else (either mobile or your Mac Book) came along and grabbed the old IP address of the Mini whilst it was turned off, or was rebooting.
Hope this helps.
-
Here is another way to test all this that may be helpful to you.
On your Mini, do the following:
- To find your internal IP address, choose Apple menu > System Preferences, click Network, then select which network service your using, either Ethernet or Wi-Fi, depending on how your Mini is connected.
- Open the Network Utility app, located in the /System/Library/CoreServices/Applications folder.
- Click Port Scan, enter the Internal IP address of the Mini, then check the box for Only test ports between, enter ports 49250 and 49255, and click the Scan button.
- Be patient whilst the scan is running - it takes longer than you think it will, but eventually it will return the results and you can see which of those ports are open.
About the port range, if you are not using RCP, only one of those ports will be open. This is normal. WeatherCat does not need all the ports open. It just needs one of the ports in the range, but you forward the entire range to allow Weathercat to grab one if some other software has grabbed the first one in the range. If you use the RCP version of the iOS app, you should have two ports in the range open, one for the Client and 49255 for RCP.
I have attached a screenshot showing the results of my port scan. Your internal IP address are probably not using 10.0.1.x as that is how home networks are setup if you started out using an Apple Time Capsule router. Everyone else in the world uses, either 192.168.x.x or 172.16.x.x.
-
Thanks Blick and Xairbusdriver
Updating the WeatherCatClient app did the trick. As you say xairbusdriver, how it worked after upgrading to Catalina is a puzzle ?!?!
When I get 5 minutes I will download the RCP version and check your other recommendations Blick.
Many thanks for the time you put into this, much appreciated. 👍👍👍👍👍
-
This is one heck of an impressive technical support team! ThU32:-)
-
I love it when a WeatherCatter is able to resolve an issue. Good work Terry.