MiOS - User contributions [en]

Luup Requests

2014-03-20T23:28:25Z

Mcvdennis: /* action */

[[Category:Development]]
In addition to sending requests using standard UPnP, you can also do most things using a simple HTTP requests. Use the built-in URL <tt>data_request</tt>, and pass the following on the URL:
*<tt>id</tt> the id of the request (prior to 15 Oct 2010 all requests had an lu_ in front, which is now optional),
*<tt>output_format</tt> the format in which you want a response as <tt>json</tt>, <tt>xml</tt> or <tt>text</tt>.
Not all requests support all <tt>output_format</tt> options.

Here is the list of requests:

==user_data==

Example: http://ip_address:3480/data_request?id=user_data&output_format=xml

This returns the configuration data for Vera, which is a list of all devices and the UPnP variables which are persisted between resets as well as rooms, names, and other data the user sets as part of the configuration.

==status==
This returns the current status for all devices including all the current UPnP variables and the status of any active jobs.

Examples:
* http://ip_address:3480/data_request?id=status&output_format=xml
Or for a specific device:
* http://ip_address:3480/data_request?id=status&output_format=xml&UDN=uuid:4d494342-5342-5645-0002-000000000002
* http://ip_address:3480/data_request?id=status&output_format=xml&DeviceNum=6

==sdata==

