MiOS - User contributions [en]

Wayne Dalton WDTC-20

2017-11-15T13:21:59Z

George:

[[Category:3rd Party]]
Wayne Dalton WDTC-20 EnergySavingsHeating mode

I would like to see the Heat button change to Save when I click on it when it's blue. Also, there should be a way to set the EnergySavingsHeating set point, that I cannot seem to figure out a workaround for?? I did however find that using SwitchPower, I could set the thermostat to EnergySavingsHeating mode, the set point has to be set on the thermostat itself.

EnergySavingsHeating:

urn:upnp-org:serviceId:HVAC_UserOperatingMode1
ModeStatus=EnergySavingsHeating
ModeTarget=EnergySavingsHeating

urn:upnp-org:serviceId:SwitchPower1
Target:0

HeatOn:

urn:upnp-org:serviceId:HVAC_UserOperatingMode1
ModeStatus=HeatOn
ModeTarget=HeatOn

urn:upnp-org:serviceId:SwitchPower1
Target:1

As a workaround, currently I have built a scene with a luup script that puts all of my WDTC-20 thermostats in EnergySavingsHeating mode: (Replace the 24 with your device)

local lul_arguments = {}
lul_arguments["newTargetValue"]=0
lul_resultcode,lul_resultstring,lul_job,lul_returnarguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",lul_arguments,24)

luup.variable_set("urn:upnp-org:serviceId:HVAC_UserOperatingMode1","ModeStatus","EnergySavingsHeating",24)

luup.variable_set("urn:upnp-org:serviceId:HVAC_UserOperatingMode1","ModeTarget","EnergySavingsHeating",24)

Firmware Flash Vera2

2017-11-06T14:30:59Z

George: /* Begin the process for flashing the firmware */

== Prerequisites ==

*YOU NEED TO FOLLOW THIS TUTORIAL ONLY IF YOUR VERA2 UNIT IS NOT BOOTING ANYMORE, THIS MEANS THAT WHILE BEING CONNECTED TO THE INTERNET/YOUR NETWORK ON THE '''ETH1 PORT''', THE POWER LED IS ORANGE AND OTHER LEDS ARE GREEN WITH THE EXCEPTION OF ETH1 and ZWAVE WHICH ARE OFF FOR MORE THAN 30 MINUTES !

*The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications should be run in Windows XP SP3 compatibility mode.

*Make sure your computer is connected to your network through an Ethernet cable. Make sure to disable any wireless networking interfaces before continuing.

NOTE: Failure to disable your wireless network before continuing could result in an unusable unit.

*Please deactivate all Firewall and Antivirus software which is running during the upgrade process.

Note: If you are running Windows Vista/7 please follow the next guide to enable the TFTP Client and then continue with the re-flash steps. Guide: http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

=== If the restoration utility does not work on Windows 7 ===

Please note that this is only available for Windows 7 Professional, Enterprise and Ultimate editions. 

