Stuck with Ecowitt GW-1100B / WN36 Hubitat integration

I am setting up the Ecowitt GW-1100B / WN36 pool temperature monitor thanks to suggestion by @kahn-hubitat and @velvetfoot - thanks!

So far I connected the GW-1100B to my Wifi and linked the WN36. Everything works with the Ecowitt app and I can monitor temperature with that.

I installed the Ecowitt and Sensor drivers on my C8 with the Hubitat Package Manager. I set up a virtual device for the GW-1100B and it seemed to be OK.

I used the Ecowitt app to set up the local data upload server using my Hubitat IP address, path/data, port: 39501

Everything seemed to go OK but I am not getting this response in Hubitat Devices:

Any help or suggestions appreciated.

Thanks!

is the ecowitt app itself showing the pool sensor.. that is a relatively new device and the firmeware in the gw1100b may need to be updated to see it.

you could also try clicking on resync sensors in the main ecowitt parent device.

1 Like

Thank you for the prompt response!

It does show something but no little picture. That explains it. I do get temperature data on the Ecowitt app.

the picture corresponds to all 8 of devices in that class.. weird though it is slotted into the normal wn31 sensor class. i dont use the floating sensor.. i use the wired wn34bl or somthing.

I did a resync sensors but it just says resync pending for several hours so far.

that means it is not communicating with the hub.. turn on debuggining int the parent device and child main device. and check the logs./. and double check that the ip address has not changed for the 1100b.. you do have it in your dhcp correct. if it changes yhou will get a warning in your logs for sys:1 about an unknown device.

also that picture you posted with ch1. is NOT lthe pool sensor according to your othe post it would be ch1 your hallway ambient sensor

1 Like

Maybe the WN36 needs to be included specifically in the Hubitat Ecowitt driver but is not there yet?

there are two things going on the fact that it is not in the ecowitt app. and the resync issue.. resync should occur regardless.

not showing in the ecowitt app means it is not picking up the sensor.. check battery, put it closer to receiver and also double check the ecowitt app is not showing a firmware update available.

1 Like

Thanks for the help!

The WN36 and the Ecowitt were communicating fine before I started setting up the C8. There is also a little battery icon in the WN36 LCD and it shows full so I think that the battery is OK.

There was a firmware update when I first set up the Ecowitt and that went OK. It shows no option to update now.

I set the IP for the Ecowitt in my router.

Let's take a break.
Thanks for your help!

Not sure if it would help, but moving this to the driver thread may more visibility by people who are into this. Maybe you could get some ideas. I recall just following the instructions (key, lol) and it worked. It doesn't sound like you're getting anything from the gateway into Hubitat.

Maybe you didn't get the MAC right?

1 Like

Thank you for the reply.

I do not know how to move the thread to the driver section. Are we entirely sure that it a driver issue?

I double checked the MAC address and it is correct.

Baffled. I'm not sure what to try next.

@Timbb I saw that you managed to get this working. Any suggestions?

I know less than nothing about coding drivers but I do not see WN36 in the device ID list in the driver. Is this a problem?

It still feels like you might not be getting the data feed through to HE or it is not linking it to the GE device (that's why the MAC/IP is important in the HE gateway preferences. If you go to the logs page on your HE, do you see any logs for "sys" indicating that data was received from an unknown source (it will like the MAC address in the log entry as well).

If you are still stuck I can try and take a closer look later tonight.

1 Like

Thank you for helping!

The MAC is correct. I used the copy function and checked it several times. I also tried with the IP address instead of the MAC. I am not seeing any Data errors in the log. I am giving up for the evening.

Thanks again!

No worries, can see it is getting late over there. Does seem odd if you are not seeing any debug log with the data feed then. Must be in the gateway setup then... Will look some more at your earlier posts....

1 Like

I think it would help to see your setup for the data feed in the EcoWitt App on your phone / tablet. I am wondering i this may not be setup correctly. If it is setup correctly, then it is a question of why you are not seeing either the debug log messages against the gateway device or the system log entry each time the data feed is being sent....

Have you confirmed that port is not being blocked on your router? You can test the connection to the Hubitat Hub at that port.

In PowerShell on a windows machine on the same network as the Ecowitt gateway:

Test-NetConnection "hubip" -Port 39501

ComputerName : 10.0.0.23
RemoteAddress : 10.0.0.23
RemotePort : 39501
InterfaceAlias : Ethernet 2
SourceAddress : 10.0.0.133
TcpTestSucceeded : True

I've been using Ecowitt on Hubitat for a few years now, and I have had the floating pool thermometer for the last two summers now. It works great!! I sleep it in the winter, and I am hoping to get five summers out of the irreplaceable battery.

I also use the soil moisture sensors and a bunch of extra temp/humidity sensors.

I just use IP in the Wifi Gateway preferences.

1 Like

Thanks for the thoughtful replies!

DestinationHostUnreachable

!

I will work on that.

1 Like