I have had a Tempest at the top of my mast for the last couple of summers. (I realize this is a small group of users. Maybe one user, me.)
Of course, that creates issues with wind data in particular. Until recently, I was using Node-RED/Signalk to adjust the wind direction and wind speed based on the boat’s compass heading and speed over ground. The N face of the tempest points toward the bow, so the wind angle is always relative to the bow.
Recently, I ported the Node-RED flows to a TS Signalk plugin. Signalk is an open-source boat data management system that many run on RPIs on boats. But I also have it running on my Mac and an Ubuntu AWS micro instance. I think it would largely work with anything on the move, with some minor tweaking and a connected GNSS/IMU device.
The Plugin consumes all UDP data and all other standard data defined in the WeatherFlow UDP, WS, and REST docs.
However, while I can correct for wind speed and wind angle, I cannot dynamically change the location of the hub, so the forecast data is useless unless I am in my homeport. (And in some way, my data is also corrupting the underlying weatherflow data and may result in seemingly odd readings in general for my station. The data is corrected locally but not in the data sent to weatheflow from the hub)
If others use SignalK and have their Tempest on a moving object, here is the repo: GitHub - motamman/signalk-weatherflow
Of course, I may be a member of a club of one.
Pax,
Mo