I am not receiving inputs from the GW3000 Weather Station Gateway. Installed Ecowitt RF Sensor and the Ecowitt WiFi Gateway (believe that I have the latest versions). A Warn message is returned which states:
Received data from 192.168.1.35, no matching device found for 192.168.1.35, C0A80123:CE68, 38182BF0AE48 or C0A80123.
HE hub (2.4.3.167) and Ecowitt (V1.1.4) have both been rebooted. Instructions were followed from the Ecowitt WiFi Gateway in GitHub Documentation. I have double checked the values in both HE and Ecowitt.
Guessing that maybe I need an updated driver. Is anyone working on the Ecowitt stuff that could help? or suggestions on what else I can try.
That type of message (from the perspective of my drivers at least) implies that there is no virtual device created that would match the MAC address of the Ecowitt GW3000 that is trying to send data to the Hubitat. Usually, the DNI of the virtual device would have to match the Ecowitt's MAC, but with no ":" and all CAPS.
Ex: Ecowitt MAC = ab:cd:ef:12:34:56 so the DNI should be ABCDEF123456
The Type of the Gateway should be "Ecowitt WiFi Gateway". I assume you are using @sburke781's drivers from the looks of this. Here is the github link to it that has detailed setup instructions, but I think the main thing is the Gateway driver being wrong.
Both @snell and @kahn-hubitat are right about selecting the right driver and configuring the MAC / IP address of the gateway in the device preferences of the gateway device.
If you have not had these configured correctly so far, then I would assume you created the sensor device manually? If that is the case you do not need to do this, the gateway device / driver will create the sensors in HE automatically for you, so you can remove the sensor device.
Anyway - I deleted everything and started over. I ended up with the same error message: Received data from 192.168.1.35, no matching device found for 192.168.1.35, C0A80123:CE68, 38182BF0AE48 or C0A80123.
I change the MAC address and removed the colon between characters as I read this in an earlier post in the community, but this still did not work.
Next, I set the value to the IP address, now HE is receiving the values. (Yes, I checked and double checked the MAC address) - so not sure why I am having issues using the MAC address vs the IP Address.
It could be differences in the driver methods. I do not know @sburke781's driver well, so I could have been off on the MAC recommendation. If it is working now, then that is the main point.
Possibly the same issue I was having. The ecowitt MAC address listed in their app is for the PHYSICAL network adapter and you are probably connecting over wifi. I had to use the MAC for the wifi MAC (it is shown in your syslog or you can look it up in your router connections)
Ecowitt, in their app, was telling me a MAC that ended in "E43" but the actual wifi adapter had an identical MAC that ended in "E40" instead.
To better illustrate, the Eocwitt settings page is on the left, the router entry for the device is on the right. I do not know why Ecowitt fails to identify the MAC that is actually connected to the network. But, the address you want will be the one in your routers entry.
You should also be able to get the correct MAC in the syslog error messages. Took me a second to realize it was off by one digit. But once I saw it, it was a doh moment for me.
Maybe just add a note in the install instructions pointing out that the Ecowitt app (and the bottom of the unit itself) will only show the physical MAC address. Then instruct the individuals who use Wifi to get the MAC from their router's table showing the correct MAC which should only be different in the last digit.
Figured it was a fairly new issue. I think I may have been the only one to report it as of a year ago according to my comment in the main ecowitt thread. I was just suggesting they add a note to avoid this becoming a recurring issue.
The different MAC address was the issue. Since I was only connected via WiFi who would have thought to look at the router to get the correct MAC. (the MAC difference for my device was 48 vs 4B)
Thanks to everyone who has replied. The support of the community is Great!
I am now up and running.
One other thing that I was unaware of is that I was not seeing any values from GW3000, then I noticed an ">" next the Device ID. You have to select the ">" to see the Sensor.
It appears that when they added a physical port, they neglected to tell their users anything other than the physical port (I checked the outside of the packaging, the app, etc.) Luckily for me, the visual difference was easier to see (....43 vs ....40). I can imagine the difference between ....48 and ....4B to be annoyingly easy to miss.
PS.... Did the syslog error in HE include the correct MAC? If not, this may not work.
If so, it is an easy copy paste option for the initial part of set up (since you should start getting those messages after you set up the Ecowitt side and before you get to the preferences in HE)
I think there may be some confusion between the configuration of the physical ecowitt gateway, and the devices created on Hubitat.
The physical ecowitt gateway has a temperature/humidity sensor directly tethered to it. Pertinently, this sensor will show up as a child device in Hubitat to the parent gateway device. And only the child device will be updated with data from the sensor.
Same deal here, swapped out a GW1000 for a GW3000. Reports fine to ecowitt site. Assigned static IP on the GW3000 and router, pings fine. Wont report to Hubitat. All MAC addresses match router. Whats the trick?
I've even found it can be a bit funny sometimes when setting it up, although I haven't done it very often. I think I have had better success with using the MAC address in the Preference setting. Best thing, I find, is to first make sure the data is coming through to Hubitat.
If you did not have a device setup on your HE hub, but the EcoWitt gateway was still successfully sending the data feed, then you would see a warning in the HE logs that includes the various values you can use for the IP / MAC address.
Importantly this warning log appears against the system, not a specific device or app.
I explained this in a bit more detail in an old post on the drivers topic:
Check if you can see this in your HE logs. If you see this message, copy the second last value in the log entry and paste it in the MAC / IP Address setting for the Gateway device on HE, adding in full-colon's in between each two-value pairs (this is the value that starts with 68C6 in my screenshot above, which I would paste as 68:C6:...). If you are not currently seeing this warning in your HE logs, then try turning on the trace level logging in the Preferences for the Gateway device on HE and see if any logs appear. If no trace / debug logs appear, then it is likely the Gateway is not sending the data feed for some reason or it is not arriving at the HE hub.
I might stop there and wait to see where the problem may be...
