MiOS - User contributions [en]

How to connect 3G modem to Vera

2013-02-23T16:11:04Z

Cj man: /*  Possible issues : */

= How to connect a 3G modem to Vera 3 =

This guide applies to Vera 3 units with firmware versions older than 1.5.600. 

== Instructions ==

Connect to the unit by ssh as explained [http://wiki.micasaverde.com/index.php/Logon_Vera_SSH here], then follow these steps: 1. Plug in USB Modem in Vera 

2. Check if the modem is insterted correctly and that vera can see it .
<pre>gcom info /dev/ttyUSBx | x = 0 or 1 </pre>
3. In /etc/config/network add the following :
<pre>config 'interface' 'wan'
option 'ifname' 'eth0.2'
option 'device' '/dev/ttyUSB0'
option 'apn' 'internet'
option 'service' 'umts'
option 'proto' '3g'
</pre>
If the modem has a PIN code add it : 
<pre> option 'pincode' '1234' </pre>
If the modem requires an username and password set it : 
<pre> option username yourusername
option password yourpassword
</pre>
Save and exit

 

4. Check 3G chatscripts ( they are used for the method of connection )
<pre>cat /etc/chatscripts/3g.chat

ABORT BUSY
    ABORT   'NO CARRIER'
    ABORT   ERROR
    REPORT  CONNECT
    TIMEOUT 10
    ""      "AT+CSQ"
    OK      "ATE1"
    OK      'AT+CGDCONT=1,"IP","$USE_APN"'
    SAY     "Calling UMTS/GPRS"
    TIMEOUT 30
    OK      "ATD*99***1#"
    CONNECT ' '
</pre>
 Settings should be like the ones above.

 5. Restart network (be sure to on lan conected to it , not by wan !! IT will not show debugging info )
<pre>/etc/init.d/network restart

BRIDGE ADDBR : brctl addbr br-lan
BRIDGE ADDIF br-lan eth0.1
BRIDGE ADDIF : brctl addif br-lan wlan0
BRIDGE DELIF : brctl delif br-lan
Configuration file: /var/run/hostapd-phy0.conf
Using interface wlan0 with hwaddr 00:0e:XX:XX:XX:XX and ssid 'mios_wifi'
BRIDGE DELIF : brctl delif br-lan wlan0
BRIDGE ADDIF : brctl addif br-lan wlan0
</pre>
6. Watch logread with the following parameters :
<pre>logread -f | grep local2.info </pre>
It should be like this
<pre> Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: abort on (BUSY)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: abort on (NO CARRIER)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: abort on (ERROR)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: report (CONNECT)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: timeout set to 10 seconds
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: send (AT+CSQ^M)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: expect (OK)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: AT+CSQ^M^M
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: +CSQ: 24,99^M
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: ^M
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: OK
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: -- got it
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: send (ATE1^M)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: expect (OK)
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: ^M
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: ATE1^M^M
Feb 15 04:18:15 MiOS_31000000 local2.info chat[11495]: OK
</pre>
 7. Check ifconfig

 

3g-wan Link encap:Point-to-Point Protocol
inet addr:172.22.205.5 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:2671 errors:0 dropped:0 overruns:0 frame:0
TX packets:2449 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1025131 (1001.1 KiB) TX bytes:717822 (700.9 KiB)

 8. Start and stop 3G

To stop it : 
<pre>ifdown wan
</pre>
To start it  : 
<pre>ifup wan </pre>
  If you encounter any issues you can check the logs at : 
<pre>logread -f | grep local2.info </pre>
==  Possible issues : ==

1. Not being able to connect to the modem (on /etc/init.d/network restart -> no such device ) 

'''Cause ''': USB port miss-configuration 

'''Resolution ''':

Type the code below until the USB modem is detected
<pre>gcom info /dev/ttyUSBx
</pre>
Then update the option 'device' '/dev/ttyUSB0' in
<pre>/etc/config/network </pre>
2. 3G (error) PIN code incorrect :

Be sure to set the PIN if it has one, or if it doesn't have one dont set it at all.

3. Remote access doesn't work anymore :

Certain providers block the remote access port, so the unit can't connect anymore to the remote access server.
A possible solution would be to check "FailSafe Tunnels" from Net&Wifi page

How to connect 3G modem to Vera

2013-02-23T16:10:47Z

Cj man: /*  Possible issues : */

How to connect 3G modem to Vera

2013-02-23T14:57:18Z

Cj man:

Source Code

2012-06-07T19:01:14Z

Cj man:

[[Category:Development]]
[[Category:Obsolete]]
----
'''This page is WIP'''
----
Vera is based on OpenWRT. The full source tree for OpenWRT is available at openwrt.org.

We're using the following revisions :

Vera1 : 11404 (https://svn.openwrt.org/openwrt/trunk)

Vera2 : 21644 (svn://svn.openwrt.org/openwrt/branches/backfire)

Our modified OpenWRT bins are : 
broadcom-diag :

Our modified apps are : 
dnsmasq :

Our modified library are : 
libjson :
libupnp :

Source code for Vera's applications: 
version 1.0.602, is available here: http://download.findvera.com/source-1.0.602.tar.gz

This includes DCERouter and some other libraries. The source code for Vera's Z-Wave stack and the router plugins are not included as they include licensed code and were created under NDA's. However these are not needed to extend the functionality of Vera because it is a plugin architecture so the proper way to add new functionality is to create another plugin or DCE device, rather than to add it into one of our existing devices. The binaries with the .602 release match the code, so you should be able to build a new firmware with the OpenWRT source tree + this source code, and add back in the non-open source Vera binaries. Note that the Z-Wave device (/usr/bin/ZWave) is not free or open source; license fees are paid per unit sold.

version 1.5.346, is available here: http://download.mios.com/opensource/source-1.5.346.tar.gz

The exciting part is that our new [[LuaUPnP]] module will largely replace the need for developers to use the C/C++ code. This is a collaborative environment that makes it much easier to extend the functionality of Vera and will facilitate making more powerful applications than building DCE devices. You will be able to do virtually anything you want to extend Vera with the [[LuaUPnP]] module. And any devices created with LuaUPnP will be automatically UPnP devices. Plus you can specify if you want to make the devices available to the community for use, for development, or private.

Originally our plan to help facilitate developers wanting to add-on to Vera was to setup a build server with virtual machines. However we ran into some bugs and performance problems in the virtual machine emulators that made cross-compiling within a VM very difficult. So, we figured our developers' time is better spent on LuaUPnP since that will be a lot more useful tool for developers who want to make their own customizations and add-ons to Vera.

License

2012-06-07T18:37:56Z

Cj man:

[[Category:Glossary]]
[[Category:Development]]
Vera strongly supports the open source movement. Vera is based on Linux and couldn't happen without the contributions of the open source community. All changes to GPL and LGPL are naturally published in compliance with those licenses. When possible, Mi Casa Verde also releases its own code as open source, however, many of the software modules in Vera contain code that was commercially licensed and, thus, cannot be open sourced. 
You can get our source code from here : [[Source_Code]]

Time Syncronization

2012-05-10T13:45:02Z

Cj man: /* Instructions */

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on '''port 37 for rdate''' and '''port 123 for ntpclient''' if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 
'''Note: Please remember to keep the same format of the file when you edit it.'''

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Optionally you can install the ntpclient also. Run the following commands to install the NTP client by ssh: 
<pre>opkg update</pre>
<pre>opkg install ntpclient</pre>

The ntp servers are define in this file : /etc/config/ntpclient

To edit the file you can use '''vim '''editor:
<pre>vim /etc/config/ntpclient</pre>

To view the current entries in it type: 
<pre>cat /etc/config/ntpclient</pre>

'''''Note: Please remember to keep the same format of the file when you edit it.''''' 

Check if Vera can connect to the default ntp servers : 
<pre>BASE_NTP_SRV="openwrt.pool.ntp.org"; for i in 0 1 2 3 5; do NTP_SRV="$i.$BASE_NTP_SRV"; echo -n "$NTP_SRV : "; ntpclient -c 1 -p 123 -h $NTP_SRV || echo "FAILED"; done</pre>

Force ntpclient to re-read the ntp servers and to do a time sync : 
<pre>/etc/init.d/ntpclient restart</pre>
To check if the ntp client is running use this command : 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp</pre>

Time Syncronization

2012-05-10T13:43:33Z

Cj man: /* Instructions */

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 
'''Note: Please remember to keep the same format of the file when you edit it.'''

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Optionally you can install the ntpclient also. Run the following commands to install the NTP client by ssh: 
<pre>opkg update</pre>
<pre>opkg install ntpclient</pre>

The ntp servers are define in this file : /etc/config/ntpclient

To edit the file you can use '''vim '''editor:
<pre>vim /etc/config/ntpclient</pre>

To view the current entries in it type: 
<pre>cat /etc/config/ntpclient</pre>

'''''Note: Please remember to keep the same format of the file when you edit it.''''' 

Check if Vera can connect to the default ntp servers : 
<pre>BASE_NTP_SRV="openwrt.pool.ntp.org"; for i in 0 1 2 3 5; do NTP_SRV="$i.$BASE_NTP_SRV"; echo -n "$NTP_SRV : "; ntpclient -c 1 -p 123 -h $NTP_SRV || echo "FAILED"; done</pre>

Force ntpclient to re-read the ntp servers and to do a time sync : 
<pre>/etc/init.d/ntpclient restart</pre>
To check if the ntp client is running use this command : 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp</pre>

Time Syncronization

2012-05-10T13:41:12Z

Cj man:

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Optionally you can install the ntpclient also. Run the following commands to install the NTP client by ssh: 
<pre>opkg update</pre>
<pre>opkg install ntpclient</pre>

The ntp servers are define in this file : /etc/config/ntpclient

To edit the file you can use '''vim '''editor:
<pre>vim /etc/config/ntpclient</pre>

To view the current entries in it type: 
<pre>cat /etc/config/ntpclient</pre>

'''''Note: Please remember to keep the same format of the file when you edit it.''''' 

Check if Vera can connect to the default ntp servers : 
<pre>BASE_NTP_SRV="openwrt.pool.ntp.org"; for i in 0 1 2 3 5; do NTP_SRV="$i.$BASE_NTP_SRV"; echo -n "$NTP_SRV : "; ntpclient -c 1 -p 123 -h $NTP_SRV || echo "FAILED"; done</pre>

Force ntpclient to re-read the ntp servers and to do a time sync : 
<pre>/etc/init.d/ntpclient restart</pre>
To check if the ntp client is running use this command : 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp</pre>

Time Syncronization

2012-05-10T13:38:32Z

Cj man: /* Installing the NTP client */

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Optionally you can install the ntpclient also. Run the following commands to install the NTP client by ssh: 
<pre>opkg update
</pre> <pre>opkg install ntpclient

The ntp server are define in this file : /etc/config/ntpclient
To edit the file you can use the '''vim '''editor:

<pre>vim /etc/config/ntpclient</pre>
To view the current entries in it type: 
<pre>cat /etc/config/ntpclient
</pre>
 '''''Note: Please remember to keep the same format of the file when you edit it.''''' Check if Vera can connect to the default ntp servers : 

</pre>
<pre>BASE_NTP_SRV="openwrt.pool.ntp.org"; for i in 0 1 2 3 5; do NTP_SRV="$i.$BASE_NTP_SRV"; echo -n "$NTP_SRV : "; ntpclient -c 1 -p 123 -h $NTP_SRV || echo "FAILED"; done
Force ntpclient to re-read the ntp servers and to do a time sync : 
</pre><pre>/etc/init.d/ntpclient restart
</pre>
To check if the ntp client is running use this command : 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp
</pre>

Time Syncronization

2012-05-08T16:45:49Z

Cj man: /* Installing the NTP client */

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Optionally you can install the ntpclient also.
Run the following commands to install the NTP client by ssh: 
<pre>opkg update
</pre> <pre>opkg install ntpclient
</pre><pre>for i in 0 1 2 3; do ntpclient -c 1 -p 123 -h $i.openwrt.pool.ntp.org; done
</pre><pre>/etc/init.d/ntpclient restart
</pre>
To check if the ntp client is running use this command: 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp
</pre>
To edit the ntp.conf file you can use the '''vim '''editor:
<pre>vim /etc/ntp.conf</pre>
To view the current entries in your ntp.conf type: 
<pre>cat /etc/ntp.conf
</pre>
 '''''Note: Please remember to keep the same format of the file when you edit it.'''''

Time Syncronization

2012-05-08T16:17:56Z

Cj man:

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC 858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Run the following commands to install the NTP client by ssh: 
<pre>opkg update
</pre> <pre>opkg install ntpclient
</pre><pre>for i in 0 1 2 3; do ntpclient -c 1 -p 123 -h $i.openwrt.pool.ntp.org; done
</pre><pre>/etc/init.d/ntpclient restart
</pre>
To check if the ntp client is running use this command: 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp
</pre>
To edit the ntp.conf file you can use the '''vim '''editor:
<pre>vim /etc/ntp.conf</pre>
To view the current entries in your ntp.conf type: 
<pre>cat /etc/ntp.conf
</pre>
 '''''Note: Please remember to keep the same format of the file when you edit it.'''''

Time Syncronization

2012-05-08T16:17:20Z

Cj man:

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol and does one time query and synchronization. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' (RFC858) is not related or compatible with '''Network Time Protocol''' (RFC 958) used by ntpclient/ntpd/openntp. 

== Prerequisites ==

*Vera hardware
*Root acces to your OpenWRT

 

== Instructions ==

Gain ssh access to your Vera (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH [1]]

Time Servers are listening on port 37 and Network Time Servers on 123. '''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

Check if Vera can sync with a Time Server : 
<pre>rdate -p server</pre>
''The -p switch prints the date and time from the server''. 

Set the time from a Time Server:
<pre>rdate -l -s server</pre>
''The -l switch allows for logging results to Syslog, -s sets the system time.''

There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here [http://support.ntp.org/bin/view/Servers/WebHome [2]] 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here [http://tf.nist.gov/tf-cgi/servers.cgi# [3]] 

Here is a list of working servers (at this moment):
<pre>nist1.aol-va.symmetricom.com
nist1.columbiacountyga.gov
nist1-atl.ustiming.org
nist1-chi.ustiming.org
nist.expertsmi.com
nisttime.carsoncity.k12.mi.us
nist1-lnk.binary.net
wwv.nist.gov
time.nist.gov
utcnist.colorado.edu
utcnist2.colorado.edu
ntp-nist.ldsbc.edu
nist1-lv.ustiming.org
nist-time-server.eoni.com
nist1.aol-ca.symmetricom.com
nist1.symmetricom.com
nist1-sj.ustiming.org
nist1-la.ustiming.org
</pre>
To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 
<pre>touch /tmp/timeservers.txt
</pre>
Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 
<pre>while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt
</pre>
After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 
<pre>ash -x /usr/bin/sync_time.sh
</pre>
 

== Creating a local time server ==

If you want to create a local time servers you can use '''xinetd '''and you can read more about it here [http://ecloud.org/index.php?title=Rdate_server [4]] 

Once all the settings have been made you need to restart '''xinetd '''by using this command :
<pre>/etc/init.d/xinetd reload
</pre>
== ''' ''' Installing the NTP client ==

Run the following commands to install the NTP client by ssh: 
<pre>opkg update
</pre> <pre>opkg install ntpclient
</pre><pre>for i in 0 1 2 3; do ntpclient -c 1 -p 123 -h $i.openwrt.pool.ntp.org; done
</pre><pre>/etc/init.d/ntpclient restart
</pre>
To check if the ntp client is running use this command: 
<pre>ps fax | grep ntp</pre>
If you see this message then you've successfully installed the NTP client: 
<pre>4188 root 1068 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
14454 root 1672 S grep ntp
</pre>
To edit the ntp.conf file you can use the '''vim '''editor:
<pre>vim /etc/ntp.conf</pre>
To view the current entries in your ntp.conf type: 
<pre>cat /etc/ntp.conf
</pre>
 '''''Note: Please remember to keep the same format of the file when you edit it.'''''

Time Syncronization

2012-05-08T15:03:38Z

Cj man:

The '''Vera '''units use by default '''rdate '''to synchronize the time. 
Rdate is a client program which uses the Time protocol. Rdate servers are running the Time service protocol on '''port 37''' which conforms to RFC 868. Clients can use either TCP or UDP. 
The '''Time Protocol''' is not related or compatible with '''Network Time Protocol''' (RFC 958). This service does one time query and synchronization. 
Rdate use Time Protocol (RFC858) '''which is not compatibile with ntpclinet/openntp''' Network Time Protocol (RFC958). 
Time Servers are listening on port 37 and Network Time Servers on 123. 
'''Note:''' In order for you Vera unit to successfully syncronize its time you have to allow connections from it to the time servers on port 37 for rdate and port 123 for ntpclient if you install it. 

To check the servers used to synchronize time use : 

'''rdate -p server'''

''The -p switch prints the date and time''. 

To set the time from that server use this command:

'''rdate -l -s server'''

''The -l switch allows for logging results to Syslog, -s sets the system time.''

 There is no worldwide list of Time servers available. Many, but not all, Network Time Protocol (NTP) servers also serve Time on port 37. There is a list of NTP servers here : http://support.ntp.org/bin/view/Servers/WebHome 

The National Institute of Standards and Technology (United States Gov't) offers about a dozen Time servers to the public. Their server list is available here: http://tf.nist.gov/tf-cgi/servers.cgi# 

Here is a list of working servers (at this moment):

 

nist1.aol-va.symmetricom.com nist1.columbiacountyga.gov nist1-atl.ustiming.org nist1-chi.ustiming.org nist.expertsmi.com nisttime.carsoncity.k12.mi.us nist1-lnk.binary.net wwv.nist.gov time.nist.gov utcnist.colorado.edu utcnist2.colorado.edu ntp-nist.ldsbc.edu nist1-lv.ustiming.org nist-time-server.eoni.com nist1.aol-ca.symmetricom.com nist1.symmetricom.com nist1-sj.ustiming.org nist1-la.ustiming.org 

 

To test on your '''Vera '''unit which servers are working, log in by ssh and then create a new file called timeservers.txt in /tmp with this command : 

'''touch /tmp/timeservers.txt''' 

Then edit it and copy the servers from the list using vim, and then run this command at least 5 times : 

'''while read server; do echo -n "Server $server :"; rdate -p $server && echo "OK" || echo "FAILED"; done < /tmp/timeservers.txt ''' 

After that compare the results and pick the servers that only display OK, these will be the most reliable, and then add them to the list here /etc/config/timeserver . 

To sync the time use the following command : 

''' ash -x /usr/bin/sync_time.sh''' 

 

'''Creating a local timeserver'''

 If you want to create a local time servers you can use '''xinetd '''and you can read more about it here http://ecloud.org/index.php?title=Rdate_server 

Once all the settings have been made you need to restart '''xinetd '''by using this command :

'''/etc/init.d/xinetd reload ''' 

 

<span style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;" id="internal-source-marker_0.35288017772422464">How to install NTP: 

Please use these commands to install NTP:

opkg update opkg install ntpclient for i in 0 1 2 3; do ntpclient -c 1 -p 123 -h $i.openwrt.pool.ntp.org; done /etc/init.d/ntpclient restart ps fax | grep ntp 

After the last command you should see this in the console:

 14188 root      1068 S    /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org 14454 root      1672 S    grep ntp

If you do then you've successfully installed the NTP client on your Vera unit.

Release Notes

2010-05-18T13:09:30Z

Cj man: /* Unreleased fixes */

== Unreleased fixes ==

1. Fix problems with getting alerts for both 'over' and 'under' a certain temperature

2. Fix problem with getting an 'over' and 'under' temperature alert every time the sensor reports the temperature

3. Automatically set the clock on ZWave devices that support COMMAND_CLASS_CLOCK

4. Fix compatibility with the Fortrezz water valve

5. Fix problem where sometimes you can't remove a dead node

6. Fix one Vera importing and controlling the devices from another.

7. Fix one Vera controlling other UPnP devices.

8. Change the way the version is reported so it's compatible with a new SQ Remote update

9. Fix a problem with include/exclude ZWave not working when using the buttons while Vera is disconnected from the network

10. Strip UPNP XML files of any non-standard characters (like accented characters) since this can cause some upnp scanners, like Device Spy, to ignore them.

----------- After 996

11. Occasionally a device that was properly configured could show as incorrectly configured if it failed to config and then was immediately reconfigured and succeeded the 2nd time before the 1st failure had been purged from the log.

12. Fortrezz Water + Temp sensor now supports both events.

13. Scenes can be 'active' or 'inactive' based on either 2 settings: 1) all devices in the scene are set, or 2) any device in the scene is on.

14. Automatically set the LED's in a Leviton scene controller based on #13

15. Fix a crash while logging DHCP requests

16. Don't try to configure a node right away if it failed configuration on the last attempt to reduce long latency caused by continuously reconfiguring dead nodes.

17. Migrate to the new server structure with redundannt servers

18. Add ability to do ZWave multi-cast.

19. Fix a bug where it got stuck retrying to download plugins despite a network failure.

20. Set default root password to the same as the Wifi Password/ HouseID, so telnet is disabled now by default.

== 1.1.319 and 1.0.994 - April 21, 2010 - final UI2 and UI3 ==

Both versions, 1.1.319 and 1.0.994, have the same back end engine. The difference is 1.0.994 has the older web html & javascript user interface (UI2), and 1.1.319

1. [[http://bugs.micasaverde.com/view.php?id=739 Bug 739]]: Fix an intermittent problem with 'handler not found' error when trying to access the smartphone or WAP plugin

2. Fix an error with pan/tilt buttons on a camera not working

3. Add support for the Kwikset ZWave lock's built-in scheduling

4. Improve configuring a Schlage lock. We discovered a 'hidden' configuration setting you can use to get all the user codes states at once rather than polling each code individually as per the official ZWave spec.

5. Correct the reporting of lock/unlock on the Schlage deadbolt. Previously if a lock or unlock was sent to the deadbolt and the deadbolt reported it was executed OK, Vera assumed the lock was really locked/unlocked. Now we use the alarms from the lock instead so the state is always accurate.

6. Fix so the include/exclude mode when triggered with the physical buttons stays on indefinitely.

7. For advanced users, add capability to send door lock NONCE's with ACK by adding the UPNP variable urn:micasaverde-com:serviceId:ZWaveDevice1/NonceACK=1

8. Unmount the filesystem and kill all processes before flashing the firmware. Also report to a central server when the process starts, and when it reboots after an upgrade so we have a log to accurately measure how often an upgrade fails. We're trying to reduce the number of instances where Vera's firmware gets messed up during an upgrade. This process of upgrading isn't in our code, actually. It's part of the base Linux distro (OpenWRT), and, officially, the only way it should ever happen unless the user pulls the plug while the firwmare is being written, or a brown out. However we have had users experience it even though they insist the power was on steady during the whole firmware write process.

9. For UI3 the problems with drag and drop are solved, and there's a new list view if you don't like the floorplan view. Several other cosmetic and usability issues have been fixed by the Flash team.

10. Fix reset_to_factory_default script, it deleted some required files for the user manual. Now deletes only certain files.

11. Add default free dns servers: OpenDNS.org

== 1.0.979 - October 24, 2009 - final beta ==

All known issues of stability and memory leaks have now been resolved. The infrared and INSTEON/X10 modules are also fully functioning. The next couple weeks we will closely monitor the forums and trouble tickets to see if there are any lingering issues and then issue a release candidate.

'''Fixes:'''

0. '''IMPORTANT:''' The concept of method #1 and method #2 for programming scenes into scene controllers and handheld remotes no longer exists. The 'Treat Scenes as Events' checkbox is no longer used. Now, to assign a scene, select the scene, click 'Add Event', choose the scene controller or handheld remote, choose the event 'A Scene is Activated', and pick the scene or button ID, such as 3 for button 3 on a scene controller. Any Up/Down or Off buttons now work fine, plus you can add thermostats, door locks, and other non-scene devices to a scene and Vera will still trigger them. So with release 979, it's all automatic and you no longer have to make a decision for method #1 or method #2, and there is no longer a sacrifice with one method over the other. The [[ZWave_Add_Controller]] page has been updated.

1. There was a file handle leak with files in /tmp that were deleted but not closed. This caused the system to run out of resources and crash after a few days.

2. [[http://bugs.micasaverde.com/view.php?id=666 Bug 666]]: Unable to control the Panasonic BL-C131A camera after upgrading to version 1.0.939

3. [[http://bugs.micasaverde.com/view.php?id=682 Bug 682]]: can't add an ir device

4. [[http://bugs.micasaverde.com/view.php?id=671 Bug 671]]: associate light switches with scene controllers

5. [[http://bugs.micasaverde.com/view.php?id=625 Bug 625]]: confirm specific user code notification works. Now you get the name of the user code entered on a Schlage lock in the notification

6. [[http://bugs.micasaverde.com/view.php?id=610 Bug 610]]: ha09 and method 0000001 not working

7. [[http://bugs.micasaverde.com/view.php?id=598 Bug 598]]: handle missing variables in smartphone

8. [[http://bugs.micasaverde.com/view.php?id=597 Bug 597]]: add buttons to window controller

9. [[http://bugs.micasaverde.com/view.php?id=572 Bug 572]]: Prevent Timers to run if date is not correct

10. [[http://bugs.micasaverde.com/view.php?id=638 Bug 638]]: Unable to add manually Panasonic IP camera easely

11. [[http://bugs.micasaverde.com/view.php?id=631 Bug 631]]: combine method 0000001 and method 0000002

12. [[http://bugs.micasaverde.com/view.php?id=634 Bug 634]]: job icons

13. [[http://bugs.micasaverde.com/view.php?id=640 Bug 640]]: Camera PTZ broken in 899 and it keeps to be broken if you upgrade to 918

14. [[http://bugs.micasaverde.com/view.php?id=641 Bug 641]]: Files from /etc/cmh-lu/ and /etc/cmh-ludl/ are not updated accordingly between firmware updates

15. [[http://bugs.micasaverde.com/view.php?id=630 Bug 630]]: info panel not showing BACKUP jobs

16. [[http://bugs.micasaverde.com/view.php?id=618 Bug 618]]: get rid of hardcoded filenames using FK instead

17. [[http://bugs.micasaverde.com/view.php?id=627 Bug 627]]: temperature event not working

18. [[http://bugs.micasaverde.com/view.php?id=596 Bug 596]]: after saving the info panel isn't updated

19. [[http://bugs.micasaverde.com/view.php?id=636 Bug 636]]: IP CAMERA CONTROLS NOT WORKING IN IE

20. [[http://bugs.micasaverde.com/view.php?id=475 Bug 475]]: need an input box on the iphone and wap ui

21. [[http://bugs.micasaverde.com/view.php?id=458 Bug 458]]: backup/restore zwave dongle's firmware

Release Notes

2010-04-27T12:50:59Z

Cj man: /* 1.1.319 and 1.0.994 - April 21, 2010 - final UI2 and UI3 */

== Unreleased fixes ==

1. Fix problems with getting alerts for both 'over' and 'under' a certain temperature

2. Fix problem with getting an 'over' and 'under' temperature alert every time the sensor reports the temperature

3. Automatically set the clock on ZWave devices that support COMMAND_CLASS_CLOCK

4. Fix compatibility with the Fortrezz water valve

5. Fix problem where sometimes you can't remove a dead node

== 1.1.319 and 1.0.994 - April 21, 2010 - final UI2 and UI3 ==

Both versions, 1.1.319 and 1.0.994, have the same back end engine. The difference is 1.0.994 has the older web html & javascript user interface (UI2), and 1.1.319

1. [[http://bugs.micasaverde.com/view.php?id=739 Bug 739]]: Fix an intermittent problem with 'handler not found' error when trying to access the smartphone or WAP plugin

2. Fix an error with pan/tilt buttons on a camera not working

3. Add support for the Kwikset ZWave lock's built-in scheduling

4. Improve configuring a Schlage lock. We discovered a 'hidden' configuration setting you can use to get all the user codes states at once rather than polling each code individually as per the official ZWave spec.

5. Correct the reporting of lock/unlock on the Schlage deadbolt. Previously if a lock or unlock was sent to the deadbolt and the deadbolt reported it was executed OK, Vera assumed the lock was really locked/unlocked. Now we use the alarms from the lock instead so the state is always accurate.

6. Fix so the include/exclude mode when triggered with the physical buttons stays on indefinitely.

7. For advanced users, add capability to send door lock NONCE's with ACK by adding the UPNP variable urn:micasaverde-com:serviceId:ZWaveDevice1/NonceACK=1

8. Unmount the filesystem and kill all processes before flashing the firmware. Also report to a central server when the process starts, and when it reboots after an upgrade so we have a log to accurately measure how often an upgrade fails. We're trying to reduce the number of instances where Vera's firmware gets messed up during an upgrade. This process of upgrading isn't in our code, actually. It's part of the base Linux distro (OpenWRT), and, officially, the only way it should ever happen unless the user pulls the plug while the firwmare is being written, or a brown out. However we have had users experience it even though they insist the power was on steady during the whole firmware write process.

9. For UI3 the problems with drag and drop are solved, and there's a new list view if you don't like the floorplan view. Several other cosmetic and usability issues have been fixed by the Flash team.

10. Fix reset_to_factory_default script, it deleted some required files for the user manual. Now deletes only certain files.

11. Add default free dns servers: OpenDNS.org

== 1.0.979 - October 24, 2009 - final beta ==

All known issues of stability and memory leaks have now been resolved. The infrared and INSTEON/X10 modules are also fully functioning. The next couple weeks we will closely monitor the forums and trouble tickets to see if there are any lingering issues and then issue a release candidate.

'''Fixes:'''

0. '''IMPORTANT:''' The concept of method #1 and method #2 for programming scenes into scene controllers and handheld remotes no longer exists. The 'Treat Scenes as Events' checkbox is no longer used. Now, to assign a scene, select the scene, click 'Add Event', choose the scene controller or handheld remote, choose the event 'A Scene is Activated', and pick the scene or button ID, such as 3 for button 3 on a scene controller. Any Up/Down or Off buttons now work fine, plus you can add thermostats, door locks, and other non-scene devices to a scene and Vera will still trigger them. So with release 979, it's all automatic and you no longer have to make a decision for method #1 or method #2, and there is no longer a sacrifice with one method over the other. The [[ZWave_Add_Controller]] page has been updated.

1. There was a file handle leak with files in /tmp that were deleted but not closed. This caused the system to run out of resources and crash after a few days.

2. [[http://bugs.micasaverde.com/view.php?id=666 Bug 666]]: Unable to control the Panasonic BL-C131A camera after upgrading to version 1.0.939

3. [[http://bugs.micasaverde.com/view.php?id=682 Bug 682]]: can't add an ir device

4. [[http://bugs.micasaverde.com/view.php?id=671 Bug 671]]: associate light switches with scene controllers

5. [[http://bugs.micasaverde.com/view.php?id=625 Bug 625]]: confirm specific user code notification works. Now you get the name of the user code entered on a Schlage lock in the notification

6. [[http://bugs.micasaverde.com/view.php?id=610 Bug 610]]: ha09 and method 0000001 not working

7. [[http://bugs.micasaverde.com/view.php?id=598 Bug 598]]: handle missing variables in smartphone

8. [[http://bugs.micasaverde.com/view.php?id=597 Bug 597]]: add buttons to window controller

9. [[http://bugs.micasaverde.com/view.php?id=572 Bug 572]]: Prevent Timers to run if date is not correct

10. [[http://bugs.micasaverde.com/view.php?id=638 Bug 638]]: Unable to add manually Panasonic IP camera easely

11. [[http://bugs.micasaverde.com/view.php?id=631 Bug 631]]: combine method 0000001 and method 0000002

12. [[http://bugs.micasaverde.com/view.php?id=634 Bug 634]]: job icons

13. [[http://bugs.micasaverde.com/view.php?id=640 Bug 640]]: Camera PTZ broken in 899 and it keeps to be broken if you upgrade to 918

14. [[http://bugs.micasaverde.com/view.php?id=641 Bug 641]]: Files from /etc/cmh-lu/ and /etc/cmh-ludl/ are not updated accordingly between firmware updates

15. [[http://bugs.micasaverde.com/view.php?id=630 Bug 630]]: info panel not showing BACKUP jobs

16. [[http://bugs.micasaverde.com/view.php?id=618 Bug 618]]: get rid of hardcoded filenames using FK instead

17. [[http://bugs.micasaverde.com/view.php?id=627 Bug 627]]: temperature event not working

18. [[http://bugs.micasaverde.com/view.php?id=596 Bug 596]]: after saving the info panel isn't updated

19. [[http://bugs.micasaverde.com/view.php?id=636 Bug 636]]: IP CAMERA CONTROLS NOT WORKING IN IE

20. [[http://bugs.micasaverde.com/view.php?id=475 Bug 475]]: need an input box on the iphone and wap ui

21. [[http://bugs.micasaverde.com/view.php?id=458 Bug 458]]: backup/restore zwave dongle's firmware

Help:Contents

2010-04-16T13:55:54Z

Cj man:

For any users help and discussions please use our forum boards located at: [http://forum.micasaverde.com http://forum.micasaverde.com]

IP Cameras

2010-03-26T18:07:57Z

Cj man: /* Cameras that work */

If you buy an IP camera from Mi Casa Verde, we will pre-configure it to work with Vera right out of the box. If you get the camera yourself, and it's a model that is 'Plug and Play' compatible with Vera (see 'Supported Cameras' below), then you should be sure the camera is configured to get an IP address automatically, and that the username is set to: '''dceadmin''' and the password is set to: '''dcepass'''. Vera will add the camera automatically and fill in the settings. (Specific info for users of [[Panasonic IP Cameras|Panasonic IP Cameras]])  When adding a camera that is not on the supported list, see the section ''''Manually adding a camera'''' below.

=== '''Supported Cameras''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Notes
|-
| Panasonic
| IP Camera
| BL-C131/BL-C30
| all
| 
| Indoor
| 
| 
| The Panasonic IP cameras work well with Vera. However, for unknown reasons, the Panasonic camera will not get an IP address on your LAN until you run the Windows software supplied with it. You do not need to install the software; just insert the CD and tell the camera to get an IP address automatically (DHCP). If you buy the camera from the Mi Casa Verde web shop we do this before we ship it so the camera will work out of the box. Mac/Linux users who buy the camera elsewhere will need a Windows PC to 'activate' the camera. Set the default username/password on the camera to: dceadmin and dcepass for Vera to detect the camera automatically, or, if you use your own username/password, add the camera to Vera manually and provide Vera your username/password to access the camera.
|}

=== '''Cameras that work''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Notes
|-
| Linksys
| IP Camera
| WVC54GCA
| all
| 2009
| Indoor
| img/snapshot.cgi
| 
| An inexpensive camera with moderate image quality. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address.
|-
| Linksys
| IP Camera
| WVC210
| all
| 2009
| Indoor
| img/snapshot.cgi
| 
| A more expensive camera with good image quality and pan/tilt ability. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address. Pan/tilt controls will not work with Vera.
|-
| Linksys
| IP Camera
| WVC80N
| all
| 2009
| Indoor
| img/snapshot.cgi?size=2&quality=1
| 
| A more expensive camera with good image quality and wireless N. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address. Pan/tilt controls will not work with Vera.
Size can be (160 x 120 = 1,320 x 240 = 2,640 x 480 = 3) and Quality can be (Very High= 1,High= 2,Normal= 3,Low= 4,Very Low= 5)
|-
| iCamView
| IP Camera Server
| iCV-22, iCV-32
| all
| 2009 
| Indoor/Outdoor
| pda.cgi?user=admin&password=1234&page=image&cam=1 pda.cgi?user=admin&password=1234&page=image&cam=2 
| 
| Feature-rich IP camera server, suports up to two compatible USB cameras, optional WiFi support, USB storage, USB hubs, motion; works with range of cameras, see icamview.co.uk. Excellent modular solution. They do ship to North America.
|-
| SmartHome.com.au
| IP Camera
| Z~Series Wireless Camera
| all
| 2009 
| Indoor
| tmpfs/auto.jpg
| 
| Inexpensive IP security camera designed for the Australian and New Zealand Z-Wave users, but shipping world wide.
|-
| [http://global.level1.com LevelOne]
| IP Camera
| WCS-2030
| all
| 2010
| Indoor
| cgi-bin/video.jpg
| [http://reviews.cnet.com/search-results/levelone-camcon-wcs-2030/1707-5_7-31972011.html CNET review]
| An inexpensive IP camera with good image quality. Can be connected wired or wirelessly. Most LevelOne cameras use the same path for the JPEG image, so most of their line (both low and high end) should be compatible. Video and audio also stream over RTSP, which can be customized through the camera's web interface.
|}

=== '''Cameras that don't work''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Added by
! Notes
|-
| Trendnet
| IP Camera
| TV-IP100W
| all
| 2007 
| Indoor
| none 
| 
| 
| This camera can only serve images using DirectX or Java. The workaround is complex: "using a PC you can use MPlayer to strip out a JPG image from the video stream (asf). You can then store the JPG snapshot on a PC, then run a web server and vera can then "fetch" the image from the PC instead of the camera."
|-
| D-Link
| IP Camera
| DCS-950G
| firmware 1.07
|  ?
| Indoor
| /_gCVimage.jpg
|
| Ap15e
| It takes about 9(!) seconds to get the jpg file from the camera, but Vera's generic Luup IP camera plugin times out after 5 seconds (FileUtils::ReadURL url: http://192.168.178.28/_gCVimage.jpg returned 28 /curl: (28) Operation timed out after 5000 ms with 0 bytes received) ...
|-
| Schlage
| IP Camera
| WCW100
| all
| 2010
| Indoor
| none
|
| Ray
| This camera does not give an IP address out of the box. In order for it work, it needs to be activated using the Schlage LiNK system. Without paying for the Schlage LiNK membership, this camera cannot be used with Vera unless there's a way of forcing the activation.
|-
| Asante
| IP Camera
| Voyager I
| firmware 2.00
| 2010
| Indoor
| none
|
| Ray
| This camera is inexpensive, very feature rich, has very good image quality, and has night vision capabilities. However, there is no publically accessible URL to grab a live JPG from the camera. The web interface requires an ActiveX plug-in to view the live video feed and there is a snapshot button that will deliver a JPG. Asante is reportedly making changes to their camera in the next version of the firmware that should resolve some of these issues.
|}

=== '''Manually adding a camera''' ===

[[Image:Camera1.jpg|thumb|center|512px]] [[Image:Camera2.jpg|thumb|center|512px|Manually adding a camera]]

In Vera's setup page click Devices, Luup plugins, Install/uninstall plugins, and click 'install' next to either the 'Generic IP Camera' plugin, or, if you see a plugin for your particular camera, such as 'Panasonic IP Camera with Pan/Tilt/Zoom' use that instead.

If you have more than one camera, you can click "install another" to have multiple instances of the plugin.

In most cases, IP cameras have a URL method for obtaining a SNAPSHOT or JPG image from the camera. If your camera supports this method, you can then use it with Vera and the FindVera.com service can archive these snapshots over time for security purposes. Most IP/Network cameras made in the past few years will have a JPG Snapshot mode. Some examples from Linksys are WVC54GCA, WVC200/WVC210.  D-link, Trend-Net, and many others make similar cameras.

If your camera is not a 'Plug and Play' model or not on the supported list, you need to specify the settings for the camera by going to the 'Devices' tab on Vera's setup page, adding the camera if it's not already there, and clicking the '+' icon to edit the camera's settings.

You will need to specify:

1. the IP address or domain name of the camera 2. the URL or path to retrieve the current image from the camera as a JPEG file 3. any username and password to retrieve the JPEG file

The URL (your camera's manual may denote this as "path" or "snapshot address") needs to retrieve the actual JPEG file, not just an HTML page that has the JPEG file somewhere on it. For example, if you can view a JPEG file from your camera with this URL: '''http://192.168.81.5/Snapshot.JPG?Quality=Standard''', then put in these settings:

IP Address: '''192.168.81.5''' Path: '''Snapshot.JPG?Quality=Standard'''

and be sure to provide the username/password if one is needed. After you specify this information, click the red 'Save' button, and then you can see the camera by clicking the 'View Camera' option.

=== '''Configuring the Panasonic IP camera to connect wirelessly to Vera''' ===

The Panasonic IP Cameras have a switch on the bottom: WIRED/WIRELESS. In order to connect your camera wirelessly to Vera, you'll need to follow these steps:

- set the switch to WIRED
- connect your camera to Vera's LAN port using an Ethernet cable
- turn the camera on, confirm Vera's LAN LED turns orange, and wait for the IP Cam LED to turn green
- wait for the camera to be detected in Devices -> Unassigned Device
- assign the camera to a 'Room' and click 'Save'
(for the camera to be detected it should have the default username/password: dceadmin/dcepass and listen on port 80)
- confirm that you can see images from the camera
- click on the "+" sign near your camera and note its IP address (e.g. 192.168.81.200)

- connect your computer to the same network as your camera
- open your web browser and type in: http://camera1_ip (in this example, http://192.168.81.200)
- login with the default camera username: dceadmin and password: dcepass
- go to Setup -> Wireless and set SSID, Cipher and Password to Vera's wireless settings
which can be found an the bottom of Vera. (default Cipher is WPA2-PSK)
- click 'Save Settings'
- turn the camera's bottom switch to WIRELESS and reboot your camera by cycling its power

Your camera should now connect wirelessly to Vera. If you change your Vera's wireless settings you'll have first to update them on your cameras, so you won't lose connection to them.

=== Example of using a Linksys WVC54GCA or WVC210 camera with Vera ===

For example, if you can view a JPEG file from your camera with this URL: http://192.168.81.5/img/snapshot.cgi, then put in these settings: Domain or IP: 192.168.81.5 (or ''YourDomain.MyLinksysCam.com'' if remote access is enabled) Path: img/snapshot.cgi A username and password must be used unless all users are allowed in the USERS section. 

*If you have more than one camera, you will be using the PORT as part of the URL. If your second camera is on PORT 1024 and the IP is 192.168.81.6, you would use 192.168.81.6:1024 or YourDomain.MyLinksysCam.com:1024

 

=== iCAMView and some Lorex network cameras ===

For [http://www.icamview.co.uk iCAMView] based cameras, including a few Lorex-branded ones, the path would be: <tt>showimg_pda.cgi?cam=1 for the first camera</tt> <tt>showimg_pda.cgi?cam=2 for the second camera</tt> 

Older models may require slightly different path: <tt>pda.cgi?cam=1 for the first camera</tt> <tt>pda.cgi?cam=2 for the second camera</tt> 

Other parameters would be the same as above.

=== Axis IP Cameras ===

Path: axis-cgi/jpg/image.cgi (or ''lastshot.jpg'' depending of the model) More information here: [http://www.axis.com/techsup/cam_servers/tech_notes/live_snapshots.htm Axis live_snapshots] [http://www.axis.com/techsup/cam_servers/cam_200p/techoverview.htm Axis techoverview]

Firmware Flash Vera 1

2010-02-24T22:58:55Z

Cj man:

= Please note: This is working only for Vera 1 (Asus) platform. =

{| width="653" cellspacing="1" cellpadding="1" border="1" align="center" style=""
|-
| Vera 1 (Asus)
| Vera 2 
|-
| [[Image:VeraFrontQSG.png|center|320x240px|Vera Hardware Version 1]]
| [[Image:Vera Hardware v2.jpg|center|320x240px]]
|}

 

If Vera's power light blinks consistently (not a double pulsing blink) within a few seconds of powering on, then Vera's firmware has become corrupted. This can happen if Vera was unplugged while in the middle of performing a firmware update ("flash"). When it does, you will probably need to use a firmware restoration utility, which runs on Windows. Here is how to restore Vera's firmware once it has become corrupted:

Please note: This is working only for Vera 1 (Asus) platform.

= PC ( Windows version ) =

1. Download Vera's firmware and store it on your PC's hard drive. You can get the firmware here:

UI2 - v.1.0.979 http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx

UI2 - v.1.0.985 http://download.findvera.com/betafirmware/ftp/wl500gP_Luup_ui2-1.0.985-1.trx

UI3 - v.1.1.288 http://download.findvera.com/betafirmware/ftp/wl500gP_Luup_ui3-1.1.228-1.trx

2. Download the firmware restoration utility and unzip it into a folder on your PC. The utility is here: http://download.controlmyhouse.net/flash_firmware.zip

3. Connect your PC's network connection the LAN 1 port of Vera. (It must be LAN 1, not any of the other LAN ports.)

4. Give your PC a static IP: 192.168.1.2, with subnet mask 255.255.255.0. You can leave the Gateway and DNS server blank. To do this in Windows XP, choose Start, Control Panel, Network Connections. Be sure all connections are disabled except for "Local Area Connection", which you right-click on and choose Properties. Scroll down to "Internet Protocol (TCP/IP)" and click Properties. Make note of the current settings so you can restore them when you're done. Choose "Use the following IP address", and put 192.168.1.2 in the IP address field and 255.255.255.0 in the subnet mask. Leave the other fields alone. Click 'OK' to close the window, and then 'OK' on the other window.

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code.

6. Unplug the power to Vera. Hold the black button in while you reconnect the power. Let go of the black button when the power light starts blinking.

7. Click 'upload' in the firmware utility. It takes up to 5 minutes to flash the firmware. 

'''Note'''

(*) The rescue utility is known to work only on Windows XP and with only ONE network card (disable wireless and other network cards if your computer has any)

= Mac OS Version =

Tested it on one of our test unit. It worked and should work for you as well if you follow exactly the instructions.
First, download the firmware version http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx and put it somewhere in the root directory of your Mac or another place and remember the path.

Notes: Now, you may need to manually specify your computers IP address as discussed in the previous mails (in order to use tftp to upload the files) if for some reason DHCP is not working. I also did this by entering the following settings:

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html

* '''Step 1''': Connect your computer via ethernet cable to LAN port 1
* '''Step 2''': Unplug the power cord from the router
* '''Step 3''': Wait 20 seconds
* '''Step 4''': Press and hold the reset button on the back of the router. Note that the reset button is recessed and you need a pen or paper clip to press it in. The button protruding from the back is the EZ Setup, which is not what you want to press.
* '''Step 5''': While holding the reset black button, plug the power cord into the router. Continue to hold the reset button until the power light starts flashing. Let go of the reset button.
* '''Step 6''': Can be done using 1) Terminal.app (command line) or 2) TFTP client with GUI.

1) Start Terminal.app (inside /Applications/Utilities) and go to the directory where you have saved that file (cd /your/directory/).

Then use this commands:
user@box:$ tftp 192.168.1.1
> mode binary
> trace
> put wl500gP_Luup-1.0.979.trx

2) You can download MacTFTP Client from http://www.versiontracker.com/dyn/moreinfo/macosx/8122 for example.

Start MacTFTP, type "192.168.1.1" inside the Address field.
Click on the "File..." button and select the firmware file you want to update Vera with and click "Start".
Wait for completion and proceed to next step.

* '''Step 7''': Tftp should report a successful file transfer in 10-20 seconds. The router will load the firmware and begin to flash it into nvram. During this time, the power indicator on the router will go out. Wait until this light comes back on, or wait at least 8 minutes for the flashing process to complete. If the power indicator has not come back on after 8 minutes, cycle the power on the router.
*'''Step 8''': Unplug the power cord from the router, wait 20 seconds, and plug the power cord back into the router WITHOUT PRESSING THE BLACK BUTTON. In less than a minute, your Vera is up.

The Vera should now boot to the new firmware. Go to 192.168.1.1 or 192.168.81.1 to confirm. You may need to power cycle your cable modem (if applicable) to get an internet connection and setup the network to automatically get settings via DHCP again.

This is the Mac OS version of the firmware restoration since the engineers from Asus didn't release an application to do this.

Also, read this posted on opewrt site: http://nuwiki.openwrt.org/oldwiki/OpenWrtDocs/Hardware/Asus/Flashing

Firmware Flash Vera 1

2010-02-24T21:49:09Z

Cj man: /* Please note: This is working only for Vera 1 (Asus) platform. */

= Please note: This is working only for Vera 1 (Asus) platform. =

{| width="653" cellspacing="1" cellpadding="1" border="1" align="center" style=""
|-
| Vera 1 (Asus)
| Vera 2 (Sercomm)
|-
| [[Image:VeraFrontQSG.png|center|320x240px|Vera Hardware Version 1]]
| [[Image:Vera Hardware v2.jpg|center|320x240px]]
|}

 

If Vera's power light blinks consistently (not a double pulsing blink) within a few seconds of powering on, then Vera's firmware has become corrupted. This can happen if Vera was unplugged while in the middle of performing a firmware update ("flash"). When it does, you will probably need to use a firmware restoration utility, which runs on Windows. Here is how to restore Vera's firmware once it has become corrupted:

Please note: This is working only for Vera 1 (Asus) platform.

= PC ( Windows version ) =

1. Download Vera's firmware and store it on your PC's hard drive. You can get the firmware here:

UI2 - v.1.0.979 http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx

UI2 - v.1.0.985 http://download.findvera.com/betafirmware/ftp/wl500gP_Luup_ui2-1.0.985-1.trx

UI3 - v.1.1.288 http://download.findvera.com/betafirmware/ftp/wl500gP_Luup_ui3-1.1.228-1.trx

2. Download the firmware restoration utility and unzip it into a folder on your PC. The utility is here: http://download.controlmyhouse.net/flash_firmware.zip

3. Connect your PC's network connection the LAN 1 port of Vera. (It must be LAN 1, not any of the other LAN ports.)

4. Give your PC a static IP: 192.168.1.2, with subnet mask 255.255.255.0. You can leave the Gateway and DNS server blank. To do this in Windows XP, choose Start, Control Panel, Network Connections. Be sure all connections are disabled except for "Local Area Connection", which you right-click on and choose Properties. Scroll down to "Internet Protocol (TCP/IP)" and click Properties. Make note of the current settings so you can restore them when you're done. Choose "Use the following IP address", and put 192.168.1.2 in the IP address field and 255.255.255.0 in the subnet mask. Leave the other fields alone. Click 'OK' to close the window, and then 'OK' on the other window.

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code.

6. Unplug the power to Vera. Hold the black button in while you reconnect the power. Let go of the black button when the power light starts blinking.

7. Click 'upload' in the firmware utility. It takes up to 5 minutes to flash the firmware. 

'''Note'''

(*) The rescue utility is known to work only on Windows XP and with only ONE network card (disable wireless and other network cards if your computer has any)

= Mac OS Version =

Tested it on one of our test unit. It worked and should work for you as well if you follow exactly the instructions.
First, download the firmware version http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx and put it somewhere in the root directory of your Mac or another place and remember the path.

Notes: Now, you may need to manually specify your computers IP address as discussed in the previous mails (in order to use tftp to upload the files) if for some reason DHCP is not working. I also did this by entering the following settings:

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html

* '''Step 1''': Connect your computer via ethernet cable to LAN port 1
* '''Step 2''': Unplug the power cord from the router
* '''Step 3''': Wait 20 seconds
* '''Step 4''': Press and hold the reset button on the back of the router. Note that the reset button is recessed and you need a pen or paper clip to press it in. The button protruding from the back is the EZ Setup, which is not what you want to press.
* '''Step 5''': While holding the reset black button, plug the power cord into the router. Continue to hold the reset button until the power light starts flashing. Let go of the reset button.
* '''Step 6''': Can be done using 1) Terminal.app (command line) or 2) TFTP client with GUI.

1) Start Terminal.app (inside /Applications/Utilities) and go to the directory where you have saved that file (cd /your/directory/).

Then use this commands:
user@box:$ tftp 192.168.1.1
> mode binary
> trace
> put wl500gP_Luup-1.0.979.trx

2) You can download MacTFTP Client from http://www.versiontracker.com/dyn/moreinfo/macosx/8122 for example.

Start MacTFTP, type "192.168.1.1" inside the Address field.
Click on the "File..." button and select the firmware file you want to update Vera with and click "Start".
Wait for completion and proceed to next step.

* '''Step 7''': Tftp should report a successful file transfer in 10-20 seconds. The router will load the firmware and begin to flash it into nvram. During this time, the power indicator on the router will go out. Wait until this light comes back on, or wait at least 8 minutes for the flashing process to complete. If the power indicator has not come back on after 8 minutes, cycle the power on the router.
*'''Step 8''': Unplug the power cord from the router, wait 20 seconds, and plug the power cord back into the router WITHOUT PRESSING THE BLACK BUTTON. In less than a minute, your Vera is up.

The Vera should now boot to the new firmware. Go to 192.168.1.1 or 192.168.81.1 to confirm. You may need to power cycle your cable modem (if applicable) to get an internet connection and setup the network to automatically get settings via DHCP again.

This is the Mac OS version of the firmware restoration since the engineers from Asus didn't release an application to do this.

Also, read this posted on opewrt site: http://nuwiki.openwrt.org/oldwiki/OpenWrtDocs/Hardware/Asus/Flashing

File:Vera Hardware v2.jpg

2010-02-24T20:40:12Z

Cj man: Vera Hardware Version 2

Vera Hardware Version 2

ZWave Dongle

2009-12-18T21:37:43Z

Cj man:

Your Vera purchase includes a Z-Wave dongle, which must remain plugged into the back of Vera for her Z-Wave functions to work. You do not need to do anything for the dongle to work with Vera.

If you want to use the dongle separately from Vera, or purchased an extra dongle on its own, you will need the appropriate CP210x USB-RS232 drivers for your operating system. They are available here: https://www.silabs.com/products/interface/usbtouart/Pages/default.aspx

1. Download the Windows drivers for the Zwave Stick:
2.1. Go to: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
2.2. Download [b]VCP Driver Kit [/b] https://www.silabs.com/Support%20Documents/Software/CP210x_VCP_Win2K_XP_S2K3.zip
2.3. If you don't have an unzip program (a program to extrac the zip archive) grab 7zip from here: http://www.7-zip.org/
2.3.1. Download [b]7-Zip 4.65 [/b] http://downloads.sourceforge.net/sevenzip/7z465.exe
2.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe
2.4.1. Install the Drivers.
3. Plug the black Zwave dongle in your PC USB PORT

Once the drivers are installed, the dongle should show up as a COM port or serial device. Then any software designed to work with the Z-Wave serial API, such as ControlThink, HomeSeer, etc., should work fine. Windows users may need to edit the port settings and set them as follows: Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: none

To add devices to the dongle, tap the button so the blue light is blinking slowly. Then activate your nearby Z-Wave devices. To remove devices, press and hold the button until it blinks quickly, then activate your nearby Z-Wave devices. You can also add/remove devices while the dongle is attached to the PC's USB interface using your Z-Wave software's add/remove device function. Use your Z-Wave software to replicate the Z-Wave network.

'''Z-Wave Dongle Versions:'''

* ''2.40'' = Zensys Firmware ''4.27'';
* ''2.48'' = Zensys Firmware ''5.02'';
* ''2.60'' = Zensys Firmware ''5.02 Service Pack 2'';
* ''2.78'' = Zensys Firmware ''5.02 Service Pack 3''.

You can determine the dongle version looking at the Version: line on the More Z-Wave Options page (Devices -> Z-Wave -> More Z-Wave Options).

Schlage Lock Troubleshooting

2009-11-30T18:52:07Z

Cj man:

<div lang="x-western" class="moz-text-html">'''In order to pair your lock please follow this step by step instructions carefully: ''' - place Vera near the lock (under 10ft) and keep Vera connected to the internet and the black zwave dongle in it's usb port !!! - open Vera's dashboard - go to Setup->Advanced->Logs and enable verbose logging - locate your Schlage 6 digit programing code     ( more infos about schlage lock pairing are on this manual page: [[Schlage Lock|http://wiki.micasaverde.com/index.php/Schlage_Lock]]  ) - go to Devices->Zwave Options and '''exclude''' your lock by:     ( more infos about full power inclusion are on this manual page:  [[Full Power Inclusion|http://wiki.micasaverde.com/index.php?title=Full_Power_Inclusion]] )     +changing INCLUDE to EXCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the exclude procedure''' --- - go to Devices and confirm that your lock doesn't appear there anymore, if it's there repeat the exclude procedure - go to the lock and reset it to factory defaults as it says on its user manual on page 4: [http://part2.schlage.com/docs/lock_user_guide.pdf http://part2.schlage.com/docs/lock_user_guide.pdf]     *Note: Restoring factory settings WILL NOT exclude the lock from the bridge.                 DO NOT reset your lock unless you are able to locate the original programming code. Customer service cannot retrieve a lost programming code.         +1. For FE599, disconnect the batteries. For BE369, disconnect the 9V battery.         +2. On the lock keypad, press and release the Schlage button.         +3. Reconnect the battery and wait until the Schlage button is no longer lit.         +4. Within ten (10) seconds, press and hold the Schlage button '''until it lights green and the lock beeps.''' - go  to Devices->Zwave Options and  '''include''' your lock by:     +set to INCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the include procedure''' --- * you can see the progress written in blue text at the top of the page, bellow "Z-Wave options" page title - wait for the lock to be added and the zwave network to be restarted then - go to Devices and observe the lock configuration progress by going with the mouse pointer over its BLUE COG WHEEL     ( more infos about device status are on this manual page:  [[Device_Control_Status|http://wiki.micasaverde.com/index.php/Device_Control_Status]] ) ''* during the lock configuration time you should not unplug Vera from the power cord or change / save other settings on it * - assign the lock into a Room, press Continue and the press the Red SAVE button. Vera will continue the lock configuration. '' - after the cog wheel turns green test your lock: send lock/unlock commands, then add an user code     ''- confirm that you can control your lock when Vera it's near it, then move Vera at it's initial place'' - after you've put back Vera at it's initial place you have to update the zwave network routing table by running "Repair my Network" from     Device->Zwave Options with 5 minute stress time. More informations can be found here: [[Heal Network|http://wiki.micasaverde.com/index.php/Heal_Network]]     ''- wait for the Heal Network process to finish then test again your lock ''- if the cog wheel turns RED or your lock doesn't respond to commands and you are sure that you've followed the above steps carefully and at every step you've seen the lock schlage led blinking GREEN then go to Advanced->Tech Support: enable it and submit a trouble report with your logs attached and tell us at what step the configuration stage failed.</div>

Schlage Lock Troubleshooting

2009-11-30T18:51:38Z

Cj man:

<div lang="x-western" class="moz-text-html">'''In order to pair your lock please follow this step by step instructions carefully: ''' - place Vera near the lock (under 10ft) and keep Vera connected to the internet and the black zwave dongle in it's usb port !!! - open Vera's dashboard - go to Setup->Advanced->Logs and enable verbose logging - locate your Schlage 6 digit programing code     ( more infos about schlage lock pairing are on this manual page: [[Schlage_Lock|http://wiki.micasaverde.com/index.php/Schlage_Lock]]  ) - go to Devices->Zwave Options and '''exclude''' your lock by:     ( more infos about full power inclusion are on this manual page:  [[Full_Power_Inclusion|http://wiki.micasaverde.com/index.php?title=Full_Power_Inclusion]] )     +changing INCLUDE to EXCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the exclude procedure''' --- - go to Devices and confirm that your lock doesn't appear there anymore, if it's there repeat the exclude procedure - go to the lock and reset it to factory defaults as it says on its user manual on page 4: [http://part2.schlage.com/docs/lock_user_guide.pdf http://part2.schlage.com/docs/lock_user_guide.pdf]     *Note: Restoring factory settings WILL NOT exclude the lock from the bridge.                 DO NOT reset your lock unless you are able to locate the original programming code. Customer service cannot retrieve a lost programming code.         +1. For FE599, disconnect the batteries. For BE369, disconnect the 9V battery.         +2. On the lock keypad, press and release the Schlage button.         +3. Reconnect the battery and wait until the Schlage button is no longer lit.         +4. Within ten (10) seconds, press and hold the Schlage button '''until it lights green and the lock beeps.''' - go  to Devices->Zwave Options and  '''include''' your lock by:     +set to INCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the include procedure''' --- * you can see the progress written in blue text at the top of the page, bellow "Z-Wave options" page title - wait for the lock to be added and the zwave network to be restarted then - go to Devices and observe the lock configuration progress by going with the mouse pointer over its BLUE COG WHEEL     ( more infos about device status are on this manual page:  [[../../../../index.php/Device_Control_Status|http://wiki.micasaverde.com/index.php/Device_Control_Status]] ) ''* during the lock configuration time you should not unplug Vera from the power cord or change / save other settings on it * - assign the lock into a Room, press Continue and the press the Red SAVE button. Vera will continue the lock configuration. '' - after the cog wheel turns green test your lock: send lock/unlock commands, then add an user code     ''- confirm that you can control your lock when Vera it's near it, then move Vera at it's initial place'' - after you've put back Vera at it's initial place you have to update the zwave network routing table by running "Repair my Network" from     Device->Zwave Options with 5 minute stress time. More informations can be found here: [[Heal_Network|http://wiki.micasaverde.com/index.php/Heal_Network]]     ''- wait for the Heal Network process to finish then test again your lock ''- if the cog wheel turns RED or your lock doesn't respond to commands and you are sure that you've followed the above steps carefully and at every step you've seen the lock schlage led blinking GREEN then go to Advanced->Tech Support: enable it and submit a trouble report with your logs attached and tell us at what step the configuration stage failed.</div>

Schlage Lock Troubleshooting

2009-11-30T18:51:11Z

Cj man: New page: <div lang="x-western" class="moz-text-html">'''In order to pair your lock please follow this step by step instructions carefully: ''' - place Vera near the lock (under 10ft) and keep V...

<div lang="x-western" class="moz-text-html">'''In order to pair your lock please follow this step by step instructions carefully: ''' - place Vera near the lock (under 10ft) and keep Vera connected to the internet and the black zwave dongle in it's usb port !!! - open Vera's dashboard - go to Setup->Advanced->Logs and enable verbose logging - locate your Schlage 6 digit programing code     ( more infos about schlage lock pairing are on this manual page: [[../../../../index.php/Schlage_Lock|http://wiki.micasaverde.com/index.php/Schlage_Lock]]  ) - go to Devices->Zwave Options and '''exclude''' your lock by:     ( more infos about full power inclusion are on this manual page:  [[../../../../index.php?title=Full_Power_Inclusion|http://wiki.micasaverde.com/index.php?title=Full_Power_Inclusion]] )     +changing INCLUDE to EXCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the exclude procedure''' --- - go to Devices and confirm that your lock doesn't appear there anymore, if it's there repeat the exclude procedure - go to the lock and reset it to factory defaults as it says on its user manual on page 4: [http://part2.schlage.com/docs/lock_user_guide.pdf http://part2.schlage.com/docs/lock_user_guide.pdf]     *Note: Restoring factory settings WILL NOT exclude the lock from the bridge.                 DO NOT reset your lock unless you are able to locate the original programming code. Customer service cannot retrieve a lost programming code.         +1. For FE599, disconnect the batteries. For BE369, disconnect the 9V battery.         +2. On the lock keypad, press and release the Schlage button.         +3. Reconnect the battery and wait until the Schlage button is no longer lit.         +4. Within ten (10) seconds, press and hold the Schlage button '''until it lights green and the lock beeps.''' - go  to Devices->Zwave Options and  '''include''' your lock by:     +set to INCLUDE     +low power to FULL POWER     +and timeout from 30 to 120 seconds then press GO button and go to your lock and:     +type the programing code, wait for the schlage led to blink ORANGE     + press Schlage button then 0 key and confirm that the led blinks ''GREEN'' --- '''if the lock led blinks RED then repeat the include procedure''' --- * you can see the progress written in blue text at the top of the page, bellow "Z-Wave options" page title - wait for the lock to be added and the zwave network to be restarted then - go to Devices and observe the lock configuration progress by going with the mouse pointer over its BLUE COG WHEEL     ( more infos about device status are on this manual page:  [[../../../../index.php/Device_Control_Status|http://wiki.micasaverde.com/index.php/Device_Control_Status]] ) ''* during the lock configuration time you should not unplug Vera from the power cord or change / save other settings on it * - assign the lock into a Room, press Continue and the press the Red SAVE button. Vera will continue the lock configuration. '' - after the cog wheel turns green test your lock: send lock/unlock commands, then add an user code     ''- confirm that you can control your lock when Vera it's near it, then move Vera at it's initial place'' - after you've put back Vera at it's initial place you have to update the zwave network routing table by running "Repair my Network" from     Device->Zwave Options with 5 minute stress time. More informations can be found here: [[../../../../index.php/Heal_Network|http://wiki.micasaverde.com/index.php/Heal_Network]]     ''- wait for the Heal Network process to finish then test again your lock ''- if the cog wheel turns RED or your lock doesn't respond to commands and you are sure that you've followed the above steps carefully and at every step you've seen the lock schlage led blinking GREEN then go to Advanced->Tech Support: enable it and submit a trouble report with your logs attached and tell us at what step the configuration stage failed.</div>

Vera Luup Releases

2009-11-16T15:19:35Z

Cj man:

'''IMPORTANT NOTE: DO NOT LEAVE THE DOWNLOAD PAGE BEFORE THE UPGRADE HAS FINISHED!!!'''

'''''NOTE:'''''

'''''    *If you upgrade from a pre-Luup version, after the upgrade has completed successfully, you have to clear your browser cache.'''''

'''''        See here how to [[Clear Browser Cache]].'''''

''    **Please check this Forum page to see the latest Luup Version: http://forum.micasaverde.com/index.php?board=4.0''

When Luup is officially released everyone's system will automatically notify them and allow them to upgrade to the latest version. In the meantime, you can upgrade to the latest version.

#Go to Advanced, Download and put one of the URL's from bellow in the 'Firmware url' field.
#After the download is completed, click the Backup button to save your current configuration, maybe you'll need it later.
#'''IMPORTANT''' Do not leave the upgrade page!
#Select keep settings (will preserve your current configuration)  or restore to factory default (will erase all your settings and start with an empty, default settings) 
#Begin the upgrade and wait for Vera to notify you when it's done.
#Clear your browser cache and then reload the page.

 Much of the functionality which exists in the current Vera was written as closed-source plugins in C/C++. These plugins are being converted to Luup plugins so users can change the code to customize the functionality. Since version 1.0.979, only the Energy Metering isn't re-written as a plugin, in rest all the 1.0.616 functionality are pressent in the luup release.

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx

== 2009-October-15 1.0.967 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.967.trx

== 2009-August-14 1.0.862 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.862.trx

== 2009-August-7 1.0.843 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.843.trx

We are intending to release this as an official beta for the general public on Monday if no issues are reported over the weekend. This is the first version that has passed all our test plans.

== 2009-July-17 1.0.790 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

This fixes an issue in 789 with getting a persistent 'VERY IMPORTANT - Clear your cache' error in the browser. If that browser error makes upgrading difficult, you can manually upgrade by logging into Vera and typing:

wget -O /tmp/firmware.img http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

/usr/bin/cmh-upgrade.sh

== 2009-July-16 1.0.789 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.789.trx

This fixes many issues, including fixes to the web-based WAP and Iphone browser and the addition of the automatic installation of plugins from the Luup gallery.

== 2009-July-10 1.0.770 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.770.trx

This fixes a couple bugs with the adding of custom serial ports. The job icons are not appearing, though.

Note: If you added serial ports with 765 and they don't show up on the 'Serial Port Configuration' page, remove the usb->serial adapter, upgrade to 770. After it comes back up, reconnect the usb->serial adapter, and reboot Vera (Advanced, Tech Support, 'reboot router').

There are some issues with the Linux usb-serial driver that cause conflicts with other usb-serial devices, like the Z-Wave dongle, when you insert the usb-serial adapter while the system is already running (ie hotplugging). Until these issues are resolved in the Linux kernel, it's best that you reboot Vera after you connect a usb-serial adapter, or, of course, connect it before you power on Vera.

== 2009-July-9 1.0.765 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.765.trx

This includes the ability to add your own USB->serial devices to the 'recognized list' and fixes some bugs in the serial port handling.

== 2009-July-6 1.0.756 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.756.trx

With this version we have included a sample RS232 device for control of the Somfy motorized blinds. This version has also fixed all the obvious bugs so we can complete our standard test sequence without incident. And all the existing plug-in functionality is now implemented in Luup, including timers and events, with the exception of real-time energy consumption reporting.

== 2009-June-27 1.0.745 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.745.trx

Lots of bug fixes.

== 2009-June-23 1.0.733 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.733.trx

The basic WAP cell phone interface is back in, now as a Luup plugin, and the red/black button control needed to do inclusion of the Schlage locks is back too.

== 2009-June-20 1.0.716 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.716.trx

This fixes a few crashes with configuring devices.

== 2009-June-15 1.0.711 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.711.trx

This fixes an issue with the software not restarting after removing/reinserting the dongle. It also fixes the 'do something after x seconds' in scenes.

== 2009-June-12 1.0.710 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.710.trx

This is the initial beta release of the Luup engine. The following functionality which exists in the current release of Vera is not yet working in this release: In scenes the 'after x seconds/minutes' do something else, many of the events are not implemented, event notifications, energy monitoring and setting pin codes on door locks. The rest of the Z-Wave commands should work. A Luup plugin for the Global Cache GC100 is included and the serial ports work for controlling RS232 devices and also the i/r transmitters. You can start creating support for i/r devices although it will be tedious at the moment to do this by hand putting pronto codes in the XML files until the web-based generator tool is available.

This release is for Luup developers only and is not suitable for mainstream users yet because of the missing functionality.

 

NOTE: If you upgrade to a Luup version lower than 1.0.862 you'll need to choose 'restore to factory default' in order to get Vera working, so read the instructions carefully.

Vera Luup Releases

2009-11-16T15:18:43Z

Cj man:

'''IMPORTANT NOTE: DO NOT LEAVE THE DOWNLOAD PAGE BEFORE THE UPGRADE HAS FINISHED!!!'''

''''''NOTE: *If you upgrade from a pre-Luup version, after the upgrade has completed successfully, you have to clear your browser cache. See here how to [[Clear Browser Cache]].'''''

''**Please check this Forum page to see the latest Luup Version: http://forum.micasaverde.com/index.php?board=4.0''

When Luup is officially released everyone's system will automatically notify them and allow them to upgrade to the latest version. In the meantime, you can upgrade to the latest version.

#Go to Advanced, Download and put one of the URL's from bellow in the 'Firmware url' field.
#After the download is completed, click the Backup button to save your current configuration, maybe you'll need it later.
#'''IMPORTANT''' Do not leave the upgrade page!
#Select keep settings (will preserve your current configuration)  or restore to factory default (will erase all your settings and start with an empty, default settings) 
#Begin the upgrade and wait for Vera to notify you when it's done.
#Clear your browser cache and then reload the page.

 Much of the functionality which exists in the current Vera was written as closed-source plugins in C/C++. These plugins are being converted to Luup plugins so users can change the code to customize the functionality. Since version 1.0.979, only the Energy Metering isn't re-written as a plugin, in rest all the 1.0.616 functionality are pressent in the luup release.

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx

== 2009-October-15 1.0.967 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.967.trx

== 2009-August-14 1.0.862 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.862.trx

== 2009-August-7 1.0.843 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.843.trx

We are intending to release this as an official beta for the general public on Monday if no issues are reported over the weekend. This is the first version that has passed all our test plans.

== 2009-July-17 1.0.790 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

This fixes an issue in 789 with getting a persistent 'VERY IMPORTANT - Clear your cache' error in the browser. If that browser error makes upgrading difficult, you can manually upgrade by logging into Vera and typing:

wget -O /tmp/firmware.img http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

/usr/bin/cmh-upgrade.sh

== 2009-July-16 1.0.789 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.789.trx

This fixes many issues, including fixes to the web-based WAP and Iphone browser and the addition of the automatic installation of plugins from the Luup gallery.

== 2009-July-10 1.0.770 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.770.trx

This fixes a couple bugs with the adding of custom serial ports. The job icons are not appearing, though.

Note: If you added serial ports with 765 and they don't show up on the 'Serial Port Configuration' page, remove the usb->serial adapter, upgrade to 770. After it comes back up, reconnect the usb->serial adapter, and reboot Vera (Advanced, Tech Support, 'reboot router').

There are some issues with the Linux usb-serial driver that cause conflicts with other usb-serial devices, like the Z-Wave dongle, when you insert the usb-serial adapter while the system is already running (ie hotplugging). Until these issues are resolved in the Linux kernel, it's best that you reboot Vera after you connect a usb-serial adapter, or, of course, connect it before you power on Vera.

== 2009-July-9 1.0.765 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.765.trx

This includes the ability to add your own USB->serial devices to the 'recognized list' and fixes some bugs in the serial port handling.

== 2009-July-6 1.0.756 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.756.trx

With this version we have included a sample RS232 device for control of the Somfy motorized blinds. This version has also fixed all the obvious bugs so we can complete our standard test sequence without incident. And all the existing plug-in functionality is now implemented in Luup, including timers and events, with the exception of real-time energy consumption reporting.

== 2009-June-27 1.0.745 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.745.trx

Lots of bug fixes.

== 2009-June-23 1.0.733 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.733.trx

The basic WAP cell phone interface is back in, now as a Luup plugin, and the red/black button control needed to do inclusion of the Schlage locks is back too.

== 2009-June-20 1.0.716 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.716.trx

This fixes a few crashes with configuring devices.

== 2009-June-15 1.0.711 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.711.trx

This fixes an issue with the software not restarting after removing/reinserting the dongle. It also fixes the 'do something after x seconds' in scenes.

== 2009-June-12 1.0.710 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.710.trx

This is the initial beta release of the Luup engine. The following functionality which exists in the current release of Vera is not yet working in this release: In scenes the 'after x seconds/minutes' do something else, many of the events are not implemented, event notifications, energy monitoring and setting pin codes on door locks. The rest of the Z-Wave commands should work. A Luup plugin for the Global Cache GC100 is included and the serial ports work for controlling RS232 devices and also the i/r transmitters. You can start creating support for i/r devices although it will be tedious at the moment to do this by hand putting pronto codes in the XML files until the web-based generator tool is available.

This release is for Luup developers only and is not suitable for mainstream users yet because of the missing functionality.

 

NOTE: If you upgrade to a Luup version lower than 1.0.862 you'll need to choose 'restore to factory default' in order to get Vera working, so read the instructions carefully.

Vera Luup Releases

2009-11-16T15:17:16Z

Cj man:

'''IMPORTANT NOTE: DO NOT LEAVE THE DOWNLOAD PAGE BEFORE THE UPGRADE HAS FINISHED!!!'''

 ''''''''NOTE: If you upgrade from a pre-Luup version, after the upgrade has completed successfully, you have to clear your browser cache. See here how to [[Clear Browser Cache]].'''

Please check this Forum page to see the latest Luup Version: http://forum.micasaverde.com/index.php?board=4.0

When Luup is officially released everyone's system will automatically notify them and allow them to upgrade to the latest version. In the meantime, you can upgrade to the latest version.

#Go to Advanced, Download and put one of the URL's from bellow in the 'Firmware url' field.
#After the download is completed, click the Backup button to save your current configuration, maybe you'll need it later.
#'''IMPORTANT''' Do not leave the upgrade page!
#Select keep settings (will preserve your current configuration)  or restore to factory default (will erase all your settings and start with an empty, default settings) 
#Begin the upgrade and wait for Vera to notify you when it's done.
#Clear your browser cache and then reload the page.

 Much of the functionality which exists in the current Vera was written as closed-source plugins in C/C++. These plugins are being converted to Luup plugins so users can change the code to customize the functionality. Since version 1.0.979, only the Energy Metering isn't re-written as a plugin, in rest all the 1.0.616 functionality are pressent in the luup release.

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.979.trx

== 2009-October-15 1.0.967 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.967.trx

== 2009-August-14 1.0.862 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.862.trx

== 2009-August-7 1.0.843 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.843.trx

We are intending to release this as an official beta for the general public on Monday if no issues are reported over the weekend. This is the first version that has passed all our test plans.

== 2009-July-17 1.0.790 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

This fixes an issue in 789 with getting a persistent 'VERY IMPORTANT - Clear your cache' error in the browser. If that browser error makes upgrading difficult, you can manually upgrade by logging into Vera and typing:

wget -O /tmp/firmware.img http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

/usr/bin/cmh-upgrade.sh

== 2009-July-16 1.0.789 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.789.trx

This fixes many issues, including fixes to the web-based WAP and Iphone browser and the addition of the automatic installation of plugins from the Luup gallery.

== 2009-July-10 1.0.770 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.770.trx

This fixes a couple bugs with the adding of custom serial ports. The job icons are not appearing, though.

Note: If you added serial ports with 765 and they don't show up on the 'Serial Port Configuration' page, remove the usb->serial adapter, upgrade to 770. After it comes back up, reconnect the usb->serial adapter, and reboot Vera (Advanced, Tech Support, 'reboot router').

There are some issues with the Linux usb-serial driver that cause conflicts with other usb-serial devices, like the Z-Wave dongle, when you insert the usb-serial adapter while the system is already running (ie hotplugging). Until these issues are resolved in the Linux kernel, it's best that you reboot Vera after you connect a usb-serial adapter, or, of course, connect it before you power on Vera.

== 2009-July-9 1.0.765 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.765.trx

This includes the ability to add your own USB->serial devices to the 'recognized list' and fixes some bugs in the serial port handling.

== 2009-July-6 1.0.756 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.756.trx

With this version we have included a sample RS232 device for control of the Somfy motorized blinds. This version has also fixed all the obvious bugs so we can complete our standard test sequence without incident. And all the existing plug-in functionality is now implemented in Luup, including timers and events, with the exception of real-time energy consumption reporting.

== 2009-June-27 1.0.745 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.745.trx

Lots of bug fixes.

== 2009-June-23 1.0.733 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.733.trx

The basic WAP cell phone interface is back in, now as a Luup plugin, and the red/black button control needed to do inclusion of the Schlage locks is back too.

== 2009-June-20 1.0.716 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.716.trx

This fixes a few crashes with configuring devices.

== 2009-June-15 1.0.711 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.711.trx

This fixes an issue with the software not restarting after removing/reinserting the dongle. It also fixes the 'do something after x seconds' in scenes.

== 2009-June-12 1.0.710 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.710.trx

This is the initial beta release of the Luup engine. The following functionality which exists in the current release of Vera is not yet working in this release: In scenes the 'after x seconds/minutes' do something else, many of the events are not implemented, event notifications, energy monitoring and setting pin codes on door locks. The rest of the Z-Wave commands should work. A Luup plugin for the Global Cache GC100 is included and the serial ports work for controlling RS232 devices and also the i/r transmitters. You can start creating support for i/r devices although it will be tedious at the moment to do this by hand putting pronto codes in the XML files until the web-based generator tool is available.

This release is for Luup developers only and is not suitable for mainstream users yet because of the missing functionality.

 

NOTE: If you upgrade to a Luup version lower than 1.0.862 you'll need to choose 'restore to factory default' in order to get Vera working, so read the instructions carefully.

Supported Hardware

2009-11-16T14:43:30Z

Cj man: /* Thermostat Devices */

This is a page for Supported Z-Wave devices.

Alternative hardware pages exist for

*[[ZWave Add Controller|Z-Wave Handheld Remote Controls, Gateways and Scene Controllers]]
*[[IP Cameras|IP Enabled Cameras]]
*[[Insteon Supported Hardware|Insteon/X10 devices]]
*USB, or USB-Serial, [[Serial Supported Hardware|Interface devices]]

In general, any device with the Z-Wave logo should work with Vera. A list of tested Z-Wave devices is below, with specific notes for each type of device. This is a wiki, so feel free to add to the page.

== Hardware Reported to Work ==

*We strongly encourage users to list any and all products they tested and installed.
*If a product works but you did not like it, please list it anyway. It may be the only product available to some users.

 

----

'''IMPORTANT! The devices listed here have been added by installers, technicians and users like yourself. Results may vary upon installations. MiCasaVerde does not guarantee operation and compatibility with your installation. The listed devices were found to work with their specific installation. Mixing different series and brands of equipment is not guaranteed in any way to work with other series and brands. It is very likely that users have not fully tested all features of the devices, so it is possible that a device listed here as compatible, will not prove compatible with your hardware. If you are editing this wiki DO NOT REMOVE a listed working device if it hasn't worked for you. Seek help to get the device to work under your individual circumstance. If you are adding to this wiki, please provide links to data for the device and add any tips you feel may benefit someone wanting to implement the device into an installation.'''

----

 

=== '''Lighting Devices''' ===

{| cellpadding="2" border="1" style="width: 1220px; height: 491px;"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Leviton
| Dimmer Switch
| VRM10-1LX
| 1
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=104&products_id=170 Link]
| [http://www.amazon.com/review/product/B000ZKM7I8/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=65 mark-hc]
| This is a high quality dimmer geared towards high-end installations
|-
| Intermatic
| 300 watt dimmer
| HA06
| 
| July 2007
| Indoor
| [http://www.homesettings.com/products/modules/ha06.aspx Link]
| 
| 
| Affordable Dimmer Switch. incandescent/halogen only. Loads for 300 watts or less no neutral required. Great for dimming one bulb.
|-
| Cooper
| Accessory (3-way slave)
|
|
|
| Indoor
|
| 
|
| See [[Cooper_Accessory_Slave]]
|-
| Intermatic
| 3-way Switch
| HA18
| 
| Dec 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha18.aspx Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Affordable 3-way Switch
|-
| Intermatic
| 3-way Dimmer Switch
| HA20
| 
| Nov 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha20.aspx Link]
| [http://www.amazon.com/Intermatic-Settings-Three-Way-Dimmer-HA20C/dp/B000WS4SJ41 Link]
| 
| Affordable 3-way 600W dimmer
|-
| ACT
| 2-way Dimmer Switch
| ZDW120
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, easy to install, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 3-way Dimmer Switch
| ZDW103
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 2-way Relay Switch
| ZRW113
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Controls Florescent Lamps very well! No humming at all.
|-
| ACT
| Companion Switch
| AS101
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, The trick here is to install this device where the power comes in.
|-
| ACT 
| 3-way Dimmer Switch, 2 rocker 
| ZDM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZDM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Dimmer, Wall-mount, 230v, 500W, 3-way, 3 Wire, 2 rocker 
|-
| ACT
| 3-way Relay Switch, 2 rocker
| ZRM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZRM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Relay, Wall-mount, 230v, 6A, 3-way, 3 Wire, 2 rocker - '''Status polling does not work with Vera''' 
|-
| Innovus
| Relay Switch Adapter
| RAone SmartPower
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartpower_zw_tech_doc.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Innovus
| Dimmer Switch Adapter
| RAone SmartDimmer
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartdimmer-00110001-tech.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Intermatic
| Screw-in Module
| HA05C
| 
| Nov 2008
| Outdoor
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Easy install, easy to pair with Vera!
|-
| Merten
| Radio sensor cover for dimmer inserts
| 5026xx, 5036xx, 5046xx
| 6,2,7,1,5
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5026_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Radio sensor cover for switch inserts
| 5024xx, 5034xx, 5044xx
| 6,2,27,2,2
|  
| Indoor
| [http://www.merten.de/download/DL_doku/5024xx_5034xx_5044xx_Sensorflaeche4pin_CONNECT_INT.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Single Radio flush-mounted receiver
| 507001
| 6,2,27,2,2
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5070_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| switch, flush-mounted
| 507501, 507601
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5075_581_00_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Merten
| 1-gang universal dimmer, flush-mounted
| 507900
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5079_581_01_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Schlage
| Lamp Module
| RP200
| 1.0
| Aug 2009
| Indoor
| [http://consumer.schlage.com/products/Productdetail3.asp?StyleID=139&FinishID=12&FunctionID=77 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Works well Sold with Schlage LiNK lock system
|-
| Leviton
| Dimmer Switch
| VRI06-1LX
|  
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=305784&section=25501 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well
|-
| Leviton
| 4-Scene Controller with Switch
| VRCS4-MRX
| 7,2,67,0,2
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=433270&section=28563 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well, pair as per [http://wiki.micasaverde.com/index.php/Leviton_Scene_Controller Leviton 4-Scene Controller], then again holding "2" and "4" to pair the Switch ("Load") itself.
|}

=== '''Plug & Receptacle Devices''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Intermatic
| In-Wall Receptacle
| CA3500
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=105&products_id=97 Link]
| [http://www.amazon.com/review/product/B000U3XYPA/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| 
| This is a decent, but expensive solution for in-wall receptacles. One receptacle RF controlled, the other is hot
|-
| Intermatic
| Appliance Module
| HA02C
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=108&products_id=98 Link]
| [http://www.amazon.com/Intermatic-HA02C-Settings-Heavy-Duty-Appliance/dp/B000BJSDZO/ref=sr_1_3?ie=UTF8&qid=1227467418&sr=8-3 Link]
| 
| Seems to work well
|-
| ACT
| In-Wall Receptacle
| ZRR150W
| 2.2
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| 
| Works like a champ! Easy to Install. One receptacle RF controlled, the other is hot
|-
| Cooper Wiring Devices
| In-Wall Receptacle
| RFTR9505-T
|  
|  
|  
| Indoor
| [http://solutions.cooperwiringdevices.com/common/brands.cfm?pg=Detail&brandName=CWD%20Technology&category=Aspire%20RF%20Lighting%20Control%20System%3A%20Receptacles&id=16772 Link]
|
| 
| One receptacle is RF controlled, the other is hot
|-
| Intermatic
| Outdoor Module
| HA04C
| 1
|  
| Dec 2008
| Outdoor
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Easy to Install.
|-
| Monster Central
| 1800W Appliance Module
| ML-LAS1000
| 1
|  
| Jan 2009
| Indoor
| [http://www.monstercable.com/productdisplay.asp?pin=3164 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Easy to Install. I use this as a ZWave signal repeater. Appears to be a badge-engineering of [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=309748&section=25542 Leviton VRP15-1LW]
|-
| Duwi
| Z-Wave switch 3500 W
| 05437
|  
| EU
| Feb 2009
| Indoor
| [http://www.duewi.com/ Link]
|
| ezhome
| High quality Plug-in switch, Easy install and works well
|-
| Merten
| switch, plug adapter, 2000 W
| 508519
| 6,2,7,1,5
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5085_581_01_web.pdf Link]
|  
| Ap15e
| Works well.
|}

=== '''Thermostat Devices''' ===

{| border="1" cellpadding="2"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Wayne Dalton
| Wall Stat
| WDTC-20
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/WDTC-20---Z-Wave-Thermostat-Wayne-Dalton-P599C38.aspx Link]
| [http://www.amazon.com/Wayne-Dalton-Corporation-Z-Wave-Thermostat/dp/B001F8QKYQ Link]
| 
| Has 2 inclusion modes: 1) press and release the bind button and the STAT will be included as a thermostat and works with Vera, 2) press and hold the bind button and it will be added as a binary switch for compatibility with old, non-compliant remotes. If it's added in the wrong mode, remove it and re-add it. Works great simple to use!
|-
| HAI
| Wall Stat
| RC-80BZ
|  ??
|  
| Nov 2007
| Indoor
| [http://www.homeauto.com Link]
| [http://www.homeauto.com/Downloads/Products/Omnistat/rcr80.pdf Link]
| 
| Shows up as Standard Thermostat in Vera, Hold button feature not able to control by Vera at this time. Priced above 200.00. Has internal setback programs. Works great.
|-
| RCS
| Wall Stat
| TZ43
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| 
| Shows up as Standard Thermostat in Vera, much more feature rich the the WDTC-20 but comes with a hefty price tag ($214.95). Wish Vera could use all the features in this Thermostat! '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Schlage/Trane
| Wall Stat
| Trane
|  ??
|  
|  ??
| Indoor
| [http://www.link.schlage.com/Products/Pages/Thermostat.aspx Link]
| [http://www.trane.com/Residential/Products/Thermostats Link]
| 
| It's the same thermostat as the RCS TZ43 and it has the same issue: it's accepting "Set Temp Point" commands only in the measurement unit that is displayed on its screen. '''Note:'''''You need to set the thermostat to show the temperature, on its screen, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Intermatic
| InTouch
| CA8900
| 
|  
| Nov 2008
| Indoor
| [http://www.smarthome-products.com/p-663-intermatic-intouch-ca8900-z-wave-digital-thermostat.aspx Link]
| 
| 
| Looks very similar to the Wayne Dalton WDTC-20 listed here. works great, simple to use
|-
| Danfoss
| Radiator thermostat
| RA PLUS-w
| 
| EU
| 
| Indoor
| [http://raplusw.com/Content/E962FC0B-6461-4319-82FE-3E1E765142CF.html Link] [http://raplusw.com/PCMPDF/Data%20sheet%20RA-PLUS-w_02.pdf Link]
| 
| 
| See: [[Danfoss Thermostat]] for installation instructions If the device cannot be configured at the final location, move the device closer to Vera and try again (this device might require a direct connection to Vera for configuration).
|}

=== '''Sensors''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| ACT
| Motion Sensor
| ZIR000 / ZIR010
| 
| EU (ZIR010) or US (ZIR000)
| 
| Indoor
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR000_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR000_instr.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR010_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR010_instr.pdf Link]
| 
| 
| Remove the cover, pair to Vera's dongle by using the push-button on the left of the circuit board. Vera must configure it to work, and it can only be configured within a few minutes of inserting the batteries. With Vera's dongle removed, remove/reinsert the batteries, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page
|-
| Express Controls aka HomeSeer
| 3-in-1 sensor (light/temperature/motion)
| HSM100 / EZMotion
| 
| EU or US
| 
| 
| [http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf Link]
| 
| 
| See [[ExpressControls3in1]] If the motion sensor does not work right after inclusion and configuration, remove the batteries for a few seconds.
|-
| EverSpring/Hawking/Home Manageables
| Door/window sensor
| SM103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=355&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110873R01_SM103_-ECR.pdf Link]
|  
| Ap15e
| Pair using the intrusion button. The sensor will accept configuration within a few minutes of the initial pairing, or of pressing the intrusion button on the back even after it's paired. Pair the device, or if it's already paired, press the intrusion button, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page. NOTE: There is some confusion about the orientation of the sensor. The main sensor body has a back (where the intrusion is), a front (where the logo and LED is), and the 2 other surfaces, one of which has a curved edge, and the other is flat. The magnet needs to go against the flat surface. And the flat surface on the magnet should be as close as possible to the flat surface on the sensor, lined up in the middle so the line which passes through the LED lines up with the sensor.
|-
| Everspring
| Motion Detector
| SP103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=354&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110874R01_SP103_%20-%20ECR.pdf Link]
|  
| Ap15e
| Works well
|-
| Fortrezz
| Water /Freeze
| WWA-001
|  ??????
| US
| Apr 2009
| Indoor
| [http://www.Fortrezz.com Link] [http://www.fortrezz.com/resources/WWA_manual_01May2009.pdf Link]
| 
| Zmistro
| Works great I would place a few in your house. Bathrooms, laundry , kitchen , basement. Great product!
|-
| Merten
| 4-gang radio transmitter, flush-mounted
| 506004
| 2,2,27,1,4
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5060_581_02_web.pdf Link]
|  
| Ap15e
| Quite complex device; partially supported by Vera; can be used as a window/door sensor (as of firmware 1.0.900) ...
|}

=== '''Door Locks''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Schlage
| Door lock and deadbolt
| BE369 (deadbolt)
| 
| Mid 2009
| Indoor
| [http://consumer.schlage.com/link/product_tour/ Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Read the instructions here: [[Schlage Lock]]
|}

=== '''Drapes/Blinds''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Electronic Solutions
| Drape/Blind motor
| DBMZ
| 
| 
| Indoor
| 
| [http://www.smarthus.info/support/manuals/zw_motorkontroll/DBMZ.pdf Link]
| 
| 
|}

=== '''Relay controls''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Intermatic
| Contactor control box
| CA3750
| 
| Nov 2007
| Indoor/Outdoor
| [http://www.intouchcontrols.com/~/media/Files/InTouchControls/Products/Spec%20Sheets/CA3750.ashx Link]
| 
| 
| Multi-instance class supported for this device. Vera is able to control each of the 2 relays independently if desired. please note unit shows as three switches this is a bug with Intermatic not a real issue.You can check the box in devices to not show the second listing of the first relay in "Dasboard" You can control heavy loads like a water heater ,pool pump motor/s. great device
|}

=== '''Window Coverings''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Merten
| Radio roller shutter push-button
| 5025xx, 5035xx, 5045xx
| 6,2,27,2,3 and 6,2,27,2,4
| EU
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5025_581_01_web.pdf Link]
|  
| Ap15e
| Open/Close buttons work well, but slide bar does not work. GUI buttons do not work with Luup release 1.0.843 and 1.0.862 (fixed with Luup release 1.0.879). Workaround: Use a Luup Scene with the following code:<tt></tt>
<tt>local lul_arguments = {}</tt>

<tt>lul_arguments["newTargetValue"]="0"</tt>

<tt>lul_resultcode,lul_resultstring,lul_job,lul_returnarguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",lul_arguments,6) </tt> Replace "6" with your device number, replace "0" with "1" for inverse action.

|-
| Duewi
| Radio roller shutter push-button
| 054368
| 6,2,51,1,0
| EU
| Jun 2009
| Indoor
| [http://www.duewi.de/index.php?productid=37344 Link]
|  
| Lutz
| Open/Close buttons work well, but slide bar does not work.
|}

Supported Hardware

2009-11-16T14:39:19Z

Cj man: /* Thermostat Devices */

This is a page for Supported Z-Wave devices.

Alternative hardware pages exist for

*[[ZWave Add Controller|Z-Wave Handheld Remote Controls, Gateways and Scene Controllers]]
*[[IP Cameras|IP Enabled Cameras]]
*[[Insteon Supported Hardware|Insteon/X10 devices]]
*USB, or USB-Serial, [[Serial Supported Hardware|Interface devices]]

In general, any device with the Z-Wave logo should work with Vera. A list of tested Z-Wave devices is below, with specific notes for each type of device. This is a wiki, so feel free to add to the page.

== Hardware Reported to Work ==

*We strongly encourage users to list any and all products they tested and installed.
*If a product works but you did not like it, please list it anyway. It may be the only product available to some users.

 

----

'''IMPORTANT! The devices listed here have been added by installers, technicians and users like yourself. Results may vary upon installations. MiCasaVerde does not guarantee operation and compatibility with your installation. The listed devices were found to work with their specific installation. Mixing different series and brands of equipment is not guaranteed in any way to work with other series and brands. It is very likely that users have not fully tested all features of the devices, so it is possible that a device listed here as compatible, will not prove compatible with your hardware. If you are editing this wiki DO NOT REMOVE a listed working device if it hasn't worked for you. Seek help to get the device to work under your individual circumstance. If you are adding to this wiki, please provide links to data for the device and add any tips you feel may benefit someone wanting to implement the device into an installation.'''

----

 

=== '''Lighting Devices''' ===

{| cellpadding="2" border="1" style="width: 1220px; height: 491px;"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Leviton
| Dimmer Switch
| VRM10-1LX
| 1
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=104&products_id=170 Link]
| [http://www.amazon.com/review/product/B000ZKM7I8/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=65 mark-hc]
| This is a high quality dimmer geared towards high-end installations
|-
| Intermatic
| 300 watt dimmer
| HA06
| 
| July 2007
| Indoor
| [http://www.homesettings.com/products/modules/ha06.aspx Link]
| 
| 
| Affordable Dimmer Switch. incandescent/halogen only. Loads for 300 watts or less no neutral required. Great for dimming one bulb.
|-
| Cooper
| Accessory (3-way slave)
|
|
|
| Indoor
|
| 
|
| See [[Cooper_Accessory_Slave]]
|-
| Intermatic
| 3-way Switch
| HA18
| 
| Dec 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha18.aspx Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Affordable 3-way Switch
|-
| Intermatic
| 3-way Dimmer Switch
| HA20
| 
| Nov 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha20.aspx Link]
| [http://www.amazon.com/Intermatic-Settings-Three-Way-Dimmer-HA20C/dp/B000WS4SJ41 Link]
| 
| Affordable 3-way 600W dimmer
|-
| ACT
| 2-way Dimmer Switch
| ZDW120
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, easy to install, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 3-way Dimmer Switch
| ZDW103
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 2-way Relay Switch
| ZRW113
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Controls Florescent Lamps very well! No humming at all.
|-
| ACT
| Companion Switch
| AS101
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, The trick here is to install this device where the power comes in.
|-
| ACT 
| 3-way Dimmer Switch, 2 rocker 
| ZDM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZDM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Dimmer, Wall-mount, 230v, 500W, 3-way, 3 Wire, 2 rocker 
|-
| ACT
| 3-way Relay Switch, 2 rocker
| ZRM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZRM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Relay, Wall-mount, 230v, 6A, 3-way, 3 Wire, 2 rocker - '''Status polling does not work with Vera''' 
|-
| Innovus
| Relay Switch Adapter
| RAone SmartPower
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartpower_zw_tech_doc.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Innovus
| Dimmer Switch Adapter
| RAone SmartDimmer
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartdimmer-00110001-tech.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Intermatic
| Screw-in Module
| HA05C
| 
| Nov 2008
| Outdoor
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Easy install, easy to pair with Vera!
|-
| Merten
| Radio sensor cover for dimmer inserts
| 5026xx, 5036xx, 5046xx
| 6,2,7,1,5
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5026_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Radio sensor cover for switch inserts
| 5024xx, 5034xx, 5044xx
| 6,2,27,2,2
|  
| Indoor
| [http://www.merten.de/download/DL_doku/5024xx_5034xx_5044xx_Sensorflaeche4pin_CONNECT_INT.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Single Radio flush-mounted receiver
| 507001
| 6,2,27,2,2
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5070_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| switch, flush-mounted
| 507501, 507601
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5075_581_00_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Merten
| 1-gang universal dimmer, flush-mounted
| 507900
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5079_581_01_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Schlage
| Lamp Module
| RP200
| 1.0
| Aug 2009
| Indoor
| [http://consumer.schlage.com/products/Productdetail3.asp?StyleID=139&FinishID=12&FunctionID=77 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Works well Sold with Schlage LiNK lock system
|-
| Leviton
| Dimmer Switch
| VRI06-1LX
|  
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=305784&section=25501 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well
|-
| Leviton
| 4-Scene Controller with Switch
| VRCS4-MRX
| 7,2,67,0,2
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=433270&section=28563 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well, pair as per [http://wiki.micasaverde.com/index.php/Leviton_Scene_Controller Leviton 4-Scene Controller], then again holding "2" and "4" to pair the Switch ("Load") itself.
|}

=== '''Plug & Receptacle Devices''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Intermatic
| In-Wall Receptacle
| CA3500
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=105&products_id=97 Link]
| [http://www.amazon.com/review/product/B000U3XYPA/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| 
| This is a decent, but expensive solution for in-wall receptacles. One receptacle RF controlled, the other is hot
|-
| Intermatic
| Appliance Module
| HA02C
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=108&products_id=98 Link]
| [http://www.amazon.com/Intermatic-HA02C-Settings-Heavy-Duty-Appliance/dp/B000BJSDZO/ref=sr_1_3?ie=UTF8&qid=1227467418&sr=8-3 Link]
| 
| Seems to work well
|-
| ACT
| In-Wall Receptacle
| ZRR150W
| 2.2
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| 
| Works like a champ! Easy to Install. One receptacle RF controlled, the other is hot
|-
| Cooper Wiring Devices
| In-Wall Receptacle
| RFTR9505-T
|  
|  
|  
| Indoor
| [http://solutions.cooperwiringdevices.com/common/brands.cfm?pg=Detail&brandName=CWD%20Technology&category=Aspire%20RF%20Lighting%20Control%20System%3A%20Receptacles&id=16772 Link]
|
| 
| One receptacle is RF controlled, the other is hot
|-
| Intermatic
| Outdoor Module
| HA04C
| 1
|  
| Dec 2008
| Outdoor
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Easy to Install.
|-
| Monster Central
| 1800W Appliance Module
| ML-LAS1000
| 1
|  
| Jan 2009
| Indoor
| [http://www.monstercable.com/productdisplay.asp?pin=3164 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Easy to Install. I use this as a ZWave signal repeater. Appears to be a badge-engineering of [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=309748&section=25542 Leviton VRP15-1LW]
|-
| Duwi
| Z-Wave switch 3500 W
| 05437
|  
| EU
| Feb 2009
| Indoor
| [http://www.duewi.com/ Link]
|
| ezhome
| High quality Plug-in switch, Easy install and works well
|-
| Merten
| switch, plug adapter, 2000 W
| 508519
| 6,2,7,1,5
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5085_581_01_web.pdf Link]
|  
| Ap15e
| Works well.
|}

=== '''Thermostat Devices''' ===

{| border="1" cellpadding="2"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Wayne Dalton
| Wall Stat
| WDTC-20
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/WDTC-20---Z-Wave-Thermostat-Wayne-Dalton-P599C38.aspx Link]
| [http://www.amazon.com/Wayne-Dalton-Corporation-Z-Wave-Thermostat/dp/B001F8QKYQ Link]
| 
| Has 2 inclusion modes: 1) press and release the bind button and the STAT will be included as a thermostat and works with Vera, 2) press and hold the bind button and it will be added as a binary switch for compatibility with old, non-compliant remotes. If it's added in the wrong mode, remove it and re-add it. Works great simple to use!
|-
| HAI
| Wall Stat
| RC-80BZ
|  ??
|  
| Nov 2007
| Indoor
| [http://www.homeauto.com Link]
| [http://www.homeauto.com/Downloads/Products/Omnistat/rcr80.pdf Link]
| 
| Shows up as Standard Thermostat in Vera, Hold button feature not able to control by Vera at this time. Priced above 200.00. Has internal setback programs. Works great.
|-
| RCS
| Wall Stat
| TZ43
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| 
| Shows up as Standard Thermostat in Vera, much more feature rich the the WDTC-20 but comes with a hefty price tag ($214.95). Wish Vera could use all the features in this Thermostat! '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Schlage/Trane
| Wall Stat
| Trane
|  ??
|  
|  ??
| Indoor
| [http://www.link.schlage.com/Products/Pages/Thermostat.aspx Link]
| [http://www.trane.com/Residential/Products/Thermostats Link]
| 
| It's the same thermostat as the RCS TZ43 and it has the same issue: it's accepting "Set Temp Point" commands only in the measurement unit that is dysplaied on its screen. '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Intermatic
| InTouch
| CA8900
| 
|  
| Nov 2008
| Indoor
| [http://www.smarthome-products.com/p-663-intermatic-intouch-ca8900-z-wave-digital-thermostat.aspx Link]
| 
| 
| Looks very similar to the Wayne Dalton WDTC-20 listed here. works great, simple to use
|-
| Danfoss
| Radiator thermostat
| RA PLUS-w
| 
| EU
| 
| Indoor
| [http://raplusw.com/Content/E962FC0B-6461-4319-82FE-3E1E765142CF.html Link] [http://raplusw.com/PCMPDF/Data%20sheet%20RA-PLUS-w_02.pdf Link]
| 
| 
| See: [[Danfoss Thermostat]] for installation instructions If the device cannot be configured at the final location, move the device closer to Vera and try again (this device might require a direct connection to Vera for configuration).
|}

=== '''Sensors''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| ACT
| Motion Sensor
| ZIR000 / ZIR010
| 
| EU (ZIR010) or US (ZIR000)
| 
| Indoor
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR000_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR000_instr.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR010_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR010_instr.pdf Link]
| 
| 
| Remove the cover, pair to Vera's dongle by using the push-button on the left of the circuit board. Vera must configure it to work, and it can only be configured within a few minutes of inserting the batteries. With Vera's dongle removed, remove/reinsert the batteries, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page
|-
| Express Controls aka HomeSeer
| 3-in-1 sensor (light/temperature/motion)
| HSM100 / EZMotion
| 
| EU or US
| 
| 
| [http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf Link]
| 
| 
| See [[ExpressControls3in1]] If the motion sensor does not work right after inclusion and configuration, remove the batteries for a few seconds.
|-
| EverSpring/Hawking/Home Manageables
| Door/window sensor
| SM103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=355&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110873R01_SM103_-ECR.pdf Link]
|  
| Ap15e
| Pair using the intrusion button. The sensor will accept configuration within a few minutes of the initial pairing, or of pressing the intrusion button on the back even after it's paired. Pair the device, or if it's already paired, press the intrusion button, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page. NOTE: There is some confusion about the orientation of the sensor. The main sensor body has a back (where the intrusion is), a front (where the logo and LED is), and the 2 other surfaces, one of which has a curved edge, and the other is flat. The magnet needs to go against the flat surface. And the flat surface on the magnet should be as close as possible to the flat surface on the sensor, lined up in the middle so the line which passes through the LED lines up with the sensor.
|-
| Everspring
| Motion Detector
| SP103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=354&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110874R01_SP103_%20-%20ECR.pdf Link]
|  
| Ap15e
| Works well
|-
| Fortrezz
| Water /Freeze
| WWA-001
|  ??????
| US
| Apr 2009
| Indoor
| [http://www.Fortrezz.com Link] [http://www.fortrezz.com/resources/WWA_manual_01May2009.pdf Link]
| 
| Zmistro
| Works great I would place a few in your house. Bathrooms, laundry , kitchen , basement. Great product!
|-
| Merten
| 4-gang radio transmitter, flush-mounted
| 506004
| 2,2,27,1,4
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5060_581_02_web.pdf Link]
|  
| Ap15e
| Quite complex device; partially supported by Vera; can be used as a window/door sensor (as of firmware 1.0.900) ...
|}

=== '''Door Locks''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Schlage
| Door lock and deadbolt
| BE369 (deadbolt)
| 
| Mid 2009
| Indoor
| [http://consumer.schlage.com/link/product_tour/ Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Read the instructions here: [[Schlage Lock]]
|}

=== '''Drapes/Blinds''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Electronic Solutions
| Drape/Blind motor
| DBMZ
| 
| 
| Indoor
| 
| [http://www.smarthus.info/support/manuals/zw_motorkontroll/DBMZ.pdf Link]
| 
| 
|}

=== '''Relay controls''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Intermatic
| Contactor control box
| CA3750
| 
| Nov 2007
| Indoor/Outdoor
| [http://www.intouchcontrols.com/~/media/Files/InTouchControls/Products/Spec%20Sheets/CA3750.ashx Link]
| 
| 
| Multi-instance class supported for this device. Vera is able to control each of the 2 relays independently if desired. please note unit shows as three switches this is a bug with Intermatic not a real issue.You can check the box in devices to not show the second listing of the first relay in "Dasboard" You can control heavy loads like a water heater ,pool pump motor/s. great device
|}

=== '''Window Coverings''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Merten
| Radio roller shutter push-button
| 5025xx, 5035xx, 5045xx
| 6,2,27,2,3 and 6,2,27,2,4
| EU
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5025_581_01_web.pdf Link]
|  
| Ap15e
| Open/Close buttons work well, but slide bar does not work. GUI buttons do not work with Luup release 1.0.843 and 1.0.862 (fixed with Luup release 1.0.879). Workaround: Use a Luup Scene with the following code:<tt></tt>
<tt>local lul_arguments = {}</tt>

<tt>lul_arguments["newTargetValue"]="0"</tt>

<tt>lul_resultcode,lul_resultstring,lul_job,lul_returnarguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",lul_arguments,6) </tt> Replace "6" with your device number, replace "0" with "1" for inverse action.

|-
| Duewi
| Radio roller shutter push-button
| 054368
| 6,2,51,1,0
| EU
| Jun 2009
| Indoor
| [http://www.duewi.de/index.php?productid=37344 Link]
|  
| Lutz
| Open/Close buttons work well, but slide bar does not work.
|}

Supported Hardware

2009-11-16T14:33:21Z

Cj man:

This is a page for Supported Z-Wave devices.

Alternative hardware pages exist for

*[[ZWave Add Controller|Z-Wave Handheld Remote Controls, Gateways and Scene Controllers]]
*[[IP Cameras|IP Enabled Cameras]]
*[[Insteon Supported Hardware|Insteon/X10 devices]]
*USB, or USB-Serial, [[Serial Supported Hardware|Interface devices]]

In general, any device with the Z-Wave logo should work with Vera. A list of tested Z-Wave devices is below, with specific notes for each type of device. This is a wiki, so feel free to add to the page.

== Hardware Reported to Work ==

*We strongly encourage users to list any and all products they tested and installed.
*If a product works but you did not like it, please list it anyway. It may be the only product available to some users.

 

----

'''IMPORTANT! The devices listed here have been added by installers, technicians and users like yourself. Results may vary upon installations. MiCasaVerde does not guarantee operation and compatibility with your installation. The listed devices were found to work with their specific installation. Mixing different series and brands of equipment is not guaranteed in any way to work with other series and brands. It is very likely that users have not fully tested all features of the devices, so it is possible that a device listed here as compatible, will not prove compatible with your hardware. If you are editing this wiki DO NOT REMOVE a listed working device if it hasn't worked for you. Seek help to get the device to work under your individual circumstance. If you are adding to this wiki, please provide links to data for the device and add any tips you feel may benefit someone wanting to implement the device into an installation.'''

----

 

=== '''Lighting Devices''' ===

{| cellpadding="2" border="1" style="width: 1220px; height: 491px;"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Leviton
| Dimmer Switch
| VRM10-1LX
| 1
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=104&products_id=170 Link]
| [http://www.amazon.com/review/product/B000ZKM7I8/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=65 mark-hc]
| This is a high quality dimmer geared towards high-end installations
|-
| Intermatic
| 300 watt dimmer
| HA06
| 
| July 2007
| Indoor
| [http://www.homesettings.com/products/modules/ha06.aspx Link]
| 
| 
| Affordable Dimmer Switch. incandescent/halogen only. Loads for 300 watts or less no neutral required. Great for dimming one bulb.
|-
| Cooper
| Accessory (3-way slave)
|
|
|
| Indoor
|
| 
|
| See [[Cooper_Accessory_Slave]]
|-
| Intermatic
| 3-way Switch
| HA18
| 
| Dec 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha18.aspx Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Affordable 3-way Switch
|-
| Intermatic
| 3-way Dimmer Switch
| HA20
| 
| Nov 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha20.aspx Link]
| [http://www.amazon.com/Intermatic-Settings-Three-Way-Dimmer-HA20C/dp/B000WS4SJ41 Link]
| 
| Affordable 3-way 600W dimmer
|-
| ACT
| 2-way Dimmer Switch
| ZDW120
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, easy to install, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 3-way Dimmer Switch
| ZDW103
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 2-way Relay Switch
| ZRW113
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Controls Florescent Lamps very well! No humming at all.
|-
| ACT
| Companion Switch
| AS101
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, The trick here is to install this device where the power comes in.
|-
| ACT 
| 3-way Dimmer Switch, 2 rocker 
| ZDM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZDM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Dimmer, Wall-mount, 230v, 500W, 3-way, 3 Wire, 2 rocker 
|-
| ACT
| 3-way Relay Switch, 2 rocker
| ZRM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZRM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Relay, Wall-mount, 230v, 6A, 3-way, 3 Wire, 2 rocker - '''Status polling does not work with Vera''' 
|-
| Innovus
| Relay Switch Adapter
| RAone SmartPower
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartpower_zw_tech_doc.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Innovus
| Dimmer Switch Adapter
| RAone SmartDimmer
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartdimmer-00110001-tech.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Intermatic
| Screw-in Module
| HA05C
| 
| Nov 2008
| Outdoor
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Easy install, easy to pair with Vera!
|-
| Merten
| Radio sensor cover for dimmer inserts
| 5026xx, 5036xx, 5046xx
| 6,2,7,1,5
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5026_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Radio sensor cover for switch inserts
| 5024xx, 5034xx, 5044xx
| 6,2,27,2,2
|  
| Indoor
| [http://www.merten.de/download/DL_doku/5024xx_5034xx_5044xx_Sensorflaeche4pin_CONNECT_INT.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Single Radio flush-mounted receiver
| 507001
| 6,2,27,2,2
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5070_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| switch, flush-mounted
| 507501, 507601
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5075_581_00_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Merten
| 1-gang universal dimmer, flush-mounted
| 507900
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5079_581_01_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Schlage
| Lamp Module
| RP200
| 1.0
| Aug 2009
| Indoor
| [http://consumer.schlage.com/products/Productdetail3.asp?StyleID=139&FinishID=12&FunctionID=77 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Works well Sold with Schlage LiNK lock system
|-
| Leviton
| Dimmer Switch
| VRI06-1LX
|  
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=305784&section=25501 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well
|-
| Leviton
| 4-Scene Controller with Switch
| VRCS4-MRX
| 7,2,67,0,2
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=433270&section=28563 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well, pair as per [http://wiki.micasaverde.com/index.php/Leviton_Scene_Controller Leviton 4-Scene Controller], then again holding "2" and "4" to pair the Switch ("Load") itself.
|}

=== '''Plug & Receptacle Devices''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Intermatic
| In-Wall Receptacle
| CA3500
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=105&products_id=97 Link]
| [http://www.amazon.com/review/product/B000U3XYPA/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| 
| This is a decent, but expensive solution for in-wall receptacles. One receptacle RF controlled, the other is hot
|-
| Intermatic
| Appliance Module
| HA02C
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=108&products_id=98 Link]
| [http://www.amazon.com/Intermatic-HA02C-Settings-Heavy-Duty-Appliance/dp/B000BJSDZO/ref=sr_1_3?ie=UTF8&qid=1227467418&sr=8-3 Link]
| 
| Seems to work well
|-
| ACT
| In-Wall Receptacle
| ZRR150W
| 2.2
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| 
| Works like a champ! Easy to Install. One receptacle RF controlled, the other is hot
|-
| Cooper Wiring Devices
| In-Wall Receptacle
| RFTR9505-T
|  
|  
|  
| Indoor
| [http://solutions.cooperwiringdevices.com/common/brands.cfm?pg=Detail&brandName=CWD%20Technology&category=Aspire%20RF%20Lighting%20Control%20System%3A%20Receptacles&id=16772 Link]
|
| 
| One receptacle is RF controlled, the other is hot
|-
| Intermatic
| Outdoor Module
| HA04C
| 1
|  
| Dec 2008
| Outdoor
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Easy to Install.
|-
| Monster Central
| 1800W Appliance Module
| ML-LAS1000
| 1
|  
| Jan 2009
| Indoor
| [http://www.monstercable.com/productdisplay.asp?pin=3164 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Easy to Install. I use this as a ZWave signal repeater. Appears to be a badge-engineering of [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=309748&section=25542 Leviton VRP15-1LW]
|-
| Duwi
| Z-Wave switch 3500 W
| 05437
|  
| EU
| Feb 2009
| Indoor
| [http://www.duewi.com/ Link]
|
| ezhome
| High quality Plug-in switch, Easy install and works well
|-
| Merten
| switch, plug adapter, 2000 W
| 508519
| 6,2,7,1,5
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5085_581_01_web.pdf Link]
|  
| Ap15e
| Works well.
|}

=== '''Thermostat Devices''' ===

{| border="1" cellpadding="2"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Wayne Dalton
| Wall Stat
| WDTC-20
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/WDTC-20---Z-Wave-Thermostat-Wayne-Dalton-P599C38.aspx Link]
| [http://www.amazon.com/Wayne-Dalton-Corporation-Z-Wave-Thermostat/dp/B001F8QKYQ Link]
| 
| Has 2 inclusion modes: 1) press and release the bind button and the STAT will be included as a thermostat and works with Vera, 2) press and hold the bind button and it will be added as a binary switch for compatibility with old, non-compliant remotes. If it's added in the wrong mode, remove it and re-add it. Works great simple to use!
|-
| HAI
| Wall Stat
| RC-80BZ
|  ??
|  
| Nov 2007
| Indoor
| [http://www.homeauto.com Link]
| [http://www.homeauto.com/Downloads/Products/Omnistat/rcr80.pdf Link]
| 
| Shows up as Standard Thermostat in Vera, Hold button feature not able to control by Vera at this time. Priced above 200.00. Has internal setback programs. Works great.
|-
| RCS
| Wall Stat
| TZ43
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| 
| Shows up as Standard Thermostat in Vera, much more feature rich the the WDTC-20 but comes with a hefty price tag ($214.95). Wish Vera could use all the features in this Thermostat! '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Schlage
| Wall Stat
| Trane
|  ??
|  
|  ??
| Indoor
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| 
| Shows up as Standard Thermostat in Vera, much more feature rich the the WDTC-20 but comes with a hefty price tag ($214.95). Wish Vera could use all the features in this Thermostat! '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862 (luup)'''
|-
| Intermatic
| InTouch
| CA8900
| 
|  
| Nov 2008
| Indoor
| [http://www.smarthome-products.com/p-663-intermatic-intouch-ca8900-z-wave-digital-thermostat.aspx Link]
| 
| 
| Looks very similar to the Wayne Dalton WDTC-20 listed here. works great, simple to use
|-
| Danfoss
| Radiator thermostat
| RA PLUS-w
| 
| EU
| 
| Indoor
| [http://raplusw.com/Content/E962FC0B-6461-4319-82FE-3E1E765142CF.html Link] [http://raplusw.com/PCMPDF/Data%20sheet%20RA-PLUS-w_02.pdf Link]
| 
| 
| See: [[Danfoss Thermostat]] for installation instructions If the device cannot be configured at the final location, move the device closer to Vera and try again (this device might require a direct connection to Vera for configuration).
|}

=== '''Sensors''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| ACT
| Motion Sensor
| ZIR000 / ZIR010
| 
| EU (ZIR010) or US (ZIR000)
| 
| Indoor
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR000_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR000_instr.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR010_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR010_instr.pdf Link]
| 
| 
| Remove the cover, pair to Vera's dongle by using the push-button on the left of the circuit board. Vera must configure it to work, and it can only be configured within a few minutes of inserting the batteries. With Vera's dongle removed, remove/reinsert the batteries, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page
|-
| Express Controls aka HomeSeer
| 3-in-1 sensor (light/temperature/motion)
| HSM100 / EZMotion
| 
| EU or US
| 
| 
| [http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf Link]
| 
| 
| See [[ExpressControls3in1]] If the motion sensor does not work right after inclusion and configuration, remove the batteries for a few seconds.
|-
| EverSpring/Hawking/Home Manageables
| Door/window sensor
| SM103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=355&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110873R01_SM103_-ECR.pdf Link]
|  
| Ap15e
| Pair using the intrusion button. The sensor will accept configuration within a few minutes of the initial pairing, or of pressing the intrusion button on the back even after it's paired. Pair the device, or if it's already paired, press the intrusion button, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page. NOTE: There is some confusion about the orientation of the sensor. The main sensor body has a back (where the intrusion is), a front (where the logo and LED is), and the 2 other surfaces, one of which has a curved edge, and the other is flat. The magnet needs to go against the flat surface. And the flat surface on the magnet should be as close as possible to the flat surface on the sensor, lined up in the middle so the line which passes through the LED lines up with the sensor.
|-
| Everspring
| Motion Detector
| SP103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=354&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110874R01_SP103_%20-%20ECR.pdf Link]
|  
| Ap15e
| Works well
|-
| Fortrezz
| Water /Freeze
| WWA-001
|  ??????
| US
| Apr 2009
| Indoor
| [http://www.Fortrezz.com Link] [http://www.fortrezz.com/resources/WWA_manual_01May2009.pdf Link]
| 
| Zmistro
| Works great I would place a few in your house. Bathrooms, laundry , kitchen , basement. Great product!
|-
| Merten
| 4-gang radio transmitter, flush-mounted
| 506004
| 2,2,27,1,4
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5060_581_02_web.pdf Link]
|  
| Ap15e
| Quite complex device; partially supported by Vera; can be used as a window/door sensor (as of firmware 1.0.900) ...
|}

=== '''Door Locks''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Schlage
| Door lock and deadbolt
| BE369 (deadbolt)
| 
| Mid 2009
| Indoor
| [http://consumer.schlage.com/link/product_tour/ Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Read the instructions here: [[Schlage Lock]]
|}

=== '''Drapes/Blinds''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Electronic Solutions
| Drape/Blind motor
| DBMZ
| 
| 
| Indoor
| 
| [http://www.smarthus.info/support/manuals/zw_motorkontroll/DBMZ.pdf Link]
| 
| 
|}

=== '''Relay controls''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Intermatic
| Contactor control box
| CA3750
| 
| Nov 2007
| Indoor/Outdoor
| [http://www.intouchcontrols.com/~/media/Files/InTouchControls/Products/Spec%20Sheets/CA3750.ashx Link]
| 
| 
| Multi-instance class supported for this device. Vera is able to control each of the 2 relays independently if desired. please note unit shows as three switches this is a bug with Intermatic not a real issue.You can check the box in devices to not show the second listing of the first relay in "Dasboard" You can control heavy loads like a water heater ,pool pump motor/s. great device
|}

=== '''Window Coverings''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Merten
| Radio roller shutter push-button
| 5025xx, 5035xx, 5045xx
| 6,2,27,2,3 and 6,2,27,2,4
| EU
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5025_581_01_web.pdf Link]
|  
| Ap15e
| Open/Close buttons work well, but slide bar does not work. GUI buttons do not work with Luup release 1.0.843 and 1.0.862 (fixed with Luup release 1.0.879). Workaround: Use a Luup Scene with the following code:<tt></tt>
<tt>local lul_arguments = {}</tt>

<tt>lul_arguments["newTargetValue"]="0"</tt>

<tt>lul_resultcode,lul_resultstring,lul_job,lul_returnarguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",lul_arguments,6) </tt> Replace "6" with your device number, replace "0" with "1" for inverse action.

|-
| Duewi
| Radio roller shutter push-button
| 054368
| 6,2,51,1,0
| EU
| Jun 2009
| Indoor
| [http://www.duewi.de/index.php?productid=37344 Link]
|  
| Lutz
| Open/Close buttons work well, but slide bar does not work.
|}

Supported Hardware

2009-11-16T14:17:49Z

Cj man: /* Thermostat Devices */

This is a page for Supported Z-Wave devices.

Alternative hardware pages exist for

*[[ZWave Add Controller|Z-Wave Handheld Remote Controls, Gateways and Scene Controllers]]
*[[IP Cameras|IP Enabled Cameras]]
*[[Insteon Supported Hardware|Insteon/X10 devices]]
*USB, or USB-Serial, [[Serial Supported Hardware|Interface devices]]

In general, any device with the Z-Wave logo should work with Vera. A list of tested Z-Wave devices is below, with specific notes for each type of device. This is a wiki, so feel free to add to the page.

== Hardware Reported to Work ==

*We strongly encourage users to list any and all products they tested and installed.
*If a product works but you did not like it, please list it anyway. It may be the only product available to some users.

 

----

'''IMPORTANT! The devices listed here have been added by installers, technicians and users like yourself. Results may vary upon installations. MiCasaVerde does not guarantee operation and compatibility with your installation. The listed devices were found to work with their specific installation. Mixing different series and brands of equipment is not guaranteed in any way to work with other series and brands. It is very likely that users have not fully tested all features of the devices, so it is possible that a device listed here as compatible, will not prove compatible with your hardware. If you are editing this wiki DO NOT REMOVE a listed working device if it hasn't worked for you. Seek help to get the device to work under your individual circumstance. If you are adding to this wiki, please provide links to data for the device and add any tips you feel may benefit someone wanting to implement the device into an installation.'''

----

 

=== '''Lighting Devices''' ===

{| cellpadding="2" border="1" style="width: 1220px; height: 491px;"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Leviton
| Dimmer Switch
| VRM10-1LX
| 1
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=104&products_id=170 Link]
| [http://www.amazon.com/review/product/B000ZKM7I8/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=65 mark-hc]
| This is a high quality dimmer geared towards high-end installations
|-
| Intermatic
| 300 watt dimmer
| HA06
| 
| July 2007
| Indoor
| [http://www.homesettings.com/products/modules/ha06.aspx Link]
| 
| 
| Affordable Dimmer Switch. incandescent/halogen only. Loads for 300 watts or less no neutral required. Great for dimming one bulb.
|-
| Cooper
| Accessory (3-way slave)
|
|
|
| Indoor
|
| 
|
| See [[Cooper_Accessory_Slave]]
|-
| Intermatic
| 3-way Switch
| HA18
| 
| Dec 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha18.aspx Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Affordable 3-way Switch
|-
| Intermatic
| 3-way Dimmer Switch
| HA20
| 
| Nov 2008
| Indoor
| [http://www.homesettings.com/products/new%20products/ha20.aspx Link]
| [http://www.amazon.com/Intermatic-Settings-Three-Way-Dimmer-HA20C/dp/B000WS4SJ41 Link]
| 
| Affordable 3-way 600W dimmer
|-
| ACT
| 2-way Dimmer Switch
| ZDW120
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://store.homeseer.com/store/ZDW120---Z-Wave-600-Watt-2-Wire-Dimmer-ACT-HomePro-P17C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, easy to install, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 3-way Dimmer Switch
| ZDW103
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://store.homeseer.com/store/ZDW103---Z-Wave-500-Watt-3-way-Dimmer-ACT-HomePro-P19C64.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, LED is a very bright blue....can be programmed to be off when the light is off or on.
|-
| ACT
| 2-way Relay Switch
| ZRW113
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://store.homeseer.com/store/ZRW113---Z-Wave-20-Amp-3-way-ISO-Relay-ACT-HomePro-P491C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Controls Florescent Lamps very well! No humming at all.
|-
| ACT
| Companion Switch
| AS101
| 
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://store.homeseer.com/store/AS101---Z-Wave-3-Way-Companion-Switch-ACT-HomePro-P10C63.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Works well, can be tricky to install due to the different combination of 3 way circuits, The trick here is to install this device where the power comes in.
|-
| ACT 
| 3-way Dimmer Switch, 2 rocker 
| ZDM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZDM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Dimmer, Wall-mount, 230v, 500W, 3-way, 3 Wire, 2 rocker 
|-
| ACT
| 3-way Relay Switch, 2 rocker
| ZRM230 
| 1.1 
| Aug 2009 
| Indoor 
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZRM230_spec.pdf Link] 
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker] 
| Relay, Wall-mount, 230v, 6A, 3-way, 3 Wire, 2 rocker - '''Status polling does not work with Vera''' 
|-
| Innovus
| Relay Switch Adapter
| RAone SmartPower
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartpower_zw_tech_doc.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Innovus
| Dimmer Switch Adapter
| RAone SmartDimmer
|  
| Aug 2009
| Indoor
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smartdimmer-00110001-tech.pdf Link]
|  
| [http://forum.micasaverde.com/index.php?action=profile;u=3015 TedStriker]
| Works very well + it has a build in powermeter which works perfect with Vera
|-
| Intermatic
| Screw-in Module
| HA05C
| 
| Nov 2008
| Outdoor
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://store.homeseer.com/store/HA05C---Z-Wave-IndoorOutdoor-Screw-in-Module-Intermatic-HomeSettings-P1C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=49 WSeverino]
| Easy install, easy to pair with Vera!
|-
| Merten
| Radio sensor cover for dimmer inserts
| 5026xx, 5036xx, 5046xx
| 6,2,7,1,5
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5026_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Radio sensor cover for switch inserts
| 5024xx, 5034xx, 5044xx
| 6,2,27,2,2
|  
| Indoor
| [http://www.merten.de/download/DL_doku/5024xx_5034xx_5044xx_Sensorflaeche4pin_CONNECT_INT.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| Single Radio flush-mounted receiver
| 507001
| 6,2,27,2,2
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5070_581_01_web.pdf Link]
|  
| Ap15e
| Works well
|-
| Merten
| switch, flush-mounted
| 507501, 507601
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5075_581_00_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Merten
| 1-gang universal dimmer, flush-mounted
| 507900
|  
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5079_581_01_web.pdf Link]
|  
| Ap15e
| Works well (according to [http://forum.micasaverde.com/index.php?topic=276.15 Link])
|-
| Schlage
| Lamp Module
| RP200
| 1.0
| Aug 2009
| Indoor
| [http://consumer.schlage.com/products/Productdetail3.asp?StyleID=139&FinishID=12&FunctionID=77 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Works well Sold with Schlage LiNK lock system
|-
| Leviton
| Dimmer Switch
| VRI06-1LX
|  
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=305784&section=25501 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well
|-
| Leviton
| 4-Scene Controller with Switch
| VRCS4-MRX
| 7,2,67,0,2
| Aug 2009
| Indoor
| [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=433270&section=28563 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Works well, pair as per [http://wiki.micasaverde.com/index.php/Leviton_Scene_Controller Leviton 4-Scene Controller], then again holding "2" and "4" to pair the Switch ("Load") itself.
|}

=== '''Plug & Receptacle Devices''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Intermatic
| In-Wall Receptacle
| CA3500
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=105&products_id=97 Link]
| [http://www.amazon.com/review/product/B000U3XYPA/ref=dp_top_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1 Link]
| 
| This is a decent, but expensive solution for in-wall receptacles. One receptacle RF controlled, the other is hot
|-
| Intermatic
| Appliance Module
| HA02C
| 1
|  
| Nov 2008
| Indoor
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=108&products_id=98 Link]
| [http://www.amazon.com/Intermatic-HA02C-Settings-Heavy-Duty-Appliance/dp/B000BJSDZO/ref=sr_1_3?ie=UTF8&qid=1227467418&sr=8-3 Link]
| 
| Seems to work well
|-
| ACT
| In-Wall Receptacle
| ZRR150W
| 2.2
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| [http://store.homeseer.com/store/ZRR150W---Z-Wave-Split-Duplex-Receptacle-ACT-HomePro-P528C123.aspx Link]
| 
| Works like a champ! Easy to Install. One receptacle RF controlled, the other is hot
|-
| Cooper Wiring Devices
| In-Wall Receptacle
| RFTR9505-T
|  
|  
|  
| Indoor
| [http://solutions.cooperwiringdevices.com/common/brands.cfm?pg=Detail&brandName=CWD%20Technology&category=Aspire%20RF%20Lighting%20Control%20System%3A%20Receptacles&id=16772 Link]
|
| 
| One receptacle is RF controlled, the other is hot
|-
| Intermatic
| Outdoor Module
| HA04C
| 1
|  
| Dec 2008
| Outdoor
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://store.homeseer.com/store/HA04C---Z-Wave-Outdoor-Module-Intermatic-HomeSettings-P6C62.aspx Link]
| [http://forum.micasaverde.com/index.php?action=profile;u=66 Kozanator]
| Easy to Install.
|-
| Monster Central
| 1800W Appliance Module
| ML-LAS1000
| 1
|  
| Jan 2009
| Indoor
| [http://www.monstercable.com/productdisplay.asp?pin=3164 Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2618 guessed]
| Easy to Install. I use this as a ZWave signal repeater. Appears to be a badge-engineering of [http://www.leviton.com/OA_HTML/ibeCCtpItmDspRte.jsp?item=309748&section=25542 Leviton VRP15-1LW]
|-
| Duwi
| Z-Wave switch 3500 W
| 05437
|  
| EU
| Feb 2009
| Indoor
| [http://www.duewi.com/ Link]
|
| ezhome
| High quality Plug-in switch, Easy install and works well
|-
| Merten
| switch, plug adapter, 2000 W
| 508519
| 6,2,7,1,5
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5085_581_01_web.pdf Link]
|  
| Ap15e
| Works well.
|}

=== '''Thermostat Devices''' ===

{| border="1" cellpadding="2"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Wayne Dalton
| Wall Stat
| WDTC-20
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/WDTC-20---Z-Wave-Thermostat-Wayne-Dalton-P599C38.aspx Link]
| [http://www.amazon.com/Wayne-Dalton-Corporation-Z-Wave-Thermostat/dp/B001F8QKYQ Link]
| 
| Has 2 inclusion modes: 1) press and release the bind button and the STAT will be included as a thermostat and works with Vera, 2) press and hold the bind button and it will be added as a binary switch for compatibility with old, non-compliant remotes. If it's added in the wrong mode, remove it and re-add it. Works great simple to use!
|-
| HAI
| Wall Stat
| RC-80BZ
|  ??
|  
| Nov 2007
| Indoor
| [http://www.homeauto.com Link]
| [http://www.homeauto.com/Downloads/Products/Omnistat/rcr80.pdf Link]
| 
| Shows up as Standard Thermostat in Vera, Hold button feature not able to control by Vera at this time. Priced above 200.00. Has internal setback programs. Works great.
|-
| RCS
| Wall Stat
| TZ43
|  ??
|  
| Nov 2008
| Indoor
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| [http://store.homeseer.com/store/TZ43---Z-Wave-Thermostat-RCS-P627C67.aspx Link]
| 
| Shows up as Standard Thermostat in Vera, much more feature rich the the WDTC-20 but comes with a hefty price tag ($214.95). Wish Vera could use all the features in this Thermostat! '''Note:'''''You need to set the thermostat to show the temperature, on its display, in Celsius degree in order to be able to receive "Set Temp" commands from Vera. This is no longer required in firmwares above '''''1.0.862'''
|-
| Intermatic
| InTouch
| CA8900
| 
|  
| Nov 2008
| Indoor
| [http://www.smarthome-products.com/p-663-intermatic-intouch-ca8900-z-wave-digital-thermostat.aspx Link]
| 
| 
| Looks very similar to the Wayne Dalton WDTC-20 listed here. works great, simple to use
|-
| Danfoss
| Radiator thermostat
| RA PLUS-w
| 
| EU
| 
| Indoor
| [http://raplusw.com/Content/E962FC0B-6461-4319-82FE-3E1E765142CF.html Link] [http://raplusw.com/PCMPDF/Data%20sheet%20RA-PLUS-w_02.pdf Link]
| 
| 
| See: [[Danfoss Thermostat]] for installation instructions If the device cannot be configured at the final location, move the device closer to Vera and try again (this device might require a direct connection to Vera for configuration).
|}

=== '''Sensors''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| ACT
| Motion Sensor
| ZIR000 / ZIR010
| 
| EU (ZIR010) or US (ZIR000)
| 
| Indoor
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR000_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR000_instr.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR010_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR010_instr.pdf Link]
| 
| 
| Remove the cover, pair to Vera's dongle by using the push-button on the left of the circuit board. Vera must configure it to work, and it can only be configured within a few minutes of inserting the batteries. With Vera's dongle removed, remove/reinsert the batteries, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page
|-
| Express Controls aka HomeSeer
| 3-in-1 sensor (light/temperature/motion)
| HSM100 / EZMotion
| 
| EU or US
| 
| 
| [http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf Link]
| 
| 
| See [[ExpressControls3in1]] If the motion sensor does not work right after inclusion and configuration, remove the batteries for a few seconds.
|-
| EverSpring/Hawking/Home Manageables
| Door/window sensor
| SM103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=355&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110873R01_SM103_-ECR.pdf Link]
|  
| Ap15e
| Pair using the intrusion button. The sensor will accept configuration within a few minutes of the initial pairing, or of pressing the intrusion button on the back even after it's paired. Pair the device, or if it's already paired, press the intrusion button, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page. NOTE: There is some confusion about the orientation of the sensor. The main sensor body has a back (where the intrusion is), a front (where the logo and LED is), and the 2 other surfaces, one of which has a curved edge, and the other is flat. The magnet needs to go against the flat surface. And the flat surface on the magnet should be as close as possible to the flat surface on the sensor, lined up in the middle so the line which passes through the LED lines up with the sensor.
|-
| Everspring
| Motion Detector
| SP103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=354&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110874R01_SP103_%20-%20ECR.pdf Link]
|  
| Ap15e
| Works well
|-
| Fortrezz
| Water /Freeze
| WWA-001
|  ??????
| US
| Apr 2009
| Indoor
| [http://www.Fortrezz.com Link] [http://www.fortrezz.com/resources/WWA_manual_01May2009.pdf Link]
| 
| Zmistro
| Works great I would place a few in your house. Bathrooms, laundry , kitchen , basement. Great product!
|-
| Merten
| 4-gang radio transmitter, flush-mounted
| 506004
| 2,2,27,1,4
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5060_581_02_web.pdf Link]
|  
| Ap15e
| Quite complex device; partially supported by Vera; can be used as a window/door sensor (as of firmware 1.0.900) ...
|}

=== '''Door Locks''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Schlage
| Door lock and deadbolt
| BE369 (deadbolt)
| 
| Mid 2009
| Indoor
| [http://consumer.schlage.com/link/product_tour/ Link]
| 
| [http://forum.micasaverde.com/index.php?action=profile;u=2870 LibraSun]
| Read the instructions here: [[Schlage Lock]]
|}

=== '''Drapes/Blinds''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Electronic Solutions
| Drape/Blind motor
| DBMZ
| 
| 
| Indoor
| 
| [http://www.smarthus.info/support/manuals/zw_motorkontroll/DBMZ.pdf Link]
| 
| 
|}

=== '''Relay controls''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Intermatic
| Contactor control box
| CA3750
| 
| Nov 2007
| Indoor/Outdoor
| [http://www.intouchcontrols.com/~/media/Files/InTouchControls/Products/Spec%20Sheets/CA3750.ashx Link]
| 
| 
| Multi-instance class supported for this device. Vera is able to control each of the 2 relays independently if desired. please note unit shows as three switches this is a bug with Intermatic not a real issue.You can check the box in devices to not show the second listing of the first relay in "Dasboard" You can control heavy loads like a water heater ,pool pump motor/s. great device
|}

=== '''Window Coverings''' ===

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| Merten
| Radio roller shutter push-button
| 5025xx, 5035xx, 5045xx
| 6,2,27,2,3 and 6,2,27,2,4
| EU
| Apr 2009
| Indoor
| [http://www.merten.de/download/DL_doku/V5025_581_01_web.pdf Link]
|  
| Ap15e
| Open/Close buttons work well, but slide bar does not work. GUI buttons do not work with Luup release 1.0.843 and 1.0.862 (fixed with Luup release 1.0.879). Workaround: Use a Luup Scene with the following code:<tt></tt>
<tt>local lul_arguments = {}</tt>

<tt>lul_arguments["newTargetValue"]="0"</tt>

<tt>lul_resultcode,lul_resultstring,lul_job,lul_returnarguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",lul_arguments,6) </tt> Replace "6" with your device number, replace "0" with "1" for inverse action.

|-
| Duewi
| Radio roller shutter push-button
| 054368
| 6,2,51,1,0
| EU
| Jun 2009
| Indoor
| [http://www.duewi.de/index.php?productid=37344 Link]
|  
| Lutz
| Open/Close buttons work well, but slide bar does not work.
|}

Advanced Network Setup

2009-11-05T15:35:46Z

Cj man:

<div>
'''=== INSTALL DYNDNS PACKAGE ====''' - login to vera using telnet or ssh then: ( telnet local.findvera.com ) cd /tmp wget [http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk] tar xzvf ddns-scripts_1.0.0-1_mipsel.ipk cd / tar xzvf /tmp/data.tar.gz '' ''vim /etc/config/ddns (press ''INSERT'' to start editing, to save and quit press ''ESC'' then write '':wq'' and press ''ENTER'')

Note: DynDns package is installed by default for firmware versions 1.0.616 and above

''Note: You can edit the file also from the web interface, go to: Advanced->Net&Wifi->Advanced Settings ->System->File Edito''r

 
<div align="center">'''A. Vera behind another router'''</div>
 '''=== FORWARD PORTS TO VERA ===''' If you're using Vera behind your router you'll need to forward some ports to it to make it work: '''PORT 80''' : it's used for the web page viewing, you can secure access by using username and password (go to ''SETUP->USERS'': add an user and check ''"Require a username and password to access Vera from within my home network."'' then press ''SAVE'') '''PORT 23''' : telnet access, not recommended because it can't be secured, anyone can login remotely '''PORT 22''' : ssh access, it's enabled after you set a root password and then telnet access is disabled. 

If you don't know how to forward ports from your router have a look here: [http://portforward.com/ http://portforward.com/] '''===  VERA NETWORK SETTINGS ===''' You've mentioned that your router can't assign the same IP every time. You can overcome this by setting a static IP to vera. Go to SETUP->ADVANCED->Net&Wi-Fi '''= IP Address =''' How can I connect to the Internet? = STATIC Set an IP from your class ie: 192.168.81.2 Subnet Mask 255.255.255.0 Gateway: 192.168.81.1 (your router IP) DNS: 192.168.81.1 (and your provider's DNS server) '''= Firewall =''' Since you already have other router in front of Vera, set firewall to 'No Firewall - bridge'. '''= Lan ='''  Since you have another DHCP server, set Vera's DHCP to 'disable'. Note: I've noticed that your Belkin router has the same IP address as Vera's internal lan: 192.168.81.1. If you're using Vera in 'Bridge' mode you should change Vera's LAN IP to an address different from your Belkin router's IP. (i.e.: set it to 192.168.8.1 ) 
<div align="center">'''B.Vera connected directly to the internet'''</div>
 '''=== OPEN PORTS ON VERA ===''' If Vera's connected directly to the internet and you have your firewall activated you'll need to open port 80 to access Vera's UI. Go to ADVANCED->Net&Wi-Fi->Advanced configuration OpenWRT Web UI Will open. Here you need to go to: NETWORK->FIREWALL New Rule:  Accept -> press ADD Select from the upper drop-down Protocol: TCP -> press ADD Destination Ports: 80 Press SAVE Press bottom 'Apply Changes' And now you should be able to access your Vera. Protect Vera UI with User and Password Right now everyone can access your Vera UI.  Go to 'Users' tab, check "Require a username and password to access Vera from within my home network." and add a Username. This will prevent unauthorized persons from having access to your Vera web site. '''=== FORWARD PORTS FROM VERA TO Another IP device ===''' In order to setup port forwarding go to: Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Firewall New Rule: FORWARD -> press ADD Forward to: ''internal IP of your camera'' (i.e. 192.168.81.150) Port: ''port of your camera'' (80 is for HTTP) Also select from the upper drop down:     Protocol: TCP     Destination Ports: ''Vera external port ''(i.e. 81) Press SAVE and then 'Apply Changes' from the bottom of the page. In this scenario I've created a port forwarding from Vera's external IP, on port 81, to 192.168.81.150 internal IP to port 80. So [http://vera_external_ip:81/ http://vera_external_ip:81] requests will go to [http://192.168.81.150/ http://192.168.81.150] Note: If you don't know your camera IP and this is dynamically allocated by Vera's DHCP, follow these steps after you note down your camera MAC Address (which should be on the bottom of the device). '''-= Identify Camera DHCP IP =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Status->DHCP Clients According to the MAC address you should be able to identify the IP address here. In order for the camera not to change its IP, you should also set the DHCP server to allocate the same IP every time: '''-= Configure DHCP Server leases =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Hosts Complete the  "MAC Address" and the "IP Address" fields from "Static IP addresses (for DHCP)" tab with the current MAC and IP of your camera then press Add, Save Changes and Apply.
</div>

Advanced Network Setup

2009-11-05T15:35:10Z

Cj man:

<div>
'''=== INSTALL DYNDNS PACKAGE ====''' - login to vera using telnet or ssh then: ( telnet local.findvera.com ) cd /tmp wget [http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk] tar xzvf ddns-scripts_1.0.0-1_mipsel.ipk cd / tar xzvf /tmp/data.tar.gz '' ''vim /etc/config/ddns (press ''INSERT'' to start editing, to save and quit press ''ESC'' then write '':wq'' and press ''ENTER'')

Note: DynDns package is installed by default for firmware versions 1.0.616 and above

''Note: You can edit the file also from the web interface, go to: Advanced->Net&Wifi->Advanced Settings ->System->File Edito''r

<div align="center">'''A. Vera behind another router'''</div>
 '''=== FORWARD PORTS TO VERA ===''' If you're using Vera behind your router you'll need to forward some ports to it to make it work: '''PORT 80''' : it's used for the web page viewing, you can secure access by using username and password (go to ''SETUP->USERS'': add an user and check ''"Require a username and password to access Vera from within my home network."'' then press ''SAVE'') '''PORT 23''' : telnet access, not recommended because it can't be secured, anyone can login remotely '''PORT 22''' : ssh access, it's enabled after you set a root password and then telnet access is disabled. 

If you don't know how to forward ports from your router have a look here: [http://portforward.com/ http://portforward.com/] '''===  VERA NETWORK SETTINGS ===''' You've mentioned that your router can't assign the same IP every time. You can overcome this by setting a static IP to vera. Go to SETUP->ADVANCED->Net&Wi-Fi '''= IP Address =''' How can I connect to the Internet? = STATIC Set an IP from your class ie: 192.168.81.2 Subnet Mask 255.255.255.0 Gateway: 192.168.81.1 (your router IP) DNS: 192.168.81.1 (and your provider's DNS server) '''= Firewall =''' Since you already have other router in front of Vera, set firewall to 'No Firewall - bridge'. '''= Lan ='''  Since you have another DHCP server, set Vera's DHCP to 'disable'. Note: I've noticed that your Belkin router has the same IP address as Vera's internal lan: 192.168.81.1. If you're using Vera in 'Bridge' mode you should change Vera's LAN IP to an address different from your Belkin router's IP. (i.e.: set it to 192.168.8.1 ) 
<div align="center">'''B.Vera connected directly to the internet'''</div>
 '''=== OPEN PORTS ON VERA ===''' If Vera's connected directly to the internet and you have your firewall activated you'll need to open port 80 to access Vera's UI. Go to ADVANCED->Net&Wi-Fi->Advanced configuration OpenWRT Web UI Will open. Here you need to go to: NETWORK->FIREWALL New Rule:  Accept -> press ADD Select from the upper drop-down Protocol: TCP -> press ADD Destination Ports: 80 Press SAVE Press bottom 'Apply Changes' And now you should be able to access your Vera. Protect Vera UI with User and Password Right now everyone can access your Vera UI.  Go to 'Users' tab, check "Require a username and password to access Vera from within my home network." and add a Username. This will prevent unauthorized persons from having access to your Vera web site. '''=== FORWARD PORTS FROM VERA TO Another IP device ===''' In order to setup port forwarding go to: Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Firewall New Rule: FORWARD -> press ADD Forward to: ''internal IP of your camera'' (i.e. 192.168.81.150) Port: ''port of your camera'' (80 is for HTTP) Also select from the upper drop down:     Protocol: TCP     Destination Ports: ''Vera external port ''(i.e. 81) Press SAVE and then 'Apply Changes' from the bottom of the page. In this scenario I've created a port forwarding from Vera's external IP, on port 81, to 192.168.81.150 internal IP to port 80. So [http://vera_external_ip:81/ http://vera_external_ip:81] requests will go to [http://192.168.81.150/ http://192.168.81.150] Note: If you don't know your camera IP and this is dynamically allocated by Vera's DHCP, follow these steps after you note down your camera MAC Address (which should be on the bottom of the device). '''-= Identify Camera DHCP IP =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Status->DHCP Clients According to the MAC address you should be able to identify the IP address here. In order for the camera not to change its IP, you should also set the DHCP server to allocate the same IP every time: '''-= Configure DHCP Server leases =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Hosts Complete the  "MAC Address" and the "IP Address" fields from "Static IP addresses (for DHCP)" tab with the current MAC and IP of your camera then press Add, Save Changes and Apply.
</div>

Advanced Network Setup

2009-11-05T15:33:48Z

Cj man:

<div>
'''=== INSTALL DYNDNS PACKAGE ====''' - login to vera using telnet or ssh then: ( telnet local.findvera.com ) cd /tmp wget [http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-1_mipsel.ipk] tar xzvf ddns-scripts_1.0.0-1_mipsel.ipk cd / tar xzvf /tmp/data.tar.gz ''Note: DynDns package is installed by default for firmware verions 1.0.616 and above'' vim /etc/config/ddns (press ''INSERT'' to start editing, to save and quit press ''ESC'' then write '':wq'' and press ''ENTER'') 

''Note: You can edit the file also from the web interface, go to: Advanced->Net&Wifi->Advanced Settings ->System->File Edito''r
<div align="center">'''A. Vera behind another router'''</div>
 '''=== FORWARD PORTS TO VERA ===''' If you're using Vera behind your router you'll need to forward some ports to it to make it work: '''PORT 80''' : it's used for the web page viewing, you can secure access by using username and password (go to ''SETUP->USERS'': add an user and check ''"Require a username and password to access Vera from within my home network."'' then press ''SAVE'') '''PORT 23''' : telnet access, not recommended because it can't be secured, anyone can login remotely '''PORT 22''' : ssh access, it's enabled after you set a root password and then telnet access is disabled. 

If you don't know how to forward ports from your router have a look here: [http://portforward.com/ http://portforward.com/] '''===  VERA NETWORK SETTINGS ===''' You've mentioned that your router can't assign the same IP every time. You can overcome this by setting a static IP to vera. Go to SETUP->ADVANCED->Net&Wi-Fi '''= IP Address =''' How can I connect to the Internet? = STATIC Set an IP from your class ie: 192.168.81.2 Subnet Mask 255.255.255.0 Gateway: 192.168.81.1 (your router IP) DNS: 192.168.81.1 (and your provider's DNS server) '''= Firewall =''' Since you already have other router in front of Vera, set firewall to 'No Firewall - bridge'. '''= Lan ='''  Since you have another DHCP server, set Vera's DHCP to 'disable'. Note: I've noticed that your Belkin router has the same IP address as Vera's internal lan: 192.168.81.1. If you're using Vera in 'Bridge' mode you should change Vera's LAN IP to an address different from your Belkin router's IP. (i.e.: set it to 192.168.8.1 ) 
<div align="center">'''B.Vera connected directly to the internet'''</div>
 '''=== OPEN PORTS ON VERA ===''' If Vera's connected directly to the internet and you have your firewall activated you'll need to open port 80 to access Vera's UI. Go to ADVANCED->Net&Wi-Fi->Advanced configuration OpenWRT Web UI Will open. Here you need to go to: NETWORK->FIREWALL New Rule:  Accept -> press ADD Select from the upper drop-down Protocol: TCP -> press ADD Destination Ports: 80 Press SAVE Press bottom 'Apply Changes' And now you should be able to access your Vera. Protect Vera UI with User and Password Right now everyone can access your Vera UI.  Go to 'Users' tab, check "Require a username and password to access Vera from within my home network." and add a Username. This will prevent unauthorized persons from having access to your Vera web site. '''=== FORWARD PORTS FROM VERA TO Another IP device ===''' In order to setup port forwarding go to: Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Firewall New Rule: FORWARD -> press ADD Forward to: ''internal IP of your camera'' (i.e. 192.168.81.150) Port: ''port of your camera'' (80 is for HTTP) Also select from the upper drop down:     Protocol: TCP     Destination Ports: ''Vera external port ''(i.e. 81) Press SAVE and then 'Apply Changes' from the bottom of the page. In this scenario I've created a port forwarding from Vera's external IP, on port 81, to 192.168.81.150 internal IP to port 80. So [http://vera_external_ip:81/ http://vera_external_ip:81] requests will go to [http://192.168.81.150/ http://192.168.81.150] Note: If you don't know your camera IP and this is dynamically allocated by Vera's DHCP, follow these steps after you note down your camera MAC Address (which should be on the bottom of the device). '''-= Identify Camera DHCP IP =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Status->DHCP Clients According to the MAC address you should be able to identify the IP address here. In order for the camera not to change its IP, you should also set the DHCP server to allocate the same IP every time: '''-= Configure DHCP Server leases =-''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Hosts Complete the  "MAC Address" and the "IP Address" fields from "Static IP addresses (for DHCP)" tab with the current MAC and IP of your camera then press Add, Save Changes and Apply.
</div>

Intro Universal Remote

2009-10-07T18:02:30Z

Cj man:

Vera will allow you to use your iPhone or iPod touch as a handy universal remote control. You will see the buttons for your TV and Stereo on the iPhone/iPod display, and when you touch the button, Vera will send the command to your TV/Stereo, just like you were using the original factory remote or a normal universal remote. You will need an infrared transmit device which you will put in front of the TV/Stereo. This is what sends the actual command to the TV/Stereo.

'''Infrared device creation'''

1. Go to devices > Infrared

2. Click new IR device

3. Pick one infrared transmitter

4. Pick device type and manufacturer.

4.a. If there are any remotes whith the same manufacturer/device type, they will be displayed and you will be able to test the codes for every command. If they works, click "use this model", if not click "another model".

4.b. If there are no remotes with the same manufacturer/device type or you used "another model", a list of available codes will be displayed with a test button for each code. Click "test" buttons to see what codeset works and select either all codes or only those who works. Once selection is completed, type a model description and click "GO".

5. This will create the device and will prompt for install. Click "install".

6. Click "Save" on top left.

7. Repeat for each device you want to create.

 '''Remote creation'''

1. Go to scenes

2. Pick a scene who doesn't have a remote ("add remote" button is not pressed) and click "Add remote"

3. A list of available remotes will be displayed. Click "Create remote" on top right.

4. Type a remote description, pick a png files from those used for layout, platform iPhone, private, click Next

5. Define action zones on remote. Click and drag to resize/move them

6. For each zone defined, pick "Send a command" then from action the corresponding action (e.g. Volume/Mute, TogglePower/OnOff etc).

7. For zones who are supposed to execute a scene, pick "run a scene".

8. If the remote need to go to another page, pick "Go to another page", for "exit remote" pick corresponding action.

9. Save when you finished editing remote, then go back to Vera UI and click refresh botton at the bottom of remotes list.

10. Pick your new created remote.

11. Match remote buttons with the IR devices you previous created and those who execute scenes with a scene from dropdown.

12. Save from top left button.

 

At this point you should be able to control your IR devices with the remote. https://findvera.com/mobile pick smarphone app then pick the room where the scene with remote is, and click "go". You will be redirected to remote screen.
 

''Note: On your Vera dashboard when you click on the GO button of the remote it will execute only the scenes attached to the remote, it won't take you to the remote screen, for this you'll have to connect through the mobile page.''

 
For more information on upcoming features see [[Roadmap|the roadmap]].

Intro Universal Remote

2009-10-07T18:02:06Z

Cj man:

Vera will allow you to use your iPhone or iPod touch as a handy universal remote control. You will see the buttons for your TV and Stereo on the iPhone/iPod display, and when you touch the button, Vera will send the command to your TV/Stereo, just like you were using the original factory remote or a normal universal remote. You will need an infrared transmit device which you will put in front of the TV/Stereo. This is what sends the actual command to the TV/Stereo.

'''Infrared device creation'''

1. Go to devices > Infrared

2. Click new IR device

3. Pick one infrared transmitter

4. Pick device type and manufacturer.

4.a. If there are any remotes whith the same manufacturer/device type, they will be displayed and you will be able to test the codes for every command. If they works, click "use this model", if not click "another model".

4.b. If there are no remotes with the same manufacturer/device type or you used "another model", a list of available codes will be displayed with a test button for each code. Click "test" buttons to see what codeset works and select either all codes or only those who works. Once selection is completed, type a model description and click "GO".

5. This will create the device and will prompt for install. Click "install".

6. Click "Save" on top left.

7. Repeat for each device you want to create.

 '''Remote creation'''

1. Go to scenes

2. Pick a scene who doesn't have a remote ("add remote" button is not pressed) and click "Add remote"

3. A list of available remotes will be displayed. Click "Create remote" on top right.

4. Type a remote description, pick a png files from those used for layout, platform iPhone, private, click Next

5. Define action zones on remote. Click and drag to resize/move them

6. For each zone defined, pick "Send a command" then from action the corresponding action (e.g. Volume/Mute, TogglePower/OnOff etc).

7. For zones who are supposed to execute a scene, pick "run a scene".

8. If the remote need to go to another page, pick "Go to another page", for "exit remote" pick corresponding action.

9. Save when you finished editing remote, then go back to Vera UI and click refresh botton at the bottom of remotes list.

10. Pick your new created remote.

11. Match remote buttons with the IR devices you previous created and those who execute scenes with a scene from dropdown.

12. Save from top left button.

 

At this point you should be able to control your IR devices with the remote. https://findvera.com/mobile pick smarphone app then pick the room where the scene with remote is, and click "go". You will be redirected to remote screen.
 
''Note: On your Vera dashboard when you click on the GO button of the remote it will execute only the scenes attached to the remote, it won't take you to the remote screen, for this you'll have to connect through the mobile page.''
 
For more information on upcoming features see [[Roadmap|the roadmap]].

Install Remotes

2009-10-07T17:24:43Z

Cj man:

click [[Intro_Universal_Remote|here]]

Install Remotes

2009-10-07T17:23:46Z

Cj man: New page: Intro_Universal_Remote

[[Intro_Universal_Remote|Intro_Universal_Remote]]

Intro Universal Remote

2009-10-07T14:48:36Z

Cj man:

Vera will allow you to use your iPhone or iPod touch as a handy universal remote control. You will see the buttons for your TV and Stereo on the iPhone/iPod display, and when you touch the button, Vera will send the command to your TV/Stereo, just like you were using the original factory remote or a normal universal remote. You will need an infrared transmit device which you will put in front of the TV/Stereo. This is what sends the actual command to the TV/Stereo.

'''Infrared device creation'''

1. Go to devices > Infrared

2. Click new IR device

3. Pick one infrared transmitter

4. Pick device type and manufacturer.

4.a. If there are any remotes whith the same manufacturer/device type, they will be displayed and you will be able to test the codes for every command. If they works, click "use this model", if not click "another model".

4.b. If there are no remotes with the same manufacturer/device type or you used "another model", a list of available codes will be displayed with a test button for each code. Click "test" buttons to see what codeset works and select either all codes or only those who works. Once selection is completed, type a model description and click "GO".

5. This will create the device and will prompt for install. Click "install".

6. Click "Save" on top left.

7. Repeat for each device you want to create.

 '''Remote creation'''

1. Go to scenes

2. Pick a scene who doesn't have a remote ("add remote" button is not pressed) and click "Add remote"

3. A list of available remotes will be displayed. Click "Create remote" on top right.

4. Type a remote description, pick a png files from those used for layout, platform iPhone, private, click Next

5. Define action zones on remote. Click and drag to resize/move them

6. For each zone defined, pick "Send a command" then from action the corresponding action (e.g. Volume/Mute, TogglePower/OnOff etc).

7. For zones who are supposed to execute a scene, pick "run a scene".

8. If the remote need to go to another page, pick "Go to another page", for "exit remote" pick corresponding action.

9. Save when you finished editing remote, then go back to Vera UI and click refresh botton at the bottom of remotes list.

10. Pick your new created remote.

11. Match remote buttons with the IR devices you previous created and those who execute scenes with a scene from dropdown.

12. Save from top left button.

 

At this point you should be able to control your IR devices with the remote. https://findvera.com/mobile pick smarphone app then pick the room where the scene with remote is, and click "go". You will be redirected to remote screen.

For more information on upcoming features see [[Roadmap|the roadmap]].

Intro Universal Remote

2009-10-07T14:21:02Z

Cj man:

Vera will allow you to use your iPhone or iPod touch as a handy universal remote control. You will see the buttons for your TV and Stereo on the iPhone/iPod display, and when you touch the button, Vera will send the command to your TV/Stereo, just like you were using the original factory remote or a normal universal remote. You will need an infrared transmit device which you will put in front of the TV/Stereo. This is what sends the actual command to the TV/Stereo.

'''Infrared device creation'''

1. Go to devices > Infrared

2. Click new IR device

3. Pick one infrared transmitter

4. Pick device type and manufacturer.

4.a. If there are any remotes whith the same manufacturer/device type, they will be displayed and you will be able to test the codes for every command. If they works, click "use this model", if not click "another model".

4.b. If there are no remotes with the same manufacturer/device type or you used "another model", a list of available codes will be displayed with a test button for each code. Click "test" buttons to see what codeset works and select either all codes or only those who works. Once selection is completed, type a model description and click "GO".

5. This will create the device and will prompt for install. Click "install".

6. Click "Save" on top left.

7. Repeat for each device you want to create.

 '''Remote creation'''

1. Go to scenes

2. Pick a scene who doesn't have a remote ("add remote" button is not pressed) and click "Add remote"

3. A list of available remotes will be displayed. Click "Create remote" on top right.

4. Type a remote description, pick a png files from those used for layout, platform iPhone, private, click Next

5. Define action zones on remote. Click and drag to resize/move them

6. For each zone defined, pick "Send a command" then from action the corresponding action (e.g. Volume/Mute, TogglePower/OnOff etc).

7. For zones who are supposed to execute a scene, pick "run a scene".

8. If the remote need to go to another page, pick "Go to another page", for "exit remote" pick corresponding action.

9. Save when you finished editing remote, then go back to Vera UI and click refresh botton at the bottom of remotes list.

10. Pick your new created remote.

11. Match remote buttons with the IR devices you previous created and those who execute scenes with a scene from dropdown.

12. Save from top left button.

At this point you should be able to control your IR devices with the remote. https://findvera.com/mobile pick smarphone app then pick the room where the scene with remote is, and click "go". You will be redirected to remote screen.

''Note: You won't see the remotes on your dashboard, you need to use the smartphone app in order to access them.''

For more information on upcoming features see [[Roadmap|the roadmap]].

Intro Universal Remote

2009-10-07T14:11:41Z

Cj man:

Vera will allow you to use your iPhone or iPod touch as a handy universal remote control. You will see the buttons for your TV and Stereo on the iPhone/iPod display, and when you touch the button, Vera will send the command to your TV/Stereo, just like you were using the original factory remote or a normal universal remote. You will need an infrared transmit device which you will put in front of the TV/Stereo. This is what sends the actual command to the TV/Stereo.

Infrared device creation
1. Go to devices > Infrared
2. Click new IR device
3. Pick one infrared transmitter
4. Pick device type and manufacturer.
4.a. If there are any remotes whith the same manufacturer/device type, they will be displayed and you will be able to test the codes for every command.
If they works, click "use this model", if not click "another model".
4.b. If there are no remotes with the same manufacturer/device type or you used "another model", a list of available codes will be displayed with a test button for each code.
Click "test" buttons to see what codeset works and select either all codes or only those who works.
Once selection is completed, type a model description and click "GO".
5. This will create the device and will prompt for install. Click "install".
6. Click "Save" on top left.
7. Repeat for each device you want to create.

Remote creation
1. Go to scenes
2. Pick a scene who doesn't have a remote ("add remote" button is not pressed) and click "Add remote"
3. A list of available remotes will be displayed. Click "Create remote" on top right.
4. Type a remote description, pick a png files from those used for layout, platform iPhone, private, click Next
5. Define action zones on remote. Click and drag to resize/move them
6. For each zone defined, pick "Send a command" then from action the corresponding action (e.g. Volume/Mute, TogglePower/OnOff etc).
7. For zones who are supposed to execute a scene, pick "run a scene".
8. If the remote need to go to another page, pick "Go to another page", for "exit remote" pick corresponding action.
9. Save when you finished editing remote, then go back to Vera UI and click refresh botton at the bottom of remotes list.
10. Pick your new created remote.
11. Match remote buttons with the IR devices you previous created and those who execute scenes with a scene from dropdown.
12. Save from top left button.

At this point you should be able to control your IR devices with the remote.
https://findvera.com/mobile pick smarphone app then pick the room where the scene with remote is, and click "go". You will be redirected to remote screen.

Note: You won't see the remotes on your dashboard, you need to use the smartphone app in order to access them.

For more information on upcoming features see [[Roadmap|the roadmap]].

ZWave Add Controller

2009-09-28T20:07:10Z

Cj man:

With most Z-Wave devices, you add them to Vera's Z-Wave network by clicking the 'Add other Z-Wave devices' on the 'Devices' tab in Vera's menu and following the instructions where you remove Vera's black Z-Wave dongle and carry it to your Z-Wave device. But, battery-operated handheld controllers are special cases. To add them you leave Vera's black dongle connected, bring them to Vera, and chose the 'Add Z-Wave Controller' option instead. In general, when adding these handheld controllers, there are a few more steps, as explained below. Most in-wall controllers that are connected to your house's electricity (i.e. ''not'' battery operated) can be added like any other Z-Wave device and do not need to be treated like the battery operated controllers. (See '''Supported controllers/gateways''' below for a list.)

There are two ways you can get your Z-Wave handheld controllers and scene controllers to control other Z-Wave devices: 

'''Method #1''' is the traditional Z-Wave method where you program a scene into the remote control. All Z-Wave remotes and scene controllers have their own built-in way of doing this. Vera can help with this process: After you add the controller into Vera you can have Vera transfer the scenes to the controller for you. 

 

'''Method #2''' allows you to create scenes within Vera, which can do anything and control any device, and you can assign an event so the scene is triggered when a button on the controller is pushed. This gives you unlimited possibilities with your scenes. You can even add user notification so that when a button on a handheld controller is pressed, you get an email or text message.

With either method, the first step is to add the controller into Vera.

== Adding battery operated handheld controllers to Vera ==

[[Image:AddZ-Wave.jpg|thumb|center|512px|Add Z-Wave Controller Screen]]

When you want to add a handheld Z-Wave controller, go to Vera's [[Quick Start|setup page]], choose the "Devices" tab, and click the "Add Z-Wave controller" link or button. You will have 60 seconds to add the controller to an existing Z-Wave network, by bringing the handheld controller within 3 feet (1 meter) of Vera and pressing the buttons on the handheld controller. This process is different for each handheld controller, and is often given different names. A chart of some popular Z-Wave handheld controllers is shown below, along with the steps to add the controller to Vera, and what the process is called. Vera shows the status and progress in blue at the top of the page, starting with: "''Running: Job is waiting: Ready...''", which means Vera is waiting for your handheld controller to start.

If you cannot add the controller to Vera, it's possible the controller is already part of another Z-Wave network. In this case, you must first reset the controller before you can add it to Vera. Instructions for resetting some popular controllers are shown below.

== Adding in-wall scene controllers to Vera ==

As mentioned above, in general you can add these devices like any other Z-Wave device and don't need to use the 'Add Z-Wave Controller' link.

== Method #1: Traditional scene assignments for controllers ==

Normally handheld controllers are battery operated, and, to save battery life, they do not allow Vera to talk to them to configure them except at the moment that Vera is adding them to the network. Many handheld controllers are programmable. For example, most have one or more button to activate "Scenes" or channels. Vera can help you configure your controller, such as assigning scenes to the buttons. To do this, you must first add the controller to Vera's Z-Wave network, so Vera knows about it, as explained above. Then you can use Vera's web interface to configure the controller and assign scenes.

For in-wall scene controllers which are not battery-operated, Vera can transfer the scene assignments at any time. But battery-operated handheld controllers, to save battery life, only let Vera transfer the scenes when they are being added. So, after the scene assignments are set up, you will need to go back to "Add Z-Wave controller" again, and repeat the process of adding the controller. It's okay to add the controller multiple times like this. The controller will not appear multiple times in Vera's device list. Vera knows that you already added the controller, and, so when you add it again, Vera will simply update the controller with new scene assignments and configuration. 

The only time you will have the same controller added more than once is if, after adding the controller to Vera, you press the buttons on the Z-Wave controller to 'reset' it. Resetting clears out everything in the controller, including the unique ID Vera gave it. So that means if you then re-add the controller again, Vera will think it's a new controller and add it again, and you'll have the same controller listed twice in Vera's device list. If this happens, it's easy to get rid of the old controller; click the '+' button next to it and then click 'Permanently remove dead node' to remove it from Vera's Z-Wave network.

Note that Method #1 uses traditional Z-Wave scenes, and most Z-Wave controllers cannot control anything but lights. If you want more flexible scenes, look at Method #2 below.

The step-by-step instructions for assigning scenes to your handheld controller are:

'''1'''. Create the scenes in Vera's web interface. See [[Scenes]] for instructions. '''2'''. If this is an in-wall scene controller, add it like any other Z-Wave device and skip to step 5. '''3'''. If it's a battery-operated remote controller which is not brand new, has already been paired with Z-Wave devices, or used with another Z-Wave controller, press the buttons on the controller to do a "Reset" to clear out all the controller's old data. (See the chart below for help.) '''4'''. Click the "Add Z-Wave Controller" button on Vera's "Devices" tab, to add the controller. (See the chart below for help.) '''5'''. After the device is added, it should show up on Vera's [[Unassigned devices]] page. If not, click the "Devices" tab again. You will need to pick a room for the controller. Although most handheld controllers are battery operated and can be used throughout the house, Vera requires you to assign each device to a room. This is just Vera's way of keeping the device list organized, and does not in any way limit what rooms you can use the controller in. It's just for your benefit to keep the device list manageable. So pick the room the controller will most often be stored in, and click 'Continue'. '''6'''. Find the controller on the "Devices" list, and click the '+' button next to the controller. Then click 'Custom Z-Wave Settings'. (See [[ZWave Configuration Options|Z-Wave configuration options]] for a full explanation of this page.) '''7'''. Click 'Add Scene assignment'. In the 'Key' field, type a number to indicate which key/button on the handheld controller you want to assign a scene to. (Some handheld controllers only have 1 scene button, so just put in '1'.) Then choose the scene you want assigned to that button. Repeat this for all the scenes you want to assign to buttons. '''8'''. When you are finished, click the red 'Save' button to save your changes. '''9'''. If this is a battery operated controller that you added with the "Add Z-Wave Controller" link, then after your changes are saved, you can click 'Continue' and then go back to the 'Devices' tab and choose "Add Z-Wave Controller" again. Do this just like you did the time before in step 4. Now when Vera re-adds the handheld controller, Vera will transfer the scenes to it.

--todoal: screen shot of 'Add Scene Assignment', showing a controller with the '+' button pressed.

[[Image:AddScene1.jpg|thumb|center|512px|Add Scene Assignment]]

== Method #2: Vera's special way of handling scene assignments ==

Add the controller to Vera's Z-Wave network the same way as Method #1. (See steps 1-5 above.) Next, click the '+' button next to the device and check the box ''''Treat scene buttons as events''''. This tells Vera to take over the scene buttons on the remote. Save your changes. If this is a battery-operated handheld controller that you added with 'Add Z-Wave Controller', you will need to add it again to Vera, because Vera can only program it to take over the scene buttons while it's being added. (Read the notes above with Method #1, step 9.)

Once your scene controller or handheld controller is configured to let Vera take over scene management, then you can create your scenes in Vera as you normally would. The scenes can do anything and control any device. To make a scene trigger when you press a button on the remote, click 'Add Event' next to the scene, choose the event 'Scene button is pressed', then choose the scene controller or handheld controller from the device pull down, and lastly indicate which button number should trigger the scene. (If there's only 1 button, just enter 1.) You can repeat this process if you want to have multiple buttons on multiple controllers trigger the same scene. When done, save your changes. With Method #2, there is no need to add battery-operated handheld controllers again. You can simply change the scenes and button assignments in Vera whenever you want.

If your scene controller has one or more 'scene off' buttons, you can generally make those trigger a scene by adding an event with button 0. Note that if your remote control has more than 1 'scene off' button, Vera cannot know which one you pressed and all 'scene off' buttons will trigger the event tied to 'button 0'.

For a better explanation of the difference between Method 1 and 2 see http://forum.micasaverde.com/index.php?topic=1960.msg7383#msg7383

== '''Supported controllers/gateways''' ==

'''These devices are added by bringing the controller near Vera and choosing 'Add Z-Wave Controller'.'''

The 'Add Sequence' is how you tell the controller to add to Vera. The 'Reset Sequence' is how you clear the controller if it's already been added to another Z-Wave network and can't be added to Vera.

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Specs
! Product Review
! Add Sequence
! Reset Sequence
! Notes
|-
| Cooper Wiring Devices
| Handheld Controller
| RFHDCSG
| 
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link]
| [http://store.homeseer.com/store/RFHDCSG---Z-Wave-Handheld-Controller-Cooper-Aspire-RF-P477C56.aspx Link]
| Menu, Settings, Replicate, Receive, From Unknown Controller
| Menu, Settings, Reset
| Works well with Vera. Can transfer devices from Vera to the handheld but doesn't transfer device names. Also very expensive.
|-
| Intermatic
| Handheld Controller
| HA07
| 
| [http://www.intermatic.com/images/instruction_sheets/158ha11645-art.pdf Link]
| 
| 
| 
| Read [[Intermatic Handheld Remotes]]
|-
| GE/Jasco Products
| Handheld Controller
| Z-Wave Home Theater Remote-45608
| 
| [http://www.jascoproducts.com/z-wave/Z-Wave-Products.asp Link]
| [http://www.myhomeserver.com/?page_id=236 Link]
| Z-Wave Setup Mode, Transfer, when displays Create Secondary scroll to RECEIVE. Press OK and remote shows RECEIVING, click ADD Z-WAVE CONTROLLER in Vera
| RESET: Z-Wave Setup mode, scroll to NETWORK, press OK and displays RESET. Click OK to reset the Z-wave on remote
| Works well with Vera, Also controls A/V devices and includes X10 IR codes and Logitech Squeezebox IR codes, blue blacklit buttons, LCD screen allows editing labels of scenes, devices, etc. In order to control Scenes with Vera, use METHOD#2, method 1 didnt work. Can also control Z-Wave and A/V devices using macros so you can "play DVD" and the lights will dim with this command. VERY NICE REMOTE!
|-
| Wayne Dalton
| Gateway
| WDHA-12R
|  ??
| [http://www.waynedaltonstore.com/product/74171410873.html Link]
| [http://www.zwaveworld.com/prodrevs/091406/reviews-pg4.php Link]
| 
| 
| Shows as Z-Wave controller, a pain to sync with Homelink car remote, able to associate with devices. Can now turn on/off All Z-wave devices from car. '''This gateway is required for the 3-button remote sold by them.''' Translates commands to Z-Wave Scenes. As firmware 1.0.602 it's working with Vera, it's seen as a secondary controller.Vera needs to be configured so that it interprets the WDHA-12 as sending "Button Presses" instead of "Scene Activation" events.
|-
| Wayne Dalton
| Handheld Controller
| WDHC-20
|  
|  
|  
| Add Zwave Controller in Vera, on remote; HOME, hold SETUP until HOME blinks twice, enter 967, HOME blinks twice if successful. Enable 'Treat scene buttons as events see: method #2' and click Configure node right now on Vera, and repeat on remote.
|  
| I added this about a week ago, and typed this from memory, so it may not work 100%, but I know it does have to be programmed on the remote twice to enable 'method #2'. Only On works, couldn't find setting for Off, don't have a dimmer to test Bright/Dim.
|-
| Innovus
| Handheld Controller
| SmoothRemote
|
| [http://www.innovus.eu/fileadmin/user_upload/manual/z-wave/smoothremote-00120001-tech.pdf Link]
|
|
1. Add Z-Wave Controller on Vera 2. Press 3 times shift (Button 9) 3. Configure device on Vera (Associations) 4. To transfer your config settings, repeat step 1 & 2 

|
| Device can be configured using Vera. Has no scene buttons, so you can not trigger scenes with it (V1.0.616) which hopefully will be changed in further versions. Button 8 is always "ALL ON / ALL OFF"
|}

 

 '''These devices are added like normal Z-Wave devices by choosing 'Add other Z-Wave devices' on Vera's menu and bringing Vera's Z-Wave dongle to the device'''

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Specs
! Product Review
! Add Sequence
! Reset Sequence
! Notes
|-
| Cooper
| 5 Scene Controller
| RFWDC
| 
| 
| 
| 
| 
| Read [[Cooper Scene Controller]]
|-
| Leviton
| 4 Scene Controller
| RZCS4
| 
| 
| 
| 
| 
| Read [[Leviton Scene Controller]]
|-
| Leviton
| 1 Scene Controller
| RZCZ1-1LX
| Unknown
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link]
| [http://shop.micasaverde.com/index.php?main_page=product_info&cPath=106&products_id=116 Link]
| [http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=4K.TQNnHt8AaVpmZu8gZrg&label=IBE&appName=IBE&LC12RP=qKakohvv7vJh2mB6bpElERJ8:S&LC12RP_pses=ZG4A2E9F82D5405FB0AA12ACDF90AC2545B909744B9ED50C8FDF1E42E5DDB0DBDAA696B9BE833B1E5A5FAF3CD3DD6FEF48EE84A0FF16567733 Link]
| 
| Read [[Leviton Scene Controller]]
|}

== '''Unsupported / Partially supported controllers/gateways''' ==

Not working as of firmware version wl500gP-1.0.584.trx

{| cellpadding="2" border="1"
|-
! Manufacturer
! Model
! Notes
|-
| Sylvania
| SH50201
| '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)'''
To program this controller put vera in add controller mode and then hit "menu", then press right arrow until you see setup. Press ok. Righ arrow to copy remote control. Press ok. Right arrow to receive information and click ok. Wait for vera to confirm the controller was added.

|-
| ACT HomePro
| ZTH100
| Sylvania is a rebranded ACT Homepro '''"all on" and "all off" buttons work but scene buttons are not supported at this time. (3/28/2009)'''
|-
| Merten
| 1-gang radio push button 5051.., 5061.., 5071..
| Use method #2; only button 0 works; press button 0 and then button 1, otherwise, Vera does not catch button 0 (8/17/2009, firmware 1.0.862)'''
|-
| Merten
| 2-gang radio push button 5052.., 5062.., 5072..
| Use method #2; only button 0 works; press button 0 and then button 1, otherwise, Vera does not catch button 0 (8/17/2009, firmware 1.0.862)'''
|}

== '''Troubleshooting''' ==

In case your controller it's not working please follow this steps before submitting a trouble report.

1. Open Vera's Dashboard 
2. Go to Advanced and enable Verbose Logging 
3. Go to Location choose your timezone and synchronize your watch 
4. Go to Devices->Zwave->More Zwave Options tab and where it says 
"House/Node", make note of the node ID of your dongle (node x.y where x is the node id). 
5. Go to Devices->Zwave tab, if you have any devices called "ZWave Controller/Scene Controller" besides the built-in one, be sure to rename them so you can tell which is which.
Also be sure 'scenes as events' is not checked for this controller. 
6. Go to Devices->Zwave, expand your controller properties by clicking on the "+" sign near it and then press 'Custom Zwave Settings'. 
Under Associations add group 2 and when you click 'set', add 2 associations: both the device you want to control *and* the 
"ZWave Controller" (ie Vera's dongle), which is probably in the 'unassigned' area. 
Press SAVE and wait until the 'Please wait.... configuring' is done. 
7. Press every button on your controller and note the exact time at which you've press it. 
8. Go to Advanced->Tech Support and submit a trouble report in which you have to indicate 
- the controller make and model and a link to its user manual 
- the controller's NodeID 
- the time when you hit 'configure right now' and when you hit each button

Leviton Scene Controller

2009-09-28T18:45:52Z

Cj man:

These instructions work for the Leviton RZCS4. They also work for the RZCZ4 which is a zone controller, not a scene controller. However the zone controller is more limited in its functionality and you must use 'Method #2' described below.

== Adding the RZCS4 to your Z-Wave network ==

1. Be sure the scene controller is not already paired with another network. The best way to do this is to hold down the scene 1 and scene 3 buttons simultaneously for 10 seconds. Hold down the left side of the buttons, near the LED lights. When you first press them, one of the buttons may blink red momentarily. After you've held them down for about 4 seconds, all 4 lights will turn amber, and if you keep them held down, after another 4 seconds all 4 lights will turn red. This means the scene controller is reset, and can now be included with Vera.

2. Take Vera's dongle to the scene controller and be sure Vera's dongle is off. If the light on the dongle is blinking, tap the button on the dongle so it is off. The dongle must be off when you put the scene controller into program mode. Now, press and hold scene buttons 1 and 3 on the left side, near the LED lights, for 4 seconds. All 4 lights will turn amber. Let go. The 4 lights will blink amber every 1 second or so to indicate the scene controller is in program mode.

3. Only after you completed step 2 and the scene controller is in program mode, tap the button on Vera's dongle to put the dongle in include mode. After about 5 seconds, the dongle's light should stay solid for a second and the scene controller's 4 amber lights will interrupt their normal blinking pattern. This means the scene controller was successfully included. You can put Vera's dongle back in Vera, or take it to include another device you wish to include. If including another Leviton scene controller, be sure to tap the button on the dongle to turn it off again before repeating step 1.

4. When you re-insert the dongle in Vera, after a few seconds you should see the scene controller show up as an unassigned device on the devices tab in Vera's setup site. If you don't reload Vera's web page and go back to the devices tab. Pick the room the scene controller is in, and give the scene controller a name if you want.

If you do not want Vera to assign scenes to the scene controller, but will do that using another device, you can stop here. If you want Vera to assign scenes, keep going with step 5.

''Now you have to make a decision if you want to use Method #1 or Method #2 as described in [[ZWave Add Controller|Z-Wave Add Controller]].'' The bottom line is that with Method #1, which is the traditional way of creating scenes, the Leviton's up/down buttons work, and you can turn a scene on as well as off. However, this only works with some light switches and lamp modules which support 'scenes', and you can only set lighting levels. You can't control a thermostat, lock a door, turn on a TV, etc. with Method #1. To see if a device is scene capable and can work with a Leviton scene controller in Method #1, click the '+' button next to the device, look at the "Capabilities" line and look for the number 44 after the | sign. If it's there, the device is scene capable. Method #2 is more flexible. With Method #2 the Leviton scene controller's buttons are tied to scenes in Vera, which can do anything with any device because Vera is actually running the scene. However with Method #2 the up/down buttons on the scene controller don't work, nor does the 'Toggle a scene on/off' feature. With Method #2 if you have 3 lighting mood scenes and an 'off' scene, you'll assign the 'off' scene to one of the 4 buttons, but you won't be able to use the remote's toggle feature to turn any of the 3 scenes off.

=== Method #1 ===

5. Create a scene that adjusts the light to the level you want. Save your changes.

6. Click the '+' button next to the scene controller and choose 'Custom Z-Wave settings', and 'Add scene assignment'. Choose the key to assign the scene to (1-4) and the scene to assign to the key. Save your changes.

7. The scene should work fine. If you want to change the scene, go to the 'Scenes' tab and modify the scene as you want, save your changes, and then go to 'Devices', click '+' next to the scene controller, and choose 'Configure right now'. That will reconfigure the scene controller.

=== Method #2 ===

5. After you assigned the scene controller to a room, click the + button next to the scene controller on the 'Devices' tab on Vera's 'Setup' site. Check the box "Treat scene buttons as events". After you save your changes, Vera will start to reconfigure the scene controller and if successful, you will see a [[Device Control Status|green cog]] next to the scene controller indicating it was successfully configured. There must be a green cog next to the scene controller for it to work.

6. On the 'Scenes' tab on Vera's 'Setup' site, create the scenes you want assigned to the scene controller. Click the red 'Save' button to save your scenes. If you haven't yet added all the lights and other Z-Wave devices you want in the scene you'll have to do that first, of course, and come back to this step later. Click the 'Add Event' button for your scene. Choose the event 'Scene button is pressed'. Then choose the scene controller from the pull-down. Then enter the scene button you want to trigger the scene; enter a number between 1 and 4 to designate one of the controller's four scene buttons.

After you save your changes, pressing the left side of the scene button, next to the LED, will trigger the scene. Note that the scene can include delays. For example, if you have a 'go to bed' scene, you may want the scene to lock the doors, turn down the thermostat, and turn off all the lights. But, you might not want the bedroom lights to go off immediately if the scene controller is on the opposite side of the room from the bed. So, in the scene, for the bedroom lights, choose the command "On" then choose "After 30 seconds", then "Set a new setting", then "Off". This way, when you choose the scene, the bedroom lights will come on for 30 seconds so you have time to walk across the room, and then turn off.

The 4 scene buttons on the scene controller can be pushed to the left or to the right. The left is the normal way to trigger a scene. If you press any of the scene buttons to the right, it is treated as 'button 0'. You can create a scene as described above, and in step 6 choose button #0. But this means that no matter which of the 4 scene buttons you press to the right, they all trigger the scene for button #0. (See [[ZWave Add Controller|Z-Wave Add Controller]] Method #2 for an explanation.) Also, the scene controller only triggers button #0 when you press the button to the right if you already pressed the button to the left. If this is confusing, just stick to the normal usage of buttons 1-4 by clicking the button to the left. The scene up and down functions do not do anything.

=== Note ===

As explained in [[ZWave Add Controller|Z-Wave Add Controller]] you can leave "Treat scene buttons as events" unchecked, and then create scenes the traditional Z-Wave way (i.e. '''Method #1'''). In this case the scene up and down buttons do work as expected and so does the off. However, the scenes are much more limited. You cannot have delays, or adjust thermostats, or lock doors and so on. Also, '''when you want to program the scene into the scene controller, you can only do this by re-adding the scene controller to Vera while the dongle is inserted. You cannot carry the dongle to the scene controller; you must put the scene controller in program mode, as explained in Step 2 above, and then choose 'Add Z-Wave Controller' from the Devices tab on Vera's 'Setup' menu'''. Therefore it is a bit cumbersome to do this unless you have a separate handheld controller to help program the scenes. If you do want Vera to do it for you this way, create your scenes, add the scene controller, leave "Treat scene buttons as events" unchecked, choose 'Custom Z-Wave Settings', and choose the 'Add scene assignments' to assign the scenes to buttons. Then put the scene controller in program mode, and choose 'Add Z-Wave controller' from Vera's setup page.

== Removing the RZCS4 from your Z-Wave network ==

If you already paired the RZCS4 and want to remove it:

1. Take Vera's dongle to the scene controller and be sure Vera's dongle is off. If the light on the dongle is blinking, tap the button on the dongle so it is off. The dongle must be off when you put the scene controller into program mode. Now, press and hold scene buttons 1 and 3 on the left side, near the LED lights, for 4 seconds. All four lights will turn amber. Let go. The lights will blink amber once every second or so to indicate the scene controller is in program mode.

2. Only after you completed Step 1 and the scene controller is in program mode, press and hold the button on Vera's dongle continuously for 5 seconds until the dongle's blue light blinks quickly, then let go. After about 5 seconds, the dongle's light should stay solid for a second and the scene controller's four amber lights will interrupt their normal blinking pattern. This means the scene controller has been removed. You can put Vera's dongle back in Vera, or take it to include another device.

Quick Start Hardware

2009-08-24T09:12:48Z

Cj man:

1. Insert the black Z-Wave dongle into either of the matching ports on the back of Vera.

2. Screw the antenna to the gold 'antenna' port on the back of Vera and leave the antenna pointed up.

3. Use a standard network cable (included) to connect the network port on the back of Vera marked '''''WAN''''' into either your DSL or cable modem, or into your existing home network. Vera will use this port to connect to the internet.

4. Connect the power cord and plug Vera in. '''Wait 2 minutes after plugging Vera in before continuing.'''

[[Image:VeraBackQSG.png|thumb|512px|center|caption text| The Back of Vera]]

5. After you have waited 2 minutes, look at the power light on the front of Vera. If it is on solid that means Vera was able to connect to the Internet. Proceed to step 6. Otherwise, read the network troubleshooting section before proceeding.

[[Image:VeraFrontQSG.png|thumb|512px|center|caption text| The Front of Vera with the Power Light On]]

'''Note: To setup Vera you will need an internet web browser. The web browser can be anywhere on the same home network as Vera. Or connect your computer to one of Vera's 4 ports marked LAN. Or, connect to the wireless home network Vera setup for you automatically using the network name and password on the front of this guide.
'''

6. Open your web browser and go to: http://findvera.com. Click the green "Setup Vera" button as shown below (left). If you don't see that button, read the network troubleshooting section.

--todoal: Update the screen shot in the adobe illustrator quick start guide, and put both pics here so it matches

7. You should now see Vera's setup page in your web browser (above right). Vera has helpful videos to guide you and links to online documentation with detailed instructions. You should be up and running in just a few minutes. If you do not see Vera's setup page, read the [[Networking_Setup | network troubleshooting]] section. If you don't have an internet connection you can still use Vera, but you will not see the videos or online documents.

'''Note: Vera will share your internet connection automatically. Connect other network devices to Vera's LAN1-LAN4 ports or to Vera's wireless network. Vera will automatically detect compatible devices, like security cameras, and let you control or view them from outside the home using Vera's secure network. If you purchased wireless devices from Mi Casa Verde, like wireless security cameras, they were shipped to you pre-configured to work with Vera's wireless network. Just plug them in; there is nothing to configure.
'''

Vera Luup Releases

2009-08-21T10:59:27Z

Cj man:

'''NOTE: If upgrade from a pre-Luup version and do not choose 'restore to factory default' your Vera will not work, so read the instructions below first.'''

When Luup is officially released everyone's system will automatically notify them and allow them to upgrade to the latest version. In the meantime, you can upgrade to the latest version by going to Advanced, Download and putting one of the URL's in the 'Firmware url' field. The first time you go from the current release of Vera (ie 1.0.604 or lower) to one of the Luup releases (1.0.700 and greater) you *must* choose 'restore to factory' default when it asks you if you want to keep your settings. This is because we have not yet written the conversion utility to convert the configuration from a pre-Luup firmware to Luup. If you upgrade with 'preserve my settings', you will need to upgrade again with 'restore to factory default'. Once you have setup your configuration with a Luup release, then you can choose 'preserve my settings' to upgrade to another Luup release and keep your settings.

Much of the functionality which exists in the current Vera was written as closed-source plugins in C/C++. These plugins are being converted to Luup plugins so users can change the code to customize the functionality. So many of the features in the .602 version of Vera are missing from the Luup version because they have not yet been re-written as Luup plugins.

== 2009-August-14 1.0.862 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.862.trx

== 2009-August-7 1.0.843 ==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.843.trx

We are intending to release this as an official beta for the general public on Monday if no issues are reported over the weekend. This is the first version that has passed all our test plans.

==2009-July-17 1.0.790==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

This fixes an issue in 789 with getting a persistent 'VERY IMPORTANT - Clear your cache' error in the browser. If that browser error makes upgrading difficult, you can manually upgrade by logging into Vera and typing:

wget -O /tmp/firmware.img http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.790.trx

/usr/bin/cmh-upgrade.sh

==2009-July-16 1.0.789==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.789.trx

This fixes many issues, including fixes to the web-based WAP and Iphone browser and the addition of the automatic installation of plugins from the Luup gallery.

==2009-July-10 1.0.770==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.770.trx

This fixes a couple bugs with the adding of custom serial ports. The job icons are not appearing, though.

Note: If you added serial ports with 765 and they don't show up on the 'Serial Port Configuration' page, remove the usb->serial adapter, upgrade to 770. After it comes back up, reconnect the usb->serial adapter, and reboot Vera (Advanced, Tech Support, 'reboot router').

There are some issues with the Linux usb-serial driver that cause conflicts with other usb-serial devices, like the Z-Wave dongle, when you insert the usb-serial adapter while the system is already running (ie hotplugging). Until these issues are resolved in the Linux kernel, it's best that you reboot Vera after you connect a usb-serial adapter, or, of course, connect it before you power on Vera.

==2009-July-9 1.0.765==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.765.trx

This includes the ability to add your own USB->serial devices to the 'recognized list' and fixes some bugs in the serial port handling.

==2009-July-6 1.0.756==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.756.trx

With this version we have included a sample RS232 device for control of the Somfy motorized blinds. This version has also fixed all the obvious bugs so we can complete our standard test sequence without incident. And all the existing plug-in functionality is now implemented in Luup, including timers and events, with the exception of real-time energy consumption reporting.

==2009-June-27 1.0.745==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.745.trx

Lots of bug fixes.

==2009-June-23 1.0.733==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.733.trx

The basic WAP cell phone interface is back in, now as a Luup plugin, and the red/black button control needed to do inclusion of the Schlage locks is back too.

==2009-June-20 1.0.716==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.716.trx

This fixes a few crashes with configuring devices.

==2009-June-15 1.0.711==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.711.trx

This fixes an issue with the software not restarting after removing/reinserting the dongle. It also fixes the 'do something after x seconds' in scenes.

==2009-June-12 1.0.710==

Download URL: http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.710.trx

This is the initial beta release of the Luup engine. The following functionality which exists in the current release of Vera is not yet working in this release: In scenes the 'after x seconds/minutes' do something else, many of the events are not implemented, event notifications, energy monitoring and setting pin codes on door locks. The rest of the Z-Wave commands should work. A Luup plugin for the Global Cache GC100 is included and the serial ports work for controlling RS232 devices and also the i/r transmitters. You can start creating support for i/r devices although it will be tedious at the moment to do this by hand putting pronto codes in the XML files until the web-based generator tool is available.

This release is for Luup developers only and is not suitable for mainstream users yet because of the missing functionality.

Networking Setup

2009-08-14T16:12:01Z

Cj man:

In general most people who have Vera don't need to know anything about networking and don't need to change any network settings. If you are experiencing difficulties or want to know how Vera's networking works, here is some information.

== Getting Vera an internet connection ==

Within 2 minutes after you plug Vera in, Vera will try to obtain an IP address (i.e. Internet Connection) automatically through the WAN port on the back of Vera.  If Vera succeeds in getting an IP address and connects to the network, the power light on the front of Vera comes on solid.  If Vera cannot get an internet connection, the power light will blink.  Note that you can still use Vera without an internet connection, but certain features, like remote access over cell phones and video archiving, will not work without an internet connection.

If you connected Vera directly to your DSL or cable modem, but Vera's power light is blinking, first try unplugging the DSL or cable modem for 2 minutes, then plug it in and wait a few minutes.   If Vera's power light is still blinking that probably means you have a special network setup, such as PPPoE or a static IP address.  These types of connections require special information from your internet service provider.   To specify these settings, follow the "Getting to Vera's Setup Page Without an Internet Connection" and then "Manually Configure Vera's Network" instructions below.  Then fill in the Setup Page's top section "How Can I Connect to the Internet" with the settings furnished by your internet service provider.   Also, under Firewall choose "Firewall Active", and under DHCP choose "DHCP Server ON".  Then click 'Save & Apply'.   (See the IMPORTANT NOTE below.)

== Getting to Vera's Setup Page if Vera already has an internet connection ==

Once Vera has an internet connection (the power light is on solid), you can open any web browser from anywhere on the home network and go to [http://findvera.com http://findvera.com] and click the green 'Setup' button.  The computer with your web browser can be connected directly to one of Vera's LAN ports, or it can connect to Vera wirelessly, or be anywhere else on the home network that Vera is connected to through the WAN port.

== Getting to Vera's Setup Page without an internet connection ==

If Vera does not have an internet connection, then you must connect the computer with your web browser to one of Vera's four LAN ports, or connect to Vera wirelessly using the network name (SSID) and password shown on the bottom of Vera and on on the front of the Quick Start Guide.  Then open your web browser and go to:  '''http://local.findvera.com''' If that fails, try:   '''http://192.168.81.1''' Vera's setup page should appear.

== Manually configuring your network ==

Normally Vera will automatically configure the network for you.   If you want to configure the network manually, click the Advanced button in Vera's setup page and choose the 'Net & Wi-Fi' option.  Set the network the way you want and click 'Save & Apply' at the bottom of the page.  Note that once you click 'Save & Apply,' Vera's automatic network configuration will be bypassed and Vera will use the network settings you provide.   (See the IMPORTANT NOTE below if you want to do this.)

== Common problem: Vera isn't sharing the network connection ==

When Vera gets an internet connection through the WAN port, Vera decides automatically if you already have a home network setup with another device (a router) that is sharing your internet connection.  If Vera decides that you connected Vera directly to your DSL or cable modem, and don't already have a home network setup, then Vera will automatically create a home network for you and share the internet connection that Vera got from your DSL or cable modem.  Some DSL or cable modems "trick" Vera into thinking you already have a home network, when in fact you do not.  This happens when all of the following are true: 1) You connected Vera's WAN to your DSL or cable modem and do not already have a router. 2) Vera got an internet connection from your DSL or cable modem and you can tell this because Vera's power light is on solid. 3) Other computers in the home that you connect to Vera's 4 LAN ports, or connect to Vera wirelessly, are not able to get an internet connection.

If those 3 things are all true, then that probably means Vera is not sharing your internet connection because Vera thinks you already have a home network.   This happens when your DSL or modem "tricks" Vera by acting like a router.   This problem is easy to solve.  First, unplug the cable going into Vera's WAN port.  Wait a few seconds for Vera's power light to start blinking.  Now try again to connect your computer to Vera using the 4 LAN ports or with the wireless connection.   Open your web browser and go to: http://local.findvera.com, or to http://192.168.81.1. Click the 'Advanced' button, choose 'Net & Wi-Fi'.

Set the following settings:

How can I connect to the Internet? '''DHCP'''

Firewall: '''Firewall active'''

DHCP server: '''On'''

Then click 'Save & Apply'.  Reconnect the cable to the WAN port.  Wait 30 seconds.  Then Vera should share the internet connection with any other PC's and devices connected to Vera's 4 LAN ports, or that connect to Vera wirelessly.  (See the IMPORTANT NOTE below.)

== I already have a home router (i.e. DHCP server) and don't want Vera to replace my router ==

Normally this should be handled automatically.   You simply connect Vera's WAN port to your existing home network and Vera should automatically detect that you already have a router, and then Vera will automatically turn off Vera's built-in router functions, like firewall and DHCP server, thus becoming a normal network device.  You can still find Vera on your home network using the [http://findvera.com findvera.com] web site, and you can connect any network devices to Vera's 4 LAN ports or to Vera's Wi-Fi network, and they will work just fine on your home network, getting an IP address from your existing home router. When you go to the 'Net & Wi-Fi' tab on Vera, you will see the DHCP server is set to "OFF", and the firewall is set to "No Firewall".  (See the IMPORTANT NOTE below.)

== IMPORTANT NOTE: Vera's automatic network configuration may be disabled ==

To make Vera as easy as possible for the novice user, Vera will attempt to configure the network automatically for you.  This means if you have an existing home router, Vera will work well with it.  And if you do not, Vera will assume the role of your primary home router automatically.  But, once you go to Vera's 'Net & Wi-Fi' tab and make any changes, then Vera assumes you know what you're doing, and Vera will not again attempt to automatically configure the network unless you [[Factory Reset|reset Vera to the factory default]].  This means, for example, that if you manually turn off Vera's firewall, and you then put Vera directly on the internet, other people may be able to access your Vera.  For most users, we recommend you just leave the network settings alone and let Vera handle everything automatically.

== Technical Explanation: How Vera's auto networking works ==

This paragraph is for advanced users who understand networking concepts.  Vera tries to obtain an IP address on the WAN port using DHCP.  If Vera gets an internal IP address from another router, namely an address that starts with 192.168., or 172., or 10., then Vera assumes you already have a network router sharing your network connection and a DHCP server giving out IP addresses.   So Vera goes into 'switch' mode.  This means the WAN port and the 4 LAN ports are bridged, like a normal switch, and Vera's firewall and DHCP server are disabled.   If Vera gets a routable IP address (not a 192.168., 172., or 10. address), Vera assumes she is connected directly to your Cable/DSL modem and that Vera should share the network connection for you.  In this case, Vera turns on her DHCP server and gives out IP addresses in the 192.168.81.xx range on the four LAN ports.  Vera's firewall is enabled and Vera only accepts connections from the 4 lan ports.

== Advanced Network Settings ==
[[Networking_Setup:Advanced_Network_Setup]]

== Troubleshoot Network Settings ==
[[Networking_Setup:Troubleshooting]]

Full Power Inclusion

2009-08-14T15:13:30Z

Cj man:

In order for Vera to use Z-Wave devices, those devices must be "paired" or "included" into Vera's Z-Wave network. Generally this is done by removing Vera's black Z-Wave dongle and bringing it within 3 feet (1 meter) of the Z-Wave device you want included and then turn on/off or otherwise activating the Z-Wave device. This is called "low power inclusion" because the wireless signals used to talk with the Z-Wave device are intentionally sent at a very low power so that only devices that are very close to the dongle will get included. This way if you live in an apartment, and your neighbors also have Z-Wave devices, you do not need to worry that one of their Z-Wave devices might get activated and thereby included in your Z-Wave network by mistake. The other advantage to the standard low power inclusion is that you get immediate feedback on Vera's black Z-Wave dongle that the new Z-Wave device was successfully paired because the blinking light on the dongle momentarily stops blinking. This is particularly useful if you're having trouble pairing a node because you can [[Reset Node|reset the node]] and get instant feedback that it's working.

If there are no neighbors within a 20 foot (about 6 meter) range of Vera, you might also try "full power" inclusion. This means you leave Vera's Z-Wave dongle connected and Vera will use the normal, full power setting of the Z-Wave network to try to include nodes. To do this, go to 'Devices', choose 'Z-Wave Options', as shown [[ZWave Options|here]]. Using the pull-down menu to the left of the ''''Go'''' button, change 'low power' to 'full power'. If you want to reset/exclude nodes, instead of including them, change the first pull-down menu to 'Exclude'. If you leave the 2nd pull-down at 'one', then as soon as Vera has included/excluded one node, Vera will stop trying. If you change it to say 'Multiple', then for however many seconds you specify in the 'Timeout' box (default 30 seconds) you can include/exclude as many nodes as you want. You can also change the 'Type' pull down if you want to limit the type of nodes being included/excluded. When you're all done, click ''''''''''Go''''.

Full power inclusion doesn't always work. Only newer Z-Wave devices support it, and, they don't always support the full 'mesh network' functions needed to reliably include. So you can use full power inclusion to pick up as many nodes as you can, and then remove Vera's Z-Wave dongle and carry it around to pick up the nodes that you couldn't get with full power inclusion.

[[Image:Full_Power_Include.jpg|400px|thumb|left|Full Power Inclusion]]
[[Image:Full_Power_Exclude.jpg|400px|thumb|right| Full Power Exclusion]]

File:Full Power Exclude.jpg

2009-08-14T15:09:59Z

Cj man:

File:Full Power Include.JPG

2009-08-14T15:07:15Z

Cj man:

File:Full Power Include.jpg

2009-08-14T15:05:39Z

Cj man: Full Power Include

Full Power Include

Full Power Inclusion

2009-08-14T15:05:00Z

Cj man:

In order for Vera to use Z-Wave devices, those devices must be "paired" or "included" into Vera's Z-Wave network. Generally this is done by removing Vera's black Z-Wave dongle and bringing it within 3 feet (1 meter) of the Z-Wave device you want included and then turn on/off or otherwise activating the Z-Wave device. This is called "low power inclusion" because the wireless signals used to talk with the Z-Wave device are intentionally sent at a very low power so that only devices that are very close to the dongle will get included. This way if you live in an apartment, and your neighbors also have Z-Wave devices, you do not need to worry that one of their Z-Wave devices might get activated and thereby included in your Z-Wave network by mistake. The other advantage to the standard low power inclusion is that you get immediate feedback on Vera's black Z-Wave dongle that the new Z-Wave device was successfully paired because the blinking light on the dongle momentarily stops blinking. This is particularly useful if you're having trouble pairing a node because you can [[Reset Node|reset the node]] and get instant feedback that it's working.

If there are no neighbors within a 20 foot (about 6 meter) range of Vera, you might also try "full power" inclusion. This means you leave Vera's Z-Wave dongle connected and Vera will use the normal, full power setting of the Z-Wave network to try to include nodes. To do this, go to 'Devices', choose 'Z-Wave Options', as shown [[ZWave Options|here]]. Using the pull-down menu to the left of the ''''Go'''' button, change 'low power' to 'full power'. If you want to reset/exclude nodes, instead of including them, change the first pull-down menu to 'Exclude'. If you leave the 2nd pull-down at 'one', then as soon as Vera has included/excluded one node, Vera will stop trying. If you change it to say 'Multiple', then for however many seconds you specify in the 'Timeout' box (default 30 seconds) you can include/exclude as many nodes as you want. You can also change the 'Type' pull down if you want to limit the type of nodes being included/excluded. When you're all done, click ''''''''''Go''''.

Full power inclusion doesn't always work. Only newer Z-Wave devices support it, and, they don't always support the full 'mesh network' functions needed to reliably include. So you can use full power inclusion to pick up as many nodes as you can, and then remove Vera's Z-Wave dongle and carry it around to pick up the nodes that you couldn't get with full power inclusion.

[[Image:Full_Power_Include.jpg | Full Power Inclusion]]
[[Image:Full_Power_Exclude.jpg | Full Power Exclusion]]