MiOS - User contributions [en]

UI5 Issues

2011-09-18T09:45:50Z

Henk:

[[Category:UI5]]

=== Problems reported ===

== oTi@ ==

1. The upgrade wiped out the logs on the USB stick. vali: mantis http://bugs.micasaverde.com/view.php?id=1699 assigned to it_team

2. MiOS routing may have been automatically enabled? I'd have to downgrade to make sure it wasn't already automagically enabled before the upgrade. aaron:This shouldn't have happened. We'll check the logs. 
''oTi@: turned out MiOS routing was already enabled before the upgrade; so not an upgrade issue.''

5. It looks like some of my scenes didn't carry over properly. (Dimmer settings lost.)

6. When I tried to edit the scene remotely through cp.mios, I got a message saying: 'You are not allowed to save the settings on this system'. vali: you were probably connected as a guest, in UI5 only administrators are allowed to save

7. Switched to VPN and edited the scene; let me save it, but it doesn't look like it actually saved. vali: http://bugs.micasaverde.com/view.php?id=1694

14. Dimmers will show the percentages, right? (Especially useful when setting a scene.) vali: yes

17. (repeat) Devices > Sensor tab would be nice; somewhere towards the left. Motion/3-in-1/Door-Window stuff now shows up all the way to the right under Other. I imagine many folks may have some of these. vali: mantis http://bugs.micasaverde.com/view.php?id=1698

18. What's Devices > Mobile Phones?

19. Events/Timers get names. Given the various times it has come up on the forum, it seems intuitive for folks that you can then later refer to these events/timers and not have to define them again. I.e. defining 'Kitchen Motion Sensor Tripped' and 'Wednesday at 5pm' once. This probably has some UI design impact; but well, this is a new major version.

20. SQRemote rejects version 1.5.56. That should probably be mentioned somewhere (or made compatible by SquareConnect) upon public release. vali: scenes syntax is different, the other stuff should work 
''oTi@: ok, but when are changes communicated to CP developers? It would be nice if they could upgrade their apps before public release of UI5, and/or there should be an item in the UI5 release notes that warns the user. It's not fun for users to upgrade to UI5 and then have SQRemote not work.''

21. When adding a device it is now not quite clear where to look for it / see what's going on. It'll show up as Other for a bit and then jump to whatever tab is appropriate, once Vera has configured it. Likely to confuse folks? (Example: add a relay; shows up in Other; than jumps to Lights.) vali: we may have another tab in devices for Un-configured devices and have all the other tabs to show only devices which are configured (e.g. working devices); to be discuss

==strangely==

24. You shouldn't have to click the wrench to view a camera.
 vali: camera devices should have buttons to view and achive

25. Still no conditional expressions.

26. There should be another tab next to pinned devices in the dashboard that allows you to see all devices on one page without pinning.
 vali: to be discuss

27. Notification scenes are now showing up
 vali: mantis http://bugs.micasaverde.com/view.php?id=1690

28. Where are you supposed to set notifications?
 vali: as always, in control panel of the device, click on notifications

29. When trying to edit a scene that involves my alarm plugin, there is no panel or partition device available under any of the category tabs
 vali: mantis http://bugs.micasaverde.com/view.php?id=1701

30. Scenes that involved the old advanced tab in UI4 don't seem to be editable or viewable anymore?
 vali: mantis http://bugs.micasaverde.com/view.php?id=1691

31. Standard scenes don't seem to editable either
 vali: possible conversion failure, trouble ticket needed to investigate

32. There doesn't seem to be any way to see what the existing timers are? I'm not talking about scheduled timers, but more things like "after 2 hours turn off etc" which I've found out dont seem to work after migrating anyway.
 vali: friendly description for timers is very difficult due localization, since the wording is different in other languages than English

34. Sensors do not visually show if tripped or not
 vali: mantis http://bugs.micasaverde.com/view.php?id=1702, Aaron please comment on it since Alexus team said design is made with static icons

35. What is the purpose of the small arrow highlighted in my attached picture, and why do some devices have these only on the bypass button only?
 vali: it's "restore to previous settings" button, and should not appear for both controls, mantis http://bugs.micasaverde.com/view.php?id=1703

== garretwp ==

36. Thermostat: shows my temperatures in C and not in F. vali: mantis http://bugs.micasaverde.com/view.php?id=1704

37. Thermostat: does not show the current temp. vali: mantis http://bugs.micasaverde.com/view.php?id=1705

38. Thermostat: fan mode still not working.

39. Notification of command sent does not clear vali: mantis http://bugs.micasaverde.com/view.php?id=1700

46. oTi@ reported not all scenes carried over properly. I can also state the same. Especially the scenes that involve dimmers. This also goes for thermostats as well

47. Edit a scene that involves a dimmer and having the level set in the scene does not get saved. vali: mantis http://bugs.micasaverde.com/view.php?id=1547

