Funny you should bring this up. I just got a GW1000 this week and have been working with the interceptor driver to get it to work with it in ecowitt mode. I think I've got it working, but I haven't hooked it up to weewx yet. I plan to do that today. When I think it's ready, I'll post it so people can try it out. It won't be completely done because I don't have all of the sensors that are supported by the GW1000. But I don't think it will be difficult to add them as they come up.
The WeeWx Interceptor driver was designed for WU protocol type not Ecowitt protocol type.
With Ecowitt protocol type it sends all the sensors including extra temperature, soil, PM2.5 ..etc. But the WeeWx Interceptor was not designed for this because besides the data being different overall protocol is different.
With WU protocol type it only sends those parameters that are defined in the WU upload protocol. Therefore you are limited and you don't get data from the extra sensors.
Once the API is out I'm sure other weather software like WeeWx and Weather-Display and Cumulus will adopt support for it. For now it is exclusive to the Meteobridge. The API has just not been finalized. With the API you'll have access to all the sensors and be much better than "intercepting" the data. It is worth noting also that only the GW1000 at this time has support for this API. Other Ecowitt consoles like the WH2551 do not have this API. The WH2551 does have the "Cuztomized" server for both WU and Ecowitt protocol types.
You may be wondering what the Ecowitt protocol type is for. Well I suppose it is there for you to develop your own script to acquire data. I suppose there is also nothing stopping other software developers from embracing this Ecowitt protocol type instead of waiting for the API to be finalized.
I'm not certain but I think the API will be a more elegant solution than the Ecowitt protocol type upload method and the WU protocol type upload. The preferred method for applications to talk to each other is through a JSON API rather than just blindly sending data. I'm not a developer so I probably can't express this in the best words, but the Ecowitt protocol type upload (and WU upload) is more like an HTTP blind send. The JSON API can carry more information about the transfer and error handling...its more capable and intelligent. Beats me ...something like that. But maybe I'm totally wrong.