Awesome, thanks for the update. For my case, one extra destination suffices!
This was very helpful I was trying to figure out what I was doing wrong. For some reason scrolled past this on the setup instructions.
For people using the new Ecowitt this setup can be found by selecting your weather station. Clicking the three dots in the top right of the app and clicking "DIY Upload Server".
Hi All, my Netatmo Rain Gauge died - so I ended up buying an Ecowitt GW1101 (GW1100 + WS69) 7-in-1 PWS as it was cheaper than buying a new Rain Gauge. 
It helped that there was a $40 AUD voucher on Amazon yesterday. 
Anyhoo, I have it all working with Hubitat, however I cant find any doco on which PWS device to select in WU when setting that up - which device did you guy's use?
I just picked other for hardware on WU, I also went from a Netatmo a few years ago now as it died once within 12 months, got replaced and then died again out of warranty 
I've selected Other, but the data hasn't shown up yet, I might need to wait longer.
Mine looks like it receives data about every 10 seconds
I think I found the problem, I mistook the "O" for a Zero in the station ID.
EDIT: yep, solved.
Prolly a silly question, but I was wondering if there is any issues with renaming the Child device labels? eg PWS Sensor -> Outdoors etc
If there is I haven't hit it 
All mine have been renamed
Cheers
Steve
You can use the device label field and call it whatever you want.
Sweet, I thought that would be the case, but wanted to be certain.
Glad to have you onboard @dJOS, though shame about your Netatmo setup. I looked at them when I was starting to look at a weather station, but the price put me off, so even more of a pain when they fail on you like that.
Looking at the code, I think the list of sensors is based on the Channel and Device ID in the EcoWitt setup, used to set the Device Network Id (DNI) on the HE devices. I could look further at how the device names and labels are managed, but if others are not seeing them affected, I expect that answers the question. Just in case you are wondering, I didn't write the original drivers, so am learning as I go
Sorry @Horseflesh, the forwarding of the data slipped my mind. Thankfully some extra activity with @dJOS coming onboard prompted me to look at the code again and realised I had changes. I still need to setup some of the Preference Settings I want to include for this, so will work on that over the next week or two and hopefully have something out soon. Feel free to poke me if I fall behind...
Thanks mate, I’ve had the Ecowitt in my Amazon list ever since I saw you recommending it ages ago.
It sucks that my rain gauge died, but tbh I’ve been looking for an excuse to buy the Ecowitt for ages. Luckily my lovely wife is usually quite forgiving of my purchases if they are to replace a dying item.
I was expecting to be killed for this purchase as I just spent $2k on a new 6 bay NAS to replace my 15 year old HP MicroServer. 
I’m really loving the Ecowitt so far, although I do have some dumb questions that I’ll save for tomorrow. I’m too tired to phrase them coherently ATM. 
Hey no problem! It will be cool whenever it happens.
Received and new Wittboy the other day. Was a breeze (pun intended) to set up. then decided to integrate with the hub. Downloaded the sburke driver, followed the very clear instructions on the GitHub page, and in no time thing is displaying weather stats on the kitchen monitor.
Great work! Thank you so much.
Really appreciate this app. Thank you!
Sharing my experience with a network issue in case it helps anyone else. I just spent two days trying to figure out why the Ecowitt GW2000B hub was not passing custom weather station data across VLANs even when using IP addresses on both the send and receive side.
I was getting nothing received in the Hubitat logs, I tried pointing the Ecowitt at another device and doing network sniffing. And nothing appeared to be coming out.
After a lot of experimenting, I found that I had BOTH LAN and WiFi turned on on the Ecowitt GW2000B hub. One was on my intended VLAN (192.168.4.x) and one was on my Guest Wifi/VLAN (192.168.3.x).
So the fix was to turn off the WiFi on the Ecowitt device to ensure all traffic was coming out via the LAN port. I suspect what was happening is that - even though I was connected to the control interface on the intended LAN based VLAN - the Ecowitt was likely trying to send out the custom weather station updates via the WiFi which was blocked by the Firewall.
Ever since I've had ONLY the LAN networking turned on, it's been working like a charm, even across VLANs with a firewall rule allowing only traffic between my Ecowitt Hub & Hubitat.
Anyone have or know if the ecowitt water leak sensor is compatible with this integration?
Yes it is.
What are the proper battery settings for WittBoy (WS80 or WS90) with the RF Sensor driver? The driver has preferences for Empty Battery Voltage and Full Battery Voltage, which default to 1.3 and 1.65 respectively. The WittBoy uses two AA batteries, and Ecowitt reporting shows my batteries are at 2.64 (and that value is reported in batteryOrg). I set the Empty to 2.1 and the Full to 3.2, but now the battery gauge reports 0?
And perhaps related, sometimes the batteryOrg gets reported as 4.5. This appears to match the battery value for the capacitor battery in the WittBoy (solar charged power)?
FWIW: I believe I'm using the latest drivers (v1.34.7)