*If the restoration utility does not work on Windows 7 you should use the Windows Xp Mode, offered for free by Microsoft. To install it, you have to go to this page [http://www.microsoft.com/en-us/download/details.aspx?id=8002 Windows Xp Mode] which will walk you through the entire process. 
*After this finishes and you open up the Windows Xp Mode Virtual Machine, you should go to the Menu, select Tools -> Settings, select Networking and for adapter 1 make sure to select your LAN card, the one that will be connected directly into the ETH2 port of Vera.
*Afterwards you will have to open Internet explorer inside the virtual machine, access [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2 this page] and download the Firmware flash utilities inside the virtual machine.
*On Windows 7 change the Local Area Connection settings to use the static IP and connect the Vera unit to your computer as explained at the begining of this page, then open the Firmware Flash utility inside the Virtual machine and you should be able to continue the Firmware Flash process.

== Files to download before you start the restoration process ==

*[http://download.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool]
*[http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware]

== Setup your computer to connect to Vera 2 ==

*Computer IP: 192.168.81.xxx (not 1)
*Subnet Mask: 255.255.255.0
*Default Gateway: 192.168.81.1

== Begin the process for flashing the firmware ==

#Use a network cable (CAT5e) and plug the cable from your PC into Vera's ETH2 port.
#Unplug Vera from the power cord.
#Holding down Vera's service button (not the small one, the one resembling the Z-Wave button with no label in the middle of the unit), whilst plugging in the power cord back in. Wait about 5s after you plugged the power cord back with the reset button pressed. When releasing the reset button, power LED should be blinking.
#If the power LED is not blinking, turn Vera off and try again'''(PLEASE doublecheck FIRST!!! The LED blinking can be very faint!).'''
#Start [http://download.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool].
#Click "Browse target" button.
#Vera should appear in targets list.
#Click on "*UN*checkPID" radio box, and click on "EraseNormal" drop-down box.
#Click the [Files] button.
#Download the file: [http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware] and save it on your computer.
#Select the file [http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware]
#Click the [Open] button to get the file.
#Click on the [OK] button on the BIN File Information dialog box.
#Click on the [Upgrade] button. The file will be flashed, and you will see a dialog box saying success - close Upgrade Tool.
#Put your computer's IP back to DHCP (Automatically Configure) and Vera will assign an IP like 192.168.81.xxx
#Please wait until Vera ''automatically'' reboots and the ETH1 light starts double blinking or it's solid (this can take 10 to 30 minutes).
#When you see the ETH1 double blinking, you are done.

 

== To do after the restoration has finished ==

*If you have your computer connected to the ETH2 port of Vera, open http://192.168.81.1 and you will see the Wizard to continue setup your Vera.
*If you already connected the ETH1 (Wan) cable coming from your main Router/ADSL modem, the ETH1 light on front will go solid, meaning Vera is connected to the internet.

Dont forget to update your Vera to the latest available firmware. This is explained here: [[Update Firmware]]

Next, if you also want to restore everything else in Vera, restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

== References ==

http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware http://download.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

[[Category:User_Instructions]] [[Category:How_To]]

Firmware Flash Vera2

2017-11-06T14:29:10Z

George:

== Prerequisites ==

*YOU NEED TO FOLLOW THIS TUTORIAL ONLY IF YOUR VERA2 UNIT IS NOT BOOTING ANYMORE, THIS MEANS THAT WHILE BEING CONNECTED TO THE INTERNET/YOUR NETWORK ON THE '''ETH1 PORT''', THE POWER LED IS ORANGE AND OTHER LEDS ARE GREEN WITH THE EXCEPTION OF ETH1 and ZWAVE WHICH ARE OFF FOR MORE THAN 30 MINUTES !

*The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications should be run in Windows XP SP3 compatibility mode.

*Make sure your computer is connected to your network through an Ethernet cable. Make sure to disable any wireless networking interfaces before continuing.

NOTE: Failure to disable your wireless network before continuing could result in an unusable unit.

*Please deactivate all Firewall and Antivirus software which is running during the upgrade process.

Note: If you are running Windows Vista/7 please follow the next guide to enable the TFTP Client and then continue with the re-flash steps. Guide: http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

=== If the restoration utility does not work on Windows 7 ===

Please note that this is only available for Windows 7 Professional, Enterprise and Ultimate editions. 

*If the restoration utility does not work on Windows 7 you should use the Windows Xp Mode, offered for free by Microsoft. To install it, you have to go to this page [http://www.microsoft.com/en-us/download/details.aspx?id=8002 Windows Xp Mode] which will walk you through the entire process. 
*After this finishes and you open up the Windows Xp Mode Virtual Machine, you should go to the Menu, select Tools -> Settings, select Networking and for adapter 1 make sure to select your LAN card, the one that will be connected directly into the ETH2 port of Vera.
*Afterwards you will have to open Internet explorer inside the virtual machine, access [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2 this page] and download the Firmware flash utilities inside the virtual machine.
*On Windows 7 change the Local Area Connection settings to use the static IP and connect the Vera unit to your computer as explained at the begining of this page, then open the Firmware Flash utility inside the Virtual machine and you should be able to continue the Firmware Flash process.

== Files to download before you start the restoration process ==

*[http://download.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool]
*[http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware]

== Setup your computer to connect to Vera 2 ==

*Computer IP: 192.168.81.xxx (not 1)
*Subnet Mask: 255.255.255.0
*Default Gateway: 192.168.81.1

== Begin the process for flashing the firmware ==

#Use a network cable (CAT5e) and plug the cable from your PC into Vera's ETH2 port.
#Unplug Vera from the power cord.
#Holding down Vera's service button (not the small one, the one resembling the Z-Wave button with no label in the middle of the unit), whilst pluging in the power cord back in. Wait about 5s after you plugged the power cord back with the reset button pressed. When releasing the reset button, power LED should be blinking.
#If the power LED is not blinking, turn Vera off and try again'''(PLEASE doublecheck FIRST!!! The LED blinking can be very faint!).'''
#Start [http://download1.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool].
#Click "Browse target" button.
#Vera should appear in targets list.
#Click on "*UN*checkPID" radiobox, and click on "EraseNormal" dropdown box.
#Click the [Files] button.
#Download the file: [http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware] and save it on your computer.
#Select the file [http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware]
#Click the [Open] button to get the file.
#Click on the [OK] button on the BIN File Information dialog box.
#Click on the [Upgrade] button. File will be flashed, and you will see a dialog box saying success - close Upgrade Tool.
#Put your computer's IP back to DHCP (Automatically Configure) and Vera will assign an IP like 192.168.81.xxx
#Please wait until Vera ''automatically'' reboots and the ETH1 light starts double blinking or it's solid (this can take 10 to 30 minutes).
#When you see the ETH1 double blinking, you are done.

 

== To do after the restoration has finished ==

*If you have your computer connected to the ETH2 port of Vera, open http://192.168.81.1 and you will see the Wizard to continue setup your Vera.
*If you already connected the ETH1 (Wan) cable coming from your main Router/ADSL modem, the ETH1 light on front will go solid, meaning Vera is connected to the internet.

Dont forget to update your Vera to the latest available firmware. This is explained here: [[Update Firmware]]

Next, if you also want to restore everything else in Vera, restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

== References ==

http://download.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware http://download.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

[[Category:User_Instructions]] [[Category:How_To]]

Backup and Restore

2017-02-14T12:56:35Z

George:

All units have the ability to backup the user data and restore it on the same or a new controller.

Note: Z-Wave series 300 (Z-Wave) based controllers will only be able to restore backups on other series 300 controllers. Same applies for series 500 (Z-Wave Plus) controllers. To find out the Z-Wave series of your controller check out [http://wiki.mios.com/index.php/Comparison_of_Vera_units this ]page.

Backup Controller and Save the file on your Computer

1. Using a computer and browser, log in to your unit's Dashboard.

2. From the Dashboard menu on the left, click on Settings and select Backup, and then click on the Create backup button as shown below. 

[[File:Backup 1.png]]

3. A new page will open. Click on the Backup Z-Wave Network button first to create a Z-Wave copy of your network.

Note: This will make a complete Z-Wave backup of your configuration.

4. Next, click on the Create backup button to save the file to your computer. Important: Make a note of the folder or directory where the computer is saving this file, as you'll need it later.

[[File:Backup 2.png]]

== Restoring backup on your controller ==

1. From the Dashboard click on the Settings menu and select Backup.

2. Either drag and drop the backup file into the Upload area (using a file browser such as Windows Explorer or Mac Finder), OR click the Upload button and browse to the file’s location and select it.

3. Check the Restore Z-Wave network option to include the Z-Wave network from the controller.

Note: This option will overwrite the existing Z-Wave data on the controller. The backups can be restored on the same Z-Wave series they were taken, series 300 cannot be restored on series 500 units (or vice-versa) due to different Z-Wave chips.

4. Click the Restore button to start the restoration process on your controller.

[[File:Backup 3.png]]

5. Wait. The restoration process will take a few minutes during which your controller will reboot.It is recommended that you check to make sure all your devices are communicating with the controller. For some Z-wave battery operated devices you might need to "wake them up" manually by activating them (such as by opening a window to "wake up" a window sensor, or by pressing the control button on the device.)

Backup & Restore

2017-02-14T12:50:27Z

George: George moved page Backup & Restore to Backup and Restore

#REDIRECT [[Backup and Restore]]

Backup and Restore

2017-02-14T12:50:26Z

George: George moved page Backup & Restore to Backup and Restore

All units have the ability to backup the user data and restore it on the same or a new controller.

Note: Z-Wave series 300 (Z-Wave) based controllers will only be able to restore backups on other series 300 controllers. Same applies for series 500 (Z-Wave Plus) controllers. To find out the Z-Wave series of your controller check out [http://wiki.mios.com/index.php/Comparison_of_Vera_units ''this '']page.

Backup Controller and Save the file on your Computer

1. Using a computer and browser, log in to your unit's Dashboard.

2. From the Dashboard menu on the left, click on Settings and select Backup, and then click on the Create backup button as shown below. 

[[File:Backup 1.png]]

3. A new page will open. Click on the Backup Z-Wave Networkbutton first to create a Z-Wave copy of your network.

Note: This will make a complete Z-Wave backup of your configuration.

4. Next, click on the Create backup button to save the file to your computer. Important: Make a note of the folder or directory where the computer is saving this file, as you'll need it later.

[[File:Backup 2.png]]

== Restoring backup on your controller ==

1. From the Dashboard click on the Settings menu and select Backup.

2. Either drag and drop the backup file into the Upload area (using a file browser such as Windows Explorer or Mac Finder), OR click the Upload button and browse to the file’s location and select it.

3. Check the Restore Z-Wave network option to include the Z-Wave network from the controller.

Note: This option will overwrite the existing Z-Wave data on the controller.

4. Click the Restore button to start the restoration process on your controller.

[[File:Backup 3.png]]

5. Wait. The restoration process will take a few minutes during which your controller will reboot.It is recommended that you check to make sure all your devices are communicating with the controller. For some Z-wave battery operated devices you might need to "wake them up" manually by activating them (such as by opening a window to "wake up" a window sensor, or by pressing the control button on the device.)

Backup and Restore

2017-02-14T12:49:28Z

George:

All units have the ability to backup the user data and restore it on the same or a new controller.

Note: Z-Wave series 300 (Z-Wave) based controllers will only be able to restore backups on other series 300 controllers. Same applies for series 500 (Z-Wave Plus) controllers. To find out the Z-Wave series of your controller check out [http://wiki.mios.com/index.php/Comparison_of_Vera_units ''this '']page.

Backup Controller and Save the file on your Computer

1. Using a computer and browser, log in to your unit's Dashboard.

2. From the Dashboard menu on the left, click on Settings and select Backup, and then click on the Create backup button as shown below. 

[[File:Backup 1.png]]

3. A new page will open. Click on the Backup Z-Wave Networkbutton first to create a Z-Wave copy of your network.

Note: This will make a complete Z-Wave backup of your configuration.

4. Next, click on the Create backup button to save the file to your computer. Important: Make a note of the folder or directory where the computer is saving this file, as you'll need it later.

[[File:Backup 2.png]]

== Restoring backup on your controller ==

1. From the Dashboard click on the Settings menu and select Backup.

2. Either drag and drop the backup file into the Upload area (using a file browser such as Windows Explorer or Mac Finder), OR click the Upload button and browse to the file’s location and select it.

3. Check the Restore Z-Wave network option to include the Z-Wave network from the controller.

Note: This option will overwrite the existing Z-Wave data on the controller.

4. Click the Restore button to start the restoration process on your controller.

[[File:Backup 3.png]]

5. Wait. The restoration process will take a few minutes during which your controller will reboot.It is recommended that you check to make sure all your devices are communicating with the controller. For some Z-wave battery operated devices you might need to "wake them up" manually by activating them (such as by opening a window to "wake up" a window sensor, or by pressing the control button on the device.)

File:Backup 3.png

2017-02-14T12:40:29Z

George:

File:Backup 2.png

2017-02-14T11:15:24Z

George:

File:Backup 1.png

2017-02-14T11:14:52Z

George:

Side By Side Comparison

2017-02-13T11:41:19Z

George: Reverted edits by George (talk) to last revision by DaveL17

This is meant to be an informative, objective comparison of Vera and the other Z-Wave gateways, not a 1-sided sales pitch. If other Z-Wave gateways have features we have not listed, you can add those features. You can also add other gateways that are not on the list, and correct any mistakes and add notes. This document is a wiki, editable by the public.

Note that this document, being a wiki, contains data provided by the public and our customers as well as those of our competitors. The list of features supported by the Schlage and Hawking products comes from customers who use those products and Mi Casa Verde has not independently verified all the features of our competitors products. If there are any inaccuracies, anyone is able to correct them.

'''NOTE: 27 July 2009 micasaverde: Has updated the page with the new features in our Luup release, which is now in beta, including the new cell phone apps which are in beta and will be released in about 2 weeks.'''

'''NOTE: 29 July 2009 Schlage: Has updated the page to accurately reflect the features associated with the Schlage LiNK system. Schlage is continuously improving the Schlage LiNK application to provide more features to the end user.'''

{| cellpadding="2" border="1"
|-
! 
! [http://www.micasaverde.com Vera]
! [http://www.hawkingtech.com/products/productlist.php?CatID=43&FamID=119&ProdID=392 Hawking HRPG1]
! [http://consumer.schlage.com/LiNK/ Schlage LiNK Bridge]
! Notes
|-
| align="center" | '''''Price'''''
|-
| Retail Price
| $299
| $179
| Not sold separately
| The Schlage Bridge is available only as part of a bundled kit. The Schlage locks are available without the Schlage Bridge for $199 MSRP.
|-
| Monthly charge
| Optional
| $9.99
| $12.99
| Schlage requires a monthly subscription or else you cannot use the LiNK or control Z-Wave devices. You can still manually operate the door lock without the subscription. Hawking requires a monthly subscription of $9.99 for all services including cell phone access. Vera's provides secure remote access, cell phone control, and email notifications for free. SMS texting and video archiving are $29/year.
|-
| Functionality dependent on manufacturer
| [[Image:Check.png]]
| partial
| [[Image:X.png]]
| Will the product still function if the manufacturer stops supporting it? With Vera, only the optional hosted online services depend on Mi Casa Verde, all local functions are independent, and Vera will run without an internet connection. In Hawking's case, cell phone access would stop and limited other functions would continue. User will need to know how to hack the units back door. In Schlage's case, the product will not function at all if you don't pay the monthly bill or if Schlage discontinues support for the product. However the Lock itself will still function as a keypad lock. The remote capabilities and programming will be disabled. If internet connection is lost all timers/events will cease to occur during that time. The Schlage LiNK is just a bridge no internal triggers seem to be stored in the bridge.
|-
| align="center" | '''''Z-Wave Device Compatibility'''''
|-
| Guaranteed compatible with all Z-Wave devices
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Vera is free if it doesn't work with all your Z-Wave devices as explained [[Guaranteed Compatibility|here]]. Note: Z-Wave devices must be certified by Zensys/the Z-Wave alliance to be called Z-Wave and to qualify. The Schlage LiNK Application will operate all certified Z-Wave Devices within any device class that is supported in the Schlage LiNK Application.
|-
| Light Switches/Appliance Modules
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| 
|-
| Thermostats
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Note: Schlage web portal only supports Notifications/Alerts and email functions for Schlage/Trane branded thermostats.
|-
| Door/Window/Motion Sensor
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:X.png]]
| Z-Wave door, window and motion sensors can trigger scenes, fire events, and you can be notified on your mobile phone.
|-
| Combo-sensors
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Such as the 3-in-1 light, temperature, motion sensor.
|-
| Handheld remotes
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| Handheld remotes can activate scenes in the gateway and be programed within the gateway. Handheld remotes can be secondary controllers in conjunction with the Schlage LiNK Bridge and Hawking. Schlage or Hawking cannot program the remote from the bridge. Schlage cannot give a remote the role of "secondary inclusionary".
|-
| Door locks
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| 
|-
| Scene controllers
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Same as handheld remotes.
|-
| Supports European Z-Wave
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| You must order the Euro version of Vera to support European Z-Wave.
|-
| align="center" | '''''Insteon/X10 Device Compatibility'''''
|-
| Insteon/X10
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| 
|-
| align="center" | '''''A/V Device Compatibility'''''
|-
| Infrared control
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Control TV's, stereo's, etc., with infrared emitters.
|-
| RS232 control
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| For those models of A/V devices that have serial control ports provides direct control without infrared.
|-
| Universal remote control
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Use your mobile phone as a universal remote control.
|-
| align="center" | '''''Alarm System Compatibility'''''
|-
| RS232 alarm panels
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| USB alarm panels
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| Ethernet alarm panels
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| align="center" | '''''IP Devices Compatibility'''''
|-
| Generic IP Cameras
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Vera works with any IP camera that can return a JPEG file, such as Panasonic and most IP cameras.
|-
| Proprietary IP Cameras
| N/A
| [[Image:Check.png]]
| [[Image:Check.png]]
| Schlage cameras use proprietary firmware to ensure secure plug and play conectivity with the Schlage LiNK Apllication. Hawking also has a proprietary camera.
|-
| Pan/Tilt/Zoom
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Ability to move camera and adjust it remotely
|-
| align="center" | '''''Z-Wave features'''''
|-
| Works as a primary controller
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Schlage LiNK Bridge does not seem to support SUC/SIS. This means you cannot add a controller as a secondary inclusion conroller. A secondary inclusion controller can be used to include devices without removing a dongle or diconnecting the bridge. This setup aids in network setup as issues are immediately shown during installation.
|-
| Works as a secondary controller
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:X.png]]
| 
|-
| Can be added to an existing Z-Wave network
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| 
|-
| Supports controller shift
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:X.png]]
| 
|-
| align="center" | '''''Door lock specific'''''
|-
| Secure remote locking/unlocking of doors
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| 
|-
| Secure remote setting of user codes
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| 
|-
| Control of doors from handheld remotes and scene controllers
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:X.png]]
| A button on a Z-Wave handheld remote or scene controller can be programmed, for example, to turn off the lights and lock the doors. Schlage allows lock control through the Schlage Application and any secondary controller supporting the required device classes.
|-
| Door locks trigger events
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| For example, when you unlock the door, the porch light comes on automatically. With the Schlage application, entering a valid 4 digit code at the lock enables any pre-programmed scene within the application.
|-
| PIN codes trigger events
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| For example, you give the pool cleaner a PIN code and are notified by SMS when he unlocks the door with his PIN code.
|-
| Support Vacation Mode of Schlage LiNK lock
| [[Image:X.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| Schlage LiNK Bridge can remotely enable Vacation mode that disables keypad on the lock. Great if you don't want anyone to use their code to enter. At any time you can restore access to the keypad though Schlage LiNK web or phone app. [[http://forum.micasaverde.com/index.php?topic=2071.msg8123#msg8123 Manual Vacation Mode]]
|-
| Support all door locks
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:Check.png]]
| Vera will also support the Black & Decker door locks when they are on the market.
|-
| align="center" | '''''Automation'''''
|-
| Scenes
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| 
|-
| Timers
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Schlage LiNK only sets time based events on a 7-day week. Schlage is not able to set a time or date in the future.
|-
| Events
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| For example, turn on a light when a motion sensor is tripped.
|-
| Relative to sunset/sunrise
| [[Image:Check.png]]
| 
| 
| Trigger a scene 1 hour before the sun rises, etc.
|-
| align="center" | '''''Remote access'''''
|-
| Direct access over IP
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| You can directly control the device over the internet or local network without going through a remote server.
|-
| Works when your internet is down
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Remote access can not be provided when the internet is not available. With Vera you can still connect through your Local Area Net (LAN) to do everything else, including operating and configuring Vera.
|-
| Secure remote access through a gateway
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Both Vera and Schlage use a secure server similar to that for online banking. Vera offers this for free. Schlage offers it for a $13/month subscription.
|-
| align="center" | '''''Energy monitoring'''''
|-
| Tracks actual energy usage
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Supports the Z-Wave classes for reporting current Watts, accumulated kWh, etc.
|-
| Reports historical energy usage
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Vera shows past energy usage by room, type of device, etc.
|-
| Responds to energy alerts
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Vera allows automatic energy reduction when the utility company reports the power grid is overloaded. See [[Energy]].
|-
| align="center" | '''''Networking'''''
|-
| Built-in router/gateway
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Hawking and Schlage require connection to a standard residential router.
|-
| Built-in Wi-Fi
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Hawking and Schlage require you to purchase these separately.
|-
| align="center" | '''''Remote Control'''''
|-
| Custom remotes with your own skins/buttons
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| For example, put an iPod touch on the wall which your own wallpaper and pictures and icons that trigger scenes or control devices.
|-
| Web interface on local home network
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Direct access by http://[your bridge's IP address]
|-
| Web interface for secure remote access over the internet
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Access going through a remote server via https
|-
| Access from any cell phone
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Vera is compatible with any cell phone that has an internet connection. So you can control it from new phones, like the T-Mobile Sidekick, as well as older, basic phones.
|-
| Native iPhone/iPod touch app
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Vera's new version is due in August '09, which also has a universal remote control. Schlage and Hawking use the Crayon/Moshi application.
|-
| Native Java app (Blackberry, etc.)
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| 
|-
| Native Windows Mobile
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Schlage and Hawking use the Crayon/Moshi application.
|-
| Wi-Fi access (iPod Touch, PDA's, etc.)
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| PDA's, iPhone's, and other Wi-Fi enabled devices can control the bridge using your home network.
|-
| Handheld remotes
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| A button on a handheld remote can trigger a device.
|-
| Scene controllers
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| 
|-
| align="center" | '''''Online services'''''
|-
| Archive of surveillance camera images
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Available through the [[Find Vera Service]].
|-
| Archive of energy usage
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Available through the [[Find Vera Service]].
|-
| Archive of events
| [[Image:Check.png]]
| [[Image:Check.png]]
| [[Image:Check.png]]
| Available through the [[Find Vera Service]].
|-
| align="center" | '''''Open-ness / geek-friendly'''''
|-
| Direct login allowed
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Log in to the system with Telnet/SSH to inspect the software, verify the strength of the encryption, etc.
|-
| Allows custom scripts
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| Write your own scripts to automate tasks; scripts run in the bridge.
|-
| Published API's for custom add-ons and UI's
| [[Image:Check.png]]
| [[Image:X.png]]
| [[Image:X.png]]
| See: [[Luup Intro]].
|}

[[Category:Glossary]]

Side By Side Comparison

2017-02-13T11:39:49Z

George:

'''This page is obsolete.'''

This is meant to be an informative, objective comparison of Vera and the other Z-Wave gateways, not a 1-sided sales pitch. If other Z-Wave gateways have features we have not listed, you can add those features. You can also add other gateways that are not on the list, and correct any mistakes and add notes. This document is a wiki, editable by the public.

Note that this document, being a wiki, contains data provided by the public and our customers as well as those of our competitors. The list of features supported by the Schlage and Hawking products comes from customers who use those products and Mi Casa Verde has not independently verified all the features of our competitors products. If there are any inaccuracies, anyone is able to correct them.

'''NOTE: 27 July 2009 micasaverde: Has updated the page with the new features in our Luup release, which is now in beta, including the new cell phone apps which are in beta and will be released in about 2 weeks.'''

'''NOTE: 29 July 2009 Schlage: Has updated the page to accurately reflect the features associated with the Schlage LiNK system. Schlage is continuously improving the Schlage LiNK application to provide more features to the end user.'''

{| cellpadding="2" border="1"
|-
! 
! [http://www.micasaverde.com Vera]
! [http://www.hawkingtech.com/products/productlist.php?CatID=43&FamID=119&ProdID=392 Hawking HRPG1]
! [http://consumer.schlage.com/LiNK/ Schlage LiNK Bridge]
! Notes
|-
| style="text-align: center;" | '''''Price'''''
|-
| Retail Price
| $299
| $179
| Not sold separately
| The Schlage Bridge is available only as part of a bundled kit. The Schlage locks are available without the Schlage Bridge for $199 MSRP.
|-
| Monthly charge
| Optional
| $9.99
| $12.99
| Schlage requires a monthly subscription or else you cannot use the LiNK or control Z-Wave devices. You can still manually operate the door lock without the subscription. Hawking requires a monthly subscription of $9.99 for all services including cell phone access. Vera's provides secure remote access, cell phone control, and email notifications for free. SMS texting and video archiving are $29/year.
|-
| Functionality dependent on manufacturer
| [[File:Check.png]]
| partial
| [[File:X.png]]
| Will the product still function if the manufacturer stops supporting it? With Vera, only the optional hosted online services depend on Mi Casa Verde, all local functions are independent, and Vera will run without an internet connection. In Hawking's case, cell phone access would stop and limited other functions would continue. User will need to know how to hack the units back door. In Schlage's case, the product will not function at all if you don't pay the monthly bill or if Schlage discontinues support for the product. However the Lock itself will still function as a keypad lock. The remote capabilities and programming will be disabled. If internet connection is lost all timers/events will cease to occur during that time. The Schlage LiNK is just a bridge no internal triggers seem to be stored in the bridge.
|-
| style="text-align: center;" | '''''Z-Wave Device Compatibility'''''
|-
| Guaranteed compatible with all Z-Wave devices
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Vera is free if it doesn't work with all your Z-Wave devices as explained [[Guaranteed Compatibility|here]]. Note: Z-Wave devices must be certified by Zensys/the Z-Wave alliance to be called Z-Wave and to qualify. The Schlage LiNK Application will operate all certified Z-Wave Devices within any device class that is supported in the Schlage LiNK Application.
|-
| Light Switches/Appliance Modules
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| 
|-
| Thermostats
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Note: Schlage web portal only supports Notifications/Alerts and email functions for Schlage/Trane branded thermostats.
|-
| Door/Window/Motion Sensor
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:X.png]]
| Z-Wave door, window and motion sensors can trigger scenes, fire events, and you can be notified on your mobile phone.
|-
| Combo-sensors
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Such as the 3-in-1 light, temperature, motion sensor.
|-
| Handheld remotes
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| Handheld remotes can activate scenes in the gateway and be programed within the gateway. Handheld remotes can be secondary controllers in conjunction with the Schlage LiNK Bridge and Hawking. Schlage or Hawking cannot program the remote from the bridge. Schlage cannot give a remote the role of "secondary inclusionary".
|-
| Door locks
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| 
|-
| Scene controllers
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Same as handheld remotes.
|-
| Supports European Z-Wave
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| You must order the Euro version of Vera to support European Z-Wave.
|-
| style="text-align: center;" | '''''Insteon/X10 Device Compatibility'''''
|-
| Insteon/X10
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| 
|-
| style="text-align: center;" | '''''A/V Device Compatibility'''''
|-
| Infrared control
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Control TV's, stereo's, etc., with infrared emitters.
|-
| RS232 control
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| For those models of A/V devices that have serial control ports provides direct control without infrared.
|-
| Universal remote control
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Use your mobile phone as a universal remote control.
|-
| style="text-align: center;" | '''''Alarm System Compatibility'''''
|-
| RS232 alarm panels
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| USB alarm panels
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| Ethernet alarm panels
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Sensors from your traditional home alarm system can trigger scenes, notifications, etc., and you can remotely manage your home alarm.
|-
| style="text-align: center;" | '''''IP Devices Compatibility'''''
|-
| Generic IP Cameras
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Vera works with any IP camera that can return a JPEG file, such as Panasonic and most IP cameras.
|-
| Proprietary IP Cameras
| N/A
| [[File:Check.png]]
| [[File:Check.png]]
| Schlage cameras use proprietary firmware to ensure secure plug and play conectivity with the Schlage LiNK Apllication. Hawking also has a proprietary camera.
|-
| Pan/Tilt/Zoom
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Ability to move camera and adjust it remotely
|-
| style="text-align: center;" | '''''Z-Wave features'''''
|-
| Works as a primary controller
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Schlage LiNK Bridge does not seem to support SUC/SIS. This means you cannot add a controller as a secondary inclusion conroller. A secondary inclusion controller can be used to include devices without removing a dongle or diconnecting the bridge. This setup aids in network setup as issues are immediately shown during installation.
|-
| Works as a secondary controller
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:X.png]]
| 
|-
| Can be added to an existing Z-Wave network
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| 
|-
| Supports controller shift
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:X.png]]
| 
|-
| style="text-align: center;" | '''''Door lock specific'''''
|-
| Secure remote locking/unlocking of doors
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| 
|-
| Secure remote setting of user codes
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| 
|-
| Control of doors from handheld remotes and scene controllers
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:X.png]]
| A button on a Z-Wave handheld remote or scene controller can be programmed, for example, to turn off the lights and lock the doors. Schlage allows lock control through the Schlage Application and any secondary controller supporting the required device classes.
|-
| Door locks trigger events
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| For example, when you unlock the door, the porch light comes on automatically. With the Schlage application, entering a valid 4 digit code at the lock enables any pre-programmed scene within the application.
|-
| PIN codes trigger events
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| For example, you give the pool cleaner a PIN code and are notified by SMS when he unlocks the door with his PIN code.
|-
| Support Vacation Mode of Schlage LiNK lock
| [[File:X.png]]
| [[File:X.png]]
| [[File:Check.png]]
| Schlage LiNK Bridge can remotely enable Vacation mode that disables keypad on the lock. Great if you don't want anyone to use their code to enter. At any time you can restore access to the keypad though Schlage LiNK web or phone app. [[http://forum.micasaverde.com/index.php?topic=2071.msg8123#msg8123 Manual Vacation Mode]]
|-
| Support all door locks
| [[File:Check.png]]
| [[File:X.png]]
| [[File:Check.png]]
| Vera will also support the Black & Decker door locks when they are on the market.
|-
| style="text-align: center;" | '''''Automation'''''
|-
| Scenes
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| 
|-
| Timers
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Schlage LiNK only sets time based events on a 7-day week. Schlage is not able to set a time or date in the future.
|-
| Events
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| For example, turn on a light when a motion sensor is tripped.
|-
| Relative to sunset/sunrise
| [[File:Check.png]]
| 
| 
| Trigger a scene 1 hour before the sun rises, etc.
|-
| style="text-align: center;" | '''''Remote access'''''
|-
| Direct access over IP
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| You can directly control the device over the internet or local network without going through a remote server.
|-
| Works when your internet is down
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Remote access can not be provided when the internet is not available. With Vera you can still connect through your Local Area Net (LAN) to do everything else, including operating and configuring Vera.
|-
| Secure remote access through a gateway
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Both Vera and Schlage use a secure server similar to that for online banking. Vera offers this for free. Schlage offers it for a $13/month subscription.
|-
| style="text-align: center;" | '''''Energy monitoring'''''
|-
| Tracks actual energy usage
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Supports the Z-Wave classes for reporting current Watts, accumulated kWh, etc.
|-
| Reports historical energy usage
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Vera shows past energy usage by room, type of device, etc.
|-
| Responds to energy alerts
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Vera allows automatic energy reduction when the utility company reports the power grid is overloaded. See [[Energy]].
|-
| style="text-align: center;" | '''''Networking'''''
|-
| Built-in router/gateway
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Hawking and Schlage require connection to a standard residential router.
|-
| Built-in Wi-Fi
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Hawking and Schlage require you to purchase these separately.
|-
| style="text-align: center;" | '''''Remote Control'''''
|-
| Custom remotes with your own skins/buttons
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| For example, put an iPod touch on the wall which your own wallpaper and pictures and icons that trigger scenes or control devices.
|-
| Web interface on local home network
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Direct access by http://[your bridge's IP address]
|-
| Web interface for secure remote access over the internet
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Access going through a remote server via https
|-
| Access from any cell phone
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Vera is compatible with any cell phone that has an internet connection. So you can control it from new phones, like the T-Mobile Sidekick, as well as older, basic phones.
|-
| Native iPhone/iPod touch app
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Vera's new version is due in August '09, which also has a universal remote control. Schlage and Hawking use the Crayon/Moshi application.
|-
| Native Java app (Blackberry, etc.)
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| 
|-
| Native Windows Mobile
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Schlage and Hawking use the Crayon/Moshi application.
|-
| Wi-Fi access (iPod Touch, PDA's, etc.)
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| PDA's, iPhone's, and other Wi-Fi enabled devices can control the bridge using your home network.
|-
| Handheld remotes
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| A button on a handheld remote can trigger a device.
|-
| Scene controllers
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| 
|-
| style="text-align: center;" | '''''Online services'''''
|-
| Archive of surveillance camera images
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Available through the [[Find Vera Service]].
|-
| Archive of energy usage
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Available through the [[Find Vera Service]].
|-
| Archive of events
| [[File:Check.png]]
| [[File:Check.png]]
| [[File:Check.png]]
| Available through the [[Find Vera Service]].
|-
| style="text-align: center;" | '''''Open-ness / geek-friendly'''''
|-
| Direct login allowed
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Log in to the system with Telnet/SSH to inspect the software, verify the strength of the encryption, etc.
|-
| Allows custom scripts
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| Write your own scripts to automate tasks; scripts run in the bridge.
|-
| Published API's for custom add-ons and UI's
| [[File:Check.png]]
| [[File:X.png]]
| [[File:X.png]]
| See: [[Luup Intro]].
|}

