Port Conflict

[kj6rgx]

Trying to run WeatherDisplay and CumulusMX4 on the same Win10 computer with both grabbing data from my Tempest station. Getting this error in CumulusMX:

"Only one usage of each socket address (protocol/Network address/port) is normally permitted."

I assume the issue is both are trying to connect to the Weatherflow server. I'm wondering if there is a way to direct one of the programs to grab the data from my Tempest hub and skip the Weatherflow server? As a long time user of WeatherDisplay I am fairly certain I can't make any changes to cronweatherflow so hoping I can make changes in CumulusMX. Any ideas?


Dan

[freddie]

Could you zip up and attach the log file to a reply to this topic, please? It would be useful to have some context around that log message.

[mcrossley]

Cumulus is already configured to open the port in shared mode, so I think it must be WD that is opening it in exclusive mode

[kj6rgx]

Could you zip up and attach the log file to a reply to this topic, please? It would be useful to have some context around that log message.

I searched the diag file and cannot find the error. I see the error in the terminal window almost immediately as soon as Cumulus finished importing missed data records. I will do some digging to see if I can find if/where Cumulus records the error.

FWIW, still have some troubleshooting to perform, but I made a change in cronweatherflow to NOT use the websocket for data collection. One first glance it appears to have stopped the error showing in Cumulus, but more investigation is needed to verify all components of data collection are working correctly in cronweatherflow.

[kj6rgx]

It appears the change I made to WD/cronweatherflow to not use the websocket has stopped the error in CumulusMx. Still waiting on a rain event to see what happens, but everything else appears to be functioning correctly.


Dan

[kj6rgx]

For anyone following this thread...the change I made to use http upload in CumulusMx appears to have fixed the initial port error. But, now there is a conflict in connecting to the weatherflow server to obtain the Tempest data. I changed my WD setup to NOT use a websocket and collect the data direct from the hub. Unfortunately no rain data was being obtained, all other data was working correctly. So I switched WD back to using a websocket and re-configured CumulusMx to obtain data via Weatherlink and so far everything appears to be working correctly. Waiting on another rain event but fingers crossed this setup will continue to obtain good data.