I searched for this topic but didn't find my question. I, too, got an Ecobee 3 Lite from the utility company. I installed it, and I was able to use the generic Ecobee app and it works OK. I started to think that I would probably get more wi-fi sensors eventually, so I got an AUVIPAL OTG CABLE and a AC600 TP-LINK Z-WAVE/Wi-Fi ADAPTER and installed them (of course, after installing the wi-fi driver). My question is this: how do I tell if the thermostat is communicating directly with the adapter, or thru the ATT Pace router?
Should I exclude the thermostat already included and then include it again? If so, I need to review how to do that. I think you have to remove it from the Hubitat Dashboard, then exclude it, but I'm not positive.
I was a little skeptical about doing smart home again, and I am surprised that, so far, everything has worked exactly like I read they would.
I do have some questions about some Eaton/Cooper switches, but I'm not sure what category to post them in, any advice?
There are at least three Hubitat ecobee integrations. One built-in, one community integration written by @yracine66, and the second community integration written by @storageanarchy
Because ecobee has no public locally accessible API, all three of these integrations are dependent on accessing ecobee's cloud.
So even if you get your Hubitat a WiFi adapter, it will still only integrate with your ecobee via the cloud.
This is in contrast to WiFi devices like LIFX bulbs. Because these have a locally accessible API, your Hubitat will control them locally - as long as your Hubitat and the bulbs are on the same LAN. Note, your Hubitat can have a wired connected to the router, and it will still control LIFX or YeeLight bulbs locally. As long as they are connected to the same router.
For IP network devices like Ecobee, or LIFX as @aaiyar mentioned, Hubitat doesn’t connect directly to them. It always connects through your router.
Hubitat connects directly to z-wave and zigbee devices.
Thanx guys. The hub is connected to the router via Ethernet, and I used the built in integrator. Are either one of the community written ones better? I'm still learning the tstat and not sure if the built in app is sufficient, actually, I don't even know what data i should be looking at yet.
thanx again
Kinda depends on what you want to do with it. For the basics, the built-in app works fine. I use the Ecobee temperature sensors on dashboards and gauges. I also have some logic that shuts off thermostats to the air conditioners (not controlled by ecobee) when ecobee is in heat mode. Or if ecobee is in heat mode and someone leaves a door or window open... it makes an alexa announcement. Or if we leave the house and set the alarm to away it tells ecobee to go into away mode.
Ecobee sells temperature sensors that work directly with their thermostat. I have three of them in addition to the temperature sensor in the thermostat itself. I doubt that it will be able to use data from other temperature sensors that are not part of the Ecobee system.
Correct. But you can use the ecobee sensors in HE automations!
It can if the thermostat is controlled using a home automation system. As opposed to only using the ecobee ecosystem.
Will any of the integrations actually feed non-ecobee thermostat data back to ecobee for use in its algorithm? Or do you mean you can kind of brute force it with automation?
This.
Finesse it with automation 