Backup and Restore

2017-02-13T10:45:43Z

George: Created page with "<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black"> === This page contains ..."

<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
=== This page contains the following errors: ===
<div style="font-family:monospace;font-size:12px">error on line 1 at column 121: attributes construct error </div>
=== Below is a rendering of the page up to the first error. ===
</parsererror>

ZWave Security

2017-02-13T10:08:08Z

George: Created page with "'''Z-Wave Security''': Vera controllers offer support for S0 Security. '''Vera Edge, Plus, Secure''' are security enabled Z-Wave Plus products that are able to use encrypted ..."

'''Z-Wave Security''': Vera controllers offer support for S0 Security.

'''Vera Edge, Plus, Secure''' are security enabled Z-Wave Plus products that are able to use encrypted Z-Wave Plus messages to communicate to other security enabled Z-Wave Plus products.

How to reset your Vera controller to factory defaults

2017-01-18T09:57:06Z

George:

This procedure will guide you to reset your Vera controller running '''UI7 '''to factory defaults. Please follow the instructions for the controller you have.

=== Vera Secure ===

The Vera Plus controllers can be '''reset '''to factory defaults by pressing the reset button 6 times within 6 seconds. This will reset the Z-Wave network and change its HouseID, clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Pressing the '''reset '''button 3 times within 6 seconds will reset the network configuration settings to defaults while keeping your other settings intact.

=== Vera Plus ===

The Vera Plus controllers can be '''reset '''to factory defaults by pressing the reset button 6 times within 6 seconds. This will reset the Z-Wave network and change its HouseID, clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Pressing the '''reset '''button 3 times within 6 seconds will reset the network configuration settings to defaults while keeping your other settings intact.

=== Vera Edge ===

The Vera Edge controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change its HouseID, clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults while keeping your other settings intact.

=== Vera 3 ===

The Vera 3 controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change its HouseID, clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults while keeping your other settings intact.

=== Vera lite ===

The Vera lite controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change its HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults while keeping your other settings intact.

Store logs USB

2016-08-19T10:15:08Z

George:

'''HOWTO get your Vera log an attached USB drive.'''

== Introduction ==

On larger Vera deployments, with large numbers of Z-Wave Devices, Plugins or Scenes, it may be necessary to move the Vera log files to external storage to free-up space for Vera to function correctly.

MiOS Version 1.1.1245 introduced an option to let users attach a standard USB drive to offload Vera's log files, the details are in the MiOS [[Release Notes]], inlined here:

:''2. There is an option with Vera2 on Advanced, Logs to enable logging to a USB drive. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running.''

:''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac''

This [[:Category:How To|How To]] note shows you how to enable this option, how to validate that it's been enabled, and provides pointers to further reading.

== Prerequisites ==

This solution will require:

*Vera 2 Hardware and above (Vera 3 / Lite / Edge / Plus)
*UI4 and above
*A ''new'' USB Drive
**Drive should be at least 512Mb or higher.
**Vera will create its own partition on it which will be 512Mb in size and use that to write logfiles to it.
**Experienced users only: a ''newly'' FAT-formatted ''existing'' USB drive may work.

== Instructions ==

*After you got your usb-drive connected to the USB port on the backside of your Vera. Please be patient, it might not work the first time, but it will work. DO NOT REMOVE THE DRIVE while Vera boots/reboots or during power-cycle operations.
*Log into the UI

=== UI7 ===

*Select "Settings"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI5 ===

*Select "Setup"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI4 ===

*Select "Advanced" on the sop right (next to "MiOS developers" in the toolbox)
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

== '''Validation''' ==

For those who would like to validate it's setup correctly, here are some detailed steps.

SSH into your vera (using Putty or any other SSH client) Login as <tt>root</tt> with the password thats on the back of your box. If you don't see the root password or need help logging in see [[Logon Vera SSH#Can.27t find the root password.3F|Logon # Can't find the root password?]].

At the prompt type:

root@MiOS_1xxxx:~# df -h

If you find something like:

Filesystem Size Used Available Use% Mounted on
...
/dev/scsi/host0/bus0/target0/lun0/part1
506.2M 29.2M 451.3M 6% /tmp/log/cmh
...

Then your USB drive is being used to storing MiOS log files.

== Debugging ==

Check that /overlay isn't full.

Stop LuaUPnP before activating 'Store logs on USB device*' (/etc/init.d/cmh stop).

== References ==

*USB Drive logging discussion [http://forum.micasaverde.com/index.php?topic=6439 [1]]

Store logs USB

2016-08-19T10:14:15Z

George:

'''HOWTO get your Vera log an attached USB drive.'''

== Introduction ==

On larger Vera deployments, with large numbers of Z-Wave Devices, Plugins or Scenes, it may be necessary to move the Vera log files to external storage to free-up space for Vera to function correctly.

MiOS Version 1.1.1245 introduced an option to let users attach a standard USB drive to offload Vera's log files, the details are in the MiOS [[Release Notes]], inlined here:

:''2. There is an option with Vera2 on Advanced, Logs to enable logging to a USB drive. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running.''

:''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac''

This [[:Category:How To|How To]] note shows you how to enable this option, how to validate that it's been enabled, and provides pointers to further reading.

== Prerequisites ==

This solution will require:

*Vera 2 Hardware and above (Vera 3 / Lite / Edge / Plus)
*UI4 and above
*A ''new'' USB Drive
**Drive should be at least 512Mb or higher.
**Vera will create its own partition on it which will be 512Mb in size and use that to write logfiles to it.
**Experienced users only: a ''newly'' FAT-formatted ''existing'' USB drive may work.

== Instructions ==

*After you got your usb-drive connected to the USB port on the backside of your Vera. Please be patient, it might not work the first time, but it will work. DO NOT REMOVE THE DRIVE while Vera boots/reboots or during power-cycle operations.
*Log into the UI

=== UI7 ===

*Select "Settings"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI5 ===

*Select "Setup"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI4 ===

*Select "Advanced" on the sop right (next to "MiOS developers" in the toolbox)
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

== Validation ==

For those who would like to validate it's setup correctly, here are some detailed steps.

SSH into your vera (using Putty or any other SSH client) Login as <tt>root</tt> with the password thats on the back of your box. If you don't see the root password or need help logging in see [[Logon Vera SSH#Can.27t find the root password.3F|Logon # Can't find the root password?]].

At the prompt type:

root@MiOS_1xxxx:~# df -h

If you find something like:

Filesystem Size Used Available Use% Mounted on
...
/dev/scsi/host0/bus0/target0/lun0/part1
506.2M 29.2M 451.3M 6% /tmp/log/cmh
...

Then your USB drive is being used to storing MiOS log files.

== Debugging ==

Check that /overlay isn't full.

Stop LuaUPnP before activating 'Store logs on USB device*' (/etc/init.d/cmh stop).

== References ==

*USB Drive logging discussion [http://forum.micasaverde.com/index.php?topic=6439 [1]]

Store logs USB

2016-08-19T10:13:47Z

George:

'''HOWTO get your Vera log an attached USB drive.'''

== Introduction ==

On larger Vera deployments, with large numbers of Z-Wave Devices, Plugins or Scenes, it may be necessary to move the Vera log files to external storage to free-up space for Vera to function correctly.

MiOS Version 1.1.1245 introduced an option to let users attach a standard USB drive to offload Vera's log files, the details are in the MiOS [[Release Notes]], inlined here:

:''2. There is an option with Vera2 on Advanced, Logs to enable logging to a USB drive. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running.''

:''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac''

This [[:Category:How To|How To]] note shows you how to enable this option, how to validate that it's been enabled, and provides pointers to further reading.

== Prerequisites ==

This solution will require:

*Vera 2 Hardware and above (Vera 3 / Lite / Edge / Plus)
*UI4 and above
*A ''new'' USB Drive
**Drive should be at least 512Mb or higher.
**Vera will create its own partition on it which will be 512Mb in size and use that to write logfiles to it.
**Experienced users only: a ''newly'' FAT-formatted ''existing'' USB drive may work. The jury is out on this one.

== Instructions ==

*After you got your usb-drive connected to the USB port on the backside of your Vera. Please be patient, it might not work the first time, but it will work. DO NOT REMOVE THE DRIVE while Vera boots/reboots or during power-cycle operations.
*Log into the UI

=== UI7 ===

*Select "Settings"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI5 ===

*Select "Setup"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI4 ===

*Select "Advanced" on the sop right (next to "MiOS developers" in the toolbox)
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

== Validation ==

For those who would like to validate it's setup correctly, here are some detailed steps.

SSH into your vera (using Putty or any other SSH client) Login as <tt>root</tt> with the password thats on the back of your box. If you don't see the root password or need help logging in see [[Logon Vera SSH#Can.27t find the root password.3F|Logon # Can't find the root password?]].

At the prompt type:

root@MiOS_1xxxx:~# df -h

If you find something like:

Filesystem Size Used Available Use% Mounted on
...
/dev/scsi/host0/bus0/target0/lun0/part1
506.2M 29.2M 451.3M 6% /tmp/log/cmh
...

Then your USB drive is being used to storing MiOS log files.

== Debugging ==

Check that /overlay isn't full.

Stop LuaUPnP before activating 'Store logs on USB device*' (/etc/init.d/cmh stop).

== References ==

*USB Drive logging discussion [http://forum.micasaverde.com/index.php?topic=6439 [1]]

Store logs USB

2016-08-19T10:13:34Z

George:

'''HOWTO get your Vera log an attached USB drive.'''

== Introduction ==

On larger Vera deployments, with large numbers of Z-Wave Devices, Plugins or Scenes, it may be necessary to move the Vera log files to external storage to free-up space for Vera to function correctly.

MiOS Version 1.1.1245 introduced an option to let users attach a standard USB drive to offload Vera's log files, the details are in the MiOS [[Release Notes]], inlined here:

:''2. There is an option with Vera2 on Advanced, Logs to enable logging to a USB drive. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running.''

:''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac''

This [[:Category:How To|How To]] note shows you how to enable this option, how to validate that it's been enabled, and provides pointers to further reading.

== Prerequisites ==

This solution will requires:

*Vera 2 Hardware and above (Vera 3 / Lite / Edge / Plus)
*UI4 and above
*A ''new'' USB Drive
**Drive should be at least 512Mb or higher.
**Vera will create its own partition on it which will be 512Mb in size and use that to write logfiles to it.
**Experienced users only: a ''newly'' FAT-formatted ''existing'' USB drive may work. The jury is out on this one.

== Instructions ==

*After you got your usb-drive connected to the USB port on the backside of your Vera. Please be patient, it might not work the first time, but it will work. DO NOT REMOVE THE DRIVE while Vera boots/reboots or during power-cycle operations.
*Log into the UI

=== UI7 ===

*Select "Settings"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI5 ===

*Select "Setup"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI4 ===

*Select "Advanced" on the sop right (next to "MiOS developers" in the toolbox)
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

== Validation ==

For those who would like to validate it's setup correctly, here are some detailed steps.

SSH into your vera (using Putty or any other SSH client) Login as <tt>root</tt> with the password thats on the back of your box. If you don't see the root password or need help logging in see [[Logon Vera SSH#Can.27t find the root password.3F|Logon # Can't find the root password?]].

At the prompt type:

root@MiOS_1xxxx:~# df -h

If you find something like:

Filesystem Size Used Available Use% Mounted on
...
/dev/scsi/host0/bus0/target0/lun0/part1
506.2M 29.2M 451.3M 6% /tmp/log/cmh
...

Then your USB drive is being used to storing MiOS log files.

== Debugging ==

Check that /overlay isn't full.

Stop LuaUPnP before activating 'Store logs on USB device*' (/etc/init.d/cmh stop).

== References ==

*USB Drive logging discussion [http://forum.micasaverde.com/index.php?topic=6439 [1]]

Store logs USB

2016-08-19T10:12:04Z

George:

'''HOWTO get your Vera log an attached USB drive.'''

== Introduction ==

On larger Vera deployments, with large numbers of Z-Wave Devices, Plugins or Scenes, it may be necessary to move the Vera log files to external storage to free-up space for Vera to function correctly.

MiOS Version 1.1.1245 introduced an option to let users attach a standard USB drive to offload Vera's log files, the details are in the MiOS [[Release Notes]], inlined here:

:''2. There is an option with Vera2 on Advanced, Logs to enable logging to a USB drive. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running.''

:''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac''

This [[:Category:How To|How To]] note shows you how to enable this option, how to validate that it's been enabled, and provides pointers to further reading.

== Prerequisites ==

This solution will requires:

*Vera 2 Hardware and above (Vera 3/lite)
*Firmware 1.1.1245 and above
*A ''new'' USB Drive
**Drive should be at least 512Mb or higher.
**Vera will create its own partition on it which will be 512Mb in size and use that to write logfiles to it.
**Experienced users only: a ''newly'' FAT-formatted ''existing'' USB drive may work. The jury is out on this one.

== Instructions ==

*After you got your usb-drive connected to the USB port on the backside of your Vera. Please be patient, it might not work the first time, but it will work. DO NOT REMOVE THE DRIVE while Vera boots/reboots or during power-cycle operations.
*Log into the UI

=== UI7 ===

*Select "Settings"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI5 ===

*Select "Setup"
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

=== UI4 ===

*Select "Advanced" on the sop right (next to "MiOS developers" in the toolbox)
*Select the "Logs"tab
*Activate the "Store logs on USB device*" option and READ the text there:

:''Please connect an USB drive first then check the checkbox.''
:''WARNING: The USB drive will be erased. Wait 20 minutes after clicking OK.''
:''Status''

*Click the "OK" button.

Wait until vera reports progress.

If MiOS reports "FAILURE", repeat the process. If MiOS reports Success, you are done.

== Validation ==

For those who would like to validate it's setup correctly, here are some detailed steps.

SSH into your vera (using Putty or any other SSH client) Login as <tt>root</tt> with the password thats on the back of your box. If you don't see the root password or need help logging in see [[Logon Vera SSH#Can.27t find the root password.3F|Logon # Can't find the root password?]].

At the prompt type:

root@MiOS_1xxxx:~# df -h

If you find something like:

Filesystem Size Used Available Use% Mounted on
...
/dev/scsi/host0/bus0/target0/lun0/part1
506.2M 29.2M 451.3M 6% /tmp/log/cmh
...

Then your USB drive is being used to storing MiOS log files.

== Debugging ==

Check that /overlay isn't full.

Stop LuaUPnP before activating 'Store logs on USB device*' (/etc/init.d/cmh stop).

== References ==

