Just added two new Keen vents and things were a little different this time around. My previous five vents behaved as described in the first post on this thread. But new vents are now defaulting to a Stelpro STZB402+ ZigBee Thermostat device type. This has two interesting side effects.
First, Vera now creates a companion temperature device in addition to the thermostat. Second, I know have to change the device_type schema as well or the device wonāt save or configure properly. After a bunch of trail and error, hereās the revised steps that now work for me (copying an abridged version of Nutornās more through steps):
From Veraās main screen go to āDevicesā
Select āAdd Deviceā
Select āGeneric ZigBeeā and begin Veraās three step process
Step 1: Select Your Device
Click ānextā to get started.
Step 2: Pair Your Device
Pull the teal battery strip to power the vent
Click ānextā to begin the pairing process
Once the device is discovered and added you will be prompted to name the device and assign it to a room.
Step 3: Give it a name and assign it to a room.
Step 4: Refresh browser window
Step 5: Access the devicesā āsettingsā and select the āAdvancedā tab. Locate and change the following to match these entries:
device_type = urn:schemas-micasaverde-com:device:WindowCovering:1
device_file = D_WindowCovering1.xml
device_json = D_WindowCovering1.json
You must click outside the fieldās input box for the changes to be sent to the controller. I also had to change the following to match the values shown below:
category_num = 8
subcategory_num = 1
Once done, click the āBackā button and select āSave Changesā. You should now see the deviceās icon has changed to the Window Covering icon and you will have full control of your vent using the āOpenā, āCloseā buttons as well as the percentage slider.
Step 6: Delete the phantom temperature sensor device that was created along with the initial thermostat device. Doing so before you make the other changes seems to make the vent disappear from the Vera UI. This was a big chunk of the trial and error I encountered.
Iām not sure if this change in initial device type is due to some new firmware on later Keen vents, or a change in Vera firmware since then (Iām currently running Version 1.7.3232 on my VeraPlus) but both of my last two vents (received due to a wrong part being sent by Keen) behaved the same way. Hopefully this will save someone else some grief down the road.
it sure would be nice if these vents could be supported as first class devices some day, but these hacks seem to work for now.