mirela: mantis [http://bugs.micasaverde.com/view.php?id=1724 http://bugs.micasaverde.com/view.php?id=1724]

48. Schedules in the automation section should show the scene name that belongs to that schedule. I have similar schedule names for different scenes (e.g. wed). And looking at the schedule section shows a ton of wed names, but have no clue what scene owns that schedule. vali: click on wrench next to schedule/trigger go to edit schedule/trigger, no need to know the scene name, but in any case I added mantis http://bugs.micasaverde.com/view.php?id=1707

49. Formatting is messed up in the schedules section with having long names or long description. See attached image vali: mantis http://bugs.micasaverde.com/view.php?id=1708

50. Creating Scene to adjust my thermostat to a certain temperature does not save the temperature value. vali: mantis http://bugs.micasaverde.com/view.php?id=1709

==Henk==

52. USB logs are wiped ( but that also happened on UI4 upgrades)
 vali: see #1

53. i had some issues when removing a scene (bin didnt work) that were solved after a CTRL F5
 vali: we'll try to reproduce

55. My SM103 doorsensor does not show up in climate& security but in "other devices" where most custom plugins reside. In fact, why is there not a
secion for "Motorized control" to sort window coverings etc in?
 vali: see #17

56. Pinned scenes do not "stick" even after saves. the show up unpinned after a refresh.
 vali: we'll try to reproduce
i LOVE the breakout of scenes triggers and schedules. It made me aware that i had not named a few of them at all.

57. The button under create/save is merely invisible and therefore unreadable. After clicking the edge that WAS visible, i found out it was a "return home button" ?
 vali: it's "restore to previous settings" actually; to be discuss usability in this section

59.. My camera plugin did not show snapshot (had that on UI4 for a while too)
Worse, also streaming was broken (worked flawlessly on UI4).
I decided to remove the plugin completely and build it from scratch. Will report my findings later!

60. Hide / autocollapse emtpy rooms from any view as to not confuse users and claim more realastate for important info.
 vali: to be discuss

61. Apps/plugins installed under UI4 that get migrated to UI5 do not show version number. Workaround is to remove the plugin/app and reinstall it in UI5 using the new APPS section

62. am having trouble with luup code in events. the same luupcode for a binary light switch works. 1 binary Duewi light switch
send notification via Prowl when lights go OFF notification works when lights shut OFF., 1 FCM luup plugin (works)
Scene to pickup events from the plugin (LUUP) Event for the scene coded to send notification via prowl (same code as before and similar to the luup event for the binary switch, worked under UI4).

63. Notification does not work!
 vali: new servers issue

64. 1. Missing and corrupted scenes after migration, 2. LUUP code not working anymore after migration although the code itself is intact (luup events), 3. I have seen information from one plugin depicted in another (weather depicting FCM caller data), 4. I have noticed scenes to pop up unexpected and ive had scenes that were hard to delete, only refreshing, reloading and trying time after time made it work., 5. Pinning of scenes doesnt work (after a save and reload they are gone from the pinning list.
 vali: issue 64.4 working to reproduce, 64.5 mantis http://bugs.micasaverde.com/view.php?id=1688

65. Vera started acting up, she switched my binary plugin module off time after time when i switched it on manually at the device, using the device ON/OFF button.
 vali: any timer/event setup on it?

==mario23==

66. all scene settings didn't make it over. Also, how do I now set a scene conditions like before. Example, Turn dimmer to 50% for two hours then down to 20%???
 vali: add command to turn dimmer to 50%, type 120 next to "Add commands to be run" and click Add, add command to set dimmer to 20%. Need to add help pages for scenes editor

67. Saving settings in some scenes aren't working for me.
 vali: same as #47 I assume

==Ap15e==

68. Archive old logs: might have been activated by upgrade to UI5
 vali: this is activated by default in ui4 too
 aaron: but an upgrade with preserve settings should keep the old settings

72. motion sensors and smoke sensors are "Other" devices
 mirela: http://bugs.micasaverde.com/view.php?id=1698

73. Help is empty
 vali: we're working on it

74. Control Panels for all devices auto-close after less than a second
 vali: trying to reproduce

75. Add Devices -> most of the Add buttons don't work
 vali: need more details

76. GUI calendar has some interesting dates, e.g. 2011/11/31 ...

=== Feature requests ===

3. No more sections?

4. Can the sort order of stuff be changed? vali: mantis http://bugs.micasaverde.com/view.php?id=1684

15. I would love for the 'On' button on a dimmer to cause the dimmer to go the last setting, rather than full on, or some way at least to tell a dimmer to go the last setting. I've been missing this (and wrote a bug on it) a lot. (Currently working around it with a low-level basic set 255, followed by a poll.) vali: if we add a new upnp variable for last setting, we can also add a new button for dimmers. 
''oTi@: The proposal is for the dimmer itself to go back to its last setting, as Vera may not have the last setting (depending on device features, polling, etc.). So just have Vera send a level 255 (instead of 100), just like (motion) sensors typically do by default. (E.g. my making the level for the On button user-configurable in Vera.)''

33. Lights should be labeled lights and appliances, and if it's not possible to distinguish between these then the picture of a bulb should be editable.
 vali: to be discuss

44. The idea of hitting the on button and having the dimmer go back to last state would be nice. (I am going to add that idea into my android application!) vali: see #15

58. In devices i miss an ALL devices tab
 vali: same as #26, to be discuss

=== Cosmetic ===

8. Prefer a clock with seconds (or switchable on/off) and all digits the same size. vali: seconds won't be added because they may flip when the clock is resyncronized with the unit, for size mantis http://bugs.micasaverde.com/view.php?id=1697

9. I'd move the username over to the left, and remove the permanent 'Welcome:'. vali: to be discuss

10. A quick 'info' button to pull up firmware versions (Vera and Z-Wave), IP, PRI status, etc. would be nice. vali: to be discuss

11. Would like to be able to make the status window bigger and perhaps it can float, so all messages fit. It's an important window. vali: to be discuss, it can be different under new graphics

12. Will wait for the new graphics, etc., but I still see a lot of 'dead' space, boxes are big, etc. vali: same as #11

13. The way stuff gets laid out on the screen seems unnatural, because dimmers are bigger than switches (i.e. it's not always left-aligned). vali: same as #11

16. Minimize the number of different font types. Probably just pick one for a consistent look and feel. vali: same as #11

22. The turquoise and orange really don't work well with the rest of the colours.
 vali: to be discuss if still apply in new graphics

23. Why is there still an annoying pop up when activating a scene?
 vali: mantis http://bugs.micasaverde.com/view.php?id=1700

40. The status window should be wider. There is all that space up top. Why not either get rid of the extra space or use it for the status window. That would allow us not have to scroll in the window. vali: to be discuss for new graphics

41. Yes, graphics are missing and will have to wait when they get finished and packed into the next firmware.

42. The devices boxes should all be the same size and the alignments do get messed up. Attached image. vali: reported in mantis http://bugs.micasaverde.com/view.php?id=1581 but resolves as "by design". Please reopen and comment

43. Text in the devices that show information is too close to the veritical bar, it should be larger and darker in color. vali: mantis http://bugs.micasaverde.com/view.php?id=1706

45. I guess the energy monitory will come shortly? vali: yes

54. There are some parts of the menu that seem " unfinished" as in the text is black (default?) and not in line with the overal theme. This occurs especially in the settings tab.
 vali: mantis http://bugs.micasaverde.com/view.php?id=1710

69. trash bins for devices and for scenes are at different positions - absolutely unacceptable!
 vali: to be discuss for new graphics

70. auto-layout should use fixed width/height for device boxes
 vali: to be discuss for new graphics

71. device boxes are too large, current layout is unusable if there are > 10 devices, scene boxes are too large, current layout is unusable if there are > 15 scenes
 vali: to be discuss for new graphics

{| class=sortable border="0"
!style="background:lightgrey;" | LEGEND

|- style="background:#00C000; color:black;"
|Resolved
|-
|- style="background:#B0C4DE; color:black;"
|Not an issue
|-
|- style="background:#F0E68C; color:black;"
|To discuss
|-
|- style="background:#FFA07A; color:black;"
|Unable to reproduce
|-
|}

UI4 UI5 Migration

2011-09-18T09:45:30Z

Henk:

[[Category:UI5]]
Our newest Ui5 does some things differently than Ui4. This page explains the changes in Ui5 that may not be obvious to Ui4 users.

==Single user interface==

With UI4 there were several different user interfaces, such as the dashboard, the wizard, the cp.mios.com portal, etc. To view the current status of a device you went to the dashboard. To view the history of a device you went to cp.mios.com. Now there's just one UI and everything is one place. As always some of the features are handled locally by Vera, and others are handled by a server. But rather than having to check 2 UI's, they are all together. If you are viewing a popup or a tab that requires features handled by the server, such as a history of your notifications, you will see that you are prompted to login with your mios.com username when you try to choose those tabs or features. Also, if you do login to mios.com, but do not yet have a Vera, you will be notified of this when you select features that are handled by Vera locally, such as controlling devices.

==Scenes==

Scenes have been changes substantially. In Ui4 there were up to 4 different ways to specify "turn on light #3". On the dashboard there were on and off buttons, and in the wizard similar buttons. When adding light #3 to a scene, on and off were pull-downs. And you had the option of adding it both as a 'normal' scene and as an 'advanced' scene, and as part of a delay (ie turn off light #3 and 30 seconds later turn it on).

With Ui5 the goal is to make sure that the same action is always done exactly the same way. So if you want to turn on light #3 in the dashboard, you click the 'on' button for the light. If you're creating a scene and want it to turn on light #3, you still see the same control like on the dashboard and still click 'on' the same way.

So now when you create or edit a scene you'll see that you essentially get your dashboard. Devices that are grayed out are not involved in the scene (ie unchanged). Click one of the controls in the device to add it to the scene. Clicking 'on', like you would on the dashboard, means turn the light on. The delays are handled now by a the "Add commands to be run X seconds after the scene". So if previously in UI4 you had light #3 turn on and turn off after 30 seconds, and light #4 turn on and turn off after 45 seconds, then when you migrate to UI5 you'll have a pull-down that has "Immediate" which shows light #3 and #4 on, and also a "after 30 seconds" which has light #3 off, and also an "after 45 seconds" which has light #4 off. You can now add as many delays as you want, like, immediately do nothing to light #3, turn it on after 30 seconds, dim it to 50% after 60 seconds, and turn it off after 5 minutes.

Also in UI4 you had 'advanced' command (on the advanced tab) vs. 'normal' commands (on the command tab). And it was impossible to see all your commands in one place. In Ui5 there's no longer the concept of normal vs. advanced commands. There is still an Advanced tab, but this is only an advanced "view" of the same commands. The same commands are shown on the devices tabs as on the advanced tab. The advanced tab just presents it in a table view with all the commands in the scene. Whereas the devices tab let's you build a scene more like a macro recorder, by just clicking on the devices the same way you would on the dashboard.

==Timers==

They are now called "Schedules", but they work exactly the same way. It's a tab in the scene editor.

==Events==

They are now called "Triggers", but they work exactly the same way. It's a tab in the scene editor.

==Developer changes==

=== eventList ===
The '''eventList''' in the D_...json is now normalized. The format from UI4 was a mistake all along, treating arrays as objects. So this:

"eventList": {
"event_1": {
"label": "Incoming call from",
"serviceId": "urn:upnp-ap15e-com:serviceId:FCM1",
"norepeat": "0",
"argumentList": {
"argument_1": {
"dataType": "string",
"name": "CallSource",
"comparisson": "=",
"prefix": "Phone number",
"suffix": ""
}
}
},
"event_2": {
"label": "Outgoing call to",
"serviceId": "urn:upnp-ap15e-com:serviceId:FCM1",
"norepeat": "0",
"argumentList": {
"argument_1": {
"dataType": "string",
"name": "CallDestination",
"comparisson": "=",
"prefix": "Phone number",
"suffix": ""
}
}
}
},

now needs to be like this, where '''eventList''' and '''argumentList''' are now arrays containing an element '''''id''''' that has the id, rather than putting the id in the tag name (i.e. '''event_1''' becomes '''"id": 1'''):

"eventList": [
{
"id": 1,
"label": "Incoming call from",
"serviceId": "urn:upnp-ap15e-com:serviceId:FCM1",
"norepeat": "0",
"argumentList": [
{
"id": 1,
"dataType": "string",
"name": "CallSource",
"comparisson": "=",
"prefix": "Phone number",
"suffix": ""
}
]
},
{
"id": 2,
"label": "Outgoing call to",
"serviceId": "urn:upnp-ap15e-com:serviceId:FCM1",
"norepeat": "0",
"argumentList": [
{
"id": 1,
"dataType": "string",
"name": "CallDestination",
"comparisson": "=",
"prefix": "Phone number",
"suffix": ""
}
]
}
],

===New Tags===
====ui5_x, ui5_y====
These tags can appear in root or in '''[[#ui5_SceneGroup|ui5_SceneGroup]]''' and they represent the device box dimensions, '''ui5_x''' and '''ui5_y''' being the width and the height respectively. 1x = 100 pixels, 1y = 24 pixels.

====ui5_onDashboard====
If this tag is present and has the value '''"1"''' the device will be pinned on the dashboard at creation.

====ui5_inScene====
If this tag is present and has the value '''"1"''', the device can be used in scenes.

====ui5_image_src====
Used in '''[[#image_player|image_player]]''' controls for specifying the image file to be used for the skin.

====ui5_SceneGroup====
ui5_SceneGroup is an array which contains the definition for all the control groups (clusters).

"ui5_SceneGroup": [
{
"id": "1",
"isSingle": "1",
"ui5_top": "0",
"ui5_left": "0",
"ui5_x": "2",
"ui5_y": "1"
}
]

===New Control Types===
====image_player====
This is a skinnable button. It has the same tags as a button plus the '''[[#ui5_image_src|ui5_image_src]]''' tag for specifying the image used for the skin.

e.g. Here is the '''Up''' button from the camera:
{
"ControlType": "image_player",
"Label": {
"lang_tag": "cmd_up",
"text": "Up"
},
"Display": {
"Top": 49,
"Left": 466,
"Width": 75,
"Height": 20
},
"Command": {
"Service": "urn:micasaverde-com:serviceId:PanTiltZoom1",
"Action": "MoveUp",
"Parameters": [

]
},
"ui5_image_src": "images/player/image_control_up.png"
},

Sonos

2011-09-18T09:44:54Z

Henk:

[[Category:Hardware]]

== Sonos integration ==

[http://forum.micasaverde.com/index.php?topic=7707.0 Controlling Sonos devices from Lua code via UPnP/SOAP/HTTP]

Scene Syntax

2011-09-18T09:44:23Z

Henk:

[[Category:Development]]
If you're creating your own user interface you can create a scene using JSON and send it to the engine using the scene request as described here: [[Luup_Requests#scene]]

The Json should include a name, and optionally a room. If it includes an "id" then the existing scene with that id will be overwritten. If id is blank or invalid a new scene is added.

"groups" has all the actions, where all the actions are grouped into a json object which has a given delay. In the example below 2 lights and a thermostat are controlled immediately when the scene is executed (ie delay=0), and then a light is turned off after 10 seconds.

"triggers" has the events or triggers that will cause the scene to run. "template" refers to the "eventList" in the json file for the given device type. In this example the trigger "temp_over_80" has a trigger for a thermostat (device #79), so in D_HVAC_ZoneThermostat1.json, the eventList with ID 2 is labelled "Ambient temperature goes above" and it monitors the service "urn:upnp-org:serviceId:TemperatureSensor1" and the "argumentList" for that template monitors the variable "CurrentTemperature" the "comparisson": ">" means that the value of the variable must be > than the value in the scene, so the scene will run when the temp goes over 80. For the trigger "sensor_trip" the device is a motion sensor so in D_MotionSensor1.json template #1 is "A sensor (door/window/motion/etc.) is tripped" and monitors "Tripped" and occurs when Tripped is 1. For the "leak_alarm" in D_TempLeakSensor1.json template #5 shows the trigger occurs when urn:micasaverde-com:serviceId:HaDevice1 variable sl_Alarm = WATER_LEAK, and there are no user defined arguments.

"timers" has the timers that will cause the scene to run. The types are 1=interval, 2=day of week, 3=day of month, 4=absolute. For type 2 the field "days_of_week" indicates which days of the week (Sunday=0), and for type 3 "days_of_month" is a comma-separated list of the days of the month. In both cases "time" is the time. If the time has a T or R at the end it means the time is relative to sunset or sunrise, so -1:30:0R means 1hr 30 minutes before sunrise. For type 1 the interval tag has an h or m for hours or minutes, so 1h means every 1 hour, and 30m means every 30 minutes. For type 4 the time has the day and time.

{
"name": "Test Scene",
"groups": [
{
"delay": 0,
"actions": [
{
"device": "8",
"service": "urn:upnp-org:serviceId:SwitchPower1",
"action": "SetTarget",
"arguments": [
{
"name": "newTargetValue",
"value": "1"
}
]
},
{
"device": "9",
"service": "urn:upnp-org:serviceId:SwitchPower1",
"action": "SetTarget",
"arguments": [
{
"name": "newTargetValue",
"value": "0"
}
]
},
{
"device": "79",
"service": "urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
"action": "SetModeTarget",
"arguments": [
{
"name": "NewModeTarget",
"value": "CoolOn"
}
]
},
{
"device": "79",
"service": "urn:upnp-org:serviceId:TemperatureSetpoint1_Heat",
"action": "SetCurrentSetpoint",
"arguments": [
{
"name": "NewCurrentSetpoint",
"value": "28"
}
]
}
]
},
{
"delay": 10,
"actions": [
{
"device": "8",
"service": "urn:upnp-org:serviceId:SwitchPower1",
"action": "SetTarget",
"arguments": [
{
"name": "newTargetValue",
"value": "0"
}
]
}
]
}
],
"triggers": [
{
"name": "temp_over_80",
"enabled": 1,
"template": 2,
"device": 79,
"arguments": [
{
"id": 1,
"value": "80"
}
]
},
{
"name": "sensor_trip",
"enabled": 1,
"template": 1,
"device": 67,
"arguments": [
{
"id": 1,
"value": "1"
}
]
},
{
"name": "leak_alarm",
"enabled": 1,
"template": 5,
"device": 31
}
],
"timers": [
{
"id": 1,
"name": "mon_wed",
"type": "2",
"enabled": 1,
"days_of_week": "1,3",
"time": "4:9:0"
},
{
"id": 2,
"name": "after_sunset",
"type": "2",
"enabled": 1,
"days_of_week": "",
"time": "+1:0:0T"
},
{
"id": 3,
"name": "New schedule",
"type": 1,
"enabled": 1,
"interval": "5h"
}
],
"id": 20,
"room": 0
}

Apps.mios Developer's Guide

2011-09-18T09:42:29Z

Henk:

[[Category:Plugins]]
'''apps.mios.com''' contains a plugin creation wizard that aims to make the plugin creation process easier.

==Documentation==
The plugin which will be used as an example in this documentation is the Elk Alarm Panel Plugin.
This plugin has 8 files:

These files are for the panel itself:
* D_ElkAlarmPanel1.xml
* D_ElkAlarmPanel1.json

These files are for the partitions:
* D_ElkAlarmPartition1.xml
* D_ElkAlarmPartition1.json

These are the implementation files, which are used for both the panel and the partitions:
* I_ElkAlarmPanel1.xml
* L_ElkAlarmPanel1.lua

The are the service description files for the panel and the partitions:
* S_ElkAlarmPanel1.xml
* S_AlarmPartition2.xml

===Plugin Info===
====Plugin Information====
* Description: The description that will appear next to the title in the Marketplace.
* Instructions: Instructions for installing and configuring the plugin. Some plugins require additional steps for installation, steps which should be documented here.
* Visibility: For plugins intended to be made available to the public, the visibility should be ''public''.
* License: [http://en.wikipedia.org/wiki/Gpl GPL3], [http://en.wikipedia.org/wiki/BSD_licenses BSD], [http://en.wikipedia.org/wiki/Proprietary_software proprietary]

====UPnP Data====
This is the necessary information for creating the plugin device. If your plugin will have more than one device file, MiOS will use the information here to create the main plugin device. For the ''Elk Alarm Panel Plugin'' the main device is the panel device.

[[Image:UPnP_Data.png]]

===UPnP===
====Plugin Devices====
* The first three fields are the ones from UPnP Data. This is the necessary information for creating the plugin device. If your plugin will have more than one device file, MiOS will use the information here to create the main plugin device. For the ''Elk Alarm Panel Plugin'' the main device is the panel device.
* Invisible: An invisible device is ''for internal use only'' and won't be presented to the user. An example for this is the ''Insteon Network'' device.

===Plugin Files===
Here you can add, remove, edit, upload and download the files used by the plugin. This is an interface for the SVN repository where the files are stored.

[[Image:Plugin_Files.png]]

Pressing the Edit button will open the editor. For the device, service and implementation files there are wizards available for editing the files.

===Versions===
====Releases====
This is the list with all the released or pending for approval plugin versions.
====Add Release====
* Platform: The target platform for the plugin. While most plugins will very likely target all the platforms, some plugins need separate versions for different platforms.
* Compatible firmware: Some plugins require features present only in newer firmwares versions to run. Others did things that were later incorporated in MiOS, so are now obsolete. These versions must be specified here.
* Dev, Alpha, Beta, RC: these are some of the software development phases. Only RC (Release Candidate) versions can be submitted for approval.

After the version has been added to the Releases list, RC versions can be submitted for approval. Someone from Mi Casa Verde will have a look at the plugin and check for malicious code, and test it a little to make sure that it doesn't affect the stability or proper functioning of MiOS. If everything is OK, the plugin will be approved and it will become available to install for the targeted public (selected in the ''Visibility'' drop-down).

====Versions====
Versions are snapshots of the plugin, i.e. how the plugin looked at a particular SVN revision. It's recommended to create a version for every milestone or development phase reached, so that you can go back to it if something went wrong in the subsequent revisions.

====Publish====
Here you can publish the plugin in its current state and assign it a version. The comments will be added after the version so that you can create versions like ''1.4 Holiday Edition''. If a file contains sensitive data (e.g. a PIN code) it is recommended to encrypt it.

Upgrade AEON-labs usb dongle firmware

2011-08-19T20:04:16Z

Henk: updated

[[Category:How To]]

'''HOW TO Upgrade the z-wave firmware of your AEON-Labs usb dongle'''

==Prerequisites==
* 1 Firmwareupgradeable AEON-LAbs usb dongle (DSA02203-ZWUS/EU/AU)
* The VCP driver kit for your client (Windows / Linux / MacOS)
* Most recent compatible firmware from AEON-Labs

==Introduction==
Here's a short manual on how to upgrade the z-wave firmware on an AEON-Labs USB dongle.

==Instructions==
1. Unplug your Black Zwave dongle from Vera's USB port. 
2. Locate its part number (it's written on the back of it). If it's: DSA02203-ZWUS/EU proceed further. 

3. The procedure can be done only on a Windows PC from an account that has Administrative privileges (Administrator account). 
3.1. To see the type of your account go to: Start->Control Panel->Users (User Accounts) 
3.2. If you are an "Limited Account" you can't proceed further. Log-out and login into an account that is "Computer Administrator" 

IF NEEDED
4. Download the drivers for the Zwave Stick: 
4.1. Go to: http://www.aeon-labs.com/site/products/view/2 
4.2. Download VCP Driver Kit : 
For direct downloads see links below for Windows 2000/XP/2003/Vista, Windows 7, Linux or MacOS
4.3. If you don't have an unzip program (a program to extract the zip archive) grab 7zip from here: http://www.7-zip.org/ 
4.3.1. Download and install the latest version 
4.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe 
4.4.1. Install the Drivers. 

5. Plug the black Zwave dongle in your PC USB PORT 

6. Download the Upgrade Utility: http://www.aeon-labs.com/site/products/view/2/ or here http://www.aeon-labs.com/site/support/view/18/ 
For direct downloads see links below for US, EU and AU versions.
6.1. Run it 
7. Keep pressed the Zwave Stick button and press the UPGRADE button on the utility 

Note: If you get a message that the Zwave stick is not found you should set a correct baud rate also:

- Start -> My Computer: right click on it and then Device Manager 
- In Device Manager - expand Ports and right click on Silicon Labs CP210x USB to UART Bridge then Properties. 
- in this windows go to Port Settings and set: 
Bits per second: 115200
Data bits: 8 Parity: None
Stop bits: 1
Flow Control: none

==References==
please find more info here:
http://forum.micasaverde.com/index.php?topic=2857.0 
http://forum.mios.com/index.php?topic=2857.msg11457#msg11457 

==Downloads==
Firmwares: 
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21 
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22 
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38 

Driver kits: 
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23 
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24 
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25 
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26

Vera2 with zwave usbdongle

2011-08-18T14:53:31Z

Henk:

[[Category:How To]]

'''HOWTO use a Z-wave dongle with your Vera 2 hardware'''

==Prerequisites==
* Vera 2 hardware
* A compatible Z-wave USB dongle

==Introduction==
Here's a short description on how to us a dongle with Vera 2. Vera 2 has an internal z-wave chip. However an external dongle can still be used.

The dongle is plugged into one of Vera's USB ports and contains a Z-Wave chip that communicates to your Z-Wave devices. Also, when you pair Vera to Z-Wave devices (that is, 'Add' Z-Wave devices), that pairing information is stored in the dongle. So, if you ever need to replace your dongle, you'll have to reset the Z-Wave devices and add them again or use the internal chip of your Vera to do this again.

==Instructions==
1. From the dashboard go to Z-Wave, Options and look for port. /dev/tts/1 (this is the address for the internal chip)

To switch to USB Z-Wave you will need to change that address to (0 being the bottom usb slot and 1 being the top).

/dev/usb/tts/0

or

/dev/usb/tts/1

2. Edit the address to whatever USB slot you are using, and don't forget the first forward slash!

==References==
please find more info in the forum here:

http://forum.mios.com/index.php?topic=4761
http://forum.mios.com/index.php?topic=7030

Upgrade AEON-labs usb dongle firmware

2011-08-18T14:50:51Z

Henk:

[[Category:How To]]

'''HOW TO Upgrade the z-wave firmware of your AEON-Labs usb dongle'''

==Prerequisites==
* 1 Firmwareupgradeable AEON-LAbs usb dongle (DSA02203-ZWUS/EU)
* The VCP driver kit for your client (Windows / Linux / MacOS)
* Most recent compatible firmware from AEON-Labs

==Introduction==
Heres a short manual on how to upgrade the z-wave firmware on an AEON-Labs us dongle.

==Instructions==
1. Unplug your Black Zwave dongle from Vera's USB port. 
2. Locate it's part number (it's written on the back of it). If it's: DSA02203-ZWUS/EU proceed further. 

3. The procedure can be done only on a Windows PC from an account that has Administrative privileges (Administrator account). 
3.1. To see the type of your account go to: Start->Control Panel->Users (User Accounts) 
3.2. If you are an "Limited Account" you can't proceed further. Log-out and login into an account that is "Computer Administrator" 

4. Download the Windows drivers for the Zwave Stick: 
4.1. Go to: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx 
4.2. Download VCP Driver Kit : 
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23 
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24 
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25 
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26 
4.3. If you don't have an unzip program (a program to extract the zip archive) grab 7zip from here: http://www.7-zip.org/ 
4.3.1. Download 7-Zip 4.65 http://downloads.sourceforge.net/sevenzip/7z465.exe 
4.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe 
4.4.1. Install the Drivers. 

5. Plug the black Zwave dongle in your PC USB PORT 

6. Download the Upgrade Utility: http://www.aeon-labs.com/site/products/view/2/ 
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22 
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21 
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38 
6.1. Run it 
7. Keep pressed the Zwave Stick button and press the UPGRADE button on the utility 

Note: If you get a message that the Zwave stick is not found you should set a correct baud rate also:

- Start -> My Computer: right click on it and then Device Manager 
- In Device Manager - expand Ports and right click on Silicon Labs CP210x USB to UART Bridge then Properties. 
- in this windows go to Port Settings and set: 
Bits per second: 115200
Data bits: 8 Parity: None
Stop bits: 1
Flow Control: none

==References==
please find more info here;
http://forum.micasaverde.com/index.php?topic=2857.0 
http://forum.mios.com/index.php?topic=2857.msg11457#msg11457 

==Downloads==
Firmwares;
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22 
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21 
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38 

Upgrade utility:
http://www.aeon-labs.com/Z-Stick_US_502P3_091124.exe 

Driver kits:
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23 
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24 
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25 
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26

Upgrade AEON-labs usb dongle firmware

2011-08-18T14:49:12Z

Henk:

[[Category:How To]]

'''HOW TO Upgrade the z-wave firmware of your AEON-Labs usb dongle'''

==Prerequisites==
* 1 Firmwareupgradeable AEON-LAbs usb dongle (DSA02203-ZWUS/EU)
* The VCP driver kit for your client (Windows / Linux / MacOS)
* Most recent compatible firmware from AEON-Labs

==Introduction==
Heres a short manual on how to upgrade the z-wave firmware on an AEON-Labs us dongle.

==Instructions==
1. Unplug your Black Zwave dongle from Vera's USB port. 
2. Locate it's part number (it's written on the back of it). If it's: DSA02203-ZWUS/EU proceed further. 
3. The procedure can be done only on a Windows PC from an account that has Administrative privileges (Administrator account). 
3.1. To see the type of your account go to: Start->Control Panel->Users (User Accounts) 
3.2. If you are an "Limited Account" you can't proceed further. Log-out and login into an account that is "Computer Administrator" 
4. Download the Windows drivers for the Zwave Stick: 
4.1. Go to: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx 
4.2. Download VCP Driver Kit : 
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23 
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24 
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25 
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26 
4.3. If you don't have an unzip program (a program to extract the zip archive) grab 7zip from here: http://www.7-zip.org/ 
4.3.1. Download 7-Zip 4.65 http://downloads.sourceforge.net/sevenzip/7z465.exe 
4.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe 
4.4.1. Install the Drivers. 
5. Plug the black Zwave dongle in your PC USB PORT 
6. Download the Upgrade Utility: http://www.aeon-labs.com/site/products/view/2/ 
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22 
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21 
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38 
6.1. Run it 
7. Keep pressed the Zwave Stick button and press the UPGRADE button on the utility 

Note: If you get a message that the Zwave stick is not found you should set a correct baud rate also:

- Start -> My Computer: right click on it and then Device Manager 
- In Device Manager - expand Ports and right click on Silicon Labs CP210x USB to UART Bridge then Properties. 
- in this windows go to Port Settings and set: 
Bits per second: 115200
Data bits: 8 Parity: None
Stop bits: 1
Flow Control: none

==References==
please find more info here;
http://forum.micasaverde.com/index.php?topic=2857.0 
http://forum.mios.com/index.php?topic=2857.msg11457#msg11457 

==Downloads==
Firmwares;
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22 
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21 
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38 

Upgrade utility:
http://www.aeon-labs.com/Z-Stick_US_502P3_091124.exe 

Driver kits:
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23 
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24 
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25 
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26

Upgrade AEON-labs usb dongle firmware

2011-08-18T13:08:37Z

Henk: HOW TO Upgrade the z-wave firmware of your AEON-Labs usb dongle

[[Category:How To]]

'''HOW TO Upgrade the z-wave firmware of your AEON-Labs usb dongle'''

==Prerequisites==
* 1 Firmwareupgradeable AEON-LAbs usb dongle (DSA02203-ZWUS/EU)
* The VCP driver kit for your client (Windows / Linux / MacOS)
* Most recent compatible firmware from AEON-Labs

==Introduction==
Heres a short manual on how to upgrade the z-wave firmware on an AEON-Labs us dongle.

==Instructions==
1. Unplug your Black Zwave dongle from Vera's USB port.
2. Locate it's part number (it's written on the back of it). If it's: DSA02203-ZWUS/EU proceed further.
3. The procedure can be done only on a Windows PC from an account that has Administrative privileges (Administrator account).
3.1. To see the type of your account go to: Start->Control Panel->Users (User Accounts)
3.2. If you are an "Limited Account" you can't proceed further. Log-out and login into an account that is "Computer Administrator"
4. Download the Windows drivers for the Zwave Stick:
4.1. Go to: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
4.2. Download VCP Driver Kit :
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26
4.3. If you don't have an unzip program (a program to extract the zip archive) grab 7zip from here: http://www.7-zip.org/
4.3.1. Download 7-Zip 4.65 http://downloads.sourceforge.net/sevenzip/7z465.exe
4.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe
4.4.1. Install the Drivers.
5. Plug the black Zwave dongle in your PC USB PORT
6. Download the Upgrade Utility: http://www.aeon-labs.com/site/products/view/2/
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38
6.1. Run it
7. Keep pressed the Zwave Stick button and press the UPGRADE button on the utility

Note: If you get a message that the Zwave stick is not found you should set a correct baud rate also:

- Start -> My Computer: right click on it and then Device Manager
- In Device Manager - expand Ports and right click on Silicon Labs CP210x USB to UART Bridge then Properties.
- in this windows go to Port Settings and set:
Bits per second: 115200
Data bits: 8 Parity: None
Stop bits: 1
Flow Control: none

==References==
please find more info here;
http://forum.micasaverde.com/index.php?topic=2857.0
http://forum.mios.com/index.php?topic=2857.msg11457#msg11457

==Downloads==
Firmwares;
EU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=22
US: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=21
AU: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=38

Upgrade utility:
http://www.aeon-labs.com/Z-Stick_US_502P3_091124.exe

Driver kits:
Windows 2000/XP/2003/Vista: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=23
Windows 7: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=24
Linux: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=25
MacOS: http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=26

Vera2 with zwave usbdongle

2011-08-18T10:22:41Z

Henk: How to use Vera2 with an external Z-wave USB dongle

[[Category:How To]]

'''HOWTO use a Z-wave dongle with your Vera 2 hardware'''

==Prerequisites==
* Vera 2 hardware
* A compatible Z-wave USB dongle

==Introduction==
Here's a short manual on how to us a dongle with Vera 2. Vera 2 has an internal z-wave chip. However an external dongle can still be used.

The dongle is plugged into one of Vera's USB ports and contains a Z-Wave chip that communicates to your Z-Wave devices. Also, when you pair Vera to Z-Wave devices (that is, 'Add' Z-Wave devices), that pairing information is stored in the dongle. So, if you ever need to replace your dongle, you'll have to reset the Z-Wave devices and add them again or use the internal chip of your Vera to do this again.

==Instructions==
1. From the dashboard go to Z-Wave, Options and look for port. /dev/tts/1 (this is the address for the internal chip)

To switch to USB Z-Wave you will need to change that address to (0 being the bottom usb slot and 1 being the top).

/dev/usb/tts/0

or

/dev/usb/tts/1

2. Edit the address to whatever USB slot you are using, and don't forget the first forward slash!

==References==
please find more info in the forum here:

http://forum.mios.com/index.php?topic=4761
http://forum.mios.com/index.php?topic=7030

Main Page

2011-08-18T10:04:31Z

Henk:

[[Category:Glossary]] [[Category:User_Instructions]] [[Category:How_To]] [[Category:Troubleshooting]] [[Category:Plugins]] [[Category:Hardware]]
 
<big>'''Welcome to the Mi Casa Verde (MiOS) wiki'''</big>
----
'''*Note:''' The Wiki documentation is for both '''Vera 1''' and '''Vera 2''' units with '''UI2''' and '''UI4''' interface and all future hard and software releases.
 
=Wiki User Instructions=
This Wiki provides a lot of information on your Vera, including [[:Category:User Instructions|User Instructions]].

==Getting started==
If you are new to Vera and MiOS (former Mi Casa Verde) please check our pages on getting started, basic installation and use of menu's etc.
The pages are to be found at '''"docs.mios.com" for the older Vera UI2''' or at '''"docs2.mios.com" for the more recent Vera UI4'''. 
This last page can also be reached by clicking [http://docs2.mios.com/doc.php?language=1&manual=1&platform=0&page=preface here]. Also the homepage of MIOS provides a basic setup guide for Vera [http://www.micasaverde.com/setting-up.php here]

Vera uses custom software that can be upgraded. The latest information on features and bugfixes can be found [[Release_Notes | here]].

==FAQ, HOWTO and Troubleshooting==
There are separate pages containing Frequently Asked Questions, simple pages explaining "How To" and a section on troubleshooting.
 
Here is a link to the [[FAQ]] and initial [[Troubleshooting]] pages. 
Here is a link to the [[:Category:How To|How To]] section. 
Here is a link to the [[:Category:Troubleshooting|Troubleshooting]] section. 

==Supported Hardware==
There is a list of supported hardware available on the wiki. This list is being kept current by and for users. Please contribute to the list if you have working hardware that has not been listed here.
 
Here is the link to the [[Supported_Hardware|supported hardware]] list.

==Luup code and Plugins==
There are already various Luup coded plugins and code examples available for users. 
You can find more information about that here [[Luup_plugins_and_Luup_code|Overview of Plugins]]

=Categories=
Information and pages on the Wiki are put into categories to keep information on a certain subject together. 
Please click [[Special:Categories|here]] for all categories.

=All Pages=
See the [[Special:AllPages|overview of all Pages]] for a list of all pages.
 
----
'''For most used categories, see the links below'''

Set up of Notifications

2011-07-31T15:29:52Z

Henk:

[[Category:User Instructions]]
[[Category:Services]]
[[Category:How To]]

'''HOWTO on setting up email notifications and text notifications to your mobile phone'''

==Prerequisites==

* Vera 1 or 2 hardware
* Account for remote acces here [https://cp.mios.com/login.php]
* Personal emailaddress and/or mobile phone

==Introduction==

Vera supports the automated sending of notifications.
It will send either email messages upon a preset event or even send text messages to your mobile phone.
To use notifications you will have to create an account at https://cp.mios.com/login.php
This account will also provide you remote acces to your Vera.
How to use remote acces is explained here [http://wiki.micasaverde.com/index.php/Secure_Remote_Access] and here [http://wiki.micasaverde.com/index.php/Secure_Remote_Access_TechInfo]. Please keep in mind these pages are a bit outdated and the mentioned findvera pages will not work anymore.
Instead please use https://cp.mios.com/login.php

==Instructions==

# Login to https://cp.mios.com/login.php with your earlier created account.
# Go to the "My Contact Info" tab.
# Enter your emailaddress and/or your mobile phonenumber in the corresponding fields.
# Tick the boxes for the type of notifications you want to receive (email and/or text messages).
# Click the <Save my contact info" button.
# Login to your Vera's UI (either remote or locally).
# Select any device or scene you want to create a notification for by clicking the wrench icon.
# Select the Events tab of the device or scene you are editing.
# Click the "Add Event" button and make all the selections of your choice.
# Click "Back"
# Tick the box of users you want to notify.
# Close the device or scene and click "Save" in the upper right corner of your UI.

Notifications are now set up.

==For Iphone users==

You could also setup growl/prowl notifications. Please find more info in this thread on the forum [http://forum.micasaverde.com/index.php?topic=4508.0]

==For Android users==

You could use an app called "Home Buddy". Please find more info in this thread on the forum [http://forum.micasaverde.com/index.php?topic=292.0]

==References==

Please find more info; 
On users here [http://wiki.micasaverde.com/index.php/Users] 
Tech info on notifications here [http://wiki.micasaverde.com/index.php/Notification_Tech_Info] 
On using notifications in security here [http://wiki.micasaverde.com/index.php/Intro_Security] 
On setting up events with notifications here [http://wiki.micasaverde.com/index.php/Set_Up_Events]

Main Page

2011-07-31T15:28:53Z

Henk:

[[Category:Glossary]] [[Category:User_Instructions]] [[Category:How_To]] [[Category:Troubleshooting]] [[Category:Plugins]] [[Category:Hardware]]
 
<big>'''Welcome to the Mi Casa Verde (MiOS) wiki'''</big>
----
'''*Note:''' The Wiki documentation is for both '''Vera 1''' and '''Vera 2''' units with '''UI2''' and '''UI4''' interface.
 
=Wiki User Instructions=
This Wiki provides a lot of information on your Vera, including [[:Category:User Instructions|User Instructions]].

==Getting started==
If you are new to Vera and MiOS (former Mi Casa Verde) please check our pages on getting started, basic installation and use of menu's etc.
The pages are to be found at '''"docs.mios.com" for the older Vera UI2''' or at '''"docs2.mios.com" for the more recent Vera UI4'''. 
This last page can also be reached by clicking [http://docs2.mios.com/doc.php?language=1&manual=1&platform=0&page=preface here]. Also the homepage of MIOS provides a basic setup guide for Vera [http://www.micasaverde.com/setting-up.php here]

==FAQ, HOWTO and Troubleshooting==
There are separate pages containing Frequently Asked Questions, simple pages explaining "How To" and a section on troubleshooting.
 
Here is a link to the [[FAQ]] and initial [[Troubleshooting]] pages. 
Here is a link to the [[:Category:How To|How To]] section. 
Here is a link to the [[:Category:Troubleshooting|Troubleshooting]] section. 

==Supported Hardware==
There is a list of supported hardware available on the wiki. This list is being kept current by and for users. Please contribute to the list if you have working hardware that has not been listed here.
 
Here is the link to the [[Supported_Hardware|supported hardware]] list.

==Luup code and Plugins==
There are already various Luup coded plugins and code examples available for users. 
You can find more information about that here [[Luup_plugins_and_Luup_code|Overview of Plugins]]

=Categories=
Information and pages on the Wiki are put into categories to keep information on a certain subject together. 
Please click [[Special:Categories|here]] for all categories.

=All Pages=
See the [[Special:AllPages|overview of all Pages]] for a list of all pages.
 
----
'''For most used categories, see the links below'''

Secure Remote Access TechInfo

2011-07-31T15:24:35Z

Henk:

[[Category:User Instructions]]
[[Category:Services]]
We have made it a top priority to provide customers a safe way to remotely control their Vera that is easy for the customer, but at the same time is secure and does not expose the customer to hackers and other security risks. This page provides technical details about the security measures we have implemented so we are subject to peer review. We have provided a 'Security concerns' forum at [http://forum.micasaverde.com forum.micasaverde.com] for uncensored discussion about security concerns.

Vera listens on two network ports: port 80 is the normal web interface, and port 3451 is for a special control protocol. When Vera boots up, if the network settings have not been changed manually, Vera first checks if the IP address is an internal IP address (i.e. starts with 192.168, 10. or 172.x), and whether there is a valid internet connection. Vera does this by pinging a couple of common servers, such as google, youtube, and micasaverde, to confirm that it gets unique addresses for each domain name and that at least 2 of the 3 servers respond. If Vera has an internal IP address and a valid internet connection, all 5 ports on Vera go into 'switch' mode, meaning they're effective bridged, and there is no firewall. Thus Vera is open for access from another system on the same home network. If Vera has an external, or routable IP address, Vera goes into 'gateway' mode: The WAN and LAN ports are separated, a firewall is setup, a DHCP server runs on the LAN ports providing addresses in the 192.168.81.x range, and Vera only accepts incoming connections on ports 80 and 3451 from the LAN ports. Thus, only PC's within the home would be able to access Vera, and nothing external, unless the homeowner changes the network settings or sets up a port forward through the main router's firewall. Vera's built-in Wi-Fi is enabled by default, which allows users into the system wirelessly. So we ship Vera with WPA2 encryption turned on, and a random Wi-Fi password consisting of two dictionary words plus a number, which is printed on the bottom of Vera.

Each Vera has two unique hardware keys which are stored in the NVRAM (non-volatile memory) and assigned at the factory along with the serial number and the domain name for the remote access server that Vera will use. Only the remote access server for a particular Vera has a database with the serial numbers and hardware keys. When the user goes to the [http://findvera.com FindVera.com] tab on his setup page (i.e. from within the home) and activates the service, his username and an MD5 hash (security checksum) of the password, along with the serial number and hardware key, are sent to the remote access server using the https: (SSL encryption) protocol. The remote access server validates the connection by checking whether the serial number and hardware key match, and if so, replies with a port number that the Vera unit can use for remote access.

The Vera then uses ssh with a pre-defined ssh username and shared key to make a connection to the remote access server. The remote access server only accepts incoming ssh connections from that username with that shared key. And ssh is configured on the server so that when a connection comes in, rather than giving the ssh user a console (i.e. bash), it runs a script that requires the serial number and hardware key be sent in within 10 seconds. If they are, and they match, and the right port number was used, the ssh connection is authorized. If there is a mis-match, a log is filed with the incoming external IP address so we can add a block to this IP in the firewall in case this is a DOS (denial of service) or similar attack. The SSH connection includes a port forward of ports 80 and 3451 using the standard ssh port forward mechanism. This port forward does not allow 'gateway', that is, the ports are only accessible from within the remote access server.

NetworkMonitor runs on Vera and calls a php page on the remote access server using https, passing in the serial number and hardware key, which does a loop back test to ensure the ssh tunnel is active. If it's not, NetworkMonitor shuts it down and re-opens it.

When first logging on through [http://FindVera.com FindVera.com], the user is redirected to the remote access server, which only accepts secure (https) connections. Once the remote access server validates the username and password, then the php page on the control tab effectively acts as a gateway to the customer's Vera. It passes requests between the SSL connection and port 80 and port 3451 that are forwarded from the ssh connection on Vera by looking up the ports that are associated with that username.

It should also be noted that we purposely never ask users for their home address so that if the remote access server ever were compromised, nobody would know the address of the Vera units.

Camera Management Server

2011-07-31T15:22:31Z

Henk:

[[Category:Services]]
Certain cameras come with custom firmware so that they automatically connect to the MiOS camera management server (cms), creating a tunnel the cms can use to send commands to the camera and to act as a relay so users can view and control the camera when outside the home without having to change their firewall.

Mios operates a camera server ("cs") which is available at crX.mios.com (ie cr1.mios.com, cr2.mios.com, etc.). Cameras which are shipped with this custom firmware will automatically connect to the cs and report their Mac Address and IP address. Cs stores this in a database along with the external IP that the connection came in on.

==Locating the camera==

To get the list of all cameras and MiOS systems on your current home network, read this URL: http://sta1.mios.com/locator_json2.php which returns the list in JSON format. To add to the list all cameras that are off the home network but which can be access remotely with a given username, add a ?username=x to the URL, such as http://sta1.mios.com/locator_json2.php?username=johndoe

A camera will look like this:

{
"serialNumber": "554",
"Alive": 0,
"name": "Good camera",
"mfr": "Mios",
"ipAddress": "192.168.2.27",
"category": "2",
"subcategory": "1",
"users": "16782,3",
"ImageUrl_LR": "img/snapshot.cgi?size=320x240&quality=4",
"MJpegUrl_LR": "img/video.mjpeg",
"MP4Url_LR": "img/video.asf",
"ImageUrl_HR": "img/snapshot.cgi?size=640x480&quality=2",
"MJpegUrl_HR": "img/video.mjpeg",
"MP4Url_HR": "img/video.asf",
"CanRelay": "1",
"Port": "80",
"local_remote": "1",
"relay_remote": "1",
"active_server": "cr1.mios.com"
}

==Local vs remote access==

In the Json data above, "active_server" tells you which Cs the camera connects to. So to view or control this camera connect to cr1.mios.com. If the camera is on the same network as the client, then ipAddress will have an ip. Otherwise there is no ipAddress. If the ipAddress is specified, then you can access the camera on the local network, without going through the relay server, by using ImageUrl, MJpegUrl and MP4Url tags to fetch a JPEG Image, MJPEG stream, or MP4 stream. _LR are low res verseions, _HR are high res. If CanRelay is 1, then this camera connects to the cs and you can also view the camera remotely using the Cs.

==request_video: Request video from a camera==

To view the video from the camera, open this URL:

https://cr1.mios.com/request_video?cam=a&format=b&res=c&user=d&pass=e

where a is the serial number of the camera, 554 in the above example, b is "mp4" or "mjpeg", c is the resolution and can be "low" or "med" or "high", d and e are the username/password of the MiOS account the camera is paired with.

This will return another URL. If the viewer is on the same home network as the camera the URL will point directly to the camera. Otherwise it will be a Url, for example http://209.160.41.93:80/relay_viewer?cam=554&pass=2024848122, which points to the Cs with a use-once token. In this case the URL can only be used one time, and must be used within 1 minute of making the request.

==request_image: Request image from a camera==

To fetch a JPEG that is the current image from the camera, open this URL:

https://cr1.mios.com/request_image?cam=a&res=b&user=c&pass=d

where a is the serial number of the camera, 554 in the above example, b is "low" or "med" or "high" to indicate the resolution, c and d are the username/password of the MiOS account the camera is paired with. Calling this with "low" is the right way to get at thumbnail. This URL returns the JPEG image directly.

==archive_video: Tells the cs to archive video from the camera ==

This command causes the cs to capture video from the camera and add it to the video archive for the user. The camera must be linked to a mios.com account.

https://cr1.mios.com/archive_video?cam=a&preroll=b&duration=c&format=d&res=e&user=f&pass=g

where a is the serial number of the camera, 554 in the above example, b is 0 or 1 where 1 means to also capture whatever pre-roll is available from the camera, c is how long in seconds to capture the video, d is "mp4" or "mjpeg", e is "low" or "med" or "high" to indicate the resolution, f and g are the username/password of the MiOS account the camera is paired with.

The pre-roll is a given number of seconds at a given resolution as specified in the "config" command.

==archive_image: Tells the cs to archive an image from the camera ==

This is like archive_video except it stores a single image. If retimg=1 then the image being archived will also be returned by the Url, just like request_image.

https://cr1.mios.com/archive_image?cam=a&res=b&user=c&pass=d&retimg=e

==move_camera: Tells the cs to move the camera ==

https://cr1.mios.com/move_camera?cam=a&dir=b&user=c&pass=d

Where dir can be "up", "down", "left", "right", "in" or "out" (for zoom).

==config: Sets a configuration setting on the camera ==

https://cr1.mios.com/config?cam=a&setting=b&value=c&user=d&pass=e

This sets the setting (b) to the value (c). The possible setting/values are:

brightness: 0-100 for brightness control
contract: 0-100 for contrast

USB swapfile creation

2011-07-05T20:32:18Z

Henk:

[[Category:How To]]

'''HOWTO set up a memory swapfile on a USB stick'''

'''*NOTE''' This feature should only be set up by users with large z-wave networks and some knowledge of Linux internal commands.
The functionality has been tested by some beta testers if the userforum at http://forum.mios.com, but using the feature should still be done with caution.

==Prerequisites==
* Vera 2 hardware
* Vera firmware 1.1.1245 or later
* USB stick attached to Vera

==Introduction==
Heres a short manual on how to set up a memory swap file on a USB stick to allocate more memory for your Vera.
This is an additional feature once you have set up USB logging for Vera as described here: [[Store_logs_USB]]

The instructions contain commands for 4 indivudual steps.

Data description for 64Mb swapfile
Creating swapfile
Start using swapfile
Stop using a swapfile.

Please note that rebooting Vera will require a manual start of the swapfile.
Upgrading Vera's firmware will require setting up the swapfile from scratch as per instructions below.

==Instructions==
To set up a swapfile for Vera to use after you have have enabled to store logs on a USB stick as described here: [[Store_logs_USB]] it is required
to SSH into your Vera. This procedure is explained here: [[Logon_Vera_SSH]].

Once you are at the SSH commandline, enter these commands one by one.
Please note that the forst command can take a few minutes to complete, depending on the speed of your USB stick.

1. Data description for 64Mb swapfile for the filesystem:
dd if=/dev/zero of=/tmp/log/cmh/swapfile bs=1024 count=65536

2. Creating the actual swapfile:
mkswap /tmp/log/cmh/swapfile

3. Start using the newly created swapfile:
swapon /tmp/log/cmh/swapfile

If for some reason you would like to stop Vera using the swapfile use the following command after SSH-ing into Vera:
swapoff /tmp/log/cmh/swapfile

==References==
please find more info here: 
http://wiki.openwrt.org/doc/howto/usb.storage

Luup plugins: Static JSON file

2011-07-03T16:57:41Z

Henk:

[[Category:Development]]

Starting in UI4, Luup plugins can specify a ''static JSON'' file. This file describes how the plugin appears in the web interface.

=What the static JSON file controls=

* The icon used by the plugin in the dashboard.
* The text that displays in the one-to-two-row status message in the dashboard.
* Whether the icon changes depending on the value of a variable in the device (for example, a binary light's icon changes from lit to unlit).
* The tabs that appear in the device's detail dialog (when you click the wrench/spanner).
* The content of these tabs.

=Referencing the static JSON file from the Device XML file=

The device XML file (customarly '''D_PluginName.xml''') contains a reference to the static JSON file, in the '''staticJson''' element. Place the element as a child of the '''device''' element:

<pre><nowiki>
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion></specVersion>
<device>
<deviceType>urn:schemas-futzle-com:device:holidayvirtualswitch:1</deviceType>
<staticJson>D_HolidayVirtualSwitch1.json</staticJson>

</nowiki></pre>

Capitalization is important, as with all XML.

The static JSON file is customarily called '''D_PluginName.json'''.

=The static JSON file=

The static JSON file is a single JSON object (associative array).

==Root keys==

These keys have been seen at the top level in static JSON files in the wild:

; flashicon
: The device's icon, as a string. Despite the name, the icon is not related to Flash in UI4. See [[Luup plugin icons]].
; imgIconBody
: A string which appears to have no effect.
; imgIconDimmable
: A string which appears to have no effect.
; imgIconTurnable
: A string which appears to have no effect.
; imgIconMin
: A string which appears to have no effect.
; imgIconMax
: A string which appears to have no effect.
; halloIconsDir
: A string which appears to have no effect. Usually contains "pics\/hallo", for reasons unknown.
; DisplayStatus
: A JSON object (associative array). For devices where the icon changes based on a variable's value, describes which variable, and the range of values that produce different icon images. See [[Luup plugin icons]].
; doc_url
: A JSON object (associative array). Appears to have no effect.
; Tabs
: A JSON array. Describes the tabs in the detail dialog, and what subset of the first tab appears in the dashboard. See [[Luup plugin tabs]].
; DeviceType
: A JSON string. Must match the '''deviceType''' element in the corresponding device XML ('''D_PluginName.xml''') file.
; eventList
: A JSON object (associative array). Describes the events that this plugin can produce. Events are triggers that can fire off actions in scenes. See [[Luup plugin event list]].
; sceneList
: A JSON object (associative array). Describes the actions that this plugin can perform (for instance, as the action in a scene). See [[Luup plugin scenes]].

Luup plugin tabs

2011-07-03T16:57:20Z

Henk:

[[Category:Development]]

The '''Tabs''' key in the [[Luup_plugins:_Static_JSON_file|static JSON file]] performs two duties in the UI4 HTML interface:
* It controls how the device appears in the dashboard.
* It controls how each tab appears in the the device's detailed dialog.

The value of the '''Tabs''' key is a JSON array. Each array element is a JSON object (associative array).

=Required tab fields=

These fields must be present in each JSON object in the tab list:

; '''Label'''
: A JSON object containing two keys: '''lang_tag''' (a string) is not displayed in the HTML interface but may be used by localized UIs; '''text''' (a string) is displayed in the tab's handle at the top of the dialog.
; '''Position'''
: A string which contains a number matching the relative position of this tab in relation to the other tabs. The leftmost tab has value "0", the next tab "1", and so on.
; '''TabType'''
: A string which describes how the content of the tab is to be generated. The value may be one of '''javascript''' or '''flash'''. These are described in the following sections.

==TabType javascript==

The '''javascript''' tab type executes client-side JavaScript, producing an HTML fragment which forms the body of the tab. These additional keys are required in the tab JSON object:

; '''ScriptName'''
: The name of the JavaScript file. Conventionally, plugin JavaScript files are named '''J_PluginName.js'''.
; '''Function'''
: The function inside the JavaScript file which will be called to produce the HTML.

The JavaScript code has access to most Luup variables through the [[JavaScript API]].

==TabType flash==

The '''flash''' tab type creates a tab body with a simple page-description language. Each component of the page is placed into the body at the position specified. These additional keys are required in the tab JSON object:

; '''Control'''
: A JSON array containing each item on the page. Described below.
; '''ControlGroup'''
: Required only if the first tab is also used to display elements on the dashboard. See ''Dashboard appearance'' below.

The '''Control''' array contains JSON objects (associative arrays), one per item in the tab body. An item is either a static text label, a variable, an input field, or a button or slider. This is handled by setting the '''ControlType''' key on the object.

===ControlType label===

With '''ControlType''' set to '''label''', a fixed label is placed at the specified coordinates. The following additional keys must also be provided:

; '''Label'''
: A JSON object with two keys: '''lang_tag''' is not displayed but can be used by localizing interfaces to translate the label text. '''text''' is displayed as the content of the label.
; '''Display'''
: A JSON object with four keys: '''Top''', '''Left''', '''Width''', '''Height''' (all strings containing numbers). This controls where the label is placed in the tab.

===ControlType variable===

With '''ControlType''' set to '''variable''', the contents of a Luup variable are displayed at the specified coordinates. The following additional keys must also be provided:

; '''Display'''
: A JSON object with six keys: '''Top''', '''Left''', '''Width''', '''Height''' (all strings containing numbers, controlling where the variable's value is placed in the tab), '''Service''' (a string containing the Service Id of the variable to be displayed), and '''Variable''' (a string containing the name of the variable to be displayed).

===ControlType input===

With '''ControlType''' set to '''input''', a text box for the user to type a string is placed in the tab. The following additional keys must also be provided:

; '''ID'''
: A string which other controls (buttons) will use to refer to the string that the user has typed into this field.
; '''Display'''
: A JSON object with four keys: '''Top''', '''Left''', '''Width''', '''Height''' (all strings containing numbers). This controls where the text box is placed in the tab.

===ControlType button===

With '''ControlType''' set to '''button''', a clickable button is placed at the specified coordinates. The button will appear selected (depressed) or unselected based on the value of a variable, permitting sets of buttons to act as radio buttons. The following additional keys must also be provided:

; '''Label'''
: A JSON object with two keys: '''lang_tag''' is not displayed but can be used by localizing interfaces to translate the label text. '''text''' is displayed as the text inside the button.
; '''Display'''
: A JSON object with up to seven keys: '''Top''', '''Left''', '''Width''', '''Height''' (all strings containing numbers, controlling where the button is placed in the tab), '''Service''' (a string containing the Service Id of a variable), and '''Variable''' (a string containing the name of a variable), and (optionally) '''Value''' (a string, "1" if omitted). The specified variable's value controls whether the button appears selected (if the variable matches '''Value''') or not selected (if the variable doesn't match).
; '''Command'''
: A JSON object with three keys: '''Service''' (a string containing the service Id of an action that this device can perform), '''Action''' (a string containing the name of the action), and '''Parameters''' (a JSON array of JSON objects, forming the parameters to pass to the action). Each parameter object has a key '''Name''' for the parameter name, and either a key '''Value''' (for a fixed parameter value) or a key '''ID''' matching an input control on the page (for a user-entered parameter value).

===ControlType slider===

With '''ControlType''' set to '''slider''', a draggable slider is placed at the specified coordinates. The following additional keys must also be provided:

; '''Display'''
: A JSON object with nine keys: '''Top''', '''Left''', '''Width''', '''Height''' (all strings containing numbers, controlling where the button is placed in the tab), '''Service''' (a string containing the Service Id of a variable), and '''Variable''' (a string containing the name of a variable), '''MinValue''' and '''MaxValue''' (both strings containing numbers, controlling what range of values the slider takes) and '''ID''' (a string, used in the '''Command''' to refer to the position the user has dragged the slider to). The specified variable's value is used to display the slider's current position.
; '''Command'''
: A JSON object with three keys: '''Service''' (a string containing the service Id of an action that this device can perform), '''Action''' (a string containing the name of the action), and '''Parameters''' (a JSON array of JSON objects, forming the parameters to pass to the action). Each parameter object has a key '''Name''' for the parameter name, and either a key '''Value''' (for a fixed parameter value) or a key '''ID''' matching the slider's ID (for a value matching what the user has dragged the slider to).
; '''ControlHeader'''
: Optional. If present, must have string value "1". When set, the slider's label and value are displayed. Otherwise only the slider is shown. (TODO: This is from reverse-engineering the JavaScript code. Test this.)

=Dashboard appearance=

The first array element in the '''Tabs''' field is special. If it is of type '''flash''' then a subset of the controls on the tab can be chosen to display on the UI4 dashboard.

==Control Groups==

The dashboard box for a device has room for two rows of information and controls. These are called ''Control Groups''.

The tab object must contain the key '''ControlGroup''', which specifies how the dashboard's two available rows of information are to be handled. '''ControlGroup''' is a JSON array containing JSON objects (associative arrays). Each object has the following keys:

; '''id'''
: A string containing a number, "1" for the first object, "2" for the second, and so on.
; '''isSingle'''
: If this key is present and contains the value "1", then this control group is combined with other control groups that have '''isSingle''' similarly set onto the same row. For an example of this, see the On/Off buttons of the Binary Switch and Dimmable Switch static JSON files.
; '''type'''
: If this key is present and contains the value "info", then the controls displayed on this row are not clickable. If this key is absent, buttons may be used in the control group.

==Making a control appear on the dashboard==

All control types (label, variable, button, input, slider) can appear in the dashboard. However, by default, controls in the first tab's detail view do not appear in the dashboard. To make a control's text appear in the dashboard, add a '''ControlGroup''' to the control's JSON object. The value is a string containing a number, matching the '''id''' of one of the Tab's overall '''ControlGroup''' key. The dashboard will concatenate all of a control group's controls in the order they are presented in the '''Control''' array, and display them in a single row of text.

==Keeping controls together==

Some controls may not make sense if presented individually (for instance, an input for an alarm PIN and a "disarm" button). To keep these controls together, add a '''ControlPair''' key to all of the controls that have to appear together. Use the same value (a number in a string) for all of them.

Luup plugin icons

2011-07-03T16:57:00Z

Henk:

[[Category:Development]]

The [[Luup plugins: Static JSON file|Luup plugin static JSON file]] describes the icon that appears in the dashboard of the UI4 web interface.

=Icon format=

All of Vera's icons are 42x42 pixel PNGs with transparency. Icons of other sizes will be resized to 42x42.

=Configuration=

The top-level key '''flashicon''' contains a string. This string is the name of an image file. The filename is either a relative path or a URL starting with "http".

==Relative paths==

If the filename is a relative path, it is relative to the directory '''/www/cmh/skins/default''' on the Vera. If the filename ends in the string ".swf", this extension is changed to ".png". (This is presumably a holdover from UI3, which was flash-based. In UI4, there is no reason to maintain this ruse, so just use the ".png" extension.)

Files installed in the "icons" directory are:
* Binary_Light.png
* Binary_Light_0.png
* Binary_Light_100.png
* Dimmable_Light.png
* Dimmable_Light_0.png
* Dimmable_Light_100.png
* Dimmable_Light_25.png
* Dimmable_Light_50.png
* Dimmable_Light_75.png
* Door_Lock.png
* Door_Lock_0.png
* Door_Lock_100.png
* Generic_IO.png
* Humidity_Sensor.png
* IR_Transmitter.png
* Insteon.png
* Ip_Camera.png
* Light_Sensor.png
* Motion_Sensor.png
* Motion_Sensor_0.png
* Motion_Sensor_100.png
* Power_Meter.png
* Scenes.png
* Temperature_Sensor.png
* Thermostat.png
* USB_UIRT.png
* Window_Covering.png
* Zwave.png
* advanced.png
* default.png
* default_device.png
* default_panel.png
* default_plugins.png
* device.png
* devices.png
* energy.png
* findvera.png
* generic_icon.png
* generic_sensor.png
* intro.png
* location.png
* music_audio.png
* plugins.png
* users.png

== URLs ==

If the filename is a URL, it refers to a remote file on a web server.

=Constant icons=

For an icon that remains the same all the time, the '''flashicon''' key is all you need to provide. Ensure that the static JSON file does not contain a '''DisplayStatus''' key, and you are done.

=Variable icons=

For an icon that varies based on the value of a variable, place a '''DisplayStatus''' key at the top level of the static JSON file. Its value is a JSON object (associative array) with four keys:
; Service
: The Service ID of the variable that controls the icon. This can be found in the matching device XML file, under the '''serviceId''' element.
; Variable
: The variable name of the variable that controls the icon.
; MinValue
: The value that this variable has when it is considered "off" or at "0%". This can even be a string, if the variable is a string that takes two values.
; MaxValue
: The value that this variable has when it is considered "on" or at "100%". This can even be a string, if the variable is a string that takes two values.

Example for a binary switch:

<pre><nowiki>
"DisplayStatus": {
"Service": "urn:upnp-org:serviceId:SwitchPower1",
"Variable": "Status",
"MinValue": "0",
"MaxValue": "1"
}
</nowiki></pre>

Example for a variable which takes on a range of values.

<pre><nowiki>
"DisplayStatus": {
"Service": "urn:upnp-org:serviceId:Dimming1",
"Variable": "LoadLevelStatus",
"MinValue": "0",
"MaxValue": "100"
}
</nowiki></pre>

The filename in '''flashicon''' undergoes a special transformation for variable icons. The extension ".png" is changed to "_0.png", "_25.png", "_50.png", "_75.png" or "_100.png" depending on the value of the service variable, linearly scaled from its range of 0:(MaxValue-MinValue) to 0:100. Values round up; 1-25 produces the "_25" image; 26-50 produces the "_50" image, and so on. For images which are not found (for instance, if the web server returns '''404 Not Found''') the default image is used.

Consequently, at least three images, and as many as six, should be present for variable-icon plugins. For example, if '''flashicon''' contains '''<nowiki>http://example.com/image.png</nowiki>''', the web server must be able to serve:
* '''<nowiki>http://example.com/image.png</nowiki>''' (for when the plugin is loading in the Luup engine)
* '''<nowiki>http://example.com/image_0.png</nowiki>'''
* '''<nowiki>http://example.com/image_100.png</nowiki>'''
and it should be able to serve (if the variable is a sliding scale):
* '''<nowiki>http://example.com/image_25.png</nowiki>'''
* '''<nowiki>http://example.com/image_50.png</nowiki>'''
* '''<nowiki>http://example.com/image_75.png</nowiki>'''

==Cheating to get finer-grained variable icons==

The JavaScript code that inserts the strings "_0" to "_100" into the image filename does not check that the raw variable value is in the range '''MinValue''' to '''MaxValue'''. By deliberately choosing a '''MaxValue''' less than the highest value that a variable can take, you can make the JavaScript load images with "_125", "_150", etc., effectively providing any number of images. '''MinValue''' is similarly handled, though the results are odd with negative variables or MinValue not equal to zero: the string inserted into the filename is "_-25", "-50", etc.

That this trick works is probably accidental, and its behaviour probably should not be relied on.

Aeon HomeEnergyMonitor

2011-07-03T16:55:34Z

Henk:

[[Category:User_Instructions]]
[[Category:Hardware]]
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

Migrate To Z-wave version 452

2011-07-03T16:12:11Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

HOW TO MIGRATE FROM THE OLDER Z-WAVE VERSION (2.78) TO THE NEWER Z-WAVE VERSION (3.20)

'''NOTE: This migration only works with a Vera 2.'''

==Introduction==
Inside your Vera2, or your Vera1's dongle, is a Z-Wave chip. The Z-wave chip inside Vera 2's is upgradeable, meaning Vera can automatically load either the newer or older Z-Wave firmware into the chip.
Z-Wave has its own firmware, separate from Vera's firmware. is that its routing capabilities are improved.
This gives Vera the ability to optimize the Z-Wave network, This is particularly usefull in a large and complex network with lots of Z-Wave devices. 
As of version 3.20 Vera no longer supports inclusion controllers (ie SUC/SIS).
This feature allowed you to add a secondary, handheld (USB) controller to the Z-Wave network, and then include additional Z-Wave nodes using this controller.
We recommend new customers to always use the newer version of Z-Wave. Starting in March, 2011 new Vera's will have the newer Z-Wave version selected by default.

You can change which version Vera uses by selecting the Z-Wave icon in your toolbox, selecting the options tab, and checking the "Use Z-Wave version 3.20 instead of 2.78" box to use the newer Z-Wave, or unchecking it to use the older Z-Wave (2.78), and then saving your changes. 

==Prerequisites==
Officially you have to reset your Z-Wave network and rebuild your network from scratch.
While this is not an issue for a new user or a really small network, some Vera users have large Z-Wave networks already setup with lots of scenes and will not want to redo everything.
Therefore we have developed the following different methods which should work most of the time, and they include making a backup so you can go back if it doesn't work.

Before you upgrade it is recommended you run a Z-Wave repair/heal network, since this will create a reliability rating, or "health score", for all your Z-Wave nodes.
Then after upgrading you can run it again and see if the reliability has improved. To do this, choose the Z-Wave icon from the toolbox, choose the Repair tab, and click 'Go'. 
Depending on the size of your network the process will take anywhere from 1 hour for smaller networks, up to 8 hours for networks with 80+ Z-Wave devices.
It's best to start it at night before going to bed so nobody will be manually using the Z-Wave devices during the test as this can throw the profiling off so the health score is not accurate.
Once the process has completed, return to the Repair tab and you should be able to view the Repair report using the pull-down menu. You can save this and compare after you migrate to the newer Z-Wave firmware.

* Upgrade to the latest Vera firmware. It must be version 1.1.1221 or later (March, 2011).

== Instructions ==
There are two ways to upgrade your z-wave firmware. The first way is to update the firmware and build your network from scratch.
The second way is to upgrade the firmware using the "Hack to convert 2.78 to 3.20" option under the advanced tab of the z-wave device.
This second option allows you to keep your devices and settings without going through the reset z-wave network procedure.

'''*NOTE1, Before continuing, please make sure to backup your dongle/z-wave chip!'''
# After upgrading your Vera to the latest firmware, click the Z-Wave icon, choose the Advanced tab, and click "Backup Dongle". Confirm that within a minute or so you get a Backup: Backup done message in the info panel in the upper right corner of the dashboard, along with a green gear icon.
# Choose the advanced icon from the toolbox and click the Backup tab. Choose the option "Create Backup". This will give you the option of saving a file called "backup.mios2...something". Save this file on your computer somewhere and hold onto it. 

===Update z-wave firmware to the new firmware and build the z-wave network from scratch===
'''*NOTE2, Vera firmware 1.1.1245 currently has a bug preventing the reset to actual clear any devices. Please see the releasenotes here:'''
[[Release_Notes]] 

After Vera has finished changing the Z-Wave firmware, you should choose the "Reset Z-Wave network" button which is on the Advanced tab of the Z-Wave settings. 
This will clear out your entire Z-Wave network, removing all your devices, and starting clean. The reason for this is that the way the newer Z-Wave firmware stores the Z-Wave network data is slightly different. 

If you move from the older to the newer version without doing a reset it is likely you will not be able to add or remove any nodes. 
This "Reset Z-Wave network" resets the network data in either the newer or older format from scratch, so the Z-Wave chip will be ready to go.
More info on bringing Vera bacvk to factory defaults is to be found here: [[Factory_Reset]]

# Go into the Z-Wave option in the toolbox, click the Options tab and choose "Use Z-Wave version 3.20 instead of 2.78".
# You should also check the box "Use MiOS routing instead of Z-Wave (requires 4.5)" and "Limit neighbors to Z-Wave discovery (requries MiOS routing)".
# Close the popup and click Save. Wait about 5 minutes for Vera to finish flashing the firmware, then click the Z-Wave toolbox and choose the Options tab and confirm at the top it says "Version: 3.20".

===Update the z-wave firmware using the "Hack to convert 2.78 to 3.20" option===
Using this method will allow you to keep you current settings, included devices etc.
However, if you only have a limited network it's safer (possibilty of corrupting data) to build the 3.20 network from scratch. 
If you build from scratch, Reset Z-Wave network anyway, this will produce a new House ID and start you with a clean slate. You will have to unpair all your devices in order to include them again. 

# Go into the Z-Wave option in the toolbox, click the Options tab and choose "Use Z-Wave version 3.20 instead of 2.78".
# You should also check the box "Use MiOS routing instead of Z-Wave (requires 4.5)" and "Limit neighbors to Z-Wave discovery (requries MiOS routing)".
# Close the popup and click Save. Wait about 5 minutes for Vera to finish flashing the firmware, then click the Z-Wave toolbox and choose the Options tab and confirm at the top it says "Version: 3.20".
# Reboot or power-cycle your Vera.
# Go back into the z-wave devices settings as you did at step 1. click the options tab and tick the "Hack to convert 2.78 to 3.20" box. 

----
After updating Vera should show this at the top of your options tab of the z-wave device:
Version 3.20 L:1
House/Node
Role Master SIS:NO PRI:YES

If your role is not shown as above (for instance Role: Suc SIS:YES PRI:NO) you could try a "Shift controller form the advanced tab of the z-wave device.
Please note that some users have reported problems with this. You can refer to the forum threads on this issue.

===Downgrading to z-wave version 2.78===
# Unplug Vera's power and reconnect it.
# When Vera starts up, uncheck the "Use Z-Wave version 3.20 instead of 2.78" box, close the popup and save.
# Wait a couple minutes and confirm that the Z-Wave version is now 2.78.
# Then choose the Advanced option from the toolbox, select the backup tab, check the option "Restore Dongle", click "Choose File".
# Select the backup file you created, and click "Restore".
# Wait about 10 minutes and everything should be back to what it was before you upgraded to version 3.20.

==References==
Related forum thread: 
http://forum.mios.com/index.php?topic=6974.0 

'''Suc SIS:YES PRI:NO issues''' are discussed in these threads: 
http://forum.mios.com/index.php?topic=6301.0 
http://forum.mios.com/index.php?topic=4412.0

USB swapfile creation

2011-07-02T17:27:51Z

Henk: New page: Category:How To '''HOWTO set up a memory swapfile on a USB stick''' ==Prerequisites== * Vera 2 hardware * Vera firmware 1.1.1245 or later * USB stick attached to Vera ==Introduction...

[[Category:How To]]

'''HOWTO set up a memory swapfile on a USB stick'''

==Prerequisites==
* Vera 2 hardware
* Vera firmware 1.1.1245 or later
* USB stick attached to Vera

==Introduction==
Heres a short manual on how to set up a memory swap file on a USB stick to allocate more memory for your Vera.
This is an additional feature once you have set up USB logging for Vera as described here: [[Store_logs_USB]]

The instructions contain commands for 4 indivudual steps.

Data description for 64Mb swapfile
Creating swapfile
Start using swapfile
Stop using a swapfile.

Please note that rebooting Vera will require a manual start of the swapfile.
Upgrading Vera's firmware will require setting up the swapfile from scratch as per instructions below.

==Instructions==
To set up a swapfile for Vera to use after you have have enabled to store logs on a USB stick as described here: [[Store_logs_USB]] it is required
to SSH into your Vera. This procedure is explained here: [[Logon_Vera_SSH]].

Once you are at the SSH commandline, enter these commands one by one.
Please note that the forst command can take a few minutes to complete, depending on the speed of your USB stick.

1. Data description for 64Mb swapfile for the filesystem:
dd if=/dev/zero of=/tmp/log/cmh/swapfile bs=1024 count=65536

2. Creating the actual swapfile:
mkswap /tmp/log/cmh/swapfile

3. Start using the newly created swapfile:
swapon /tmp/log/cmh/swapfile

If for some reason you would like to stop Vera using the swapfile use the following command after SSH-ing into Vera:
swapoff /tmp/log/cmh/swapfile

==References==
please find more info here: 
http://wiki.openwrt.org/doc/howto/usb.storage

Firmware Flash Vera2

2011-07-02T16:57:51Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

== Prerequisites ==

* The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications shoudl be run in Windows XP SP3 comaptibility 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/

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

* [http://download1.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool]
* [http://download1.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 reset 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://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware] and save it on your computer.
# Select the file [http://download1.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://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware 
http://download1.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/

Migrate To Z-wave version 452

2011-07-02T16:39:10Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

HOW TO MIGRATE FROM THE OLDER Z-WAVE VERSION (2.78) TO THE NEWER Z-WAVE VERSION (3.20)

'''NOTE: This migration only works with a Vera 2.'''

==Introduction==
Inside your Vera2, or your Vera1's dongle, is a Z-Wave chip. The Z-wave chip inside Vera 2's is upgradeable, meaning Vera can automatically load either the newer or older Z-Wave firmware into the chip.
Z-Wave has its own firmware, separate from Vera's firmware. is that its routing capabilities are improved.
This gives Vera the ability to optimize the Z-Wave network, This is particularly usefull in a large and complex network with lots of Z-Wave devices. 
As of version 3.20 Vera no longer supports inclusion controllers (ie SUC/SIS).
This feature allowed you to add a secondary, handheld (USB) controller to the Z-Wave network, and then include additional Z-Wave nodes using this controller.
We recommend new customers to always use the newer version of Z-Wave. Starting in March, 2011 new Vera's will have the newer Z-Wave version selected by default.

You can change which version Vera uses by selecting the Z-Wave icon in your toolbox, selecting the options tab, and checking the "Use Z-Wave version 3.20 instead of 2.78" box to use the newer Z-Wave, or unchecking it to use the older Z-Wave (2.78), and then saving your changes. 

==Prerequisites==
Officially you have to reset your Z-Wave network and rebuild your network from scratch.
While this is not an issue for a new user or a really small network, some Vera users have large Z-Wave networks already setup with lots of scenes and will not want to redo everything.
Therefore we have developed the following different methods which should work most of the time, and they include making a backup so you can go back if it doesn't work.

Before you upgrade it is recommended you run a Z-Wave repair/heal network, since this will create a reliability rating, or "health score", for all your Z-Wave nodes.
Then after upgrading you can run it again and see if the reliability has improved. To do this, choose the Z-Wave icon from the toolbox, choose the Repair tab, and click 'Go'. 
Depending on the size of your network the process will take anywhere from 1 hour for smaller networks, up to 8 hours for networks with 80+ Z-Wave devices.
It's best to start it at night before going to bed so nobody will be manually using the Z-Wave devices during the test as this can throw the profiling off so the health score is not accurate.
Once the process has completed, return to the Repair tab and you should be able to view the Repair report using the pull-down menu. You can save this and compare after you migrate to the newer Z-Wave firmware.

* Upgrade to the latest Vera firmware. It must be version 1.1.1221 or later (March, 2011).

== Instructions ==
There are two ways to upgrade your z-wave firmware. The first way is to update the firmware and build your firmware from scratch.
The second way is to upgrade the firmware using the "Hack to convert 2.78 to 3.20" option under the advanced tab of the z-wave device.
This second option allows you to keep your devices and settings without going through the reset z-wave network procedure.

'''*NOTE1, Before continuing, please make sure to backup your dongle/z-wave chip!'''
# After upgrading your Vera to the latest firmware, click the Z-Wave icon, choose the Advanced tab, and click "Backup Dongle". Confirm that within a minute or so you get a Backup: Backup done message in the info panel in the upper right corner of the dashboard, along with a green gear icon.
# Choose the advanced icon from the toolbox and click the Backup tab. Choose the option "Create Backup". This will give you the option of saving a file called "backup.mios2...something". Save this file on your computer somewhere and hold onto it. 

===Update z-wave firmware to the new firmware and build the z-wave network from scratch===
'''*NOTE2, Vera firmware 1.1.1245 currently has a bug preventing the reset to actual clear any devices. Please see the releasenotes here:'''
[[Release_Notes]] 

After Vera has finished changing the Z-Wave firmware, you should choose the "Reset Z-Wave network" button which is on the Advanced tab of the Z-Wave settings. 
This will clear out your entire Z-Wave network, removing all your devices, and starting clean. The reason for this is that the way the newer Z-Wave firmware stores the Z-Wave network data is slightly different. 
If you move from the older to the newer version without doing a reset it is likely you will not be able to add or remove any nodes. 
This "Reset Z-Wave network" resets the network data in either the newer or older format from scratch, so the Z-Wave chip will be ready to go.

# Go into the Z-Wave option in the toolbox, click the Options tab and choose "Use Z-Wave version 3.20 instead of 2.78".
# You should also check the box "Use MiOS routing instead of Z-Wave (requires 4.5)" and "Limit neighbors to Z-Wave discovery (requries MiOS routing)".
# Close the popup and click Save. Wait about 5 minutes for Vera to finish flashing the firmware, then click the Z-Wave toolbox and choose the Options tab and confirm at the top it says "Version: 3.20".

===Update the z-wave firmware using the "Hack to convert 2.78 to 3.20" option===
Using this method will allow you to keep you current settings, included devices etc.
However, if you only have a limited network it's safer (possibilty of corrupting data) to build the 3.20 network from scratch. 
If you build from scratch, Reset Z-Wave network anyway, this will produce a new House ID and start you with a clean slate. You will have to unpair all your devices in order to include them again. 

# Go into the Z-Wave option in the toolbox, click the Options tab and choose "Use Z-Wave version 3.20 instead of 2.78".
# You should also check the box "Use MiOS routing instead of Z-Wave (requires 4.5)" and "Limit neighbors to Z-Wave discovery (requries MiOS routing)".
# Close the popup and click Save. Wait about 5 minutes for Vera to finish flashing the firmware, then click the Z-Wave toolbox and choose the Options tab and confirm at the top it says "Version: 3.20".
# Reboot or power-cycle your Vera.
# Go back into the z-wave devices settings as you did at step 1. click the options tab and tick the "Hack to convert 2.78 to 3.20" box. 

----
After updating Vera should show this at the top of your options tab of the z-wave device:
Version 3.20 L:1
House/Node
Role Master SIS:NO PRI:YES

If your role is not shown as above (for instance Role: Suc SIS:YES PRI:NO) you could try a "Shift controller form the advanced tab of the z-wave device.
Please note that some users have reported problems with this. You can refer to the forum threads on this issue.

===Downgrading to z-wave version 2.78===
# Unplug Vera's power and reconnect it.
# When Vera starts up, uncheck the "Use Z-Wave version 3.20 instead of 2.78" box, close the popup and save.
# Wait a couple minutes and confirm that the Z-Wave version is now 2.78.
# Then choose the Advanced option from the toolbox, select the backup tab, check the option "Restore Dongle", click "Choose File".
# Select the backup file you created, and click "Restore".
# Wait about 10 minutes and everything should be back to what it was before you upgraded to version 3.20.

==References==
Related forum thread: 
http://forum.mios.com/index.php?topic=6974.0 

'''Suc SIS:YES PRI:NO issues''' are discussed in these threads: 
http://forum.mios.com/index.php?topic=6301.0 
http://forum.mios.com/index.php?topic=4412.0

Firmware Flash Vera2

2011-06-27T18:13:50Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

== Prerequisites ==

* The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications shoudl be run in Windows XP SP3 comaptibility 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/

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

* [http://download1.mios.com/firmware/vera2_upgrade_tool.zip Vera2 Firmware Flash Tool]
* [http://download1.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 reset 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 isn't blinking, turn Vera off and try again.
# 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://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware] and save it on your computer.
# Select the file [http://download1.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
# Wait about 10 mins for your new system to reboot and the ETH1 light start double blinking or it's solid.
# 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.

== References==
http://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware 
http://download1.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/

Update Firmware

2011-06-25T17:00:57Z

Henk:

[[Category:How To]]

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

==Prerequisites==

* Vera hardware (either Vera 1 or Vera 2)
* Internetconnection
* Reliable powersource (do NOT update Vera while on battery operation, provide mains power)

==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 the authentication, upgrade and then re-enable the authentication from cp.mios.com after the update was succesfull.

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

==Manual updates==

'''Manually upgrading the firmware'''

To manually load a firmware to your Vera, click the advanced icon in the toolbox section of your Vera's UI. 
From there select the tab "FIRMWARE"

Vera automatically checks connectivity to the download server (download1.mios.com or download2.mios.com). 
Then 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 the specifick download URL for your Vera in the "URL for MiOS custom firmware" box. 
Please contact MiOS for the correct URL first.

----
=== Advanced manual upgrade ===

* NOTE: If you lose access through the web page you can enable SSH on Vera (see http://wiki.micasaverde.com/index.php/Logon_Vera_SSH). 
Then use scp to copy the firmware image to Vera's /tmp directory.
Then you can either manually write the firmware using this command:

mtd -r write [filename] linux

Doing a manual firmware upgrade however you will lose all your settings. 
To preserve your settings name the image: firmware.img and run:
/usr/bin/cmh-upgrade.sh
which will create a backup of your configuration online, restore the firmware, and then restore the backup on the first boot.

Advanced manual updating your firmware is described here:

More instructions on manually upgrading Vera 1 hardware: 
http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera_1

More instructions on manually upgrading Vera 2 hardware: 
http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2

===Automatic Updates===

*NOTE: Updating a Vera 1 to the latest official firmware requires an intermediate step. Always consult MiOS tech support when attempting to upgrade your Vera 1 to the latest firmware when your current firmware is older than 1.1.1062.

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. 
Also you can go to this url: 
http://micasaverde.com/vera2

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. Please contact tech support at MiOS and ask them to help you install intermediate release 1.1.1062.

* 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

==References==
please find more info here: 
Update url for your Vera | http://micasaverde.com/vera2 
Specifick update info for Vera 1 hardware | http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera_1 
Specifiak update info for Vera 1 hardware | http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2 

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

Update Firmware

2011-06-25T16:21:35Z

Henk: New page: Category:How To '''How to update Vera to a new firmware''' ==Prerequisites== * Vera hardware (either Vera 1 or Vera 2) * Internetconnection * Reliable powersource (do NOT update Vera...

Include Z-wave devices

2011-06-13T16:57:14Z

Henk: New page: Category:How To '''HOWTO add Z-Wave devices to your Vera''' ==Prerequisites== * Vera 1 or 2 hardware * UI4 firmware * Z-wave devices (battery or mains powered) ==Introduction== This...

[[Category:How To]]

'''HOWTO add Z-Wave devices to your Vera'''

==Prerequisites==
* Vera 1 or 2 hardware
* UI4 firmware
* Z-wave devices (battery or mains powered)

==Introduction==
This is a short manual on how to include new Z-Wave devices to your Vera gateway.
Although many steps might rely on the manual of your device, this How To will give general guidance on step to
take on your Vera as well as your device. Where applicable this How To will refer to your devices manual.

==Instructions==
# Go to Vera's Dashboard (Open your webbrowser and type the IP address of your Vera)
# In the UI click add/remove devices in the top of your UI
# Click the "next" button of the Z-Wave section (top section, depicted by Z-Wave icon)
# Go to the bottom section stating "Any type of Z-Wave device which you can bring close to MiOS"
# bring your Z-Wave device into inclusion mode with the steps as describes in your users manual. (usually clicking 1 or more times at the manual switch)
# Make the appropriate selections here and click "GO" (most users would like to go with the failsafe options: include 1 node of type "any" with full power)
# If you cant bring the device to Vera, take Vera over to the device. The same steps apply.
# A new node will appear in the UI in the room you selected (or the default room)
# Click the "wrench" to edit the new device, go to the settings tab and select automatically configure "YES"
# Click "configure node right now"
# Exit the settings (click cross top right of the settings screen) and click "Save" (red text in the upper left of Vera's UI)

* Note: Failsafe full power inclusions will mostly work if the device is in the specified range of your vera (30 meters indoor / 100 meters outdoor)
If you feel comfortable the device is in range of your Vera, you can also leave the default "low power" setting as is.
A network heal with or without stresstest is advisable to make sure Vera communicates to your newly added device.

*Note: Some users have mentioned problems when using the new Z-Wave firmware called 3.20L. Default your Vera will be on Z-Wave 2.78L
If you upgraded or you have a very new Vera2 box that is already on Z-Wave version 3.20L. T.the workaround is supposed to be to downgrade to Z-Wave 2.78L, include the device (Vera will now accept going into "Learning mode") and then upgrade to 3.20 again.

==References==
please refere forinfo here on some related subjects; 

[[http://forum.mios.com/index.php?topic=6648.0 Inclusion fails]]

Vera Report and Control

2011-06-09T05:33:43Z

Henk: Vera Report & Control application for windows

[[Category:3rd Party]]

'''Vera Report & Control''
Last update:
Version 1.0012

Owner/creator
Tim Alls
http://allseasyachts.com/

==Prerequisites==
* Vera hardware
* UI4 Lua capable firmware
* Windows client
* Labview framework installed on windows client

==Introduction==
Heres a short overview of capabilities

==User guide==
#
#
#

==References==
please find more info [[http://forum.mios.com/index.php?topic=6515.0 here]]<Lbr>
Get LabView [[http://www.ni.com/labview/ here]]

Main Page

2011-06-06T10:08:23Z

Henk:

[[Category:Glossary]] [[Category:User_Instructions]] [[Category:How_To]] [[Category:Troubleshooting]] [[Category:Plugins]] [[Category:Hardware]]
 
<big>'''Welcome to the Mi Casa Verde (MiOS) wiki'''</big>
----
'''*Note:''' The Wiki documentation is for both '''Vera 1''' and '''Vera 2''' units with '''UI2''' and '''UI4''' interface.
 
=Wiki User Instructions=
This Wiki provides a lot of information on your Vera, including [[:Category:User Instructions|User Instructions]].

==Getting started==
If you are new to Vera and MiOS (former Mi Casa Verde) please check our pages on getting started, basic installation and use of menu's etc.
The pages are to be found at '''"docs.mios.com" for the older Vera UI2''' or at '''"docs2.mios.com" for the more recent Vera UI4'''. 
This last page can also be reached by clicking [http://docs2.mios.com/doc.php?language=1&manual=1&platform=0&page=preface here]. Also the homepage of MIOS provides a basic setup guide for Vera [http://www.micasaverde.com/setting-up.php here]

==FAQ, HOWTO and Troubleshooting==
There are separate pages containing Frequently Asked Questions, simple pages explaining "How To" and a section on troubleshooting.
 
Here is a link to the [[FAQ]] and initial [[Troubleshooting]] pages. 
Here is a link to the [[:Category:How To|How To]] section. 
Here is a link to the [[:Category:Troubleshooting|Troubleshooting]] section. 

==Luup code and Plugins==
There are already various Luup coded plugins and code examples available for users. 
You can find more information about that here [[Luup_plugins_and_Luup_code|Overview of Plugins]]

=Categories=
Information and pages on the Wiki are put into categories to keep information on a certain subject together. 
Please click [[Special:Categories|here]] for all categories.

=All Pages=
See the [[Special:AllPages|overview of all Pages]] for a list of all pages.
 
----
'''For most used categories, see the links below'''

Heal Network

2011-06-05T18:57:10Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO "Heal" your network.'''
If you are having trouble with some of your Z-Wave nodes, this can repair and diagnose the problem.

==Introduction==
Z-Wave is a mesh network, which means that if two Z-Wave devices want to talk to each other but they are too far apart to communicate directly, they will relay messages through other Z-Wave devices that are in-between. Every device needs to know where it is in proximity to all the other devices, so it knows which devices it can use for relaying. This network map is created when you first add devices to your Z-Wave network. If you later move devices around, the map can be wrong, the relaying might not work, and control of Z-Wave devices may become unreliable.

==Instructions==
To correct this situation, go to the 'Devices' tab on Vera's 'Setup' page, choose 'Z-Wave', then 'More Z-Wave Options' and hit the 'Go' button. In the section 'Repair My Network', you can specify 3 parameters.

(1) How long Vera should wait for battery operated devices to wake up: During the first part of the heal network, Vera will attempt to locate all the devices on the network. Many battery operated devices, like sensors, will not respond except at periodic wakeup intervals. Indicate how long Vera should wait for any battery operated devices to wake up. 60 minutes is usually safe since most battery operated devices wakeup every 30-60 minutes by default.

(2) You can tell Vera to reconfigure all the devices: If you leave it checked, the green 'Device is Configured' cog wheel icons (see: [[Device Control Status]]) will turn gray or blue as Vera re-configures the devices, but, when the test is completed, the icons should be green again.

(3) Indicate how long Vera should run a stress test on the network: During this time Vera will constantly send data to all your Z-Wave nodes and measure the delay and accuracy of their responses.

Vera will go through all the devices one by one and have each device broadcast signals, and all the other devices around record those signals, and, in turn, the map gets rebuilt. At the same time, the 'Device is Configured' flags are reset, meaning Vera will attempt to re-configure your devices again.

When the heal network test is done, go back to the 'Z-Wave Options' page (click the 'Z-Wave Options' link again even if the page is still loaded), and in 'View Repair Reports' you'll see a pull-down listing the heal network test that was just completed. Choose it to view the test results. You can copy/paste the test results if you want to keep a copy of them. The repair reports will be lost when you power cycle Vera.

----
* '''''Note: Heal network can take hours to complete.''''' So it's best to let it run overnight. While the test is running, the status will say "Please wait... Configuring Z-Wave devices", and the progress of the test is shown below it. Because this generates a lot of Z-Wave traffic, your Z-Wave devices may respond very slowly if you try to use them while the test is running. If you have battery-operated devices that are always listening for commands, called FLiRS, like the Schlage LiNK door lock, the testing will use up some of their battery.
----

Firmware Flash Vera2

2011-06-05T18:55:31Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

== Prerequisites ==

* The upgrade tool is only tested in Windows XP, but may work in other versions of windows.
* 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/

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

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

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

* IP: 192.168.1.5
* Subnet Mask: 255.255.255.0
* Default Gateway: 192.168.1.1

== Begin the process for flashing the firmware ==

# Use a network cable and plug the cable from your PC into Vera's ETH2 port.
# Unplug Vera from the power cord.
# Holding down Vera's reset 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 isn't blinking, turn Vera off and try again.
# 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://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware] and save it on your computer.
# Select the file [http://download1.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
# Wait about 10 mins for your new system to reboot and the ETH1 light start double blinking or it's solid.
# 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.

== References==
http://download1.mios.com/firmware/micasaverde_backfire_v8.bin Vera2 Firmware 
http://download1.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/

Firewall

2011-06-05T18:49:38Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO use Vera as your firewall'''

==Introduction==
If you are considering using Vera as your primary firewall, please be advised that Vera does not configure itself to be properly stealthed by default. This is shown by running at test from the grc.com web site using the Shields Up port scanner utility. See the reference section

==Instructions==
* If you are already configured as 'Directly to the internet...' go to step 3.

1. From the Vera main page, go to Advanced, Net & Wi-fi.

2. Ensure that you are not configured as 'Automatically Configure' and that 'Directly to the internet. Vera is a gateway' is already configured.

* If you are configured as 'Automatically Configure', select 'Directly to the internet...'. All the default options can be accepted here. Use the tab key to move through the fields if you are having trouble scrolling down. Click 'Save and apply'. Test you internet Before proceeding. Return to the above screen once in order to proceed.

3. Click the Advanced Configuration link at the top. Caution! Where you are about to go is not for the faint at heart. Create a 'Drop' rule to further secure your vera.

4. Click Network, Firewall

5. Select 'Drop' from the drop down list, click Add

6. Click Save

7. Click Apply

8. Re-test with the shields up tool!

==Reference==
Link to the GRC shields Up tool is here:
[[http://www.grc.com/x/ne.dll?rh1dkyd2 GRC Shields UP]]

Desktop Shortcut

2011-06-05T18:41:05Z

Henk:

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

'''HOWTO setup a desktop shortcut to activate a scene or control a device.'''

==Introduction==

==Instructions for Windows==

# Get [http://users.ugent.be/~bpuype/wget/#download wget for Windows].
#Create a shortcut to it on the Desktop.
#Right click on the shortcut and open the Shortcut tab.
#In the Target field append the following:

-q -O NUL "http://<vera_IP>:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=<scene_number>"

==Examples==

To run a scene
<source lang="asp">"D:\Programs\wget.exe" -q -O NUL "http://192.168.10.1:3480/data_request?id=lu_action &serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=6"</source>

To control a device:
<source lang="asp">"http://<vera_IP>:3480/data_request?id=lu_action&output_format=xml&DeviceNum=<device_number> &serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=<1 to turn on, 0 to turn off>"</source> 
* Note: You can find the whole Luup requests list [[Luup Requests]].

To toggle the state with one statement:
<source lang="asp">"http://<veraIP>:3480/data_request?id=lu_action&output_format=xml&DeviceNum=<devId>&serviceId=urn:micasaverde-com:serviceId:HaDevice1&action=ToggleState"</source>

==Other OS==
In Linux or OSX you can use curl instead of wget.exe
Curl is nativly available on these OS'

Syntax:
curl -0

Desktop Shortcut

2011-06-05T18:32:54Z

Henk:

'''HOWTO setup a desktop shortcut to activate a scene or control a device.'''

==Introduction==

==Instructions for Windows==

# Get [http://users.ugent.be/~bpuype/wget/#download wget for Windows].
#Create a shortcut to it on the Desktop.
#Right click on the shortcut and open the Shortcut tab.
#In the Target field append the following:

-q -O NUL "http://<vera_IP>:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=<scene_number>"

==Examples==

To run a scene
<source lang="asp">"D:\Programs\wget.exe" -q -O NUL "http://192.168.10.1:3480/data_request?id=lu_action &serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=6"</source>

To control a device:
<source lang="asp">http://<vera_IP>:3480/data_request?id=lu_action&output_format=xml&DeviceNum=<device_number> &serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=<1 to turn on, 0 to turn off></source> 
* Note: You can find the whole Luup requests list [[Luup Requests]].

To toggle the state with one statement:
<source lang="asp">"http://<veraIP>:3480/data_request?id=lu_action&output_format=xml&DeviceNum=<devId>&serviceId=urn:micasaverde-com:serviceId:HaDevice1&action=ToggleState"</source>

==Other OS==
In Linux or OSX you can use '''curl -0''' instead of wget.exe
Curl is nativly available on these OS'

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

Factory Reset

2011-06-05T18:18:13Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO get Vera back to the factory default state'''

==Introduction==
You can return Vera to the factory default state, wiping out all the configuration changes you have made.

First, if you want to reset the Z-Wave network, that is the list of Z-Wave devices that you have paired using Vera's black Z-Wave dongle, open Vera's Setup page and click 'Devices', then 'Z-Wave Options' and then 'Reset Z-Wave Network'.

--todoal: show zwave options screen shot

Next, if you also want to reset everything else in Vera, including any changes you've made to Vera's networking, any rooms or scenes or users you've added, your location settings, and so on, then from Vera's setup page click 'Advanced', 'Backup' and click 'Restore Factory Defaults'. Alternatively, you can press the black button on the back of Vera marked 'restore' twice in rapid succession, then watch the power light on the front of Vera. The power light will go out when Vera is doing a reset. In order to avoid accidentally resetting Vera and losing your data, you have to double press the black button quickly. So if the power light doesn't go out, try again until it does.

--todoal: show backup screen shot

It is also possible to do a complete hard reset to factory settings. See Reference.

* '''Note: This also resets Vera's security key!''' This means if you have paired secure devices, and you do not reset the Z-Wave network, they will no longer work after you do a factory reset. At present, only Z-Wave door locks are secure devices. Remember that doing a factory reset, such as double clicking the black button, does not reset the Z-Wave network. Any devices that were paired with Vera before the reset will still be paired after the reset. Secure devices, like door locks, will still be paired after a factory reset. But, since the factory reset creates new secure encryption keys, the devices will no longer work. You have to remove them from the Z-Wave network, and then add them again.

==Reference==

Please see also [[Buttons_Indicators]]

Clone Dongle

2011-06-05T18:14:45Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO Clone your Z-Wave dongle (Vera2 has the Z-Wave chip built in, a dongle is optional)'''

== Introduction ==
The Z-Wave chip inside the black dongle maintains the master list of all the other Z-Wave devices that you have included into your Z-Wave network. Vera also maintains its own database with a list of devices, and Vera's database has a lot more detail, such as the name of the device, the room that it's in and so on. Vera continually syncs its database with the master list of devices in the Z-Wave dongle. This is why you can remove the dongle, carry it around to pair and unpair devices devices, and when you reconnect the dongle to Vera, Vera will show any new or removed devices. If you insert a new dongle in Vera, then all your devices will disappear since the new dongle doesn't have any devices paired to it and so Vera deletes the ones in its database.

Starting with Luup version 1.0.880 and higher, Vera is able to backup not only Vera's database, but also the data stored in the dongle.  Vera also has the ability to restore, or clone, this backup into another dongle.

For example, if you receive a replacement dongle, you can restore a backup of your old dongle's data to the new dongle so you don't have to rebuild your network.

== Instructions ==
To do this follow these steps:
# Be sure that you have not made any changes to Vera within the past 2 hours. Vera will backup the dongle's configuration whenever the list of devices in the dongle changes. The backup process is slow, so Vera does it in small increments when there is no activity on the Z-Wave network. In Vera's setup page, go to Devices, Z-Wave, More Z-Wave options, and look at the value for '''Last Dongle Backup'''. This will show the date & time that Vera last completed a successful backup of the dongle. Be sure that this is not empty of "''N/A''". If it is, leave Vera alone for a couple hours, refresh the Vera setup page, and check again.
# Once you've confirmed that Vera has a backup of your dongle, go to ''Advanced'', ''Backup'' and choose '''Create backup'''. Your browser will prompt you to save a file. Save it to your computer somewhere, such as on the Desktop. Be sure to wait until your browser has finished downloading.  That backup file contains both Vera's database as well as the dongle's.
# Insert your new dongle. Wait a minute to be sure that it's recognized. You should see all your Z-Wave devices have disappeared.
# Go to Advanced, Backup and in the restore section, click 'choose file' and locate the backup file. Check the box 'Restore Dongle Firmware'. Then click Restore.
# Leave Vera alone for 15 minutes. Vera will restore its database, which has all the detailed information on the device, and will also restore the dongle's data from the backup file, which takes several minutes.
# Confirm your new dongle is working and that you have a complete list of devices. 
 
* '''Note ''' In case you forgot to backup your existing settings and you have the findvera.com service activated from Findvera.com tab, your Vera will backup your data once per day. So, go to https://findvera.com and click Settings and you will see there the backups. Select the last one and restore it to your Vera unit. Read here about the restore process: [[Advanced#Backup.2FRestore|Backup / Restore]].

Clone Dongle

2011-06-05T18:12:05Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO Clone your Z-Wave dongle (For use with Vera 1 hardware)'''

=Inbtroduction=
The Z-Wave chip inside the black dongle maintains the master list of all the other Z-Wave devices that you have included into your Z-Wave network. Vera also maintains its own database with a list of devices, and Vera's database has a lot more detail, such as the name of the device, the room that it's in and so on. Vera continually syncs its database with the master list of devices in the Z-Wave dongle. This is why you can remove the dongle, carry it around to pair and unpair devices devices, and when you reconnect the dongle to Vera, Vera will show any new or removed devices. If you insert a new dongle in Vera, then all your devices will disappear since the new dongle doesn't have any devices paired to it and so Vera deletes the ones in its database.

Starting with Luup version 1.0.880 and higher, Vera is able to backup not only Vera's database, but also the data stored in the dongle.  Vera also has the ability to restore, or clone, this backup into another dongle.

For example, if you receive a replacement dongle, you can restore a backup of your old dongle's data to the new dongle so you don't have to rebuild your network.

=Instructions=
To do this follow these steps:
# Be sure that you have not made any changes to Vera within the past 2 hours. Vera will backup the dongle's configuration whenever the list of devices in the dongle changes. The backup process is slow, so Vera does it in small increments when there is no activity on the Z-Wave network. In Vera's setup page, go to Devices, Z-Wave, More Z-Wave options, and look at the value for '''Last Dongle Backup'''. This will show the date & time that Vera last completed a successful backup of the dongle. Be sure that this is not empty of "''N/A''". If it is, leave Vera alone for a couple hours, refresh the Vera setup page, and check again.
# Once you've confirmed that Vera has a backup of your dongle, go to ''Advanced'', ''Backup'' and choose '''Create backup'''. Your browser will prompt you to save a file. Save it to your computer somewhere, such as on the Desktop. Be sure to wait until your browser has finished downloading.  That backup file contains both Vera's database as well as the dongle's.
# Insert your new dongle. Wait a minute to be sure that it's recognized. You should see all your Z-Wave devices have disappeared.
# Go to Advanced, Backup and in the restore section, click 'choose file' and locate the backup file. Check the box 'Restore Dongle Firmware'. Then click Restore.
# Leave Vera alone for 15 minutes. Vera will restore its database, which has all the detailed information on the device, and will also restore the dongle's data from the backup file, which takes several minutes.
# Confirm your new dongle is working and that you have a complete list of devices. 
 
* '''Note ''' In case you forgot to backup your existing settings and you have the findvera.com service activated from Findvera.com tab, your Vera will backup your data once per day. So, go to https://findvera.com and click Settings and you will see there the backups. Select the last one and restore it to your Vera unit. Read here about the restore process: [[Advanced#Backup.2FRestore|Backup / Restore]]

Buttons Indicators

2011-06-05T17:58:35Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO on doing a factory reset, remove the Wi-Fi password and add/remove Z-Wave devices'''

* Note: The red and black buttons on the back of Vera (1) are used to do a factory reset, remove the Wi-Fi password, and add/remove Z-Wave devices. The power light on the front indicates the current status.

== Power light indicator ==

* '''Normal bootup:''' 
When turning on Vera the power light will come on for about one second when the power is first connected. But then it will remain off while Vera is starting up, except for 1 brief flash. Once Vera has finished booting up and is ready to go, the power light will either be on solid, or double flash.

* '''Solid = OK:''' 
When the power light is on solid, that means Vera was able to get an internet connection on the WAN port and everything is OK.

* '''Double blink = No internet:''' 
If the power light starts to double blink (blink twice, pause, blink twice, etc.), that means Vera is ready to go, but was unable to get an internet connection on the WAN port, so remote access and FindVera will not work. See [[Quick Start Hardware]] for details.

* '''Slow, steady blink = Firmware is corrupted:''' 
When you connect the power, if the power light starts blinking slow and steady right away, this means the firmware is corrupted and Vera cannot boot. This happens if you unplug Vera while during a firmware update. If it does, see [[Firmware Flash]] for a utility to restore Vera's firmware.

== Hardware reset & Wi-Fi password ==

* '''Black button = factory reset:''' 
If you wait until Vera has booted up and the power light is either on solid or double flashing, then you can double-click the black button to restore Vera to the factory default state. See: [[Factory Reset]]

* '''Red button = unsecure wi-fi:''' 
By default, Vera's Wi-Fi comes turned on, and the highest security setting, WPA2, is on by default. Most recent laptops and Wi-Fi devices can connect with WPA2. If your computer cannot connect wirelessly with WPA2, you can either (a) connect your computer directly to one of the LAN ports on the back of Vera, or (b) you can double-click the red button on the back of Vera. Doing so temporarily removes any encryption on Vera's Wi-Fi network, so your computer can connect wirelessly to Vera (note that this is only a ''temporary'' change).  Then, you can access Vera's 'Net & Wi-Fi' setup page to reconfigure the wireless networking as needed.  Click 'Save' to keep any changes you made.

* Note: To avoid saving your changes, simply unplug Vera and plug it in again; her original network settings will return.

Remember that when you double-click the red button and thereby remove the Wi-Fi network security, Vera's network is temporarily unsecure and anybody within 100 feet or so of Vera can connect.

It is also possible to do a (partial or complete) soft reset to factory settings.
Information on this can be found here: [http://wiki.micasaverde.com/index.php?title=Buttons_Indicators]

== Adding/Removing Z-Wave devices ==

Normally you add Z-Wave devices by removing Vera's black Z-Wave dongle as explained [[Devices|here]], or you add Z-Wave controllers as explained [[ZWave Add Controller|here]]. You can also add/remove Z-Wave devices without removing the dongle by choosing [[ZWave Options|Z-Wave Options]] on Vera's 'Setup' page. Or, you can do this with Vera's red and black buttons as explained below. This may be necessary when you want to add Z-Wave door locks or similar secure devices. This is because when you add a secure Z-Wave device, at the same time the device is being added, Vera needs to exchange encryption keys with the device. If you remove Vera's Z-Wave dongle to try adding secure devices the normal way, Vera is not able to exchange these keys. You can add them from the [[ZWave Options|Z-Wave Options]] page, but that requires a PC computer with a web browser connected to Vera so you can access Vera's 'Setup' site. This may not be practical if you want to pair a secure device you have already installed in your home, like a Z-Wave door lock, because Vera must be within a few feet of the door lock in order to pair it. The solution is to disconnect Vera, take Vera near the door lock, plug Vera in (use an extension cord if necessary), and use the red and black buttons on the back of Vera to do the pairing:

* '''Hold down black button and tap red button = Add Z-Wave device:''' 
Press and hold the black button. While it is held down, tap and release the red button once. Then let go. Be careful not to hit the black (reset) button twice in a row, as this will reset the router to the [[Factory Reset|factory default]] configuration. Vera's power light on the front will starting to blink slow and steady, about 1 time per second. This means Vera is ready to add another device. Vera will stay in this mode for 60 seconds, after which time the power light will return to normal. Each time you successfully add a device, the power light will flutter for 2 seconds to let you know it was successfully added. When you are done adding devices, you can either wait until the 60 second timeout when the power light returns to normal, or tap the black button once to stop the 'add mode'. Once you stop the 'add mode', or it times out, wait 10 seconds before disconnecting Vera's power.

* '''Hold down red button and tap black button = Remove Z-Wave device:''' 
Press and hold the red button. While it is held down, tap and release the black button once. Then let go. Vera's power light on the front will starting to blink fast and steady, about 3 times per second. This means Vera is ready to remove, or reset a device. See [[Reset Node]] for an explanation of this. Vera will stay in this mode for 60 seconds, after which time the power light will return to normal. Each time you successfully remove a device, the power light will flutter for 2 seconds to let you know it was successfully reset. When you are done reseting devices, you can either wait until the 60 second timeout when the power light returns to normal, or tap the black button once to stop the 'reset mode'. Once you stop the 'reset mode', or it times out, wait 10 seconds before disconnecting Vera's power.

* '''''IMPORTANT NOTE:''''' When you are adding/removing devices 'blindly' this way, without being able to see the Z-Wave status on Vera's 'Setup' page, you won't be able to see when the Z-Wave network is actually ready to add/remove devices. Just like when you're using the web interface, there are times that Vera is busy configuring the Z-Wave network and momentarily cannot add/remove devices. So, if you press the button sequence above and Vera's lights do not start flashing to indicate Vera is in add or remove mode, wait 30 seconds. If the light doesn't start flashing, try the button sequence again. Also remember that if you are unable to add a device, it's possible the device is already paired with another Z-Wave network. In this case you must reset it first by putting Vera in 'remove/reset' device as explained above. See also: [[Reset Node]].

Bridged Mios Engines

2011-06-05T17:47:59Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''HOWTO Create and use a combination of 2 or more (bridged) Vera systems.'''

==Introduction==
You can have one MiOS systems import, or aggregate, the devices of one or more other MiOS systems, so that all the devices appear to be on one system. You can create scenes and events which include devices from different systems.

One of the most common uses for this is a home that is too large or spread-out for one Z-Wave network. For example, there may be a main house and a guest house with a big distance in between with no Z-Wave nodes to act as repeaters. So you can put a MiOS system in the guest house, and another MiOS system in the main house. They both have separate Z-Wave networks. But, assuming they are on the same home LAN, the main system can import the devices of the guest system, so that the whole home appears to be one big system. Z-Wave scene controllers in the guest house can run scenes in the main house, and scenes can span both systems.

To do this, choose Add Device and Add control over another UPnP device, such as another MiOS. 
If the option for UPNP Scanning is not checked, you must check it first, then save your settings, and wait a few minutes before adding the other device. 
Whichever system you are using to select the Add Device will be the 'master', and whichever system you add to it is the slave.

== Technical specs ==

For those interested, the way it works is this:

# Upon adding the device the master performs an "ImportDevice" which adds the slave system as a device.
# Upon reload, the master system calls <data_request?id=master_registering> on all the slaves. It will keep retrying this until it gets an OK from the slave. It will call this every time the master reloads. The slave will store a list of all masters in the "foreign_master" tag in it's user_data. The master stores the list of all slaves as normal devices in it's user_data.
#. Upon receiving the master_registering, the slave will then call a <data_request?id=slave_data_changed> on the master immediately, and again every time any data changes on the slave or the slave reloads.
# Whenever the master receives the id=slave_data_changed call, it will do a id=status on the slave, and if the loadtime has changed, meaning the user_data is different, it will first do an <id=sud> (short user data) first.

Advanced Network Setup

2011-06-05T10:23:12Z

Henk:

[[Category:User Instructions]]
[[Category:Troubleshooting]]
[[Category:How To]]

'''HOWTO Tackle advanced network setups'''

== Install DYNDNS (Dynamic DNS) ==
Login to vera using telnet or ssh then 
cd /tmp
wget [http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-4_all.ipk http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/ddns-scripts_1.0.0-4_all.ipk]
tar xzvf ddns-scripts_1.0.0-4_all.ipk
cd / tar xzvf /tmp/data.tar.gz
vim /etc/config/ddns
(press ''INSERT'' to start editing, to save and quit press ''ESC'' then write '':wq'' and press ''ENTER'')

* '''Note: DynDns package is installed by default for firmware versions 1.0.616 and above'''
* '''Note: You can edit the file also from the web interface, go to: Advanced->Net&Wifi->Advanced Settings ->System->File Editor'''

==Vera connected directly to the internet==
=== Open ports on Vera ===
If Vera's connected directly to the internet and you have your firewall activated you'll need to open port 80 to access Vera's UI. 
Go to ADVANCED->Net&Wi-Fi->Advanced configuration OpenWRT Web UI Will open. Here you need to go to: NETWORK->FIREWALL 
New Rule:  
Accept -> press ADD 
Select from the upper drop-down 
Protocol: TCP -> press ADD Destination Ports: 80 
Press SAVE Press bottom 'Apply Changes' 
 And now you should be able to access your Vera. 
=== Protect Vera UI with User and Password ===
Right now everyone can access your Vera UI.  
Go to 'Users' tab, check "Require a username and password to access Vera from within my home network." and add a Username. This will prevent unauthorized persons from having access to your Vera web site.

=== Forward ports from Vera To another IP device ===
In order to setup port forwarding go to: Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Firewall 
New Rule: FORWARD -> press ADD Forward to: ''internal IP of your camera'' (i.e. 192.168.81.150) 
Port: ''port of your camera'' (80 is for HTTP) Also select from the upper drop down:     Protocol: TCP 
    Destination Ports: ''Vera external port ''(i.e. 81) Press SAVE and then 'Apply Changes' from the bottom of the page. 
 In this scenario port forwarding is created from Vera's external IP, on port 81, to 192.168.81.150 internal IP to port 80. So [http://vera_external_ip:81/ http://vera_external_ip:81] requests will go to [http://192.168.81.150/ http://192.168.81.150] 
* Note: If you don't know your camera IP and this is dynamically allocated by Vera's DHCP, follow these steps after you note down your camera MAC Address (which should be on the bottom of the device). 
* '''Identify Camera DHCP IP''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Status->DHCP Clients 
According to the MAC address you should be able to identify the IP address here. 
In order for the camera not to change its IP, you should also set the DHCP server to allocate the same IP every time: 
* '''Configure DHCP Server leases''' Go to Setup->Advanced->Net&Wi-Fi->Advanced configuration->Network->Hosts Complete the  "MAC Address" and the "IP Address" fields from "Static IP addresses (for DHCP)" tab with the current MAC and IP of your camera then press Add, Save Changes and Apply. 

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

If you don't know how to forward ports from your router have a look here: [http://portforward.com/ http://portforward.com/] 
 
=== Vera Network settings ===
Assiging a static IP to Vera: 
Go to SETUP->ADVANCED->Net&Wi-Fi 
'''= IP Address =''' 
How can I connect to the Internet? = STATIC 
Set an IP from your class ie: 192.168.81.2 Subnet Mask 255.255.255.0 Gateway: 192.168.81.1 (your router IP) DNS: 192.168.81.1 (and your provider's DNS server) 
 
=== Firewall ===
Since you already have other router in front of Vera, set firewall to 'No Firewall - bridge'. 
 
=== Lan ===
Since you have another DHCP server, set Vera's DHCP to 'disable'. 
* Note: I've noticed that your Belkin router has the same IP address as Vera's internal lan: 192.168.81.1. If you're using Vera in 'Bridge' mode you should change Vera's LAN IP to an address different from your Belkin router's IP. (i.e.: set it to 192.168.8.1) 

==References==

Advanced Commands

2011-06-05T10:01:11Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''Here are some notes about commands for advanced users and developer'''s: 
* Note: Telnet only works for outdated firmware versions of Vera

='''Telnet & SSH'''=
==Telnet==
Telnet is enabled by default on Vera. With the network autoconfiguration left on, if Vera gets an internal IP address on the WAN port (i.e. any 192.168.x.x, or 172... or 10... address). 
Vera is put into 'switch' mode; all 5 ports are bridged together like a switch. In this mode you can telnet into Vera using the IP Vera gets from the WAN port. 
If you don't know it, go to [http://findvera.com findvera.com] and click 'Setup my Vera in my home' to be redirected. If Vera gets an external IP address on the WAN port, or no IP at all, Vera goes into Gateway mode. 

==SSH==
For more info on how to acces Vera through SSH please click [[Logon_Vera_SSH|here]]

==Local acces==
The firewall is enabled and the DHCP server is turned on. You cannot telnet into Vera using the IP on the WAN port; you must connect your PC to the LAN 1 through LAN 4 ports and telnet to 192.168.81.1 (the default IP for Vera). Note that even in switch mode Vera will still listen to IP 192.168.81.1, so you can always set your PC to a static IP in that range. Telnet uses the default port 23.

* Note: Once you set a root password, telnet is disabled and you must use ssh instead. Set the root password either with the Linux passwd command, or by going into the OpenWRT configuration found on Vera's Advanced, Net & Wi-Fi, Advanced Configuration link.

='''Performance bottlenecks with network throughput'''=

When in gateway mode (see above 'Telnet & SSH') all network traffic runs through Vera's CPU, and the CPU maxes out at around 30 Mbps and you'll find Vera is slow to respond. If you will be needing high volume network traffic it's best to use Vera in switch mode, so the network traffic goes through at full speed without using Vera's CPU. This is not a limitation of our software, it is the nature of residential/consumer access point hardware and most access points have roughly the same performance and speed of CPU.

='''Manually upgrading the firmware'''=

If you lose access through the web page you can enable SSH on Vera by setting a root password (see above 'Telnet & SSH'). Then use scp to copy the firmware image to Vera's /tmp directory. Then you can either manually write the firmware using this command:

mtd -r write [filename] linux

However you will lose all your settings. To preserve your settings name the image: firmware.img and run: /usr/bin/cmh-upgrade.sh which will create a backup of your configuration online, restore the firmware, and then restore the backup on the first boot.

For more info check the guide for flashing your Vera 1 [[Firmware_Flash_Vera_1|here]] or for Vera 2 [[Firmware_Flash_Vera2|here]]

Advanced Commands

2011-06-05T10:00:23Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''Here are some notes about commands for advanced users and developer'''s: 
* Note: Telnet only works for outdated firmware versions of Vera

='''Telnet & SSH'''=
==Telnet==
Telnet is enabled by default on Vera. With the network autoconfiguration left on, if Vera gets an internal IP address on the WAN port (i.e. any 192.168.x.x, or 172... or 10... address). 
Vera is put into 'switch' mode; all 5 ports are bridged together like a switch. In this mode you can telnet into Vera using the IP Vera gets from the WAN port. 
If you don't know it, go to [http://findvera.com findvera.com] and click 'Setup my Vera in my home' to be redirected. If Vera gets an external IP address on the WAN port, or no IP at all, Vera goes into Gateway mode. 

==SSH==
For more info on how to acces Vera through SSH please click [[Logon_Vera_SSH|here]]

==Local acces==
The firewall is enabled and the DHCP server is turned on. You cannot telnet into Vera using the IP on the WAN port; you must connect your PC to the LAN 1 through LAN 4 ports and telnet to 192.168.81.1 (the default IP for Vera). Note that even in switch mode Vera will still listen to IP 192.168.81.1, so you can always set your PC to a static IP in that range. Telnet uses the default port 23.

* Note; 
Once you set a root password, telnet is disabled and you must use ssh instead. Set the root password either with the Linux passwd command, or by going into the OpenWRT configuration found on Vera's Advanced, Net & Wi-Fi, Advanced Configuration link.

='''Performance bottlenecks with network throughput'''=

When in gateway mode (see above 'Telnet & SSH') all network traffic runs through Vera's CPU, and the CPU maxes out at around 30 Mbps and you'll find Vera is slow to respond. If you will be needing high volume network traffic it's best to use Vera in switch mode, so the network traffic goes through at full speed without using Vera's CPU. This is not a limitation of our software, it is the nature of residential/consumer access point hardware and most access points have roughly the same performance and speed of CPU.

='''Manually upgrading the firmware'''=

If you lose access through the web page you can enable SSH on Vera by setting a root password (see above 'Telnet & SSH'). Then use scp to copy the firmware image to Vera's /tmp directory. Then you can either manually write the firmware using this command:

mtd -r write [filename] linux

However you will lose all your settings. To preserve your settings name the image: firmware.img and run: /usr/bin/cmh-upgrade.sh which will create a backup of your configuration online, restore the firmware, and then restore the backup on the first boot.

For more info check the guide for flashing your Vera 1 [[Firmware_Flash_Vera_1|here]] or for Vera 2 [[Firmware_Flash_Vera2|here]]

Advanced Network Settings

2011-06-05T09:44:11Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''This is a guide to set and use advanced network settings'''. 
In your Vera's UI you can find a toolbox section. In this section you find and icon called "Advanced" 

The 'Advanced' tab contains more advanced options:

=Net & Wi-Fi=

Vera is unique in that she automatically configures her network settings. Most users do not need to touch the network settings. If you do, you can change them on Vera's 'Net & Wi-Fi' tab. 
See [[Networking Setup|Networking Setup]] for an explanation of how Vera's automatic network settings work and under what circumstances you may want to change them.

==''Internet''==
Here you specify how Vera should connect to the internet using the WAN port. The default is DHCP, but you can also choose Static IP or PPPoE.

==''Firewall''==
Your options are:

Firewall active: Vera will not accept any incoming connections from outside the home (i.e. through the WAN port)

Firewall disabled: Vera will accept incoming connections from any of the LAN ports or the WAN port

No firewall: This means all ports (the WAN port + LAN ports) are all bridged like a switch. Vera will still have the IP address listed in the LAN section, but the WAN and LAN networks are not separated.

==''LAN''==
You can turn Vera's internal DHCP server on or off, and specify Vera's internal IP address. If the DHCP server is on, the range of IP addresses Vera will give out is automatically set to x.x.x.2 to x.x.x.255.

'''Wireless''': By default Vera comes with wireless turned on, and using the strongest encryption, WPA2. The SSID is automatically set to vera_ followed by Vera's serial number. The default password for the network is printed on the bottom of Vera and on the Getting Started Guide. Your default SSID and password are unique to your Vera and not available to the public. Mi Casa Verde implements security measures to ensure that the only staff who have access to your SSID and password are in the shipping department. We do this so that any wireless devices you order from us, like security cameras, come pre-configured with your SSID and password so that they work out of the box without any further configuration. If you press the 'ezsetup' button on the back of Vera, Vera will temporarily shut off the security/encryption on the Wi-Fi so that you can connect to Vera from a web browser on a computer that does not support WPA2 encryption. This is temporary, so you should go into the "Net & Wi-Fi" tab and change the Wi-Fi settings to what you want. Note that if you change Vera's Wi-Fi settings and then do a 'Factory Reset' of Vera by pressing the 'Reset' button, or on the 'Advanced', 'Download' tab, the password will revert to the factory default that is printed on the bottom of Vera.

=Backup/Restore=
If you check the "Backup my configuration at FindVera.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 [http://FindVera.com FindVera.com], download the last backup file, and restore it so you don't need to setup Vera again. FindVera.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 FindVera.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

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

The 'Enable it' button for tech support access tells Vera to create a temporary back door to the Mi Casa Verde support team. Vera will give you a security code which you can then give your Mi Casa Verde support representative. With this security code, the support rep can access your Vera box using that temporary back door. This is used for helping you troubleshoot problems and providing other assistance. When you are done with the support rep, click 'Disable it' to get rid of the back door. Once you click 'Disable it', there is no longer a back door nor any way for anybody at Mi Casa Verde to get into your Vera.

=Logs=
Here you can view Vera's system logs. Mi Casa Verde's tech support staff may ask you a question about your logs.

=Firmware=
This tab shows you what version software is currently installed in Vera, and what is the latest released version. If there is a newer version of the software available, you will be able to upgrade Vera, and when you do, you can preserve Vera's current settings, so you don't have to change anything after the upgrade, or you can simultaneously reset Vera to a default state so she is running the newest software, but with the same factory setup Vera originally shipped with.

Advanced Commands

2011-06-05T09:32:28Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]

'''Here are some notes about commands for advanced users and developer'''s: 
Note: Telnet only works for outdated firmware versions of Vera

='''Telnet & SSH'''=
==Telnet==
Telnet is enabled by default on Vera. With the network autoconfiguration left on, if Vera gets an internal IP address on the WAN port (i.e. any 192.168.x.x, or 172... or 10... address). 
Vera is put into 'switch' mode; all 5 ports are bridged together like a switch. In this mode you can telnet into Vera using the IP Vera gets from the WAN port. 
If you don't know it, go to [http://findvera.com findvera.com] and click 'Setup my Vera in my home' to be redirected. If Vera gets an external IP address on the WAN port, or no IP at all, Vera goes into Gateway mode. 

==SSH==
For more info on how to acces Vera through SSH please click [[Logon_Vera_SSH|here]]

==Local acces==
The firewall is enabled and the DHCP server is turned on. You cannot telnet into Vera using the IP on the WAN port; you must connect your PC to the LAN 1 through LAN 4 ports and telnet to 192.168.81.1 (the default IP for Vera). Note that even in switch mode Vera will still listen to IP 192.168.81.1, so you can always set your PC to a static IP in that range. Telnet uses the default port 23.

NOTE; 
Once you set a root password, telnet is disabled and you must use ssh instead. Set the root password either with the Linux passwd command, or by going into the OpenWRT configuration found on Vera's Advanced, Net & Wi-Fi, Advanced Configuration link.

='''Performance bottlenecks with network throughput'''=

When in gateway mode (see above 'Telnet & SSH') all network traffic runs through Vera's CPU, and the CPU maxes out at around 30 Mbps and you'll find Vera is slow to respond. If you will be needing high volume network traffic it's best to use Vera in switch mode, so the network traffic goes through at full speed without using Vera's CPU. This is not a limitation of our software, it is the nature of residential/consumer access point hardware and most access points have roughly the same performance and speed of CPU.

='''Manually upgrading the firmware'''=

If you lose access through the web page you can enable SSH on Vera by setting a root password (see above 'Telnet & SSH'). Then use scp to copy the firmware image to Vera's /tmp directory. Then you can either manually write the firmware using this command:

mtd -r write [filename] linux

However you will lose all your settings. To preserve your settings name the image: firmware.img and run: /usr/bin/cmh-upgrade.sh which will create a backup of your configuration online, restore the firmware, and then restore the backup on the first boot.

For more info check the guide for flashing your Vera 1 [[Firmware_Flash_Vera_1|here]] or for Vera 2 [[Firmware_Flash_Vera2|here]]

Firmware Flash Vera 1

2011-06-02T20:06:12Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]
=This is working only for Vera 1 (Asus) platform. =
'''Important!''' 
'''''Do not use the firmware 1.0.979''''' 
 
'''NOTE''': When upgrading a Vera 1 to 1.1.1245 from a version older than 1.1.1047 is it recommended to upgrade to version 1.1.1062 first. 
After this worked, upgrading to 1.1.1245 should work fine. 

Please contact Micasaverde to obtain firmware 1.1.1062.

= For Vera 2, S/N above 10000, see [[Firmware_Flash_Vera2]] =

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

 

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

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

= PC ( Windows version ) =

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

UI4: http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1062-1.trx

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

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

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

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code. '''NOTE''': If you are running in windows Vista or 7, you'll need to right click on rescue.exe and select "Run As Administrator" or rescue.exe won't be able to find Vera.

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

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

'''Note'''

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

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/ for Windows Vista and http://www.andrels.com/wp-en_US/index.php/2009/12/how-to-enable-telnet-and-tftp-client-on-windows-7/ for Windows 7

= Mac OS Version =

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

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

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html
Or visit the official site [http://www.mac-how.net/ Mac How]

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

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

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

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

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

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

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

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

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

Firmware Flash Vera 1

2011-06-02T20:05:31Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]
=This is working only for Vera 1 (Asus) platform. =
'''Important!''' 
'''''Do not use the firmware 1.0.979''''' 
'''NOTE''': When upgrading a Vera 1 to 1.1.1245 from a version older than 1.1.1047 is it recommended to upgrade to version 1.1.1062 first. 
After this worked, upgrading to 1.1.1245 should work fine. 

Please contact Micasaverde to obtain firmware 1.1.1062.

= For Vera 2, S/N above 10000, see [[Firmware_Flash_Vera2]] =

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

 

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

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

= PC ( Windows version ) =

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

UI4: http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1062-1.trx

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

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

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

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code. '''NOTE''': If you are running in windows Vista or 7, you'll need to right click on rescue.exe and select "Run As Administrator" or rescue.exe won't be able to find Vera.

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

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

'''Note'''

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

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/ for Windows Vista and http://www.andrels.com/wp-en_US/index.php/2009/12/how-to-enable-telnet-and-tftp-client-on-windows-7/ for Windows 7

= Mac OS Version =

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

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

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html
Or visit the official site [http://www.mac-how.net/ Mac How]

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

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

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

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

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

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

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

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

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

Firmware Flash Vera 1

2011-06-02T20:04:37Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]
=This is working only for Vera 1 (Asus) platform. =
'''Important!'''
'''''Do not use the firmware 1.0.979'''''
'''NOTE''': When upgrading a Vera 1 to 1.1.1245 from a version older than 1.1.1047 is it recommended to upgrade to version 1.1.1062 first. 
After this worked, upgrading to 1.1.1245 should work fine. 

Please contact Micasaverde to obtain firmware 1.1.1062.

= For Vera 2, S/N above 10000, see [[Firmware_Flash_Vera2]] =

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

 

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

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

= PC ( Windows version ) =

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

UI4: http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1062-1.trx

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

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

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

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code. '''NOTE''': If you are running in windows Vista or 7, you'll need to right click on rescue.exe and select "Run As Administrator" or rescue.exe won't be able to find Vera.

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

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

'''Note'''

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

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/ for Windows Vista and http://www.andrels.com/wp-en_US/index.php/2009/12/how-to-enable-telnet-and-tftp-client-on-windows-7/ for Windows 7

= Mac OS Version =

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

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

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html
Or visit the official site [http://www.mac-how.net/ Mac How]

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

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

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

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

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

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

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

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

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

Firmware Flash Vera 1

2011-06-02T19:58:31Z

Henk:

[[Category:User Instructions]]
[[Category:How To]]
= Please note: This is working only for Vera 1 (Asus) platform. =
= For Vera 2, S/N above 10000, see [[Firmware_Flash_Vera2]] =

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

 

'''''Do not use the firmware 1.0.979'''''

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

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

= PC ( Windows version ) =

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

UI4: http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1062-1.trx

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

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

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

5*. Run the program 'rescue.exe' (downloaded in Step 2). Click 'browse' and find the firmware file (downloaded in Step 1). NOTE:You may need to disable your anti-virus software to run 'rescue.exe'. The anti-virus might think this is malicious code. '''NOTE''': If you are running in windows Vista or 7, you'll need to right click on rescue.exe and select "Run As Administrator" or rescue.exe won't be able to find Vera.

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

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

'''Note'''

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

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/ for Windows Vista and http://www.andrels.com/wp-en_US/index.php/2009/12/how-to-enable-telnet-and-tftp-client-on-windows-7/ for Windows 7

= Mac OS Version =

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

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

IP address: 192.168.1.10

net mask: 255.255.255.0

gateway: 192.168.1.1

DNS: 192.168.1.1 (optional)

More you can read here about setting up networking on Mac OS: http://www.net.princeton.edu/mac/network-config-x/tcpip-enet.html
Or visit the official site [http://www.mac-how.net/ Mac How]

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

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

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

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

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

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

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

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

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

Main Page

2011-05-31T20:22:40Z

Henk:

[[Category:Glossary]] [[Category:User_Instructions]] [[Category:How_To]] [[Category:Troubleshooting]] [[Category:Plugins]] [[Category:Hardware]]
 
<big>'''Welcome to the Mi Casa Verde (MiOS) wiki'''</big>
----
'''*Note:''' The Wiki documentation is for both '''Vera 1''' and '''Vera 2''' units with '''UI2''' and '''UI4''' interface.
 
=Wiki User Instructions=
This Wiki provides a lot of information on your Vera, including [[:Category:User Instructions|User Instructions]].

==Getting started==
If you are new to Vera and MiOS (former Mi Casa Verde) please check our pages on getting started, basic installation and use of menu's etc.
The pages are to be found at '''"docs.mios.com" for the older Vera UI2''' or at '''"docs2.mios.com" for the more recent Vera UI4'''. 
This last page can also be reached by clicking [http://docs2.mios.com/doc.php?language=1&manual=1&platform=0&page=preface here]

==FAQ, HOWTO and Troubleshooting==
There are separate pages containing Frequently Asked Questions, simple pages explaining "How To" and a section on troubleshooting.
 
Here is a link to the [[FAQ]] and initial [[Troubleshooting]] pages. 
Here is a link to the [[:Category:How To|How To]] section. 
Here is a link to the [[:Category:Troubleshooting|Troubleshooting]] section. 

==Luup code and Plugins==
There are already various Luup coded plugins and code examples available for users. 
You can find more information about that here [[Luup_plugins_and_Luup_code|Overview of Plugins]]

=Categories=
Information and pages on the Wiki are put into categories to keep information on a certain subject together. 
Please click [[Special:Categories|here]] for all categories.

=All Pages=
See the [[Special:AllPages|overview of all Pages]] for a list of all pages.
 
----
'''For most used categories, see the links below'''