I think the WLL logs the data from sensors coming in an internal generic structure that is the same for all sensors, but just some of the fields are filled/relevant depending on the data the sensor provides. Request for current conditions just returns these internal structures for all transmitters in JSON format. Therefore, when you know it is a UV sensor just updating every 50 seconds, then asking for the record every 10 seconds is not wrong, but you simply should expect to get unchanged data reported a lot. When looking for wind speed, things are different. But we still have to prove, if this assumption of mine is right.
I also think that the records for itself do not tell which type of sensor it is. Some evidence can be taken from which sensor data is returned as "null", but as Greg replied my guesses are not completely right and I doubt there is a perfect guessing schema. Therefore, I will implement a feature in Meteobridge, where the user has to define per transmitter, which kind of sensor is connected. I think it is a severe design flaw with Davis sensors from the beginning, that those don't identify which kind they are. May be it makes life more easy for production (can use the ISS modules with all the other sensor types) but it adds a lot of confusion and manual hassle to get things sorted out. In general it is simply stupid to let the user tell the system that this is a pure wind sensor instead of the wind sensor telling this within its payload data. But I stop here listing what Davis engineers are not doing right on a conceptual level... would be a rather long list