This should be pretty simple to implement. The protocol is identical to the serial one - only difference is the data transport is TCP rather than serial. Changes should be limited to the parameters the DavisService takes and the _start_logging function needs to construct a TCPClientEndpoint rather than a SerialPort when configured for a WeatherLink IP. Unlikely any other code needs changing.
I don't have one of these widgets but the #84 Davis Emulator pretends to be a WeatherLink IP and seems to work with a lot of software so it should be sufficient to verify the changes work given their small size.
Implementing this feature is worthwhile even though the WeatherLink IP has been discontinued as once the Davis Emulator has been fixed up it will allow testing of changes to the Davis Logger without having to grab a spare console.
This should be pretty simple to implement. The protocol is identical to the serial one - only difference is the data transport is TCP rather than serial. Changes should be limited to the parameters the DavisService takes and the _start_logging function needs to construct a TCPClientEndpoint rather than a SerialPort when configured for a WeatherLink IP. Unlikely any other code needs changing.
I don't have one of these widgets but the #84 Davis Emulator pretends to be a WeatherLink IP and seems to work with a lot of software so it should be sufficient to verify the changes work given their small size.
Implementing this feature is worthwhile even though the WeatherLink IP has been discontinued as once the Davis Emulator has been fixed up it will allow testing of changes to the Davis Logger without having to grab a spare console.