*USB Drive logging discussion [http://forum.micasaverde.com/index.php?topic=6439 [1]]

Zigbee Command Clusters

2016-07-25T18:41:49Z

George: Created page with "The Vera engine supports the ZigBee Command Clusters listed in the SupportedClusters variable, and these are listed below: <div>Basic Cluster (0x0000)</div><div>Binary Input C..."

The Vera engine supports the ZigBee Command Clusters listed in the SupportedClusters variable, and these are listed below:
<div>Basic Cluster (0x0000)</div><div>Binary Input Cluster (0x000F)</div><div>Electrical Measurement Cluster (0x0B04)</div><div>Fan Control Cluster (0x0202)</div><div>IAS Zone Cluster (0x500)</div><div>Level Control Cluster (0x0008)</div><div>On/Off Cluster (0x0006)</div><div>Power Config Cluster (0x0001)</div><div>Relative Humidity Cluster (0x0405)</div><div>Temperature Measurement Cluster (0x0402)</div><div>Thermostat Cluster (0x0201)</div>

Vera Nand

2016-06-14T08:55:12Z

George:

The Vera units can have 8/16/32/128 MB of NAND memory as it can be seen in the Vera comparison table ([http://wiki.micasaverde.com/index.php/Comparison_of_Vera_units 1]). Below you can read more about how the NAND memory works.

== Information about NAND ==

NAND flash architecture was introduced by Toshiba in 1989. These memories are accessed much like block devices, such as hard disks or memory cards. Each block consists of a number of pages. The pages are typically 512 or 2,048 or 4,096 bytes in size. Associated with each page are a few bytes (typically 1/32 of the data size) that can be used for storage of an error correcting code (ECC) checksum.

Typical block sizes include:

*32 pages of 512+16 bytes each for a block size of 16 KB
*64 pages of 2,048+64 bytes each for a block size of 128 KB
*64 pages of 4,096+128 bytes each for a block size of 256 KB
*128 pages of 4,096+128 bytes each for a block size of 512 KB.

While reading and programming is performed on a page basis, erasure can only be performed on a block basis. Number of Operations (NOPs) is the number of times the pages can be programmed. So far, this number for MLC flash is always one while, for SLC flash, it is four.

NAND devices also require bad block management by the device driver software, or by a separate controller chip. When a logical block is accessed by high-level software, it is mapped to a physical block by the device driver or controller. A number of blocks on the flash chip may be set aside for storing mapping tables to deal with bad blocks, or the system may simply check each block at power-up to create a bad block map in RAM. The overall memory capacity gradually shrinks as more blocks are marked as bad.

NAND relies on ECC to compensate for bits that may spontaneously fail during normal device operation. A typical ECC will correct a one-bit error in each 2048 bits (256 bytes) using 22 bits of ECC code, or a one-bit error in each 4096 bits (512 bytes) using 24 bits of ECC code. If the ECC cannot correct the error during read, it may still detect the error. When doing erase or program operations, the device can detect blocks that fail to program or erase and mark them bad. The data is then written to a different, good block, and the bad block map is updated.

'''Most NAND devices are shipped from the factory with some bad blocks. These are typically marked according to a specified bad block marking strategy.'''

== FAQ ==

'''1.''' What is be the maximum number of bad blocks admissible for the Vera units ?

''If a block (512 byte unit) turns to be bad, the JFFS2 driver will skip the whole erease block (16KiB). The number of the admissible blocks depends on the size of the partition where the bad blocks are appearing. A level of 10% of the total blocks available should not cause problems.''

'''2.''' How much memory in bytes/kilobytes does a bad block take from the flash ?

''One block consumes only 512 byte of memory, but the whole erase block (16KiB) will be unusable.''

'''3.''' Will 200-300 bad blocks affect anything else except the size of the flash ?

''If a block becomes bad during writing a new firmware, that will be detected by he nandwrite utility, and it will write the actual data into the next good block, so these bad block will not cause problems.''

''If a block becomes bad when the JFFS2 driver writes out some data into the flash, that will be detected by the JFFS2, and it will write the data into another block.''

How to reset your Vera controller to factory defaults

2016-04-15T07:37:37Z

George:

This procedure will guide you to reset your Vera controller running '''UI7 '''to factory defaults. Please follow the instructions for the controller you have.

=== Vera Plus ===

The Vera Plus controllers can be '''reset '''to factory defaults by pressing the reset button 6 times whitin 6 seconds. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Pressing the '''reset '''button 3 times within 6 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera Edge ===

The Vera Edge controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera 3 ===

The Vera 3 controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera lite ===

The Vera lite controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

How to reset your Vera controller to factory defaults

2016-04-15T07:36:59Z

George:

This procedure will guide you to reset your Vera controller running '''UI7 '''to factory defaults. Please follow the instructions for the controller you have.

=== Vera Edge ===

The Vera Edge controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera Plus ===

The Vera Plus controllers can be '''reset '''to factory defaults by pressing the reset button 6 times whitin 6 seconds. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Pressing the '''reset '''button 3 times within 6 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera 3 ===

The Vera 3 controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera lite ===

The Vera lite controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

How to reset your Vera controller to factory defaults

2016-04-15T07:35:25Z

George: Created page with "This procedure will guide you to reset your Vera controller running UI7 to factory defaults. Please follow the instructions for the controller you have. === Vera Edge ==..."

This procedure will guide you to reset your Vera controller running UI7 to factory defaults. Please follow the instructions for the controller you have.

=== Vera Edge ===

The Vera Edge controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact. 

=== Vera Plus ===

The Vera Plus controllers can be '''reset '''to factory defaults by pressing the reset button 6 times whitin 6 seconds. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Pressing the '''reset '''button 3 times within 6 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera 3 ===

The Vera 3 controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

=== Vera lite ===

The Vera lite controllers can be '''reset '''to factory defaults by keeping the reset button for 20 seconds and releasing it. This will reset the Z-Wave network and change it's HouseID, and clear your account and user configuration data from your unit.

''Note: The account will only be removed from the controller, but it will continue to be in the database.''

Holding the '''reset '''button for 10 seconds will reset the network configuration settings to defaults, while keeping your other settings intact.

VeraEdge

2016-04-15T07:25:39Z

George:

== VeraEdge: The Controller for Today's Expanding Smart Home Universe ==

   Vera Edge is a security enabled Z-Wave Plus product which can use encrypted Z-Wave messages to communicate with other security enabled Z-Wave Products.

*One-touch control of your entire system
*View all your cameras and control all your devices from one easy app
*See and control your system from any smartphone or tablet from anywhere in the world (where there's Internet)
*Save money on energy, automatically!
*Expand your system to control over 220 devices
*Wireless communications makes installation a breeze in any home or small business
*Easy, intuitive setup with simple Q&A format; adding devices later is easy too with preconfigured settings for most devices
*No monthly fees required!

    With VeraEdge you can do anything today's most advanced smart homes can do. Cutting edge features like geo fencing let the system know when you're coming home, so your living room is nice and warm (or cool) when you arrive. (Save energy, automatically, when you leave, too!) One easy, intuitive app spans all platforms (Mac/Window/iOS/Android) to easily keep you in control at all times, wherever you go. Controls all the leading brands of locks, thermostats, and other devices so you don't need to compromise when selecting components. Create a better system, at a fraction of the price tag of the big guys, and with no monthly fees required. VeraEdge gives you:

*More device compatibility—faster processor allows greater compatibility with devices
*More memory for better response times and flexibility • WPS easy push button pairing for Wi-Fi devices
*Improved multi-camera management • Intuitive user set up and control
*Local control of devices to avoid any latency or connectivity issues (works locally even when your Internet goes down)

    VeraEdge is the best way to centrally control your smart home or automate your small business. Use VeraEdge to coordinate and unify devices you may already own, such as smart thermostats and smart door locks; or to start building a new system from scratch. As your system expands, you'll never outgrow VeraEdge!

*Control over 220 devices in a single location
*Geo fencing, advanced occupancy sensing, push notifications
*Over 200 3rd party apps available in the MiOS Marketplace
*Multiple trigger events for complete customization of automation scenes—by time of day, motion, day of week, sunrise/sunset, or depending on other device(s)

== VeraEdge Is Your Best Choice For A Home/Business Automation Controller ==

The world of advanced smart home automation, security, and peace of mind for your home or small business all starts with VeraEdge!

Your VeraEdge system can do many different things, depending on the other devices you add. For example:

• You can build a security system by adding door locks, door/window sensors, motion sensors, wireless video cameras, and alarm.

• Build an energy savings system with thermostats, lamp dimmers, energy meter monitor, and smart switches for AC devices.

• Create a home safety monitoring system with smoke detectors, carbon monoxide detector, and flood detector.

• Make life convenient with lamp dimmers, door locks, and lawn sprinklers that operate automatically. Or combine all these functions and more in one system!

== Best Smart Home Automation Software ==

VeraEdge incorporates Vera's award-winning seventh-generation software, Vera UI7, which makes setting up devices, operating your system, and creating custom scenes a breeze. Vera UI7 features:

• Common user interface across all platforms (PC/Mac desktops, smartphones, tablets)

• Integrated Help—simple, contextual help callouts and links to detailed documentation on the support site

• Energy management—Preconfigured Device Settings for Easy Setup; At a Glance Reporting of Household Energy Consumption; Daily, Monthly, and Annual Reporting

• Improved access control with simple PIN management

• User customizable dashboard with favorite devices pinned for easy viewing, access and control

Use VeraEdge for convenience, to save energy, and achieve the peace of mind of knowing your family is safe and your home or small business is alright—from anywhere in the world!

VeraEdge

2016-04-15T07:23:44Z

George:

== VeraEdge: The Controller for Today's Expanding Smart Home Universe ==

Vera Edge is a security enabled Z-Wave Plus product which can use encrypted Z-Wave messages to communicate with other security enabled Z-Wave Products.

• One-touch control of your entire system

• View all your cameras and control all your devices from one easy app

• See and control your system from any smartphone or tablet from anywhere in the world (where there's Internet)

• Save money on energy, automatically!

• Expand your system to control over 220 devices

• Wireless communications makes installation a breeze in any home or small business

• Easy, intuitive setup with simple Q&A format; adding devices later is easy too with preconfigured settings for most devices

• No monthly fees required!

With VeraEdge you can do anything today's most advanced smart homes can do. Cutting edge features like geo fencing let the system know when you're coming home, so your living room is nice and warm (or cool) when you arrive. (Save energy, automatically, when you leave, too!) One easy, intuitive app spans all platforms (Mac/Window/iOS/Android) to easily keep you in control at all times, wherever you go. Controls all the leading brands of locks, thermostats, and other devices so you don't need to compromise when selecting components. Create a better system, at a fraction of the price tag of the big guys, and with no monthly fees required. VeraEdge gives you:

• More device compatibility—faster processor allows greater compatibility with devices

• More memory for better response times and flexibility • WPS easy push button pairing for Wi-Fi devices

• Improved multi-camera management • Intuitive user set up and control

• Local control of devices to avoid any latency or connectivity issues (works locally even when your Internet goes down)

VeraEdge is the best way to centrally control your smart home or automate your small business. Use VeraEdge to coordinate and unify devices you may already own, such as smart thermostats and smart door locks; or to start building a new system from scratch. As your system expands, you'll never outgrow VeraEdge!

• Control over 220 devices in a single location

• Geo fencing, advanced occupancy sensing, push notifications

• Over 200 3rd party apps available in the MiOS Marketplace

• Multiple trigger events for complete customization of automation scenes—by time of day, motion, day of week, sunrise/sunset, or depending on other device(s)

== VeraEdge Is Your Best Choice For A Home/Business Automation Controller ==

The world of advanced smart home automation, security, and peace of mind for your home or small business all starts with VeraEdge!

Your VeraEdge system can do many different things, depending on the other devices you add. For example:

• You can build a security system by adding door locks, door/window sensors, motion sensors, wireless video cameras, and alarm.

• Build an energy savings system with thermostats, lamp dimmers, energy meter monitor, and smart switches for AC devices.

• Create a home safety monitoring system with smoke detectors, carbon monoxide detector, and flood detector.

• Make life convenient with lamp dimmers, door locks, and lawn sprinklers that operate automatically. Or combine all these functions and more in one system!

== Best Smart Home Automation Software ==

VeraEdge incorporates Vera's award-winning seventh-generation software, Vera UI7, which makes setting up devices, operating your system, and creating custom scenes a breeze. Vera UI7 features:

• Common user interface across all platforms (PC/Mac desktops, smartphones, tablets)

• Integrated Help—simple, contextual help callouts and links to detailed documentation on the support site

• Energy management—Preconfigured Device Settings for Easy Setup; At a Glance Reporting of Household Energy Consumption; Daily, Monthly, and Annual Reporting

• Improved access control with simple PIN management

• User customizable dashboard with favorite devices pinned for easy viewing, access and control

Use VeraEdge for convenience, to save energy, and achieve the peace of mind of knowing your family is safe and your home or small business is alright—from anywhere in the world!

VeraEdge

2016-04-15T07:05:40Z

George: Created page with "== VeraEdge: The Controller for Today's Expanding Smart Home Universe == • One-touch control of your entire system • View all your cameras and control all your devi..."

== VeraEdge: The Controller for Today's Expanding Smart Home Universe ==

• One-touch control of your entire system

• View all your cameras and control all your devices from one easy app

• See and control your system from any smartphone or tablet from anywhere in the world (where there's Internet)

• Save money on energy, automatically!

• Expand your system to control over 220 devices

• Wireless communications makes installation a breeze in any home or small business

• Easy, intuitive setup with simple Q&A format; adding devices later is easy too with preconfigured settings for most devices

• No monthly fees required!

With VeraEdge you can do anything today's most advanced smart homes can do. Cutting edge features like geo fencing let the system know when you're coming home, so your living room is nice and warm (or cool) when you arrive. (Save energy, automatically, when you leave, too!) One easy, intuitive app spans all platforms (Mac/Window/iOS/Android) to easily keep you in control at all times, wherever you go. Controls all the leading brands of locks, thermostats, and other devices so you don't need to compromise when selecting components. Create a better system, at a fraction of the price tag of the big guys, and with no monthly fees required. VeraEdge gives you:

• More device compatibility—faster processor allows greater compatibility with devices

• More memory for better response times and flexibility • WPS easy push button pairing for Wi-Fi devices

• Improved multi-camera management • Intuitive user set up and control

• Local control of devices to avoid any latency or connectivity issues (works locally even when your Internet goes down)

VeraEdge is the best way to centrally control your smart home or automate your small business. Use VeraEdge to coordinate and unify devices you may already own, such as smart thermostats and smart door locks; or to start building a new system from scratch. As your system expands, you'll never outgrow VeraEdge!

• Control over 220 devices in a single location

• Geo fencing, advanced occupancy sensing, push notifications

• Over 200 3rd party apps available in the MiOS Marketplace

• Multiple trigger events for complete customization of automation scenes—by time of day, motion, day of week, sunrise/sunset, or depending on other device(s)

== VeraEdge Is Your Best Choice For A Home/Business Automation Controller ==

The world of advanced smart home automation, security, and peace of mind for your home or small business all starts with VeraEdge!

Your VeraEdge system can do many different things, depending on the other devices you add. For example:

• You can build a security system by adding door locks, door/window sensors, motion sensors, wireless video cameras, and alarm.

• Build an energy savings system with thermostats, lamp dimmers, energy meter monitor, and smart switches for AC devices.

• Create a home safety monitoring system with smoke detectors, carbon monoxide detector, and flood detector.

• Make life convenient with lamp dimmers, door locks, and lawn sprinklers that operate automatically. Or combine all these functions and more in one system!

== Best Smart Home Automation Software ==

VeraEdge incorporates Vera's award-winning seventh-generation software, Vera UI7, which makes setting up devices, operating your system, and creating custom scenes a breeze. Vera UI7 features:

• Common user interface across all platforms (PC/Mac desktops, smartphones, tablets)

• Integrated Help—simple, contextual help callouts and links to detailed documentation on the support site

• Energy management—Preconfigured Device Settings for Easy Setup; At a Glance Reporting of Household Energy Consumption; Daily, Monthly, and Annual Reporting

• Improved access control with simple PIN management

• User customizable dashboard with favorite devices pinned for easy viewing, access and control

Use VeraEdge for convenience, to save energy, and achieve the peace of mind of knowing your family is safe and your home or small business is alright—from anywhere in the world!

Association

2016-03-28T15:46:49Z

George:

== '''Associations''' ==

=== Supported Association Groups ===

 Vera edge has support for the following associations groups:
<pre>GROUP ID: 1 - Lifeline

NUMBER OF NODES IN GROUP: 1</pre>
=== Creating a Z-Wave Association ===

Note: Leave By default Vera should automatically configure devices checked as explained above, and leave each device's Automatically configure set to 'Default Behavior'. If you tell Vera not to configure the device, Vera will leave the device alone and will not set the associations for you.
<pre>Please note that you'll have to associate the device A with the device B</pre>
 These are also unique for each device according to the manufacturer. Associations are commonly used to tell sensors to turn on lights, and to associate devices. Refer to the manufacturer's users manual that came with the Z-Wave device to learn how they handle associations. Associations are given an ID or group ID. In this case you'll have to create the association only on the sensor.

 To add an association, type in the group ID, which is a number, click 'Add Group' and then check off the Z-Wave devices you want to be associated. Vera will attempt to configure the node, and if successful, you'll see the [[Device_Control_Status#Job_icons|green 'configure job' ok icon].

If it's a battery operated device and Vera can't configure it right away, read the comments above about the Configure node right now.

 For '''UI7:'''

Click on the '>' button of your device, then go to Device Options

Add group 1 and hit Add group

 [[File:Aso1.JPG]]

 In our case we'll asociate a sensor with Vera.

 [[File:Aso2.JPG]]

 When the association is made properly should be displayed the picture below.

'''Note: If you associate a sensor with a switch at '''Set to:'''and '''Currently:'''should be displayed the id of the switch.'''

 [[File:Aso3.JPG]]

IP Cameras

2016-02-16T10:36:05Z

George: /* 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''' ===

{| class="wikitable"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Notes
|-
| Mi Casa Verde
| IP Camera
| Vistacam
| all
|
| Indoor
|
|
| The VistaCam comes pre-configured with the Vera unit so when you connect the camera to the network it should be shown on the Dashboard automatically.
|-
| 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.

Update: For Mac users please access this [http://www.networkwebcams.com/ip-camera-learning-center/2008/05/16/howto-set-up-a-panasonic-ip-camera-using-a-mac/ link] and setup your camera.
|-
| GetVera
| IP Camera
| VistaCam PT
| all
| 
| Indoor
| 
| 
|
|-
| GetVera
| IP Camera
| VistaCam SD
| all
| 
| Indoor
| 
| 
|
|-
| GetVera
| IP Camera
| VistaCam 700
| all
| 
| Indoor
| 
| 
|
|-
|}

=== '''Cameras known to work''' ===

Please note that we don't guarantee that all functions of a camera will work with our Vera controller !!!

{| class="wikitable"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Added by
! Notes
|-
| Foscam [http://www.foscam.us/ [1]] [http://www.foscam.com/ [2]]
| IP Camera
| [http://foscam.us/foscam-fi8918w-wireless-ip-camera-11.html?gclid=CPDxx_v5trECFYrP3wodpHgAwQ FI8908/FI8908W]
| firmware 11.14.1.46 / 2.4.8.12
| 2010
| Indoor
| /snapshot.cgi
| [http://www.amazon.com/Wireless-Windows-compatible-Installation-Included/product-reviews/B0030FR08W/ref=dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1 Customer reviews]
| Ap15e
| Use the Foscam IP Camera Tool for initial setup, then copy IP address and path into Vera setup fields. For Pan, Tilt, Patrol support use the attached file [http://forum.micasaverde.com/index.php/topic,8832.msg68515.html#msg68515 here].
|-
| Foscam
| IP Camera
| FI9810W FI9821 FI9831W FI9805W
|
|
| Indoor
| /cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=MYLOGIN&pwd=MYPASS
|
| mcvchris
| FI9810W & FI9805W - pan/tilt with I_FoscamPTZ.xml; FI9821 & FI9831W pan/tilt with I_Foscam98HD.xml
|-
| Foscam
| IP Camera
| FI8910W FI8918W FI8905W
|
|
| Indoor
| /snapshot.cgi?user=YOURUSERNAME&pwd=YOURPASSWORD
|
| mcvchris
| FI9810W - pan/tilt with I_FoscamPTZ.xml; FI8918W pan/tilt with I_VistaCamPT.xml
|-
| Foscam
| IP Camera
| FI9820W FI8601W
|
|
| Indoor
| tmpfs/snap.jpg or /tmpfs/auto.jpg
|
|
|
|-
| Foscam
| IP Camera
| FI8906W FI8904W
|
|
| Indoor
| /snapshot.cgi?user=USERNAME&pwd=PASSWORD&resolution=32&rate=0
|
| mcvchris
|
|-
| Linksys
| IP Camera
| [http://homesupport.cisco.com/en-us/wireless/lbc/WVC54GCA/download 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
| [http://www.cisco.com/en/US/products/ps9948/index.html 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
| [http://homesupport.cisco.com/en-us/wireless/lbc/WVC80N?referrer=www.linksysbycisco.com 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
| [http://icamview.com/icv22.htm iCV-22], [http://icamview.com/icv32.htm 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, supports 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 SmartEye [http://www.wansview.com/ Wansview]
| IP Camera
| [http://www.smarthome.com.au/zseries/wirelesssecuritycamera.php Z~Series Wireless Camera] [http://www.ipcam-central.com IPCAM Central SmartEye NC532W]
| all
| 2009 [http://www.ipcam-central.com/Smarteye-NC532W-FTP-p/nc532w-ftp.htm 2011] 
| Indoor and [http://www.ipcam-central.com/Smarteye-NC532W-FTP-p/nc532w-ftp.htm Outdoor H.264 w/FTP/email/SD]
| Static URL /tmpfs/auto.jpg (small) OR /tmpfs/snap.jpg (large)
| 
| 
| Inexpensive IP security camera designed for the Australian and New Zealand Z-Wave users, but shipping world wide. Luup file available from [http://www.ipcam-central.com [3]] but not needed unless need PTZ. Despite Vera only displaying small images use snap.jpg to get larger images in Home Buddy for Android. Informational: QT URL for IE [http://x.x.x.x/iphone/11.qt?user:password&amp http://x.x.x.x/iphone/11.qt?user:password&amp]; which reveals RTSP RTP URL rtsp://x.x.x.x/iphone/11 (credentials required though)
|-
| [http://global.level1.com LevelOne]
| IP Camera
| [http://global.level1.com/product_d.php?id=54 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.
|-
| Asante
| IP Camera
| [http://www.asante.com/products/SecureNetCam/Voyager1.asp Voyager I]
| firmware 2.02 and above
| 2010
| Indoor
| image.cgi
| 
| 
| An inexpensive IP camera that is very feature rich, has good image quality, night vision capabilities, motion detection, two-way audio, video streaming over TCP, UDP, or HTTP, and other configurable features. In firmware version 2.02, Asante added the capability to retrieve an image via a URL (however, it is delayed by 3 seconds). Offers a full-featured web interface in IE using an ActiveX plug-in (limited capabilites in other browsers).
|-
| TrendNet
| IP Camera
| [http://www.trendnet.com/products/proddetail.asp?prod=155_TV-IP512WN&cat=149 TV-IP512WN]
| all
| 2009
| Indoor
| /image/jpeg.cgi OR /cgi/jpg/image.cgi
| 
| 
| Feature-rich inexpensive IP camera with good image quality, features 802.11n, GPIO ports, not bad optics
|-
| TrendNet
| IP Camera
| TV-IP551WI
| all
|
| Indoor
| /image/jpeg.cgi OR /cgi/jpg/image.cgi
| 
| mcvchris
|
|-
| D-Link
| IP Camera
| [http://www.dlink.com/products/?pid=DCS-950G DCS-950G]
| firmware 1.07
|  ?
| Indoor
| /_gCVimage.jpg
| [http://www.amazon.com/D-Link-Securicam-DCS-950G-Wireless-Internet/product-reviews/B0006GDCD0/ref=dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1 Customer reviews]
| 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 by default. Starting with Ui4 a timeout option was added to the device settings for the camera, which you can increase to 10.
|-
| D-Link
| IP Camera
| [http://www.dlink.com/products/?pid=664 DCS-920] (also DCS-930 and DCS-932)
| firmware 1.05?
|  ?
| Indoor
| /image/jpeg.cgi
 /image.jpg

| 
| futzle
| Standard timeout (5 seconds) works. It may be necessary to turn on access control (username/password) on the camera's web configuration, and set Vera to use the username/password.
|-
| WansView
| IP Camera
| NCH532MW
|
|
| Indoor
| /tmpfs/auto.jpg
|
| mcvchris
|
|-
| WansView
| IP Camera
| NCB-541B
|
|
| Indoor
| /snapshot.cgi?user=[USERNAME]&pwd=[PASSWORD] OR
/videostream.asf?usr=[USERNAME]&pwd=[PASSWORD]

|
| mcvchris
|
|-
| Sony
| IP Camera
| SNC-DH160
|
|
| Indoor
| /oneshotimage1 OR
now.jpg?snap=spush

|
| mcvchris
|
|-
| Wanscam
| IP Camera
| aj-c2wa-c198
|
|
| Indoor
| /videostream.cgi
|
| mcvdaniel
| It may be necessary to use the original software that came with the camera to find it on the network.
|-
| Aviosys (Yoics)
| IP Camera server
| [http://www.aviosys.com/downloads/manuals/video/9100%28A%29%20Plus%20Manual-NB%20-V2.37.pdf 9100a]
| 
|   
| Indoor/Outdoor
|
/usr/yoics0.jpg /usr/yoics1.jpg /usr/yoics2.jpg

 /usr/yoics3.jpg

| 
| mcvadi
| The number for the URL depends on the port that the camera is connected to (/usr/yoics1.jpg is for port 2 on the server). Each camera uses the same IP address (the one from the camera server).
|-
| IPUX
| IP Camera
| ICS 2330
| 
|   
| Indoor
| /cgi/mjpg/mjpg.cgi 

| 
| mcvanne
| Camera must be setup to use MJPEG compression from the camera configuration page.
|-
| Hikvison
| IP Camera
| DS-2CD7153-E DS-2CD2132-4
| All
|    2012  
| Indoor/Outdoor
| /Streaming/channels/1/picture 

| 
| ndwalters
| Perform initial setup via web interface.
|-
| Hikvison
| IP Camera
| DS-2CD852MF-E
| All
|    2012
| Indoor/Outdoor
| /Streaming/channels/1/picture 

| 
| ndwalters
| Perform initial setup via web interface.
|-
| Dahua
| IP Camera
| IPC-Hx2xxxP
| Firmware 2.103.0000.0.T.20130220
|    2013
| Indoor/Outdoor
| /cgi-bin/snapshot.cgi?channel=0 
| 
| ndwalters
| Perform initial setup via web interface.
|-
| Dahua
| IP Camera
| IPC-Hx3xxxP
| Firmware 2.103.0000.0.T.20121219
|    2013
| Indoor/Outdoor
| /cgi-bin/snapshot.cgi?channel=0 
|  
| ndwalters 
| Perform initial setup via web interface.
|-
| Edimax
| IP Camera 
| IC-71110W  
| 
|    2013 
|  
| /snapshot.jpg
| 
| mcvanne
| Go to camera's control panel -> Network -> LoginFree and set the filename to snapshot.jpg
|}

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

{| class="wikitable"
|-
! 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."
|-
| 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.
Update: The camera might work after a firmware update. More info here: [http://forum.micasaverde.com/index.php?topic=6581.0] and here [http://forum.micasaverde.com/index.php?topic=5841.15]

|-
| 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 publicly 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.

|-
| Trendnet
| IP Camera
| IP672WI
|
|
| Indoor
| none
| 
|
| This camera requires ActiveX.
|}

=== '''DVRs that might work''' ===

{| class="wikitable"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Added by
! Notes
|-
| Axis M7014
| DVR
|
| all
| 
| Indoor
|
/axis-cgi/jpg/image.cgi?resolution=704x480&camera=1&dummy=1382723190384

/axis-cgi/jpg/image.cgi?resolution=704x480&camera=3&dummy=1382723190384

| 
| mcvchris 
|
The path needs to be changed for each camera, the tested DVR had 9 cameras (1-9).

|}}

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

==== '''UI7''' ====

Follow the instructions available on the support page : http://support.getvera.com/customer/portal/articles/1613389-cameras-tab-view-and-install-cameras?b_id=712

For a 3rd party camera you'll need to manually get the Snapshot or JPG URL to get an image from the camera. If your camera supports this method, you can then use it with Vera and you 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.

Once you have that URL copy it in the IP address field of the camera.

You will need to specify:

*the IP address or domain name of the camera and the URL or path to retrieve the current image from the camera as a JPEG file
*any username and password required 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 .
Save the changes and you should be able to view the camera.

==== '''UI5''' ====

The instructions are here: http://docs5.mios.com/doc.php?language=1&manual=1&platform=3Lite&page=ip_cameras

==== '''UI4''' ====

Install the "Generic IP Camera" or "Panasonic IP Camera with Pan/Tilt/Zoom" plugin from the MIOS Marketplace (click on the "+" button from your Dashboard), depending on the camera type, then fill in the blank boxes with the information below(*). To add a new camera just click on the already installed plugin and then press on Create another button.

[[Image:UI4 camera2.png|547x406px|UI4 camera2.png]]  [[Image:UI4 camera1.jpg|812x492px|UI4 camera1.jpg]]

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 you 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.

You will need to specify:

*the IP address or domain name of the camera
*the URL or path to retrieve the current image from the camera as a JPEG file
*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.

==== '''UI2''' ====

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. 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.

[[Image:Camera1.jpg|thumb|center|512px]] [[Image:Camera2.jpg|thumb|center|512px|Camera2.jpg]]

=== '''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]

 

=== '''Trendnet IP camera, TV-IP110W''' ===

Path: /cgi/jpg/image.cgi

 

== '''VistaCam''' ==

VistaCam by Mi Casa Verde is a compact Indoor IP camera that supports both wired and wireless installation. Mi Casa Verde Technical Support Team pre-provisions each VistaCam so it works right out of the box with Vera! Set-up doesn’t get any easier. Whether for Home, Business, Facility surveillance, or just for fun, the VistaCam easy to install and has all the features users need at an affordable price! 

There are 2 basic ways to setup the VistaCam to work with Vera in wireless mode. Here is what you need to do: '''A''') if you have a main router in the house and Vera and your computer are connected to it (we presume that Vera has been already configured) 1) connect the vista Cam to the same router; 2) after a minute or so Vera will auto detect the camera and install the necessary plugin; 3) after the plugin is installed you should be able to see an image when you press the little wrench key from the camera's icon on the dashboard; 4) go to the Settings tab and scroll down to the last option, IP; 5) copy that IP address and paste it into your browser's address bar and hit the Enter key (it will open the administration page for the camera); 6) on the camera's administration page go to wireless options and set up the SSID and the password (the SSID is usually "'''vera_xxxxx'''" [where xxxxx is Vera's Serial Number]; you can find the Serial number and the password on the back side of Vera[password is WiFi pass or Home ID]) and Save; 

'''Note: Vera's SSID is starting with a small letter, not a capital one: vera_xxxxx'''

Note: The password should be listed as ''''Shared Key' '''under the 'Security' section and will show up after you select the '''encryption protocol: WPA2'''. 7) remove the Internet cable connection and power cycle the camera; 8) go to the dashboard and check for image from the camera. 

----

'''B''') if by any reason you can't see the camera after you connect it to your main router here is what you need to do (we presume that Vera has been already configured): 1) go to Advanced > Net & WiFi tab and select the '''Through another gateway on my network. MiOS is a switch''' option and then ''Save and apply'' from the bottom of that page; 2) connect your camera to the '''ETH2 port''' on Vera(now Vera should "see" the camera and you should be able to see pictures); 3) go to the Settings tab and scroll down to the last option, IP; 4) copy that IP address and paste it into your browser's address bar and hit the Enter key (it will open the administration page for the camera); 5) on the camera's administration page go to wireless options and set up the SSID and the password (the SSID is usually "'''vera_xxxxx'''" [where xxxxx is Vera's Serial Number]; you can find the Serial number and the password on the back side of Vera[password is WiFi pass or Home ID]) and Save;

'''Note: Vera's SSID is starting with a small letter, not a capital one: vera_xxxxx''' 

Note: The password should be listed as ''''Shared Key' '''under the 'Security' section and will show up after you select the '''encryption protocol: WPA2'''. 6) remove the Internet cable connection and power cycle the camera; 7) go to the Dashboard and check if you receive images from the camera.

[[Category:Hardware]]

.

Comparison of Vera units

2016-02-08T09:07:54Z

George:

{| style="width: 1151px" border="1" cellpadding="1" cellspacing="1"
|-
| style="text-align: center" colspan="7" | '''Technical Specs Comparison''' 
|-
|   '''Vera Model'''
| style="text-align: center" | '''Vera Plus''' 
| style="text-align: center" | '''Vera Edge''' 
| style="text-align: center" | '''Vera Lite (G)''' 
| style="text-align: center" | '''Vera 3''' 
| style="text-align: center" | '''Vera 2''' 
| style="text-align: center" | '''Vera 1''' 
|-
|   '''CPU''' 
| style="text-align: center" | 880MHz MIPS SoC, dual core 
| style="text-align: center" | 580MHz MIPS SoC 
| style="text-align: center" | 500 MHz MIPS 
| style="text-align: center" | 500 MHz MIPS 
| style="text-align: center" | 240 MHz MIPS 
| style="text-align: center" | 240 MHz MIPS 
|-
|   '''Flash NAND''' 
| style="text-align: center" | 128 MB 
| style="text-align: center" | 128 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 16 MB 
| style="text-align: center" | 8 MB 
|-
|  '''RAM''' 
| style="text-align: center" | 256 MB DDR3 
| style="text-align: center" | 128 MB DDR2 
| style="text-align: center" | 64 MB DDR2 
| style="text-align: center" | 128 MB DDR2 
| style="text-align: center" | 32 MB DDR2 
| style="text-align: center" | 32 MB DDR 
|-
|   '''USB Ports''' 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
|-
|   '''WAN Ports''' 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
|-
|   '''LAN Ports''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | 4 
| style="text-align: center" | 1 
| style="text-align: center" | 4
|-
|   '''Z-Wave''' 
| style="text-align: center" |
Built-in with internal antenna, Z-wave Plus

| style="text-align: center" | Built-in with internal antenna, Z-wave Plus 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | USB Dongle 
|-
| '''  Zigbee''' 
| style="text-align: center" | ZigBee HA 1.2 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
|-
| '''  Bluetooth LE''' 
| style="text-align: center" | Yes 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
|-
|   '''Wi-Fi''' 
| style="text-align: center" | IEEE 802.11b/g/n/ac 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | - 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | IEEE 802.11b/g 
| style="text-align: center" | IEEE 802.11b/g 
|-
|   '''UI Version''' 
| style="text-align: center" | UI7 
| style="text-align: center" | UI7 
|   UI5 upgradeable to UI7 
|   UI5 upgradeable to UI7 
| style="text-align: center" | UI4 upgradeable to UI5 
| style="text-align: center" | UI2 upgradeable to UI4 
|-
| '''  Dimensions (HxWxD)''' 
| style="text-align: center" | 97.5mm x 61.7mm x 13.2 mm 
| style="text-align: center" | 115.5mm x 79.5mmm x 30mm 
| style="text-align: center" | 116mm x 95mm x 44mm 
| style="text-align: center" | 177mm x 130mm x 34mm 
| style="text-align: center" | 165mm x 101mm x 38mm 
| style="text-align: center" | - 
|-
|   '''Battery Pack''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | 4 AA batteries (included) 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | - 
|}

Comparison of Vera units

2016-02-01T16:18:39Z

George:

{| style="width: 1151px" border="1" cellpadding="1" cellspacing="1"
|-
| style="text-align: center" colspan="7" | '''Technical Specs Comparison''' 
|-
|   '''Vera Model'''
| style="text-align: center" | '''Vera Plus''' 
| style="text-align: center" | '''Vera Edge''' 
| style="text-align: center" | '''Vera Lite (G)''' 
| style="text-align: center" | '''Vera 3''' 
| style="text-align: center" | '''Vera 2''' 
| style="text-align: center" | '''Vera 1''' 
|-
|   '''CPU''' 
| style="text-align: center" | 880MHz MIPS SoC, dual core 
| style="text-align: center" | 580MHz MIPS SoC 
| style="text-align: center" | 500 MHz MIPS 
| style="text-align: center" | 500 MHz MIPS 
| style="text-align: center" | 240 MHz MIPS 
| style="text-align: center" | 240 MHz MIPS 
|-
|   '''Flash NAND''' 
| style="text-align: center" | 128 MB 
| style="text-align: center" | 128 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 16 MB 
| style="text-align: center" | 8 MB 
|-
|  '''RAM''' 
| style="text-align: center" | 256 MB DDR3 
| style="text-align: center" | 128 MB DDR2 
| style="text-align: center" | 64 MB DDR2 
| style="text-align: center" | 128 MB DDR2 
| style="text-align: center" | 32 MB DDR2 
| style="text-align: center" | 32 MB DDR 
|-
|   '''USB Ports''' 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
| style="text-align: center" | 2 USB 2.0 
|-
|   '''WAN Ports''' 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
|-
|   '''LAN Ports''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | 4 
| style="text-align: center" | 1 
| style="text-align: center" | 4
|-
|   '''Z-Wave''' 
| style="text-align: center" |
Built-in with internal antenna, Z-wave Plus

| style="text-align: center" | Built-in with internal antenna, Z-wave Plus 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | USB Dongle 
|-
| '''  Zigbee''' 
| style="text-align: center" | ZigBee HA 1.2 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
|-
| '''  Bluetooth BLE''' 
| style="text-align: center" | Yes 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
|-
|   '''Wi-Fi''' 
| style="text-align: center" | IEEE 802.11b/g/n/ac 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | - 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | IEEE 802.11b/g 
| style="text-align: center" | IEEE 802.11b/g 
|-
|   '''UI Version''' 
| style="text-align: center" | UI7 
| style="text-align: center" | UI7 
|   UI5 upgradeable to UI7 
|   UI5 upgradeable to UI7 
| style="text-align: center" | UI4 upgradeable to UI5 
| style="text-align: center" | UI2 upgradeable to UI4 
|-
| '''  Dimensions (HxWxD)''' 
| style="text-align: center" | 97.5mm x 61.7mm x 13.2 mm 
| style="text-align: center" | 115.5mm x 79.5mmm x 30mm 
| style="text-align: center" | 116mm x 95mm x 44mm 
| style="text-align: center" | 177mm x 130mm x 34mm 
| style="text-align: center" | 165mm x 101mm x 38mm 
| style="text-align: center" | - 
|-
|   '''Battery Pack''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | 4 AA batteries (included) 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | - 
|}

Comparison of Vera units

2016-02-01T15:48:48Z

George:

{| style="width: 1151px" border="1" cellpadding="1" cellspacing="1"
|-
| style="text-align: center" colspan="6" | '''Technical Specs Comparison''' 
| style="text-align: center" | 
|-
|   '''Vera Model'''
| style="text-align: center" | '''Vera 1''' 
| style="text-align: center" | '''Vera 2''' 
| style="text-align: center" | '''Vera Lite (G)''' 
| style="text-align: center" | '''Vera 3''' 
| style="text-align: center" | '''Vera Edge''' 
| style="text-align: center" | '''Vera Plus''' 
|-
|   '''CPU''' 
| style="text-align: center" | 240 MHz MIPS 
| style="text-align: center" | 240 MHz MIPS 
| style="text-align: center" | 500 MHz MIPS 
| style="text-align: center" |          500 MHz MIPS 
| style="text-align: center" | 600MHz MIPS SoC 
| style="text-align: center" | 880MHz MIPS SoC, dual core 
|-
|   '''Flash NAND''' 
| style="text-align: center" | 8 MB 
| style="text-align: center" | 16 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 32 MB 
| style="text-align: center" | 128 MB 
| style="text-align: center" | 128 MB 
|-
|  '''RAM''' 
| style="text-align: center" |                 32 MB DDR 
| style="text-align: center" |                  32 MB DDR2 
| style="text-align: center" |                 64 MB DDR2 
| style="text-align: center" |                  128 MB DDR2 
| style="text-align: center" | 128 MB DDR2 
| style="text-align: center" | 256 MB DDR3 
|-
|   '''USB Ports''' 
| style="text-align: center" |                 2 USB 2.0 
| style="text-align: center" |                   2 USB 2.0 
| style="text-align: center" |                  1 USB 2.0 
| style="text-align: center" |                    2 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
| style="text-align: center" | 1 USB 2.0 
|-
|   '''WAN Ports''' 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
| style="text-align: center" | 1 
|-
|   '''LAN Ports''' 
| style="text-align: center" |                  4 
| style="text-align: center" |                       1 
| style="text-align: center" |                         -
| style="text-align: center" |                         4 
| style="text-align: center" | - 
| style="text-align: center" | - 
|-
|   '''Z-Wave''' 
| style="text-align: center" |          USB Dongle 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna 
| style="text-align: center" | Built-in with internal antenna, Z-wave Plus 
| style="text-align: center" | Built-in with internal antenna, Z-wave Plus 
|-
| '''  Zigbee''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | ZigBee HA 1.2 
|-
| '''  Bluetooth BLE''' 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | - 
| style="text-align: center" | Yes 
|-
|   '''Wi-Fi''' 
| style="text-align: center" | IEEE 802.11b/g 
| style="text-align: center" | IEEE 802.11b/g 
| style="text-align: center" | - 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | IEEE 802.11b/g/n 
| style="text-align: center" | IEEE 802.11b/g/n/ac 
|-
|   '''UI Version''' 
| UI2 upgradeable to UI4 
|   UI4 upgradeable to UI5
|   UI5 upgradeable to UI7 
|   UI5 upgradeable to UI7 
| style="text-align: center" | UI7 
| style="text-align: center" | UI7 
|-
|   '''Dimensions (HxWxD)'''
| style="text-align: center" |                      - 
| style="text-align: center" | 165mm x 101mm x 38mm 
| style="text-align: center" | 116mm x 95mm x 44mm 
| style="text-align: center" | 177mm x 130mm x 34mm 
| style="text-align: center" | 115.5mm x 79.5mmm x 30mm 
| style="text-align: center" | 97.5mm x 61.7mm x 13.2 mm 
|-
|   '''Battery Pack''' 
| style="text-align: center" | - 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | 4 AA batteries (included) 
| style="text-align: center" | External, Rechargeable 
| style="text-align: center" | - 
| style="text-align: center" | - 
|}

How to reset to default network settings

2016-01-19T13:52:19Z

George:

How to reset to default network settings on your '''Vera Controller'''

By default Vera automatically configures its network, if you connect it to your router it will automatically connect to it's network. If after plugging Vera into your network, you don't see your Vera on cp.mios.com , please follow these steps to fix your networking:

'''''Note''': For '''Vera edge''' you'll have to replace the 192.168.81.1 IP address with a combination of numbers based on the unit's MAC address. Depending on which firmware version you're on you'll have to set it up like below:''

''MAC address: D4:21:22:FC:BC:9D''

'''''a.''' on firmware version 7.0.12.1 and older (1.7.1598 or older) the IP address Vera Edge can be accessed on will be generated using the last 4 digits in the mac address. For the example above it would be: 192.168.12.29''

'''''b.''' on firmware version newer than 7.0.12.1 (above 1.7.1598) the IP address Vera Edge can be accessed on will be generated using the last 4 characters of the mac address, where the letters are converted to numbers based on their order of the alphabet. For the example above it would be 192.168.23.94''

''This would mean that the PC should have an IP address in the same class as the unit, meaning 192.168.12.100 (for example) for case '''a. '''or 192.168.23.100 (for example) for case '''b.'''''

- Put a STATIC IP to your computer.

*In '''Windows 8'''

From the Tiles menu click on "PC Settings"
From the bottom left of the menu select "Control Panel"
Click on "Network and Internet" and then select "Network and Sharing Center"
Click on "Change adapter settings" in the left menu
Right click on the "Ethernet" connection and click on "Properties"
From the list highlight "Internet Protocol Version 4 (TCP/IPv4) and click on the "Properties" button
Check "Use the following IP address:" and fill in the three fields as follows:
IP address: 192.168.81.10
Subnet mask: 255.255.255.0
Default gateway: 192.168.81.1
Click OK
Click Close

*In '''Windows 7'''

Open Control Panel
View by: Large icons -> Network and Sharing Center
View by: Category -> View netork status and tasks
Click on Change adapter settings
Right click on LAN connection to Vera , then click on Properties
Highlight the Internet Protocol Version 4 (TCP/IPv4) item, and click on Properties
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK Again

*In '''Windows XP'''

Open Windows Start menu.
Open Control Panel.
Classic view: Open Network Connections
Category view: Select Network and Internet Connections, and then Network Connections.
Double-click on your the LAN connection to Vera.
Click Properties.
In the General tab, highlight the Internet Protocol (TCP/IP) item, and click Properties.
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK again

*In '''Mac OS X'''

Open the Apple Menu(Top left corner of your screen)
Click System Preferences
Click Network
Click the Locations dropdown and select Edit Locations
Click the plus sign and call your new location "Vera system Troubleshooting"
Select "Ethernet" from the list on the left
Select "Manually" from the Configure IPv4 dropdown
Enter 192.168.81.10 in the IP address field
Enter 255.255.255.0 in the subnet mask field
Enter 192.168.81.1 in the Router field
Hit "Apply"

- Unplug Vera from the power cord

- Unplug all the cables from Vera

- Plug a network cable from your computer into Vera's LAN port

Vera 2 -> eth2 port
Vera 3 -> lan port (port number 1)
Vera Lite -> ethernet port
Vera Edge -> ethernet port

- Plug Vera into the power cord

- Wait it to start

Now open an web browser and type this in the address bar: 192.168.81.1 Now you can see the DASHBOARD page of your Vera unit.

For '''UI7:'''

Go to Settings > Net & Wi-fi Click on the “Reset to default network settings” button.

[[File:Reset network UI7.png]]

 Confirm by clicking the “OK” Button on the pop-up window.

This will reset the unit to default network settings and can take up to 5 minutes. Now you can unplug the Vera unit from your computer and connect it to the internet.

 For '''UI5:'''

Go to SETUP > Net & Wifi

Click on the "reset to default network settings" button.

[[File:SETUPnetwork.JPG]]

This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

For '''UI4:''' Go to Advanced > Net & Wifi Click on the  "reset to default network settings" button. [[File:UI4 reset.PNG]]

 This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

How to reset to default network settings

2016-01-19T13:50:22Z

George:

How to reset to default network settings on your '''Vera Controller'''

By default Vera automatically configures its network, if you connect it to your router it will automatically connect to it's network. If after plugging Vera into your network, you don't see your Vera on cp.mios.com , please follow these steps to fix your networking:

'''''Note''': For '''Vera edge''' you'll have to replace the 192.168.81.1 IP address with a combination of numbers based on the unit's MAC address. Depending on which firmware version you're on you'll have to set it up like below:''

''MAC address: D4:21:22:FC:BC:9D''

'''''a.''' on firmware version 7.0.12.1 and older (1.7.1598 or older) the IP address Vera Edge can be accessed on will be generated using the last 4 digits in the mac address. For the example above it would be: 192.168.12.29''

'''''b.''' on firmware version newer than 7.0.12.1 (above 1.7.1598) the IP address Vera Edge can be accessed on will be generated using the last 4 characters of the mac address, where the letters are converted to numbers based on their order of the alphabet. For the example above it would be 192.168.23.94''

''This would mean that the PC should have an IP address in the same class as the unit, meaning 192.168.12.100 (for example) for case '''a. '''or 192.168.23.100 (for example) for case '''b.'''''

''

- Put a STATIC IP to your computer.

*In '''Windows 8'''

From the Tiles menu click on "PC Settings"
From the bottom left of the menu select "Control Panel"
Click on "Network and Internet" and then select "Network and Sharing Center"
Click on "Change adapter settings" in the left menu
Right click on the "Ethernet" connection and click on "Properties"
From the list highlight "Internet Protocol Version 4 (TCP/IPv4) and click on the "Properties" button
Check "Use the following IP address:" and fill in the three fields as follows:
IP address: 192.168.81.10
Subnet mask: 255.255.255.0
Default gateway: 192.168.81.1
Click OK
Click Close

*In '''Windows 7'''

Open Control Panel
View by: Large icons -> Network and Sharing Center
View by: Category -> View netork status and tasks
Click on Change adapter settings
Right click on LAN connection to Vera , then click on Properties
Highlight the Internet Protocol Version 4 (TCP/IPv4) item, and click on Properties
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK Again

*In '''Windows XP'''

Open Windows Start menu.
Open Control Panel.
Classic view: Open Network Connections
Category view: Select Network and Internet Connections, and then Network Connections.
Double-click on your the LAN connection to Vera.
Click Properties.
In the General tab, highlight the Internet Protocol (TCP/IP) item, and click Properties.
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK again

*In '''Mac OS X'''

Open the Apple Menu(Top left corner of your screen)
Click System Preferences
Click Network
Click the Locations dropdown and select Edit Locations
Click the plus sign and call your new location "Vera system Troubleshooting"
Select "Ethernet" from the list on the left
Select "Manually" from the Configure IPv4 dropdown
Enter 192.168.81.10 in the IP address field
Enter 255.255.255.0 in the subnet mask field
Enter 192.168.81.1 in the Router field
Hit "Apply"

- Unplug Vera from the power cord

- Unplug all the cables from Vera

- Plug a network cable from your computer into Vera's LAN port

Vera 2 -> eth2 port
Vera 3 -> lan port (port number 1)
Vera Lite -> ethernet port
Vera Edge -> ethernet port

- Plug Vera into the power cord

- Wait it to start

Now open an web browser and type this in the address bar: 192.168.81.1 Now you can see the DASHBOARD page of your Vera unit.

For '''UI7:'''

Go to Settings > Net & Wi-fi Click on the “Reset to default network settings” button.

[[File:Reset network UI7.png]]

 Confirm by clicking the “OK” Button on the pop-up window.

This will reset the unit to default network settings and can take up to 5 minutes. Now you can unplug the Vera unit from your computer and connect it to the internet.

 For '''UI5:'''

Go to SETUP > Net & Wifi

Click on the "reset to default network settings" button.

[[File:SETUPnetwork.JPG]]

This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

For '''UI4:''' Go to Advanced > Net & Wifi Click on the  "reset to default network settings" button. [[File:UI4 reset.PNG]]

 This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

How to reset to default network settings

2016-01-19T13:48:16Z

George:

How to reset to default network settings on your '''Vera Controller'''

By default Vera automatically configures its network, if you connect it to your router it will automatically connect to it's network. If after plugging Vera into your network, you don't see your Vera on cp.mios.com , please follow these steps to fix your networking:

- Put a STATIC IP to your computer.

*In '''Windows 8'''

From the Tiles menu click on "PC Settings"
From the bottom left of the menu select "Control Panel"
Click on "Network and Internet" and then select "Network and Sharing Center"
Click on "Change adapter settings" in the left menu
Right click on the "Ethernet" connection and click on "Properties"
From the list highlight "Internet Protocol Version 4 (TCP/IPv4) and click on the "Properties" button
Check "Use the following IP address:" and fill in the three fields as follows:
IP address: 192.168.81.10
Subnet mask: 255.255.255.0
Default gateway: 192.168.81.1
Click OK
Click Close

*In '''Windows 7'''

Open Control Panel
View by: Large icons -> Network and Sharing Center
View by: Category -> View netork status and tasks
Click on Change adapter settings
Right click on LAN connection to Vera , then click on Properties
Highlight the Internet Protocol Version 4 (TCP/IPv4) item, and click on Properties
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK Again

*In '''Windows XP'''

Open Windows Start menu.
Open Control Panel.
Classic view: Open Network Connections
Category view: Select Network and Internet Connections, and then Network Connections.
Double-click on your the LAN connection to Vera.
Click Properties.
In the General tab, highlight the Internet Protocol (TCP/IP) item, and click Properties.
In the IP address field enter 192.168.81.10
In the subnet mask field enter 255.255.255.0
In the Default gateway field enter 192.168.81.1
Click OK
Click OK again

*In '''Mac OS X'''

Open the Apple Menu(Top left corner of your screen)
Click System Preferences
Click Network
Click the Locations dropdown and select Edit Locations
Click the plus sign and call your new location "Vera system Troubleshooting"
Select "Ethernet" from the list on the left
Select "Manually" from the Configure IPv4 dropdown
Enter 192.168.81.10 in the IP address field
Enter 255.255.255.0 in the subnet mask field
Enter 192.168.81.1 in the Router field
Hit "Apply"

- Unplug Vera from the power cord

- Unplug all the cables from Vera

- Plug a network cable from your computer into Vera's LAN port

Vera 2 -> eth2 port
Vera 3 -> lan port (port number 1)
Vera Lite -> ethernet port
Vera Edge -> ethernet port

- Plug Vera into the power cord

- Wait it to start

Now open an web browser and type this in the address bar: 192.168.81.1 Now you can see the DASHBOARD page of your Vera unit.

'''''Important''': For '''Vera edge''' you'll have to replace the 192.168.81.1 IP address with a combination of numbers based on the unit's MAC address. Depending on which firmware version you're on you'll have to set it up like below: ''

''MAC address: D4:21:22:FC:BC:9D ''

'''''a.''' on firmware version 7.0.12.1 and older (1.7.1598 or older) the IP address Vera Edge can be accessed on will be generated using the last 4 digits in the mac address. For the example above it would be: 192.168.12.29''

'''''b.''' on firmware version newer than 7.0.12.1 (above 1.7.1598) the IP address Vera edge can be accessed on will be generated using the last 4 characters of the mac address, where the letters are converted to numbers based on their order of the alphabet. For the example above it would be 192.168.23.94 ''

''This would mean that the PC should have an IP address in the same class as the unit, meaning 192.168.12.100 (for example) for case '''a. '''or 192.168.23.100 (for example) for case '''b.'''''

For '''UI7:'''

Go to Settings > Net & Wi-fi Click on the “Reset to default network settings” button.

[[File:Reset network UI7.png]]

 Confirm by clicking the “OK” Button on the pop-up window.

This will reset the unit to default network settings and can take up to 5 minutes. Now you can unplug the Vera unit from your computer and connect it to the internet.

 For '''UI5:'''

Go to SETUP > Net & Wifi

Click on the "reset to default network settings" button.

[[File:SETUPnetwork.JPG]]

This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

For '''UI4:''' Go to Advanced > Net & Wifi Click on the  "reset to default network settings" button. [[File:UI4 reset.PNG]]

 This will reset the unit to default network settings and can take up to 5 minutes.

Now you can unplug the Vera unit from your computer and connect it to the internet.

Bridging Multiple Vera

2015-12-21T13:30:05Z

George:

<div class="doc_content"><div class="doc_content">There are several reasons why you might want to have multiple Vera in one home.  For example, you might want a Vera to be physically located next to an alarm panel. You can connect it to the alarm panel with a serial cable. One of the most common reasons is to improve the reliability of Z-Wave devices.  Z-Wave devices work using a 'mesh network'. This means if device a needs to control device b, but they're not in direct range for the wireless radio signal to reach, then other Z-Wave devices in between a and b will act as relays.  However, there are limitations to this, such as a limit to the number of hops a message can make. The signal may not travel through some barriers like brick walls, you may have a 'dead zone' area in your home where there are no nodes or other interference, or you may have separate areas like a main house and a guest house. Z-Wave is quite reliable when you have several Z-Wave devices in a small area so the number of hops is kept to a minimum.  You may want to put one Vera in the main house, another in the guest house, or divide the main house in 2 halves with a Vera right in the middle of each half so that most Z-Wave devices are in direct range of the Vera.  There is no limit to the number of Vera you can have in your home and, as long as they are all connected to the same home LAN (ie Ethernet network), multiple Vera's can be bridged so they act as one. You'll still need to look out for the maximum number of supported devices per controller, so you won't experience performance related issues. More details on : [http://wiki.mios.com/index.php/Comparison_of_Vera_units http://wiki.mios.com/index.php/Comparison_of_Vera_units] The way bridging works is that you go to one Vera and "import" or add the other one.  So, Vera #1 can import the devices from Vera #2 and Vera #3, and that way on Vera #1 you will see all devices from all 3 Vera systems together as though it was one system.  You can create scenes and events on Vera #1 that control devices from all 3 Vera, and you can attach events to those scenes that are triggered by devices on all 3 Vera systems.  When you control Vera #1 from the web interface or a mobile phone app, you will have control over all devices from all 3 Veras. There are no limitations on importing other Vera systems.  So, technically if you had 3 systems, #1 could import the devices on #2 and #3, and #3 could import the devices on #1 and #2, and in that way both #1 and #3 would have all the devices.  This, however, might lead to confusion, particularly if you have scenes and events on both #1 and #3. You might see things happening and not know which Vera is actually doing what.  To keep it simple, the best solution is to generally think of one Vera as the "Master" and have it import the devices from all the other "Slaves", and then create scenes and events only on the "Master".  You won't need to do anything with the "Slaves" except include the devices and modify the device settings for those devices. On the "Master", the 'setup' icon on the dashboard  will only let you change settings for the Master's native devices.  To change settings for a device, such as Z-Wave variables, you will need to use whatever Vera included those devices natively. To import the devices from another Vera: 
*From the Devices tab press on the "Add Device" button
*Under 'Additional Devices' scroll down and click on "UPnP devices"
*Check the checkbox "Scan for UPnP devices" and press on "Next" and press on 'Exit'
*Wait 10 minutes for Vera to scan for other Vera units in the network
*Follow the steps above and now you should be able to view the units in your network
*Click on the 'Add' button to addthe Vera system that you want to be able to control from this Vera
*You're done. You've successfully bridged two Vera units

[[File:Bridge ui7 1.png|left|Bridge ui7 1.png]]

[[File:Bridge ui7 2.png|left|Bridge ui7 2.png]]

[[File:Bridge ui7 3.png|left|Bridge ui7 3.png]]

[[File:Bridge ui7 4.png|left|Bridge ui7 4.png]]
</div></div>

Bridging Multiple Vera

2015-12-21T13:26:55Z

George:

Bridging Multiple Vera

2015-12-21T13:06:14Z

George:

<div class="doc_content"><div class="doc_content">There are several reasons why you might want to have multiple Vera in one home.  For example, you might want a Vera to be physically located next to an alarm panel. You can connect it to the alarm panel with a serial cable. One of the most common reasons is to improve the reliability of Z-Wave devices.  Z-Wave devices work using a 'mesh network'. This means if device a needs to control device b, but they're not in direct range for the wireless radio signal to reach, then other Z-Wave devices in between a and b will act as relays.  However, there are limitations to this, such as a limit to the number of hops a message can make. The signal may not travel through some barriers like brick walls, you may have a 'dead zone' area in your home where there are no nodes or other interference, or you may have separate areas like a main house and a guest house. Z-Wave is quite reliable when you have several Z-Wave devices in a small area so the number of hops is kept to a minimum.  You may want to put one Vera in the main house, another in the guest house, or divide the main house in 2 halves with a Vera right in the middle of each half so that most Z-Wave devices are in direct range of the Vera.  There is no limit to the number of Vera you can have in your home and, as long as they are all connected to the same home LAN (ie Ethernet network), multiple Vera's can be bridged so they act as one. You'll still need to look out for the maximum number of supported devices per controller, so you won't experience performance related issues. More details on : [http://wiki.mios.com/index.php/Comparison_of_Vera_units http://wiki.mios.com/index.php/Comparison_of_Vera_units] The way bridging works is that you go to one Vera and "import" or add the other one.  So, Vera #1 can import the devices from Vera #2 and Vera #3, and that way on Vera #1 you will see all devices from all 3 Vera systems together as though it was one system.  You can create scenes and events on Vera #1 that control devices from all 3 Vera, and you can attach events to those scenes that are triggered by devices on all 3 Vera systems.  When you control Vera #1 from the web interface or a mobile phone app, you will have control over all devices from all 3 Veras. There are no limitations on importing other Vera systems.  So, technically if you had 3 systems, #1 could import the devices on #2 and #3, and #3 could import the devices on #1 and #2, and in that way both #1 and #3 would have all the devices.  This, however, might lead to confusion, particularly if you have scenes and events on both #1 and #3. You might see things happening and not know which Vera is actually doing what.  To keep it simple, the best solution is to generally think of one Vera as the "Master" and have it import the devices from all the other "Slaves", and then create scenes and events only on the "Master".  You won't need to do anything with the "Slaves" except include the devices and modify the device settings for those devices. On the "Master", the 'setup' icon on the dashboard  will only let you change settings for the Master's native devices.  To change settings for a device, such as Z-Wave variables, you will need to use whatever Vera included those devices natively. To import the devices from another Vera: 
*From the Devices tab press on the "Add Device" button

[[File:Bridge ui7 1.png|left]]

*Under 'Additional Devices' scroll down and click on "UPnP devices"
*Check the checkbox "Scan for UPnP devices" and press on "Next" and press on 'Exit'

[[File:Bridge ui7 2.png|left|Bridge ui7 2.png]]

[[File:Bridge ui7 3.png|left|Bridge ui7 3.png]]

*Wait 10 minutes for Vera to scan for other Vera units in the network
*Follow the steps above and now you should be able to view the units in your network
*Click on the 'Add' button to addthe Vera system that you want to be able to control from this Vera

[[File:Bridge ui7 4.png|left|Bridge ui7 4.png]]

*You're done. You've successfully bridged two Vera units
</div></div>

Bridging Multiple Vera

2015-12-21T13:05:24Z

George:

<div class="doc_content"><div class="doc_content">There are several reasons why you might want to have multiple Vera in one home.  For example, you might want a Vera to be physically located next to an alarm panel. You can connect it to the alarm panel with a serial cable. One of the most common reasons is to improve the reliability of Z-Wave devices.  Z-Wave devices work using a 'mesh network'. This means if device a needs to control device b, but they're not in direct range for the wireless radio signal to reach, then other Z-Wave devices in between a and b will act as relays.  However, there are limitations to this, such as a limit to the number of hops a message can make. The signal may not travel through some barriers like brick walls, you may have a 'dead zone' area in your home where there are no nodes or other interference, or you may have separate areas like a main house and a guest house. Z-Wave is quite reliable when you have several Z-Wave devices in a small area so the number of hops is kept to a minimum.  You may want to put one Vera in the main house, another in the guest house, or divide the main house in 2 halves with a Vera right in the middle of each half so that most Z-Wave devices are in direct range of the Vera.  There is no limit to the number of Vera you can have in your home and, as long as they are all connected to the same home LAN (ie Ethernet network), multiple Vera's can be bridged so they act as one. You'll still need to look out for the maximum number of supported devices per controller, so you won't experience performance related issues. More details on : [http://wiki.mios.com/index.php/Comparison_of_Vera_units http://wiki.mios.com/index.php/Comparison_of_Vera_units] The way bridging works is that you go to one Vera and "import" or add the other one.  So, Vera #1 can import the devices from Vera #2 and Vera #3, and that way on Vera #1 you will see all devices from all 3 Vera systems together as though it was one system.  You can create scenes and events on Vera #1 that control devices from all 3 Vera, and you can attach events to those scenes that are triggered by devices on all 3 Vera systems.  When you control Vera #1 from the web interface or a mobile phone app, you will have control over all devices from all 3 Veras. There are no limitations on importing other Vera systems.  So, technically if you had 3 systems, #1 could import the devices on #2 and #3, and #3 could import the devices on #1 and #2, and in that way both #1 and #3 would have all the devices.  This, however, might lead to confusion, particularly if you have scenes and events on both #1 and #3. You might see things happening and not know which Vera is actually doing what.  To keep it simple, the best solution is to generally think of one Vera as the "Master" and have it import the devices from all the other "Slaves", and then create scenes and events only on the "Master".  You won't need to do anything with the "Slaves" except include the devices and modify the device settings for those devices. On the "Master", the 'setup' icon on the dashboard  will only let you change settings for the Master's native devices.  To change settings for a device, such as Z-Wave variables, you will need to use whatever Vera included those devices natively. To import the devices from another Vera: 
*From the Devices tab press on the "Add Device" button

*Under 'Additional Devices' scroll down and click on "UPnP devices"
*Check the checkbox "Scan for UPnP devices" and press on "Next" and press on 'Exit'

[[File:Bridge ui7 2.png|left|Bridge ui7 2.png]]

[[File:Bridge ui7 3.png|left|Bridge ui7 3.png]]

*Wait 10 minutes for Vera to scan for other Vera units in the network
*Follow the steps above and now you should be able to view the units in your network
*Click on the 'Add' button to addthe Vera system that you want to be able to control from this Vera

[[File:Bridge ui7 4.png|left|Bridge ui7 4.png]]

*You're done. You've successfully bridged two Vera units
</div></div>

File:Bridge ui7 4.png

2015-12-21T13:04:27Z

George: Bridge_UI7_4

Bridge_UI7_4

File:Bridge ui7 3.png

2015-12-21T12:52:32Z

George: Bridge_UI7_3

Bridge_UI7_3

File:Bridge ui7 2.png

2015-12-21T12:52:20Z

George: Bridge_UI7_2

Bridge_UI7_2

File:Bridge ui7 1.png

2015-12-21T12:52:06Z

George: Bridge_UI7_1

Bridge_UI7_1

Bridging Multiple Vera

2015-12-21T12:51:25Z

George: Created page with "<div class="doc_content"><div class="doc_content">There are several reasons why you might want to have multiple Vera in one home.  For example, you might w..."

<div class="doc_content"><div class="doc_content">There are several reasons why you might want to have multiple Vera in one home.  For example, you might want a Vera to be physically located next to an alarm panel. You can connect it to the alarm panel with a serial cable. One of the most common reasons is to improve the reliability of Z-Wave devices.  Z-Wave devices work using a 'mesh network'. This means if device a needs to control device b, but they're not in direct range for the wireless radio signal to reach, then other Z-Wave devices in between a and b will act as relays.  However, there are limitations to this, such as a limit to the number of hops a message can make. The signal may not travel through some barriers like brick walls, you may have a 'dead zone' area in your home where there are no nodes or other interference, or you may have separate areas like a main house and a guest house. Z-Wave is quite reliable when you have several Z-Wave devices in a small area so the number of hops is kept to a minimum.  You may want to put one Vera in the main house, another in the guest house, or divide the main house in 2 halves with a Vera right in the middle of each half so that most Z-Wave devices are in direct range of the Vera.  There is no limit to the number of Vera you can have in your home and, as long as they are all connected to the same home LAN (ie Ethernet network), multiple Vera's can be bridged so they act as one. You'll still need to look out for the maximum number of supported devices per controller, so you won't experience performance related issues. More details on : http://wiki.mios.com/index.php/Comparison_of_Vera_units The way bridging works is that you go to one Vera and "import" or add the other one.  So, Vera #1 can import the devices from Vera #2 and Vera #3, and that way on Vera #1 you will see all devices from all 3 Vera systems together as though it was one system.  You can create scenes and events on Vera #1 that control devices from all 3 Vera, and you can attach events to those scenes that are triggered by devices on all 3 Vera systems.  When you control Vera #1 from the web interface or a mobile phone app, you will have control over all devices from all 3 Veras. There are no limitations on importing other Vera systems.  So, technically if you had 3 systems, #1 could import the devices on #2 and #3, and #3 could import the devices on #1 and #2, and in that way both #1 and #3 would have all the devices.  This, however, might lead to confusion, particularly if you have scenes and events on both #1 and #3. You might see things happening and not know which Vera is actually doing what.  To keep it simple, the best solution is to generally think of one Vera as the "Master" and have it import the devices from all the other "Slaves", and then create scenes and events only on the "Master".  You won't need to do anything with the "Slaves" except include the devices and modify the device settings for those devices. On the "Master", the 'setup' icon on the dashboard  will only let you change settings for the Master's native devices.  To change settings for a device, such as Z-Wave variables, you will need to use whatever Vera included those devices natively. To import the devices from another Vera: 
*From the Devices tab press on the "Add Device" button
*Under 'Additional Devices' scroll down and click on "UPnP devices"
*Check the checkbox "Scan for UPnP devices" and press on "Next" and press on 'Exit'
*Wait 10 minutes for Vera to scan for other Vera units in the network
*Follow the steps above and now you should be able to view the units in your network
*Click on the 'Add' button to addthe Vera system that you want to be able to control from this Vera
*You're done. You've successfully bridged two Vera units
</div></div>

Aeon HomeEnergyMonitor

2015-11-10T12:37:12Z

George:

= Aeon HomeEnergyMonitor First Edition =

If you have version 3.58 or later of the HEM firmware (unrelated to Vera's firmware), it supports the ability to report in real-time whenever there is a change in the energy consumption.  It generates a report for Vera whenever there is a change.

For versions 3.57 and lower, the only way to get real time energy reporting was to have the HEM send Vera reports constantly, whether or not there was a change.  This required powering the HEM with USB power.  So we recommend using the USB port on the HEM to upgrade to firmware 3.58 or newer, as per the instructions on aeon-labs.com

There have been reported issues with HEM firmware less than 3.61. The latest that we know about is 3.67 and you can download it below. Please make sure to choose the right frequency for your own device.

US version: [http://wiki.micasaverde.com/images/f/f6/Home_Energy_Meter_V3_67_US.zip HEM367]

AU version - 200 A: [http://wiki.micasaverde.com/images/4/45/Home_Energy_Meter_V3_67_AU_200A.zip HEM367]

EU version - 60 A :  [http://wiki.micasaverde.com/images/3/37/Home_Energy_Meter_V3_67_EU_60A.zip HEM367]

EU version - 100 A: [http://wiki.micasaverde.com/images/2/2a/Home_Energy_Meter_V3_67_EU_100A.zip HEM367]

EU version - 200 A: [http://wiki.micasaverde.com/images/5/5e/Home_Energy_Meter_V3_67_EU_200A.zip HEM367]

== Inclusion ==

When including the HEM to the Vera unit you should have the HEM powered with the USB AC adapter.

== Note ==

You need to have it plugged in through the USB AC adapter for it to report the KWH accurately, because when it is battery operated it sleeps most of the time and it cannot accurately track KWH. 

= Aeotec HomeEnergyMonitor 2nd edition =

The Aeotec Home Energy Monitor can be found in multiple variations on the market with one, two or three measuring clamps. It's always a good practice to update the software to the latest version by using the tool from the manuafcturers [http://aeotec.com/z-wave-home-energy-measure/1262-hem-firmware.html support page.]

== Configuring the Aeotec HEM 2nd edition ==

Once the HEM will be paired with your controller it will display either two, three or four devices on the Vera interface. One will be the master device, and one child device for each clamp connected to the HEM. Below we'll check the configuration settings for the two and three clamp versions of the Aeotec HEM.

The configuration settings are done on the configuration panel of the parent device under the Device Options page. Here you'll need to adjust the following configuration parameters :

*for the two clamp edition:

Parameter 101 [4 byte dec]: 6927 (report kwh and watt on clamp 1 2 and total readings)

Parameter 111 [4 byte dec]: 240 (report every 240 seconds)

Parameter 102 and 103 [4 byte dec] set to 0 If any of the parameters are missing you can add them by pressing "Add configuration settings" button.

*for the three clamp edition:

Parameter 101 [4 byte dec]: 16143 (3 clamps to report kwh and watt)

Parameter 111 [4 byte dec]: 240 (report every 240 seconds)

Parameter 102 and 103 [4 byte dec] set to 0 If some of the parameters are missing one can add them by pressing "Add configuration settings" button.

Aeon HomeEnergyMonitor

2015-11-10T12:30:11Z

George:

= Aeon HomeEnergyMonitor First Edition =

If you have version 3.58 or later of the HEM firmware (unrelated to Vera's firmware), it supports the ability to report in real-time whenever there is a change in the energy consumption.  It generates a report for Vera whenever there is a change.

For versions 3.57 and lower, the only way to get real time energy reporting was to have the HEM send Vera reports constantly, whether or not there was a change.  This required powering the HEM with USB power.  So we recommend using the USB port on the HEM to upgrade to firmware 3.58 or newer, as per the instructions on aeon-labs.com

There have been reported issues with HEM firmware less than 3.61. The latest that we know about is 3.67 and you can download it below. Please make sure to choose the right frequency for your own device.

US version: [http://wiki.micasaverde.com/images/f/f6/Home_Energy_Meter_V3_67_US.zip HEM367]

AU version - 200 A: [http://wiki.micasaverde.com/images/4/45/Home_Energy_Meter_V3_67_AU_200A.zip HEM367]

EU version - 60 A :  [http://wiki.micasaverde.com/images/3/37/Home_Energy_Meter_V3_67_EU_60A.zip HEM367]

EU version - 100 A: [http://wiki.micasaverde.com/images/2/2a/Home_Energy_Meter_V3_67_EU_100A.zip HEM367]

EU version - 200 A: [http://wiki.micasaverde.com/images/5/5e/Home_Energy_Meter_V3_67_EU_200A.zip HEM367]

== Inclusion ==

When including the HEM to the Vera unit you should have the HEM powered with the USB AC adapter.

== Note ==

You need to have it plugged in through the USB AC adapter for it to report the KWH accurately, because when it is battery operated it sleeps most of the time and it cannot accurately track KWH. 

= Aeotec HomeEnergyMonitor 2nd edition =

== Configuring the Aeotec HEM 2nd edition ==

The Aeotec Home Energy Monitor can be found in multiple variations on the market with one, two or three measuring clamps. It's always a good practice to update the software to the latest version by using the tool from the manuafcturers [http://aeotec.com/z-wave-home-energy-measure/1262-hem-firmware.html support page.]

Once the HEM will be paired with your controller it will display either two, three or four devices on the Vera interface. One will be the master device, and one child device for each clamp connected to the HEM. Below we'll check the configuration settings for the two and three clamp versions of the Aeotec HEM.

The configuration settings are done on the configuration panel of the parent device under the Device Options page. Here you'll need to adjust the following configuration parameters :

*for the two clamp edition:

Parameter 101 [4 byte dec]: 6927 (report kwh and watt on clamp 1 2 and total readings)

Parameter 111 [4 byte dec]: 240 (report every 240 seconds)

Parameter 102 and 103 [4 byte dec] set to 0 If any of the parameters are missing you can add them by pressing "Add configuration settings" button.

*for the three clamp edition:

Parameter 101 [4 byte dec]: 16143 (3 clamps to report kwh and watt)

Parameter 111 [4 byte dec]: 240 (report every 240 seconds)

Parameter 102 and 103 [4 byte dec] set to 0 If some of the parameters are missing one can add them by pressing "Add configuration settings" button.

Logon Vera SSH

2015-10-21T08:56:41Z

George: /* Prerequisites */

[[Category:User Instructions]]
[[Category:How To]]
'''HOWTO log on to your Vera using SSH.'''

==Prerequisites==
* Vera hardware
* For Windows based clients, an open-source SSH application to access your Vera, for instance PuTTY which can be found here: [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]
* For MAC clients you could use "Rbrowser" to be found here [http://www.openssh.com] or here [http://www.rbrowser.com] 
* Linux based clients have built-in SSH support.
* Root password, to be found at the bottom of your Vera (also your initial WiFi security key)

==Introduction==
For many operations you need access to the shell of your Vera. For this reason Vera supports SSH (Secure SHell) on port 22. 
Getting access to your Vera is not something that is easy at first. 
Therefore you can follow these instructions in support of other How To's to get root access to your Vera's shell. 

==Instructions==
===Windows===
*After you have downloaded PuTTY, run it directly. 

To get shell acces to your Vera do this; 
1. Under <Host Name> type the IP address of your Vera (for example: 192.168.1.24), leave Port number 22 alone, if needed, change connection type to SSH (default) and click <Open>. 
2. At Login type: 
''root''
hit <Enter> 

The password you need is located on the label under your Vera unit assigned to "WiFI Pass". 
3. Type the password and hit <Enter>

===Mac & Linux===
1. Open a "Terminal". 
2. type:
''ssh root@192.168.1.24''

-----

You now should have access to your Vera's Root directory and it should display something like this: 

'''BusyBox v1.15.3 (2010-06-10 18:19:49 PDT) built-in shell (ash''') 
'''Enter 'help' for a list of built-in commands.'''
---------------------------------------------------
*** MiOS LTD. ( www.mios.com ) ***
*** ***
*** WARNING : ***
*** Any changes made to the system without ***
*** guidance from MiOS support will VOID ***
*** your future Support requests ***
---------------------------------------------------
'''root@MiOS_xxxxx:~#'''

---------------------------------------------------

(the xxxxx will be your Vera's name) 
From here you can use any shell command provided in other How To's or forum items.

==Can't find the root password?==

On Vera Lite's, the root password isn't printed on the bottom. So you need to access to the 'Tech Support' settings. Depending on your UI version, this is either under the Advanced tab, the Settings tab, or the Account tab. There will be an 'enable' button. Click that to turn on the tech support service. You will see a message like this:

Tech support full control enabled, access code 3000000-436969

The first number is your serial number, which is always printed on the bottom. The second number is a temporary password created for a user called "remote". So, follow the same login instructions, but, instead of typing root for the login, type remote. And instead of using the normal password, use that temporary password, 436969 in this case. Once you have gotten in to the console, you can see the actual root password using this command: nvram show | grep pass

You'll see something like this:

root@MiOS_30000000:~# nvram show | grep pass
vera_wifipass=shade83forest

So in this case, shade83forest, is the actual root password. Write it down, and from now on login as 'root' as explained earlier, and use that password. The temporary password for the remote user will only be valid for 24 hours or until you click 'Disable it' on the tech support page.

==References==
please find more info here; 
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html 
http://www.openssh.com/ 
http://www.rbrowser.com/

Firmware Flash VeraLite

2015-10-09T07:38:44Z

George: /* Prerequisites */

== Prerequisites ==

*YOU NEED TO FOLLOW THIS TUTORIAL ONLY IF YOUR VERA UNIT IS NOT BOOTING ANYMORE, THIS MEANS THAT WHILE BEING CONNECTED TO THE INTERNET THE POWER (BLUE) LED IS BLINKING AND NO OTHER LEDS ARE LIGHT UP/BLINKING FOR MORE THAN 30 MINUTES !
*The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications should be run in Windows XP SP3 compatibility mode. 

*Make sure your computer is connected to your network through an Ethernet cable. Make sure to disable any WIRELESS/BLUETOOTH/other networking interfaces before continuing. 

NOTE: Failure to disable your wireless network before continuing could result in an unusable unit.

*Please deactivate all Firewall and Antivirus software which is running during the upgrade process.

Note: If you are running Windows Vista/7 please follow the next guide to enable the TFTP Client and then continue with the re-flash steps. Guide: http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

=== If the restoration utility does not work on Windows 7 ===

Please note that this is only available for Windows 7 Professional, Enterprise and Ultimate editions.

*If the restoration utility does not work on Windows 7 you should use the Windows Xp Mode, offered for free by Microsoft. To install it, you have to go to this page [http://www.microsoft.com/en-us/download/details.aspx?id=8002 Windows Xp Mode] which will walk you through the entire process. 
*After this finishes and you open up the Windows Xp Mode Virtual Machine, you should go to the Menu, select Tools -> Settings, select Networking and for adapter 1 make sure to select your LAN card, the one that will be connected directly into any of LAN ports of Vera.
*Afterwards you will have to open Internet explorer inside the virtual machine, access [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera3 this page] and download the Firmware flash utilities inside the virtual machine.
*On Windows 7 change the Local Area Connection settings to use the static IP and connect the Vera unit to your computer as explained at the begining of this page, then open the Firmware Flash utility inside the Virtual machine and you should be able to continue the Firmware Flash process.

== Files to download before you start the restoration process ==

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera Lite Firmware Recovery Tool]
*[http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware]

==  Setup your computer to connect to Vera Lite     ==

*Computer IP: 192.168.0.100
*Subnet Mask: 255.255.255.0
*Default Gateway: 192.168.0.1 

== Begin the process for flashing the firmware ==

#Use a network cable (CAT5e) and plug the cable from your PC into Vera's '''LAN port'''.  
#Unplug Vera from the power cord.
#Holding down Vera's '''RESET button''' whilst pluging in the power cord back in. Wait about 3s after you plugged the power cord back with the Reset button pressed. When releasing the Reset button, the '''Z-Wave LED''' should be blinking.  
#If the '''Z-Wave LED''' is not blinking, turn Vera off and try again.
#Start [http://download.mios.com/firmware/vera3_recovery_tool.zip Vera Lite Firmware Recovery Tool].
#Click "Browse target" button.
#Vera should appear in targets list.
#Click on "*UN*checkPID" radiobox
#Select "EraseALL" from dropdown box. (<- this will update your unit bootloader also)
#Click the [Files] button.
#Download the file: [http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware] and save it on your computer.
#Select the file [http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware]
#Click the [Open] button to get the file.
#Click on the [OK] button on the BIN File Information dialog box.
#Click on the [Upgrade] button. File will be flashed, and you will see a dialog box saying success - close Upgrade Tool.
#Put your computer's IP to 192.168.81.100, Subnet Mask: 255.255.255.0
#Please wait until Vera ''automatically'' reboots and the '''Network'''''' led''' starts double blinking or it's solid (this can take 10 to 30 minutes).  
#When you see the Z-Wave led solid, you are done. 

== To do after the restoration has finished ==

*If you have your computer connected to the LAN port of Vera, open http://192.168.81.1 and you will see Vera's UI.  
*If you already disconnected it from the computer and connected the WAN cable coming from your main Router/ADSL modem, the Network light on front will go solid, meaning Vera is connected to the internet. 

Dont forget to update your Vera to the latest available firmware. This is explained here: [[Update Firmware]]

Next, if you also want to restore everything else in Vera, restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

== References ==

[http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware] http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera Lite Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

[[Category:User_Instructions]] [[Category:How_To]]

Firmware Flash VeraLite

2015-10-09T07:38:23Z

George: /* Prerequisites */

== Prerequisites ==

*YOU NEED TO FOLLOW THIS TUTORIAL ONLY IF YOUR VERA UNIT IS NOT BOOTING ANYMORE, THIS MEANS THAT WHILE BEING CONNECTED TO THE INTERNET THE POWER LED IS BLINKING AND NO OTHER LEDS ARE LIGHT UP/BLINKING FOR MORE THAN 30 MINUTES !
*The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications should be run in Windows XP SP3 compatibility mode. 

*Make sure your computer is connected to your network through an Ethernet cable. Make sure to disable any WIRELESS/BLUETOOTH/other networking interfaces before continuing. 

NOTE: Failure to disable your wireless network before continuing could result in an unusable unit.

*Please deactivate all Firewall and Antivirus software which is running during the upgrade process.

Note: If you are running Windows Vista/7 please follow the next guide to enable the TFTP Client and then continue with the re-flash steps. Guide: http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/

=== If the restoration utility does not work on Windows 7 ===

Please note that this is only available for Windows 7 Professional, Enterprise and Ultimate editions.

*If the restoration utility does not work on Windows 7 you should use the Windows Xp Mode, offered for free by Microsoft. To install it, you have to go to this page [http://www.microsoft.com/en-us/download/details.aspx?id=8002 Windows Xp Mode] which will walk you through the entire process. 
*After this finishes and you open up the Windows Xp Mode Virtual Machine, you should go to the Menu, select Tools -> Settings, select Networking and for adapter 1 make sure to select your LAN card, the one that will be connected directly into any of LAN ports of Vera.
*Afterwards you will have to open Internet explorer inside the virtual machine, access [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera3 this page] and download the Firmware flash utilities inside the virtual machine.
*On Windows 7 change the Local Area Connection settings to use the static IP and connect the Vera unit to your computer as explained at the begining of this page, then open the Firmware Flash utility inside the Virtual machine and you should be able to continue the Firmware Flash process.

== Files to download before you start the restoration process ==

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera Lite Firmware Recovery Tool]
*[http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware]

==  Setup your computer to connect to Vera Lite     ==

*Computer IP: 192.168.0.100
*Subnet Mask: 255.255.255.0
*Default Gateway: 192.168.0.1 

== Begin the process for flashing the firmware ==

#Use a network cable (CAT5e) and plug the cable from your PC into Vera's '''LAN port'''.  
#Unplug Vera from the power cord.
#Holding down Vera's '''RESET button''' whilst pluging in the power cord back in. Wait about 3s after you plugged the power cord back with the Reset button pressed. When releasing the Reset button, the '''Z-Wave LED''' should be blinking.  
#If the '''Z-Wave LED''' is not blinking, turn Vera off and try again.
#Start [http://download.mios.com/firmware/vera3_recovery_tool.zip Vera Lite Firmware Recovery Tool].
#Click "Browse target" button.
#Vera should appear in targets list.
#Click on "*UN*checkPID" radiobox
#Select "EraseALL" from dropdown box. (<- this will update your unit bootloader also)
#Click the [Files] button.
#Download the file: [http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware] and save it on your computer.
#Select the file [http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware]
#Click the [Open] button to get the file.
#Click on the [OK] button on the BIN File Information dialog box.
#Click on the [Upgrade] button. File will be flashed, and you will see a dialog box saying success - close Upgrade Tool.
#Put your computer's IP to 192.168.81.100, Subnet Mask: 255.255.255.0
#Please wait until Vera ''automatically'' reboots and the '''Network'''''' led''' starts double blinking or it's solid (this can take 10 to 30 minutes).  
#When you see the Z-Wave led solid, you are done. 

== To do after the restoration has finished ==

*If you have your computer connected to the LAN port of Vera, open http://192.168.81.1 and you will see Vera's UI.  
*If you already disconnected it from the computer and connected the WAN cable coming from your main Router/ADSL modem, the Network light on front will go solid, meaning Vera is connected to the internet. 

Dont forget to update your Vera to the latest available firmware. This is explained here: [[Update Firmware]]

Next, if you also want to restore everything else in Vera, restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

== References ==

[http://download.mios.com/firmware/os_rt3662/openwrt-ramips-rt3883-veralite-squashfs-full-81.bin Vera Lite Recovery Firmware] http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera Lite Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

[[Category:User_Instructions]] [[Category:How_To]]

Networking Setup

2015-07-14T07:23:44Z

George: Reverted edits by George (talk) to last revision by Mcvchris

[[Category:User Instructions]]
[[Category:Troubleshooting]]
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 (does not apply to Vera 3) ==

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]]