So I tried the newer version from a few days ago. Then I got 'SpecialSDPLength=210' and 'JabberCount=1' packets in ssMonitor but no valid data packets. Stopped the process and went back to older version, now it is working!
I don't recommend using the old version. I fixed a lot of bugs in the latest version, and I'd like to get everyone using it ASAP.
I think the problem most folks have with the new version is that your SkySpy.INI file gets corrupted by the old version or you try to run multiple copies of ssMonitor at the same time.
If you have problems with the latest version, then I recommend doing the following:
Copy your existing SkySpy.ini file to your desktop or other safe location. You will find it in the C:\ProgramData\SkySpyData folder.
Uninstall SkySpy from the Windows control panel.
Delete the following folders, along with everything in them:
- C:\Program Files\SkySpy
Note: "Program Files" will be "Program Files (x86)" on 64-bit windows machines
Now, run the latest installer. When it finishes, make sure you open the Settings dialog in ssMonitor and configure *everything*. This includes your PWS serial number and your Weather Underground (WU) and or WeatherFlow (WF) station ID. Nothing will work correctly until you configure SkySpy. Don't worry about any crazy messages in the Service Debug Information grid until you have all your settings completely correct.
If you have forgotten any of your serial number or station code info, then open the SkySpy.INI file that you saved to your desktop with Notepad. The information should be in there. You can cut-and-paste from Notepad into the Setup dialog fields. Click the Ok button on the Settings dialog and it will update SkySpy.INI (the one used by the Service in C:\ProgramData\SkySpyData).
If you are going to use Weather Alerts, then make sure you fill in all of the SkySpy SMTP settings. You can find this information in your Email reader settings or you can ask your ISP. Your ISP may have a web page that shows the suggested settings: Look for settings used by the Thunderbird Email reader. It uses similar SMTP settings to SkySpy.
It is completely normal to see JabberCount/Special SDP events in ssMonitor for the first hour or two of SkySpyService operation. This is your weather station sending "catch-up" weather data to SkySpy. Since we can't use it to update WU or WF, SkySpy simply tosses the data. When the C84612 thinks it has caught up with sending historical weather data to the server, then it stops jabbering. Jabbering will reoccur if your PWS cannot communicate with SkySpyService for more than a few minutes. You can safely ignore it.
If Jabber events persist, then make sure all of your sensors are working properly. If one or more sensors cannot communicate with the Gateway, then you will have to fix that - but this is outside the scope of the SkySpy software.
You should not need to make any special firewall rules for ssMonitor. ssMonitor does not use your network at all. It chats with SkySpyService through other means: "Named Pipes" and via the INI file.
SkySpyService on the other hand does everything network-related: It listens to your PWS Gateway Module and it talks back to it. It also talks and listens to WU and WF. Last, it sends emails to you, if you have Weather Alerts turned on.
So... You do not have to run ssMonitor at all, once you have configured all your settings. ssMonitor is simply a debug tool at this point - you can see all your weather information on WU and/or WF.
I hope this clears up some misconceptions