Well, yes, you should. But if it helps,I measured my vents and they are 7.5x13.5, and when I took them off just to be certain of the size, the opening was 6x12. So i appears like the standard metal vent cover is 1.5 inches oversized.
If yours is 9.5 inches on one side, that would seem to imply an 8 inch opening, not a six inch. YMMV, of course. If it was me, I would measure before I plunked down a credit card, if only to avoid the return hassle.
Before I had read up on it, I didn’t realize there were two protocols on the same radio (ZHA vs. ZLL) and bought a couple of the Cree Connected bulbs at Home Depot. Seems like the manufacturers don’t want to reveal which protocol they’re using (though I supposed it should be obvious.)
If they are using normal Zigbee even if their configured ZLL, you should be able to reset with Lutron Connected bulb remote and connect ZHA to ST hub. It was fairly easy with Hue although you have to have the right device handler installed.
I’ve been wanting a solution for my house, as it has an odd layout, with a backsplit addition from the 1970s, and only 1 thermostat. So the house was often uneven.
When I saw the Shark Tank pitch I called my wife down and told her they had exactly what we needed.
I jumped in with both feet and ordered enough vents for my entire house… 25 of them.
I received them a month or so ago, with the Keen hub, and the potential was there but the execution of the hub and their software left them next to unusable.
After discovering this thread, I decided to make a last ditch effort of trying out SmartThings to see if that would solve my problems. I ordered a hub plus 5 temp sensors.
The great news is, they synced real easy, have stayed synced, and using Rule Machine (for now), I’ve been able to create some starter automation rules.
So I’m cautiously optimistic this will work out for me.
It’s possible the keen hubs and software will mature with time, but right now they can’t compete with ST. Fortunately ST gives you the best of both worlds.
I’ll update on my progress.
1 Like
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
429
I think most folks are using @yvesracine vent device type. I used it to set the config and reporting parameters, then reverted back to the stock device type.
Here is the customized version to avoid too much battery usage.
See the readme for the installation steps.
There is another version built upon the same config parameters (i.e. polling interval=5 minutes instead of every minute and/or every 1 Farenheits delta detected at the vent)
Hey @Mike_Maxwell, are your vents running local by reverting them back? I know you mentioned the same for the ST sensors, but I wasn’t able to make those work. As soon as I revert them back, the temps are showing as integers again (is that just a tile conversion, I didn’t actually look to see how Keennect sees the temps).
Even if the vents were local qualified, the fact that they are in use by an app that isn’t will disqualify them from local.
I’ve not looked at the temp outputs from the vents.
My motions and other sensors that I changed over to 0.1 F reporting have not reverted.
I know that anything other than Smart Lighting and some parts of SHM doesn’t run locally, was just wondering if the stock vents as devices qualify. I didn’t pay attention when I first installed them. What about the ST sensors, are they listed as local devices after switching back to the stock handler?
I’ve switched them before without issue, it’s only the device hardware config that gets changed, so switching back to a stock local device type works just fine.
Yes, now but I still have them on modified handler. When I tried to switch them back the tiles reverted back to full number. I didn’t have time to check to see if the actual numbers were still captured as .1. I’ll try again tomorrow…