User Tools

Site Tools


supported_hardware:veraui7

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
supported_hardware:veraui7 [2018/07/08 14:39] – [Clear KWH] James Sentmansupported_hardware:veraui7 [2023/02/13 14:52] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ======Vera UI7====== ======Vera UI7======
  
-In the UI7 version of Vera software they switched to a new connection protocolWe still support the older protocol and it still works for the most part so if you are happy with the functioning of your system there is no need to update. Support for the newer UI7 protocol is currently in Beta testing as of XTension version 9.3.11. It seems to be the policy of Vera that they will not fix bugs in the older protocol nor are they going to add support in it for the newer devices or features. This means that if you have a newer device like some of the newer thermostats, or a device with more advanced features than were supported in the older version you will need to update to the new interface in order to use them. If you’re starting a new Vera connection you should start with the Beta version and only fall back if you have a problem. +This page is for the currently support “UI7” version of the XTension pluginIf you’re looking for information on the legacy plugin for older Vera units please see the [[supported_hardware:vera|legacy Vera page]] The legacy plugin is no longer included with the standard XTension distribution so if you wish to continue using it you must install the plugin manually.
 =====Converting an existing Vera Interface===== =====Converting an existing Vera Interface=====
 **It is important that you follow these instructions to convert an existing Vera install to the new protocol!** The new system uses different addressing and device type settings than the old system and you must properly convert your units. A backup of your database is made before the process begins (though you may wish to manually zip up a copy of your database just in case as well) so you can return to the older interface by putting that back if there are problems. As of XTension 9.3.11 there is no way to convert your units back to the old protocol other than doing a lot of manual editing or putting back the previous database. **It is important that you follow these instructions to convert an existing Vera install to the new protocol!** The new system uses different addressing and device type settings than the old system and you must properly convert your units. A backup of your database is made before the process begins (though you may wish to manually zip up a copy of your database just in case as well) so you can return to the older interface by putting that back if there are problems. As of XTension 9.3.11 there is no way to convert your units back to the old protocol other than doing a lot of manual editing or putting back the previous database.
Line 197: Line 196:
 ===Clear KWH=== ===Clear KWH===
 This is for KWH Measurement units and is the same as just telling the unit to turn off. That will reset the KWH reading to 0. You should not have to call this directly but you can if you wish. There is also a contextual menu option to clear a KWH devices value back to 0. Note that not all Vera devices that support sending this value support clearing the value. If your value does not go to 0 after sending this command then the device won’t let you reset it. This is for KWH Measurement units and is the same as just telling the unit to turn off. That will reset the KWH reading to 0. You should not have to call this directly but you can if you wish. There is also a contextual menu option to clear a KWH devices value back to 0. Note that not all Vera devices that support sending this value support clearing the value. If your value does not go to 0 after sending this command then the device won’t let you reset it.
 +
 +===Set Data===
 +The setData command is sent to a specific unit. It is for setting ZWave parameters or variables and is potentially dangerous. Because every brand and model of device is different you’ll have to know exactly what you need to send in order to set the data correctly. Sending incorrect data or data meant for a different device could brick the dimmer or cause any number of kinds of malfunctions. Most manufacturers print the parameter data in their user manuals. but not all of them.
 +
 +This could be used to set the local ramp rate of a dimmer switch, or an of the other configurable options in a device. For the new Home Seer HS-WD200+ dimmer this can be used to change the light color on an individual LED basis. 
 +
 +<code>
 +tell xUnit “name of unit” to setData( parameterNumber, byteCount, value)
 +</code>
 +
 +If the device is a battery operated device then the change will be sent by the Vera when the device next wakes up, if it’s a routing device then the change will be sent immediately. Most parameters i’ve seen are single bytes. The value can be a single integer number from 0 to 255 or might be a longer string of data depending on the parameter. If you have the data in hex instead of an integer you can send a string starting with a letter “x” for example “xFF” for 255.
 +
 +See the supported module section or your user manual for what parameters are available.
  
 ---- ----
supported_hardware/veraui7.1531060789.txt.gz · Last modified: 2023/02/13 14:51 (external edit)