This is an abbreviated form of [[#user_data|user_data]] and [[#status|status]] (sdata = ''summary data''). It allows a user interface that is only worried about control, and not detailed configuration, to get a summary of the data that would normally be presented to the user and to monitor the changes. See [[UI_Simple]] for a walkthrough.

Examples:
* http://ip_address:3480/data_request?id=sdata
* http://ip_address:3480/data_request?id=sdata&output_format=xml

==actions==

==device==

Example: http://ip_address:3480/data_request?id=device&action=rename&device=5&name=Chandalier&room=3

Example: http://ip_address:3480/data_request?id=device&action=rename&device=5&name=Chandalier&room=Garage

Example: http://ip_address:3480/data_request?id=device&action=delete&device=5

This renames or deletes a device. Use action=rename or action=delete. For rename, you can optionally assign a room by passing either the ID or the name.

---old---
This returns all the XML with all the UPNP device description documents. Use: http://ip_address:3480/data_request?id=device&output_format=xml&DeviceNum=x or &UDN=y to narrow it down. Then when you see the service URL's, like <SCPDURL>/luvd/S_HVAC_UserOperatingMode1.xml</SCPDURL>, you can view them with: http://ip_address:3480/luvd/S_HVAC_UserOperatingMode1.xml
---end old---

==scene==

Example: http://ip_address:3480/data_request?id=scene&action=record

Example: http://ip_address:3480/data_request?id=scene&action=pause&seconds=y

Example: http://ip_address:3480/data_request?id=scene&action=stoprecord

Example: http://ip_address:3480/data_request?id=scene&action=listrecord

Example: http://ip_address:3480/data_request?id=scene&action=deleterecord&number=x

Example: http://ip_address:3480/data_request?id=scene&action=saverecord&name=whatever&room=X

Example: http://ip_address:3480/data_request?id=scene&action=rename&scene=5&name=Chandalier&room=Garage

Example: http://ip_address:3480/data_request?id=scene&action=delete&scene=5

Example: http://ip_address:3480/data_request?id=scene&action=create&json=[valid json data]

Example: http://ip_address:3480/data_request?id=scene&action=list&scene=5

This creates, renames, or deletes a scene depending on the action.

Recording a scene means whatever actions come in after sending the 'record' will be saved into an internal buffer. listrecord shows what's recorded so far. pause adds a pause. deleterecord deletes some action in the internal buffer. When deleting, for number=x, use the same 'id' in listrecord. saverecord takes the internal buffer, the recorded macro, and saves it as an actual scene.

To create a scene by hand, rather than recording it, use 'create'. When using the 'create' command json must be valid JSON for a scene as documented in [[Scene_Syntax]]. The name, room and optional id (if you're overwriting an existing scene) are passed in the json, so nothing is on the command line except the json. Because the json data can be long it is recommended to send it as an http POST instead of GET with the data passed with the name "json"

list returns the JSON data for an existing scene.

==room==

Example: http://ip_address:3480/data_request?id=room&action=create&name=Kitchen

Example: http://ip_address:3480/data_request?id=room&action=rename&room=5&name=Garage

Example: http://ip_address:3480/data_request?id=room&action=delete&room=5

This creates, renames, or deletes a room depending on the action. To rename or delete a room you must pass the room id for the room=.

==file==
Returns the contents of a file in '''/etc/cmh''' or '''/etc/cmh-ludl'''. Has one parameter, <tt>parameters</tt>, which is the name of the file.

Example: http://ip_address:3480/data_request?id=file&parameters=D_BinaryLight1.xml

==lua==

== action ==

Sends a UPnP action.

'''Examples:'''

* Turn off a light:
http://ip_address:3480/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1

* Set a dimmable light to 30%:
http://ip_address:3480/data_request?id=action&output_format=json&DeviceNum=7&serviceId=urn:upnp-org:serviceId:Dimming1&action=SetLoadLevelTarget&newLoadLevelTarget=30

* Run a scene:
http://ip_address:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=<SceneNum>

* Install a plugin:
http://ip_address:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=<PluginNum>

==variableset==

http://ip_address:3480/data_request?id=variableset&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=Status&Value=1

If you leave off the DeviceNum and serviceID, then this sets a top-level json tag called "Variable" with the value.

==variableget==

http://ip_address:3480/data_request?id=variableget&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=Status

If you leave off the DeviceNum and serviceID, then this gets a top-level json tag called "Variable".

==reload==

Resets the Luup engine with any new configuration settings.

Example: http://ip_address:3480/data_request?id=reload

==alive==

Return OK if the engine is running.

==finddevice==

Returns the '''device number''', '''UDN''' and '''device type''' of the first device that matches any or all the parameters passed on the URL: <tt>devtype</tt>, <tt>ip</tt>, <tt>devid</tt>, where <tt>devid</tt> is the ''altid'' of the device. Or instead of <tt>devid</tt>, pass '''<tt>devnum</tt>''' and it will find the device with that number.

Example: http://ip_address:3480/data_request?id=finddevice&devid=6

==resync==

ReSync's all the devices, rooms, users, sections with event servers and returns OK

==wget==

Returns the contents of the URL you pass in the "url" argument. Optionally append "user" and "pass" arguments for http authentication, and "timeout" to specify the maximum time to wait in seconds.

==iprequests==

Returns the recent IP requests in order by most recent first, including information about devices in use and if the IP is blacklisted (ignored by the plug and play mechanism). Optionally append '''<tt>timeout</tt>''' to specify the oldest IP request in seconds.

Examples:
* This returns the devices which showed up on the network in the past hour:
http://ip_address:3480/data_request?id=iprequests&timeout=3600
* This returns the devices which showed up on the network in the last 24 hours:
http://ip_address:3480/data_request?id=iprequests&timeout=86400

==blacklistip==

Append "ip" to the URL, and optionally "remove=1" to add (or remove) the IP to the blacklist so plug and play IP devices won't be added.

Not implemented yet!

==live_energy_usage==

For backward compatibility, it reports the current energy usage in a tab delimited format.

Example: http://ip_address:3480/data_request?id=live_energy_usage

'''Device #''' '''Name''' '''Room''' '''Category''' '''Watts'''
59 Basement Light Basement 3 20
60 Bedroom Light 1st Floor 3 0
61 Porch Light Outside 3 30

To display only the watts variable : http://ip_address:3480/data_request?id=variableget&DeviceNum=34&serviceId=urn:micasaverde-com:serviceId:EnergyMetering1&Variable=Watts
and you must specify the device id for the variable and the service id.

==request_image==

Returns an image from a camera. This fetches the image from the camera using the URL variable for the device. Pass arguments:

cam = the device id of the camera. This is the only mandatory argument.
res = optional: a resolution, which gets appended to the variable. So passing "low" means the image from the URL_low variable will be returned. If it doesn't exist it reverts to the standard URL or DirectStreamingURL
timeout = optional: how long to wait for the image to be retrieved, or how long to retrieve video. defaults to 10 seconds.
url = optional: override the camera's default URL
ip = optional: override the camera's default ip
user or pass = optional: override the camera's default username/password

==archive_video==
''* UI5+ only''

Archives a MJPEG video or a JPEG snapshot.

Parameters:
* <tt>cam</tt>: the device # of the camera.
* <tt>duration</tt>: the duration, in seconds, of the video. The default value is 60 seconds.
* <tt>format</tt>: set it to '''1''' for snapshots. If this is missing or has any other value, the archive will be a MJPEG video.

Examples:

* Archive a snapshot:
http://ip_address:3480/data_request?id=archive_video&cam=8&format=1
* Archive a 40 seconds video:
http://ip_address:3480/data_request?id=archive_video&cam=3&duration=40

==jobstatus==

Returns the status of a job. The parameters are <tt>job</tt>, which is the job ID and optionally <tt>plugin</tt>, which is the plugin name. For a Z-Wave job the <tt>plugin</tt> parameter '''must''' be ''zwave''.

If <tt>job</tt> is invalid the status returned is ''-1''.

This is the list with all job statuses and their meaning:

* '''-1''': No job, i.e. job doesn't exist.
* '''0''': Job waiting to start.
* '''1''': Job in progress.
* '''2''': Job error.
* '''3''': Job aborted.
* '''4''': Job done.
* '''5''': Job waiting for callback. Used in special cases.
* '''6''': Job requeue. If the job was aborted and needs to be started, use this special value.
* '''7''': Job in progress with pending data. This means the job is waiting for data, but can't take it now.

Examples:

http://ip_address:3480/data_request?id=jobstatus&job=13

http://ip_address:3480/data_request?id=jobstatus&job=6&plugin=zwave

==invoke==

This request shows the list of devices and the actions they support through the UPnP services specified in their UPnP device description file. Only the actions with a star (*) preceding their name are implemented.

Examples:
* http://ip_address:3480/data_request?id=invoke
* http://ip_address:3480/data_request?id=invoke&DeviceNum=6
* http://ip_address:3480/data_request?id=invoke&UDN=uuid:4d494342-5342-5645-0002-000000000002

==relay==
''* UI5+ only''

This tells the system to setup a relay so that you can access a device on the home network from outside the home. This is most commonly used to fetch streaming video from a camera, although it can actually be used for any IP device. This takes either an 'ip' or 'device' argument. If you pass a device, this is assumed to be a device ID, and the system will find the ip associated with that device. Optionally pass a port argument for the port you want to be relayed. Port 80 is assumed if none is specified.

This request will return a 'server:port' which you can use externally to access the designated device. The relay stays open for 15 minutes before closing, at which point you will need to open it again.

So, assume you have a NAS device on the home network with the ip 192.168.1.55 and the NAS runs a configuration web page on port 80. You could access it by doing this:

http://ip_address:3480/data_request?id=relay&ip=192.168.1.55&port=80

and if the response is: "someserver:20202", then for 15 minutes, "http://someserver:20202" will be the NAS's configuration page.

If you want to access a camera, device #5, then do this:

http://ip_address:3480/data_request?id=relay&device=5

and if the response is "someserver:20211" and if the 'DirectStreamURL' variable (or 'streaming' in sdata) is "video.mpeg", then for 15 minutes you can access the camera's video at: http://someserver:20211/video.mpeg

Note that if the device, the camera in this case, has http authentication, you will need to pass this too. So, if the user_data or sdata for the camera shows the user name is 'johndoe' and the password is 'john123', then you can view the video at: http://john:john123@someserver:20211/video.mpeg

IMPORTANT: For the 15 minutes while this relay is open, it will be open to anyone on the internet and public. Therefore, for security, you may want to add to the data_request the argument externalip=x where x is the routable, external IP, such as 70.182.172.111, of the device that will be accessing the port. This means that when the relay is open, a firewall will be set on the relay server so that incoming connections are only accepted from that ip address.

==update_plugin==
''* UI5+ only''

Updates a plugin to the latest version.

Example: http://ip_address:3480/data_request?id=update_plugin&Plugin=Plugin_ID

== Accessing Vera remotely through the MiOS servers ==

The MiOS servers provide a secure way to remotely access and control your Vera system using the HTTP interface. Everything you can do locally with Vera on port 3480, you can do remotely with MiOS using the exact same syntax. You only need to pass the MiOS account username and password on the URL to the remote access server, along with the serial number of the unit (ie. 30012345). For example, the <tt>user_data</tt> request syntax over the Internet through the MiOS servers is:

https://fwdX.mios.com/demovera/myvera123/30012345/data_request?id=user_data

assuming ''demovera'' is the MiOS account username and ''myvera123'' is the password. '''Note that since the request is <tt>https</tt>, the username and password are encrypted because <tt>https</tt> encrypts the URL's as well as the contents of the page.'''

==What to do when the HTTP request string is too long==

http://forum.micasaverde.com/index.php/topic,10170.msg69530.html#msg69530

ExpressControls3in1

2013-01-23T21:15:01Z

Mcvdennis:

== Overview ==

The EZMotion Wireless 3-in-1 sensor is functionally identical to the HomeSeer HSM100 device. The user's manual is here: http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf

=== Features ===

This unit is a contains three sensors that report values to the Vera:

*'''Motion Sensor''' with adjustable sensitivity and timeout
*'''Temperature Sensor'''
*'''Luminosity (Light Level) Sensor''' reporting level of light as a percentage between the brightest and darkest levels it has encountered since being switched on for the first time

 The temperature and light levels are reported when the device wakes up and reports back to Vera, but the motion sensor will report automatically whenever it has been tripped, wether the device is sleeping or not. The unit has a red LED which indicates when motion is detected and it can be disabled. It can also report its battery level as a percentage to the Vera. 

 

== Basic Configuration ==

For more information about Device Options, please visit: 

[http://docs5.mios.com/doc.php?language=1&manual=1&platform=3Pro&page=add_device_zwave_properties_dev_option http://docs5.mios.com/doc.php?language=1&manual=1&platform=3Pro&page=add_device_zwave_properties_dev_option] 

=== Wake Up interval ===

The unit sleeps for the duration of the Wake Up interval, which defaults to 1800 seconds or 30 minutes. When the interval expires, it wakes up and reports Temperature and Luminosity to the Vera. Note that while all 4 devices in the Vera MIOS screen can be configured for Wake Up intervals, only the setting for the '3-in-1 Sensor' has any effect and controls both Temperature and Luminosity intervals. The Motion Sensor is unaffected by the Wakeup Interval (see On Time below)

To set the Wake Up Interval, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Setting and set Wakeup Interval to the desired interval (in seconds, e.g. 1800(seconds) = 30 min before the sensor wakes up again). Reducing the wake up interval (causing the sensor to transmit radio signals more often) reduces battery life.

=== On Time ===

When the Motion Sensor is tripped, it transmits a tripped command and changes its state to Tripped=1 for the duration of the ON TIME variable. After this time has expired, it sends an Untripped command to the Vera and resets it state to Tripped=0. While the device is in a tripped state, any motion detected resets the interval timer but doesn't report a new trip event to the Vera. During the wait time the Motion Sensor device in the Vera will show Tripped=1 in the Advanced tab.

To set the ON TIME, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 5 (or the desired interval in minutes)

'''Direct Association:''' The unit can be associated directly with another device such as a light. If you've done this, the unit will turn the light on when motion is sensed, then turn it off after the ON TIME. According to the sensor's manual up to four associated devices are supported, but associating more than one device does not work (as of Vera's firmware 1.0.900, see http://bugs.micasaverde.com/view.php?id=705).

Leave Parameter #6, "OnValue", at the default if you want the sensor tripped events in Vera.

=== Polling Frequency ===

The unit can only be polled when it is either in Test mode or within 3 seconds after waking up (see Wake Up Interval above). Polling at any other time will fail since the unit will not respond. Also, every time the unit wakes up, it updates Vera with the temperature and luminosity. This means that polling is unnecessary and the polling frequency should be set to 0 (disabled) or a long interval to avoid unnecessary traffic on Vera, which could cause updates to be missed.

An exception to this rule is when Vera is set to Always Awake (see AC Power below). In that case, the unit is always awake, so never reports its values (which happens at wake-up) and must be polled at regular intervals.

=== Example ===

Consider the following example of how to configure the sensor and the Vera for a common application. Suppose you want to install a motion sensor in your garage to turn the lights on when you enter, keep them on for as long as you move around in the garage, then turn them off 5 minutes after you've left.

'''UI4''' 

#Put the unit in Test mode by pressing the button on the side
#Configure the On Time to 5 minutes
#Create two scenes in Vera:
##Turn on the light when the unit has tripped (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=Yes)
##Turn off the light when the unit sends an untrip command which happens after the On Time interval. (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=No)

'''UI5''' 

#Put the unit in Test mode by pressing the button on the side
#Configure the On Time to 5 minutes
#Create two scenes in Vera:
##Turn on the light when the unit has tripped (Automation -> Create Scene, Triggers tab, Add trigger, Device=Motion sensor, What type of event is the trigger?=An armed sensor is tripped, Name for this trigger=whatever, Device armed is tripped)
##Turn off the light when the unit sends an untrip command which happens after the On Time interval. (Automation -> Create Scene, Triggers tab, Add trigger, Device=Motion sensor, What type of event is the trigger?=An armed sensor is tripped, Name for this trigger=whatever, Device armed is not tripped)

 

== Advanced Configuration ==

=== Running from AC Power ===

==== Overview ====

It is possible to run the unit from AC power instead of batteries, which will have the following benefits:

*Allow you to keep the unit awake permanently, allowing you to poll it and customise it without being in Test mode
*Report continuously every time motion is sensed, as opposed to waiting for the ON TIME duration in between trips
*Set the unit to report temperature and light levels at higher frequencies up to 1 minute
*Let the unit act as a Z-Wave repeater, increasing the span of your network
*Never worry about running down batteries. All of the above options are possible on battery power, but will run your batteries down within a few days

==== Configure ====

To do this, you will need to connect a AC to DC transformer that supplies 4.5v to 5.5v at up to 1amp to the battery terminals directly. Ensure that you measure that actual output voltage of the transformer using a multi/voltage meter (don't rely on its advertised rating). Any over-voltage may fry the unit. Also make sure that the polarity is correct. It may be helpful to add a diode in series with the positive terminal to prevent accidentally frying the unit if the polarity is incorrect. It will drop the voltage by 0.6v though.

'''Setting ''Stay Awake'' to On''' By default, the unit is constantly asleep and only wakes up at regular intervals to report the luminosity and temperature, before sleeping again. This is to save batteries. While asleep, the unit cannot be programmed from the Vera and cannot be polled for information. To get around this, one normally activates the Test mode by pressing the button on the side of the unit, which keeps it awake for 10 minutes so that it can be programmed. By setting the unit to stay awake constantly, you can program, poll or configure it at any time. It also has the side effect of enabling the unit to become a repeater of Z Wave signals throughout the network.

To set it, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 5 (Stay Awake) to 1 or any number greater than 0.

To activate this setting, you will need to power off and power back on the device. Remember to save your settings first.

'''Setting ''On Time'' to ''Always Fire''''' When the unit detects motion, it reports it by sending a Tripped command to the Vera. It then waits for the duration of the On Time and then sends un Untripped command to the Vera and waits for the next motion. Since battery life is not a consideration while on AC power, you can set it to 'Always Fire', which sends a Tripped command whenever motion is detected with no waiting period. Note, this will also prevent an Untripped command from being sent.

To set it, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 0.

'''Setting Poll frequency''' The unit usually only reports temperate and luminosity every time it wakes up, but since the unit is now constantly awake, you will have to configure a poll frequency to gather that information.

To set it, click on the spanner (wrench) icon for the "Motion Sensor" device, click on Settings and set "Poll this node at most every" to the required update frequency. The Wakeup interval setting on this same screen has no effect since it's been overridden by Always Awake setting..

== Known issues ==

[[Category:Hardware]] [[Category:Plugins]] [[Category:3rd_Party]]

Aeon HomeEnergyMonitor

2012-07-03T10:57:45Z

Mcvdennis:

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. If you don't have 3.61, download these files:

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. 

[[Category:User_Instructions]] [[Category:Hardware]]

Aeon HomeEnergyMonitor

2012-07-03T10:52:29Z

Mcvdennis:

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. If you don't have 3.61, download these files:

US version: [http://wiki.micasaverde.com/images/0/0c/HEM361.zip HEM361]

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. 

[[Category:User_Instructions]] [[Category:Hardware]]

Aeon HomeEnergyMonitor

2012-07-03T10:47:50Z

Mcvdennis:

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. If you don't have 3.61, download these files:

US version: [http://wiki.micasaverde.com/images/0/0c/HEM361.zip HEM361]

US version: [http://wiki.micasaverde.com/images/f/f6/Home_Energy_Meter_V3_67_US.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. 

[[Category:User_Instructions]] [[Category:Hardware]]

Aeon HomeEnergyMonitor

2012-07-03T10:43:54Z

Mcvdennis:

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. If you don't have 3.61, download these files:

US version: [http://wiki.micasaverde.com/images/0/0c/HEM361.zip HEM361]

US version: [http://wiki.micasaverde.com/index.php/File:Home_Energy_Meter_V3_67_US.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. 

[[Category:User_Instructions]] [[Category:Hardware]]

File:Home Energy Meter V3 67 EU 100A.zip

2012-07-03T10:33:43Z

Mcvdennis:

File:Home Energy Meter V3 67 US.zip

2012-07-03T10:28:23Z

Mcvdennis:

File:Home Energy Meter V3 67 EU 200A.zip

2012-07-03T10:27:59Z

Mcvdennis:

File:Home Energy Meter V3 67 EU 60A.zip

2012-07-03T10:26:29Z

Mcvdennis:

File:Home Energy Meter V3 67 AU 200A.zip

2012-07-03T10:25:10Z

Mcvdennis:

Update Firmware

2012-03-23T19:57:47Z

Mcvdennis:

'''How to update Vera to a new firmware'''

== Prerequisites ==

*Vera Hardware (Vera 1, Vera 2, Vera 3 or Vera Lite)
*Internet connection
*Reliable power source (Do NOT update Vera while on battery operation)
*You must be in the same network as your Vera unit in order to update firmware

== Introduction ==

Your Vera box can be upgraded with software from MiOS. You can either be asked to upgrade automatically or you can decide to do a manual upgrade at any point in time.

=== General Notice ===

When installing the firmware, make sure you have the login to your vera system set to standard (no http login needed) via the remote control server.

If you have chosen http authentication "YES" from the https://cp.mios.com site (settings section) you will get a pop up where you should enter username and password. Currently there is an issue that this pop-up disappears within 10 seconds in some browswers. Most users will therefore be unable to provide their username and password.

The current workaround is to

*disable authentication
*upgrade
*re-enable the authentication from cp.mios.com

== Upgrades ==

=== Create a backup! ===

You can create and restore backup form the advanced settings section in your toolbox. After double clicking that, go to the "BACKUP" tab. If you check the "Backup my configuration at MiOS.com" option, Vera will automatically backup your configuration online each night so that if Vera breaks and we send you another one, you can go to MiOS.com, download the last backup file, and restore it so you don't need to setup Vera again. MiOS.com keeps 5 daily backups, so if you somehow mess up Vera's setup, you can also restore Vera to a prior backup.

To manually backup Vera, click 'Create Backup'. Vera will give you a backup file to save to your PC.

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

You can also click 'Restore to Factory Defaults' to reset Vera's configuration just like it was when Vera first arrived.

== How to create a backup and restore it (UI5): ==

*click the "SETUP" tab from your dashboard.
*Select "Backup"
*Press on the "Press Z-Wave network" button and wait until the process ends. Look for the message "Backup: Backup done" in the top of your dashboard. 
*Then press "Create backup" button and save the backup file on your computer.
*In order to restore a backup you must check the option "Restore Dongle Firmware (takes up to 2 hours and is not recommended) and then browse for the backup file on your computer and click on "Restore" button.

=== Manual Upgrades ===

To manually load a firmware to your Vera:

*click the Advanced icon in the toolbox section of your Vera's UI.
*Select the tab "FIRMWARE"
*Vera automatically checks connectivity to the download server (download1.mios.com or download2.mios.com).
*Vera shows you the current firmware version and provides info if this firmware is up to date or not.
*You can upgrade your Vera by dropping a specific download URL for your Vera in the "URL for MiOS custom firmware" box. 

 

To manually load a firmware to your Vera 3 or Vera Lite (UI5):

*click the "SETUP" tab from your dashboard.
*Select the tab "FIRMWARE"
*Vera automatically checks connectivity to the download server (download1.mios.com or download2.mios.com).
*Vera shows you the current firmware version and provides info if this firmware is up to date or not.
*You can upgrade your Vera by dropping a specific download URL for your Vera in the "URL for MiOS custom firmware" box.

 

=== Automatic Upgrades ===

*NOTE: Updating a Vera 1 to the latest official firmware requires an intermediate step. Always create a backup file for your unit and after that please go to https://findvera.com/ in order to upgrade. 

See also: http://wiki.micasaverde.com/index.php/Vera1_To_Vera2_Migration

You can automatically update your Vera by accepting the pop-up notice that a new firmware is available, asking you if you want to upgrade. From there you can follow the steps to automatically update your Vera to the latest official firmware release.

== Known Issues ==

*Vera 1 upgrading to 1.1.1245 directly from a version older than 1.1.1062 does not work. If you go to http://findvera.com it will ask you to upgrade to an intermediate version of firmware and after it is finish you should go to http://micasaverde.com/vera to see if you have the latest firmware version. 
*Sometimes an upgrade makes Vera go back to her default locale settings (USA). For users in the EU their devices do not work anymore. As for the locale issue mentioned in this thread, please refer to [http://forum.mios.com/index.php?topic=6652.0 this Forum post]

== References ==

*Update URL for your Vera 1 or 2 Hardware http://micasaverde.com/vera2
*Update URL for your Vera 2 (if you have UI4 and you want the new user interface UI5) : http://cp.mios.com/firmware
*Update URL for your Vera 3 or Vera Lite : http://cp.mios.com/firmware
*Recovery procedures
**Vera 1 hardware [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera_1 Recovery]
**Vera 2 hardware [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2 Recovery]
**Vera 3 hardware [http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera3 Recovery]

Note: To be done only if you Vera unit doesn't boot anymore!!! See in each link how the leds should blink if this is the case !!!

*Related forum threads
**http://forum.mios.com/index.php?topic=6652.0 
**http://forum.mios.com/index.php?topic=4423.0

[[Category:How_To]]

IP Cameras

2012-02-24T18:59:00Z

Mcvdennis:

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

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

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

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

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Added by
! Notes
|-
| Foscam [http://www.foscam.us/] [http://www.foscam.com/]
| IP Camera
| [http://www.foscam.com/Products_List.asp?id=128 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 see: [http://forum.micasaverde.com/index.php?topic=3720.0 DIY instructions]
|-
| 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] 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& 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
|-
| 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.
|-
| 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.
|}

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

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Added by
! Notes
|-
| Trendnet
| IP Camera
| TV-IP100W
| all
| 2007 
| Indoor
| none 
| 
| 
| This camera can only serve images using DirectX or Java. The workaround is complex: "using a PC you can use MPlayer to strip out a JPG image from the video stream (asf). You can then store the JPG snapshot on a PC, then run a web server and vera can then "fetch" the image from the PC instead of the camera."
|-
| 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.
|}

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

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

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

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

In most cases, IP cameras have a URL method for obtaining a SNAPSHOT or JPG image from the camera. If your camera supports this method, you can then use it with Vera and 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.

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

You will need to specify:

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

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

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

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

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

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

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

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

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

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

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

 

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

 

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

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

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

Other parameters would be the same as above.

=== Axis IP Cameras ===

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

 

=== '''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]] [[Category:Supported_Devices_Table]]