MiOS - User contributions [en]

Aeon 4in1

2013-03-11T04:08:46Z

OTi: Extended instructions v0.2; editorial.

To use the Aeotec 4-in-1 MultiSensor with Vera, the following firmware is required:

- Aeotec MultiSensor firmware 1.18 [http://aeotec.com/partner/z-wave-firmware/viewcategory/7-multisensor]

- Vera firmware 1.5.622 [http://forum.micasaverde.com/index.php/topic,13956.0.html]

[[Image:Aeotec 4-in-1 1.png]]

 

To include and configure the MultiSensor, execute the following steps within 10 minutes:

1. Insert batteries into the MultiSensor.

2. Put Vera in inclusion mode.

3. Tap the black button on the MultiSensor.

Vera should detect the MultiSensor and the GUI will reload. After this, the motion part will be shown and the message ''Waiting for wakeup to configure device''.

[[Image:Aeotec 4-in-1 2.png]]

 

4. Tap the black button on the MultiSensor.

Vera will configure the MultiSensor and the GUI will reload. After this, all four sensor parts are shown, without values.

[[Image:Aeotec 4-in-1 3.png]]

 

5. On the ''Settings'' tab of the motion sensor part select ''Poll now''.

[[Image:Aeotec 4-in-1 4.png]]

 

Vera should poll the MultiSensor.

[[Image:Aeotec 4-in-1 5.png]]

 

6. Reload the browser page.

Sensor values should show. Initial setup is now complete. The MultiSensor should be fully functional. The default motion timeout is 4 minutes. Sensor values will be updated every 3 hours (approximately).

[[Image:Aeotec 4-in-1 6.png]]

 

The default wake-up interval is 28 minutes. If sensor value updates with every wake-up are desired, instead of every 3 hours, the minimum poll interval should be changed.

7. On the ''Settings'' tab of the motion sensor part, change the ''Poll this node at most once every'' value to 60.

[[Image:Aeotec 4-in-1 7.png]]

 

The default motion timeout is 4 minutes. A different value can be selected.

8. On the ''Device Options'' tab of the motion sensor part, change the ''Motion timeout'' (variable 3) to the desired value. [An example of 10 seconds is shown.]

[[Image:Aeotec 4-in-1 8.png]]

 

9. Click the red Save button.

Vera reloads and ''Waiting for wakeup to configure device'' is shown again.

10. Tap the black button on the MultiSensor.

Vera configures the MultiSensor and the GUI will reload.

11. Reload the browser page.

12. Verify the minimum poll interval is set to the correct value.

[[Image:Aeotec 4-in-1 9.png]]

 

13. Verify the motion timeout variable ''Current Value'' matches the ''Desired Value''.

[[Image:Aeotec 4-in-1 10.png]]

 

14. Rapidly triple click the black button on the MultiSensor.

The MultiSensor is now in a low-power state and the red LED will be off. It is ready for use.

[[Category:Hardware]]

Aeon 4in1

2013-03-11T03:55:26Z

OTi: Extended instructions [v0.1]

To use the Aeotec 4-in-1 MultiSensor with Vera, the following firmware is required:

- Aeotec MultiSensor firmware 1.18 [http://aeotec.com/partner/z-wave-firmware/viewcategory/7-multisensor]

- Vera firmware 1.5.622 [http://forum.micasaverde.com/index.php/topic,13956.0.html]

[[Image:Aeotec 4-in-1 1.png]]

 

To include and configure the MultiSensor, execute the following steps within 10 minutes:

1. Insert batteries into the MultiSensor.

2. Put Vera in inclusion mode.

3. Tap the black button on the MultiSensor.

Vera should detect the MultiSensor and the GUI will reload. After this, the motion part will be shown and the message ''Waiting for wakeup to configure device''.

[[Image:Aeotec 4-in-1 2.png]]

 

4. Tap the black button on the MultiSensor.

Vera will configure the MultiSensor and GUI will reload. After this, all four sensor parts are shown, without values.

[[Image:Aeotec 4-in-1 3.png]]

 

5. On the Settings tab of the motion sensor part select ''Poll now''.

[[Image:Aeotec 4-in-1 4.png]]

 

Vera should poll the MultiSensor.

[[Image:Aeotec 4-in-1 5.png]]

 

6. Reload the browser page.

Sensor values should show. Initial setup is now complete. The MultiSensor should be fully functional. The default motion timeout is 4 minutes. Sensor values will be updated every 3 hours (approximately).

[[Image:Aeotec 4-in-1 6.png]]

 

The default wake-up interval is 28 minutes. If sensor value updates with every wake-up are desired, instead of every 3 hours, the minimum poll interval should be changed.

7. On the ''Settings'' tab of the motion sensor part, change the ''Poll this node at most once every'' value to 60.

[[Image:Aeotec 4-in-1 7.png]]

 

The default motion timeout is 4 minutes. A different value can be selected.

8. On the ''Device Options'' tab of the motion sensor part, change the ''Motion timeout'' (variable 3) to the desired value. [An example of 10 seconds is shown.]

[[Image:Aeotec 4-in-1 8.png]]

 

9. Click the red Save button.

Vera reloads and ''Waiting for wakeup to configure device'' is shown again.

10. Tap the black button on the MultiSensor.

Vera configures the MultiSensor and the GUI will reload.

11. Refresh the browser page.

12. Verify the minimum poll interval is set to the correct value.

[[Image:Aeotec 4-in-1 9.png]]

 

13. Verify the motion timeout variable current value matches the desired value.

[[Image:Aeotec 4-in-1 10.png]]

 

14. Rapidly triple click the black button on the MultiSensor.

The MultiSensor is now in a low-power state and the red LED will be off. It is ready for use.

[[Category:Hardware]]

File:Aeotec 4-in-1 10.png

2013-03-11T03:11:39Z

OTi:

File:Aeotec 4-in-1 9.png

2013-03-11T03:11:29Z

OTi:

File:Aeotec 4-in-1 8.png

2013-03-11T03:11:19Z

OTi:

File:Aeotec 4-in-1 7.png

2013-03-11T03:11:09Z

OTi:

File:Aeotec 4-in-1 6.png

2013-03-11T03:10:58Z

OTi:

File:Aeotec 4-in-1 5.png

2013-03-11T03:10:47Z

OTi:

File:Aeotec 4-in-1 4.png

2013-03-11T03:10:37Z

OTi:

File:Aeotec 4-in-1 3.png

2013-03-11T03:09:44Z

OTi:

File:Aeotec 4-in-1 2.png

2013-03-11T03:09:31Z

OTi:

File:Aeotec 4-in-1 1.png

2013-03-11T03:09:14Z

OTi:

Aeon 4in1

2012-10-16T13:06:51Z

OTi: Temporary note

Note (October 2012): due to a change of the firmware in the production version of the Aeotec 4-in-1, it has been reported that the sensor is not currently fully functional in combination with Vera running firmware 1.5.408. (A private beta version of the Vera firmware appears to resolve this.)


The Aeon 4-in-1 multi-sensor is supported in firmware versions over 1.1.1280. It appears as 4 devices: a motion sensor, a light sensor, a humidity sensor, and a temp sensor.

To include the sensor, choose Add Device on your MIOS system, and then tap the black button by the battery compartment.  Once it appears in your system, if it is not yet configured, hold the black button for 3 seconds and release.   This causes the sensor to wake up so it can be configured, at which point it will appear as 4 devices.

Once the sensor is configured, you can hold the black button for 3 seconds again to force it to wake up so it can be polled for the temperature, humidity, light level, and motion sensor trip status.  Note that it will only be polled once every 10 minutes to conserve the batteries.  To force a poll on the next wakeup click the 'Poll Now' button on the MIOS dashboard for the motion sensor device.

[[Category:Hardware]]

Comparison of Vera units

2012-07-11T11:29:21Z

OTi: Change 1 LAN port to 1 WAN port for Vera Lite.

{| cellspacing="1" cellpadding="1" border="1" style="width: 1066px; height: 563px;"
|-
| colspan="5" |  '''                                                                                              Technical Specs Comparison''' 
|-
|   '''Vera Model'''
|                 '''Vera 1''' 
|                   '''Vera 2''' 
|                  '''Vera Lite''' 
|                    '''Vera 3''' 
|-
|   '''CPU''' 
|           240 MHz MIPS 
|          240 MHz MIPS 
|           500 MHz MIPS 
|          500 MHz MIPS 
|-
|   '''Flash NAND''' 
|                 8 MB 
|                  16 MB 
|                 32 MB 
|                  32 MB 
|-
|  '''RAM''' 
|                 32 MB DDR 
|                  32 MB DDR2 
|                 64 MB DDR2 
|                  128 MB DDR2 
|-
|   '''USB Ports''' 
|                 2 USB 2.0 
|                   2 USB 2.0 
|                  1 USB 2.0 
|                    2 USB 2.0 
|-
|   '''WAN Ports''' 
|                  1 
|                       1 
|                         1 
|                        1 
|-
|   '''LAN Ports''' 
|                  4 
|                       1 
|                         -
|                         4 
|-
|   '''Z-Wave''' 
|             USB Dongle 
|   Built-in with internal antenna 
|    Built-in with internal antenna 
|   Built-in with internal antenna 
|-
|   '''Wi-Fi''' 
|           IEEE 802.11b/g 
|           IEEE 802.11b/g 
|                          - 
|               IEEE 802.11b/g/n 
|-
|   '''UI Version''' 
|       UI2 upgradeable to UI4 
|         UI4 upgradeable to UI5
|                      UI5 
|                       UI5 
|-
|   '''Dimensions (HxWxD)'''
|                      - 
|     165mm x 101mm x 38mm 
|     116mm x 95mm x 44mm 
|    177mm x 130mm x 34mm 
|-
|   '''Battery Pack''' 
|                      - 
|         External, Rechargeable 
|        4 AA batteries (included) 
|         External, Rechargeable 
|}

Release Notes

2012-01-22T11:20:16Z

OTi: Add private beta banner

== UI5 : 1.5.276 - January 20, 2012 - private beta ==

Resolved issues in 1.5.276:

#Remove 2 variables for the yale
#do not consider time successfully synced if year is not between 2012 and 2020
#use a function (get_server) to get a certain server value from servers.conf file
#force a reboot in max 15 minutes if the previous scripts don't do it faster
#start force reboot in background to be sure we don't get stuck by reboot command and wait 1 minute before forcing a reboot at firmware upgrade.
#read the wan/lan ifname from /var/state first, in case the type or proto is not standard the interfaces name will be different than the one defined in the /etc/config/network
#for units with rtc : update RTC on success sync time and update system time at boot from it
#fix firewall/dhcp in client mode for Vera3 
# allow only one network restart at a time
#store last field received in FORM_timezone in file /etc/TZ instead of 3rd
#prevent php 5.3.x to lighttpd bug by stripping dirs from FORM_file_name variable
#read language and language_id directly from files 
#use main server if servers.conf file is messed up 
#log each server which is not defined
#req OpenWRT ver 75 for Vera3 and Lite
#add kernel patches to improve/fix issues related to nand driver,jffs2 and overlayfs fs
#fix time in NetworkMonitor
#fix camera relay
#fix record scene
# fix multiple room
#add custom require function
#fixes to danfoss living connect
#mantis [http://bugs.micasaverde.com/view.php?id=1978 1978] [private], [http://bugs.micasaverde.com/view.php?id=1957 1957] [Triggers for deleted devices are not deleted]
#delete wrong plugin 5 and 188
#strip independently bin and lib
#removed duplicate dir
#Fixed bug [http://bugs.micasaverde.com/view.php?id=1967 1967] [private]
#Menu changes to have separate controls for help buttons.
#add support for SWITCH_MULTILEVEL_STOP_LEVEL_CHANGE
#mantis [http://bugs.micasaverde.com/view.php?id=2047 2047] [private] and [http://bugs.micasaverde.com/view.php?id=2079 2079] [private]
#fix creation of IR devices in UI5
#mantis [http://bugs.micasaverde.com/view.php?id=2054 2054] [Inform user when the serial port assigned to a device no longer exists]
#Swapped two strings for polling settings description
#Added alerts legend
#Mantis [http://bugs.micasaverde.com/view.php?id=2007 #2007] [Add an anti caching token to list_alerts]
#Mantis [http://bugs.micasaverde.com/view.php?id=2011 #2011] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=2008 #2008] [useless message when failing to add a user]
#Mantis [http://bugs.micasaverde.com/view.php?id=2024 #2024] [Missing leading 0 from backup names]
#Mantis [http://bugs.micasaverde.com/view.php?id=2012 #2012] [clicking the 'clock' should be a shortcut to the setup, location]
#Mantis [http://bugs.micasaverde.com/view.php?id=1970 #1970] [Firebug error at click on Revert changes button]
#Mantis [http://bugs.micasaverde.com/view.php?id=1686 #1686] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1934 #1934] [Legend for My Alerts should be added]
#Fixed [http://bugs.micasaverde.com/view.php?id=2021 #2021] [fix lingering dongle text in UI5]
#Moved help urls outside tabs.
#added help button
#Archive fix for reseting page on filters change.
#Added note about auto-updating timezone. 
#Hided manually timezone set when there is internet.
#Mantis [http://bugs.micasaverde.com/view.php?id=2045 #2045] [Message please wait is not closed when ERGY plugin finish installing]
#Mantis [http://bugs.micasaverde.com/view.php?id=2033 #2033] [Remove some text from Energy/Hystoric usage]
# Added offline mode for UI. 
# Added cameras reported as accessories.
#Mantis [http://bugs.micasaverde.com/view.php?id=2025 #2025] [Gateway list is incorrectly opened]
#Mantis [http://bugs.micasaverde.com/view.php?id=2005 #2005] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1953 #1953] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1889 #1889] [Multi-language issues]
#Added Alerts tooltip
#Mantis [http://bugs.micasaverde.com/view.php?id=2075 #2075] [Heal network with /without stress test is not working]
#Mantis [http://bugs.micasaverde.com/view.php?id=2015 #2015] [SMS and Email Notification Test Button]
#Mantis [http://bugs.micasaverde.com/view.php?id=2004 #2004] [Unable to assign a device to a room in IE9]
#Fixed help urls.
#Fixed accessories to allow update only for owned devices.
#Mobile phones/av gear formatting.
#Fixed missing location box
#Added validation for set date fields

 

== UI5 : 1.5.255 (Vera2) & 1.5.254 (Vera3) - December 23, 2011 ==

New features in UI5:

1. Devices are organized and displayed in separate tabs by category: lights, sensors, cameras, etc.

2. You can pin the most often used devices and scenes on the Dashboard for quick access. The devices and scenes that are not pinned won't be displayed on the Dashboard.

3. The Add Device Wizard is now included in UI.

4. You can view and manage all the existing triggers (events) and schedules (timers) on Vera without opening any scene.

5. Creating scenes is easier and more intuitive with the new scene creator wizard.

6. You can now see the scene commands in the Advanced scene editor.

7. The MiOS Marketplace (now called MiOS Apps) functionality is now included in UI. You can:

*View app information
*Install apps
*View and Add reviews

8. The MiOS control panel (CP) functionality is now included in UI, but only if the user is authenticated. You can:

*Connect to one of your other Veras
*Add new or existing users to your Vera
*Remove users from your Vera
*Change your MiOS account password
*View alerts
*View available backups
*Change unit settings, like the Vera name and the number of SMSes and e-mails per day
*View camera archives

9. Energy monitoring using the ERGY plugin by EchoLabs, which is included in UI.

10. Real-time camera video streaming and video recording.

 

 This documents the changes since the first public beta release of UI4, 1.1.1047

== UI4 : 1.1.1338 - July 29, 2011 - RC ==

1. Use the Z-Wave double send (without ACK then with ACK) for lights only, not other devices, since its purpose was to eliminate the popcorn effect and creates unnecessary traffic otherwise.

2. Add special handling for devices made by Fibar for 2 way feedback

3. Fix NetworkMonitor so it will always reset the time if it doesn't get set at boot

4. Fix a bug in a script in the prior beta that made it incompatible with Vera 1

5. Add the pulse variable to the sdata request for energy meters

6. Fix a problem where changes saved got lost because luaupnp got a reload and the watchdog timer kicked in before it had finished flushing the files to disk.

7. Add support for Schedule Entry version 3 command class and locks by Assa Abloy

8. Tweak to the timing of the squashfs mounting to improve reliability

== 1.1.1323 - July 13, 2011 - beta ==

1. Fix a problem where a configure job could get stuck and not finish due to a race condition between multiple jobs

2. Fix problem where zwave frame collission resulted in failed job

3. Reduce incidence of EEPROM corruption in Z-Wave 4.52 where it mistakenly thinks there is a suc and gives "Failed to go into learn mode" errors when adding nodes.

4. Automatically correct situation #3 if the user has not already added devices.

5. Synchronize deleted devices with the central server

6. Add subcategory to identify types of security sensors

7. Add circulate fan mode support (not in the UI yet, but coming in UI5)

== 1.1.1298 - June 21, 2011 - beta ==

The primary reason for this release is that there was a bug in 1.1.1245 that prevented Z-Wave 'reset network' from working, and some users got stuck with a "failled to start z-wave" error.

1. Add default values for sensors as not-tripped so it appears correctly in the UI when the sensor hasn't been used yet.

2. Add support for multi-channel association

3. Add support for Danfoss thermostat

4. Fix for X10 devices that have 2 digit numeric ID's

5. Add support for Everspring motion sensors

6. Add support for Aeon 4-in-1 sensors

7. Minor enhancements to the wakeup procedure to support devices with short wakeup times

8. Fix support for the gc-100

9. Add support for the PolyControl door lock

10. Change the default PIN for locks to 8 characters instead of 4

 

== 1.1.1245 - April 20, 2011 - release ==

Most notably this release includes a new version of the Z-Wave firmware in the Z-Wave chip, and this new version allows Vera to optimize the routes the Z-Wave mesh network uses. This should improve reliability. See [[MigrateTo452]] Also Vera will no longer scan for UPnP devices unless you choose 'Add Device' and at the bottom check the option to scan for UPnP devices.

1. The energy plugin is now built into the engine. It will be removed on upgrade. Energy events are logged to your mios.com account automatically.

2. There is an option with Vera2 (Currently not working with Vera1) on Advanced, Logs to enable logging to a USB stick. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running. '''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac.'''

3. There is a fix to prevent the main engine from starting before Vera has synced the date/time, which previously had caused sunset/sunrise timers to trigger unexpectedly. There is no battery-backed up clock in Vera. It needs to get the date/time from the internet at each boot.

4. This fixes a bug causing high CPU load and reboot when certain UPnP devices are detected on the network, such as Sonos.

5. The DSC plugin, and possibly others that use serial ports, did not work because the engine was trying to open the port twice.

6. Add some extra info in the heal process, and report the health rating and heal date to our tech support server along with ZWave node info, so, when a customer calls in for support, we will know what types of devices he has and how healthy they are to make better recommendations about improving ZWave reliability.

7. Some startup messages weren't displayed properly in the info panel.

8. Bad UPnP devices on the network that constantly report themselves every 1 second with a new UUID would eventually consume all the memory causing a crash. Now the software filters these rogue devices.

8. There's a new lu_sdata request that makes it much simpler to develop third party user interfaces to control the system. See: [[UI Simple]]

9. Store a counter of all polls (PollOk) with the number that failed transmission (PollTxFail) or failed to reply (PollNoReply). All counters are reset whenever you do a heal network. The counters are visible as extra variables in the device's advanced tab. This is for troubleshooting ZWave problems.

10. Add support for viewing live, streaming video. [[Remote Camera Streaming]]

11. Fix that sometimes variables across multiple bridged MiOS systems weren't being synchronized all the time.

12. Increase the timeouts for some internet operations so it works on super, super slow connections like satellite.

13. Fix for thermostats always showing fan as 'On' when it's in auto.

14. Add support for Fortrezz WMA-02, with new 'Leak alarm' event

15. Add support for Alarm Command Class version 2

16. Fix a crash caused by wakeup interval set to the minimum value

17. Fix problem with Insteon not starting when there are a lot of existing devices.

18. Fix problem with a LuaUPnP process not cleanly exiting, causing the UPnP port to remain stuck for 2 minutes and slowing down reload.

19. Implement a new Infrared learning, identifying, transmitting engine.

20. Fix toggle state with Insteon.

21. Add basic support for Zigbee lights with a SimpleHomeNet ZBPLM and Luup Plugin

22. Fix crash when adding new A/V devices

23. Reduce the delay between Z-Wave commands to solve startup problems on large networks

24. Add support for Yale/Assa Abbloy locks

25. Fix to handle Luup plugins staying locked to the right serial port when they're unplugged/reconnected.

26. Prevent Insteon module from taking over a serial port

27. Upgrade the ftdi_sio driver to support new infrared blaster

28. Fix intermittent crash when receiving a wakeup command

29. Add attribute set to the Luup API

30. Add Sleep to the Luup API

31. Reduce number of retries for download files/plugins

32. Use separate worker threads for slow processes like downloading vs fast processes like Z-Wave response to speed up the response to time sensitive tasks.

33. Don't execute timers if time jumps, caused by a new sync to the ntp server

34. Increase wait time for Luup plugins from 45 seconds to 90 to resolve some slow plugins that take a long time to initialize.

35. Add logging for the last time the battery level was reported and show the battery icon as a ? if it's been more than 7 days.

36. Fix problem with variableset Luup command not setting value always.

37. Don't repoll or reconfigure battery operated devices that wakeup constantly. At most re-poll every 10 minutes.

38. Add new scene recorder feature for easier scene creation.

39. Fix problem with the UI4 dashboard getting out of sync with the engine.

40. Fix problem with creation of 2 cameras using the same plugin.

41. Always write user_data when child devices change in case the reload doesn't work, causing a never ending cycle

42. Log uptime and track memory leaks.

43. Add crossdomain.xml so ActionScript clients can poll

44. Fix deadlock problem when aborting an existing send data command

45. Rewrite the watchdog function so it catches threads that don't exit after the main one closes

46. Add a tracking and reporting of 'tardy' tasks that run more than 3 seconds after they should.

47. Add decoding of infrared signals to extract the protocol, device and button codes from a learned i/r signal

48. Toggle the CPLD chip if the Z-Wave module stops responding to try to wake it up.

49. Allow scenes to control A/V devices

50. Fix for Leviton ZRCS4 id=2050 for 0-3 buttons

51. Increase timeout of http fetches for slow satellite internet connections

52. Allow Luup plugins (SQRemote) to remotely turn on features with a provision flag.

53. Don't treat superceded jobs as an error.

54. Fix issue with bridged systems not syncing state changes

55. Fix issue with bridged systems and deep nested trees of devices more than 3 layers deep (ie 3-in-1 sensor)

56. Re-write bridging code to reduce memory usage.

57. Prevent UPnP devices from being marked offline if the luup plugin doesn't load.

58. Add timestamps for all stages of the Z-Wave heal

59. Add support for measuring KWH and resetting the cumulative measurement

60. Add support for new Z-Wave metering classes

61. Add buttons for streaming and still camera images

62. Fix to prevent some messages from getting lost in the info panel

63. Fix when adding/removing multiple devices with a timeout and not doing anything that it showed it stayed in 'add/remove' mode.

64. Add filter when UPnP devices broadcast constantly to prevent bogging down the system.

65. Few minor Z-Wave changes required to pass Sigma certification. Engine is now certified.

66. Re-order the on/off buttons in UI4.

67. Keep a log of polling history and success/fail, report to central server to assist tech support.

68. Filter duplicate nonce's from secure devices.

69. Fix scenes not updating from bridge's systems

70. Add an auto purge of excessive ip and/or upnp requests so the user_data file doesn't grow bigger than the memory supports.

71. Add a watchdog to the remote access tunnels to ensure access through cp.mios.com stays alive

72. If the Z-Wave network doesn't start stop resetting the Insteon network too

73. Change default poll interval on FLiRS devices to 10800 seconds instead of 60 to conserve the battery

74. Fix mantis #1293 - Can't add notification for a device if no Scene is added previously

75. Fix mantis #1275 - Add options in Scene to show all devices in all rooms or filter by their type

76. Fix mantis #1317 - Replace Archive old logs on findvera with Archive old logs on mios.com

77. Fix mantis #1238 - Wizard through cp.mios.com displaying a 404 Error.

78. Fix mantis #1115 - text tweak on the 'add camera' page in the setup wizard

79. Fix mantis #1356 - Enable mod_expire in lighttpd, have it "cache" images directories to avoid constant reload.

80. Fix mantis #1207 - be sure the 4 buttons that remove devices have ok/cancel popups

81. Fix mantis #1213 - if a device is imported, the 'wrench' setup icon should be grayed out

82. Fix mantis #1251 - easier to use cameras

83. Fix mantis #1314 - Empty Scene name

84. Fix mantis #1360 - Don't update database fields with empty strings

85. Fix scheduling user codes with a Schlage lock

86. Fix compatibility with some Leviton scene/zone controllers using 100/200 series chips

87. Prevent heal from aborting if there's lots of activity going on

88. Fix so you can create custom luup handlers for actions with the same name and service file, but separate service id's, like heat and cool.

89. Add the option of switching to the 3.20 (aka 4.52) branch of Z-Wave firmware

90. Allow for manual routing when using 3.20

91. New heal routine that tests and optimizes Z-Wave routes.

92. A basic heal will be performed automatically at night if Vera has lost communication with some nodes.

93. Advanced users can now specify routes to nodes

94. Fix deleting devices not showing up in the UI.

95. Heal will auto-resume if it's aborted due to a crash or power outage

96. Add support for meter table class (Kamstrup power meters)

97. Do not discover UPNP devices by default anymore, unless the user requests it on the Add Device page.

98. Fix mantis #1391: Cannot add control over another UPnP device

99. Remove the 'Logs' for a device in the UI4 dashboard. Now go to cp.mios.com and choose Events.

== Old, archived release notes ==

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

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

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

4. Fix compatibility with the Fortrezz water valve

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

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

7. Fix one Vera controlling other UPnP devices.

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

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

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

----

After 996

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

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

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

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

15. Fix a crash while logging DHCP requests

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

17. Migrate to the new server structure with redundannt servers

18. Add ability to do ZWave multi-cast.

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

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

21. Don't set or restore default names that have been set with ZWave node naming get (ie starting with _).

22. Add ability to specify custom device types and names for products based on the ZWave manufacturer and product ID's and an xml file, including default names and variable settings.

23. Some ZWave chips seem to have trouble going into 'add node' mode when the commands are sent fast, so added some delays.

24. Add handling for more alarms from door locks, like when new user codes are added and removed, and low battery alarms.

25. For slow IP cameras there is now a timeout setting that can be increased to allow more time to return the JPEG. Also, the engine won't block the browser if the camera takes more than 3 seconds to respond. It will continue to retrieve the image in the background return it with the subsequent request.

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

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

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

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

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

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

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

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

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

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

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

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

11. Add default free dns servers: OpenDNS.org

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

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

'''Fixes:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Glossary]]

Release Notes

2012-01-21T18:07:32Z

OTi: Add abstracts

== UI5 : 1.5.276 - January 20, 2012 - beta ==

Resolved issues in 1.5.276:

#Remove 2 variables for the yale
#do not consider time successfully synced if year is not between 2012 and 2020
#use a function (get_server) to get a certain server value from servers.conf file
#force a reboot in max 15 minutes if the previous scripts don't do it faster
#start force reboot in background to be sure we don't get stuck by reboot command and wait 1 minute before forcing a reboot at firmware upgrade.
#read the wan/lan ifname from /var/state first, in case the type or proto is not standard the interfaces name will be different than the one defined in the /etc/config/network
#for units with rtc : update RTC on success sync time and update system time at boot from it
#fix firewall/dhcp in client mode for Vera3 
# allow only one network restart at a time
#store last field received in FORM_timezone in file /etc/TZ instead of 3rd
#prevent php 5.3.x to lighttpd bug by stripping dirs from FORM_file_name variable
#read language and language_id directly from files 
#use main server if servers.conf file is messed up 
#log each server which is not defined
#req OpenWRT ver 75 for Vera3 and Lite
#add kernel patches to improve/fix issues related to nand driver,jffs2 and overlayfs fs
#fix time in NetworkMonitor
#fix camera relay
#fix record scene
# fix multiple room
#add custom require function
#fixes to danfoss living connect
#mantis [http://bugs.micasaverde.com/view.php?id=1978 1978] [private], [http://bugs.micasaverde.com/view.php?id=1957 1957] [Triggers for deleted devices are not deleted]
#delete wrong plugin 5 and 188
#strip independently bin and lib
#removed duplicate dir
#Fixed bug [http://bugs.micasaverde.com/view.php?id=1967 1967] [private]
#Menu changes to have separate controls for help buttons.
#add support for SWITCH_MULTILEVEL_STOP_LEVEL_CHANGE
#mantis [http://bugs.micasaverde.com/view.php?id=2047 2047] [private] and [http://bugs.micasaverde.com/view.php?id=2079 2079] [private]
#fix creation of IR devices in UI5
#mantis [http://bugs.micasaverde.com/view.php?id=2054 2054] [Inform user when the serial port assigned to a device no longer exists]
#Swapped two strings for polling settings description
#Added alerts legend
#Mantis [http://bugs.micasaverde.com/view.php?id=2007 #2007] [Add an anti caching token to list_alerts]
#Mantis [http://bugs.micasaverde.com/view.php?id=2011 #2011] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=2008 #2008] [useless message when failing to add a user]
#Mantis [http://bugs.micasaverde.com/view.php?id=2024 #2024] [Missing leading 0 from backup names]
#Mantis [http://bugs.micasaverde.com/view.php?id=2012 #2012] [clicking the 'clock' should be a shortcut to the setup, location]
#Mantis [http://bugs.micasaverde.com/view.php?id=1970 #1970] [Firebug error at click on Revert changes button]
#Mantis [http://bugs.micasaverde.com/view.php?id=1686 #1686] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1934 #1934] [Legend for My Alerts should be added]
#Fixed [http://bugs.micasaverde.com/view.php?id=2021 #2021] [fix lingering dongle text in UI5]
#Moved help urls outside tabs.
#added help button
#Archive fix for reseting page on filters change.
#Added note about auto-updating timezone. 
#Hided manually timezone set when there is internet.
#Mantis [http://bugs.micasaverde.com/view.php?id=2045 #2045] [Message please wait is not closed when ERGY plugin finish installing]
#Mantis [http://bugs.micasaverde.com/view.php?id=2033 #2033] [Remove some text from Energy/Hystoric usage]
# Added offline mode for UI. 
# Added cameras reported as accessories.
#Mantis [http://bugs.micasaverde.com/view.php?id=2025 #2025] [Gateway list is incorrectly opened]
#Mantis [http://bugs.micasaverde.com/view.php?id=2005 #2005] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1953 #1953] [private]
#Mantis [http://bugs.micasaverde.com/view.php?id=1889 #1889] [Multi-language issues]
#Added Alerts tooltip
#Mantis [http://bugs.micasaverde.com/view.php?id=2075 #2075] [Heal network with /without stress test is not working]
#Mantis [http://bugs.micasaverde.com/view.php?id=2015 #2015] [SMS and Email Notification Test Button]
#Mantis [http://bugs.micasaverde.com/view.php?id=2004 #2004] [Unable to assign a device to a room in IE9]
#Fixed help urls.
#Fixed accessories to allow update only for owned devices.
#Mobile phones/av gear formatting.
#Fixed missing location box
#Added validation for set date fields

 

== UI5 : 1.5.255 (Vera2) & 1.5.254 (Vera3) - December 23, 2011 ==

New features in UI5:

1. Devices are organized and displayed in separate tabs by category: lights, sensors, cameras, etc.

2. You can pin the most often used devices and scenes on the Dashboard for quick access. The devices and scenes that are not pinned won't be displayed on the Dashboard.

3. The Add Device Wizard is now included in UI.

4. You can view and manage all the existing triggers (events) and schedules (timers) on Vera without opening any scene.

5. Creating scenes is easier and more intuitive with the new scene creator wizard.

6. You can now see the scene commands in the Advanced scene editor.

7. The MiOS Marketplace (now called MiOS Apps) functionality is now included in UI. You can:

*View app information
*Install apps
*View and Add reviews

8. The MiOS control panel (CP) functionality is now included in UI, but only if the user is authenticated. You can:

*Connect to one of your other Veras
*Add new or existing users to your Vera
*Remove users from your Vera
*Change your MiOS account password
*View alerts
*View available backups
*Change unit settings, like the Vera name and the number of SMSes and e-mails per day
*View camera archives

9. Energy monitoring using the ERGY plugin by EchoLabs, which is included in UI.

10. Real-time camera video streaming and video recording.

 

 This documents the changes since the first public beta release of UI4, 1.1.1047

== UI4 : 1.1.1338 - July 29, 2011 - RC ==

1. Use the Z-Wave double send (without ACK then with ACK) for lights only, not other devices, since its purpose was to eliminate the popcorn effect and creates unnecessary traffic otherwise.

2. Add special handling for devices made by Fibar for 2 way feedback

3. Fix NetworkMonitor so it will always reset the time if it doesn't get set at boot

4. Fix a bug in a script in the prior beta that made it incompatible with Vera 1

5. Add the pulse variable to the sdata request for energy meters

6. Fix a problem where changes saved got lost because luaupnp got a reload and the watchdog timer kicked in before it had finished flushing the files to disk.

7. Add support for Schedule Entry version 3 command class and locks by Assa Abloy

8. Tweak to the timing of the squashfs mounting to improve reliability

== 1.1.1323 - July 13, 2011 - beta ==

1. Fix a problem where a configure job could get stuck and not finish due to a race condition between multiple jobs

2. Fix problem where zwave frame collission resulted in failed job

3. Reduce incidence of EEPROM corruption in Z-Wave 4.52 where it mistakenly thinks there is a suc and gives "Failed to go into learn mode" errors when adding nodes.

4. Automatically correct situation #3 if the user has not already added devices.

5. Synchronize deleted devices with the central server

6. Add subcategory to identify types of security sensors

7. Add circulate fan mode support (not in the UI yet, but coming in UI5)

== 1.1.1298 - June 21, 2011 - beta ==

The primary reason for this release is that there was a bug in 1.1.1245 that prevented Z-Wave 'reset network' from working, and some users got stuck with a "failled to start z-wave" error.

1. Add default values for sensors as not-tripped so it appears correctly in the UI when the sensor hasn't been used yet.

2. Add support for multi-channel association

3. Add support for Danfoss thermostat

4. Fix for X10 devices that have 2 digit numeric ID's

5. Add support for Everspring motion sensors

6. Add support for Aeon 4-in-1 sensors

7. Minor enhancements to the wakeup procedure to support devices with short wakeup times

8. Fix support for the gc-100

9. Add support for the PolyControl door lock

10. Change the default PIN for locks to 8 characters instead of 4

 

== 1.1.1245 - April 20, 2011 - release ==

Most notably this release includes a new version of the Z-Wave firmware in the Z-Wave chip, and this new version allows Vera to optimize the routes the Z-Wave mesh network uses. This should improve reliability. See [[MigrateTo452]] Also Vera will no longer scan for UPnP devices unless you choose 'Add Device' and at the bottom check the option to scan for UPnP devices.

1. The energy plugin is now built into the engine. It will be removed on upgrade. Energy events are logged to your mios.com account automatically.

2. There is an option with Vera2 (Currently not working with Vera1) on Advanced, Logs to enable logging to a USB stick. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running. '''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac.'''

3. There is a fix to prevent the main engine from starting before Vera has synced the date/time, which previously had caused sunset/sunrise timers to trigger unexpectedly. There is no battery-backed up clock in Vera. It needs to get the date/time from the internet at each boot.

4. This fixes a bug causing high CPU load and reboot when certain UPnP devices are detected on the network, such as Sonos.

5. The DSC plugin, and possibly others that use serial ports, did not work because the engine was trying to open the port twice.

6. Add some extra info in the heal process, and report the health rating and heal date to our tech support server along with ZWave node info, so, when a customer calls in for support, we will know what types of devices he has and how healthy they are to make better recommendations about improving ZWave reliability.

7. Some startup messages weren't displayed properly in the info panel.

8. Bad UPnP devices on the network that constantly report themselves every 1 second with a new UUID would eventually consume all the memory causing a crash. Now the software filters these rogue devices.

8. There's a new lu_sdata request that makes it much simpler to develop third party user interfaces to control the system. See: [[UI Simple]]

9. Store a counter of all polls (PollOk) with the number that failed transmission (PollTxFail) or failed to reply (PollNoReply). All counters are reset whenever you do a heal network. The counters are visible as extra variables in the device's advanced tab. This is for troubleshooting ZWave problems.

10. Add support for viewing live, streaming video. [[Remote Camera Streaming]]

11. Fix that sometimes variables across multiple bridged MiOS systems weren't being synchronized all the time.

12. Increase the timeouts for some internet operations so it works on super, super slow connections like satellite.

13. Fix for thermostats always showing fan as 'On' when it's in auto.

14. Add support for Fortrezz WMA-02, with new 'Leak alarm' event

15. Add support for Alarm Command Class version 2

16. Fix a crash caused by wakeup interval set to the minimum value

17. Fix problem with Insteon not starting when there are a lot of existing devices.

18. Fix problem with a LuaUPnP process not cleanly exiting, causing the UPnP port to remain stuck for 2 minutes and slowing down reload.

19. Implement a new Infrared learning, identifying, transmitting engine.

20. Fix toggle state with Insteon.

21. Add basic support for Zigbee lights with a SimpleHomeNet ZBPLM and Luup Plugin

22. Fix crash when adding new A/V devices

23. Reduce the delay between Z-Wave commands to solve startup problems on large networks

24. Add support for Yale/Assa Abbloy locks

25. Fix to handle Luup plugins staying locked to the right serial port when they're unplugged/reconnected.

26. Prevent Insteon module from taking over a serial port

27. Upgrade the ftdi_sio driver to support new infrared blaster

28. Fix intermittent crash when receiving a wakeup command

29. Add attribute set to the Luup API

30. Add Sleep to the Luup API

31. Reduce number of retries for download files/plugins

32. Use separate worker threads for slow processes like downloading vs fast processes like Z-Wave response to speed up the response to time sensitive tasks.

33. Don't execute timers if time jumps, caused by a new sync to the ntp server

34. Increase wait time for Luup plugins from 45 seconds to 90 to resolve some slow plugins that take a long time to initialize.

35. Add logging for the last time the battery level was reported and show the battery icon as a ? if it's been more than 7 days.

36. Fix problem with variableset Luup command not setting value always.

37. Don't repoll or reconfigure battery operated devices that wakeup constantly. At most re-poll every 10 minutes.

38. Add new scene recorder feature for easier scene creation.

39. Fix problem with the UI4 dashboard getting out of sync with the engine.

40. Fix problem with creation of 2 cameras using the same plugin.

41. Always write user_data when child devices change in case the reload doesn't work, causing a never ending cycle

42. Log uptime and track memory leaks.

43. Add crossdomain.xml so ActionScript clients can poll

44. Fix deadlock problem when aborting an existing send data command

45. Rewrite the watchdog function so it catches threads that don't exit after the main one closes

46. Add a tracking and reporting of 'tardy' tasks that run more than 3 seconds after they should.

47. Add decoding of infrared signals to extract the protocol, device and button codes from a learned i/r signal

48. Toggle the CPLD chip if the Z-Wave module stops responding to try to wake it up.

49. Allow scenes to control A/V devices

50. Fix for Leviton ZRCS4 id=2050 for 0-3 buttons

51. Increase timeout of http fetches for slow satellite internet connections

52. Allow Luup plugins (SQRemote) to remotely turn on features with a provision flag.

53. Don't treat superceded jobs as an error.

54. Fix issue with bridged systems not syncing state changes

55. Fix issue with bridged systems and deep nested trees of devices more than 3 layers deep (ie 3-in-1 sensor)

56. Re-write bridging code to reduce memory usage.

57. Prevent UPnP devices from being marked offline if the luup plugin doesn't load.

58. Add timestamps for all stages of the Z-Wave heal

59. Add support for measuring KWH and resetting the cumulative measurement

60. Add support for new Z-Wave metering classes

61. Add buttons for streaming and still camera images

62. Fix to prevent some messages from getting lost in the info panel

63. Fix when adding/removing multiple devices with a timeout and not doing anything that it showed it stayed in 'add/remove' mode.

64. Add filter when UPnP devices broadcast constantly to prevent bogging down the system.

65. Few minor Z-Wave changes required to pass Sigma certification. Engine is now certified.

66. Re-order the on/off buttons in UI4.

67. Keep a log of polling history and success/fail, report to central server to assist tech support.

68. Filter duplicate nonce's from secure devices.

69. Fix scenes not updating from bridge's systems

70. Add an auto purge of excessive ip and/or upnp requests so the user_data file doesn't grow bigger than the memory supports.

71. Add a watchdog to the remote access tunnels to ensure access through cp.mios.com stays alive

72. If the Z-Wave network doesn't start stop resetting the Insteon network too

73. Change default poll interval on FLiRS devices to 10800 seconds instead of 60 to conserve the battery

74. Fix mantis #1293 - Can't add notification for a device if no Scene is added previously

75. Fix mantis #1275 - Add options in Scene to show all devices in all rooms or filter by their type

76. Fix mantis #1317 - Replace Archive old logs on findvera with Archive old logs on mios.com

77. Fix mantis #1238 - Wizard through cp.mios.com displaying a 404 Error.

78. Fix mantis #1115 - text tweak on the 'add camera' page in the setup wizard

79. Fix mantis #1356 - Enable mod_expire in lighttpd, have it "cache" images directories to avoid constant reload.

80. Fix mantis #1207 - be sure the 4 buttons that remove devices have ok/cancel popups

81. Fix mantis #1213 - if a device is imported, the 'wrench' setup icon should be grayed out

82. Fix mantis #1251 - easier to use cameras

83. Fix mantis #1314 - Empty Scene name

84. Fix mantis #1360 - Don't update database fields with empty strings

85. Fix scheduling user codes with a Schlage lock

86. Fix compatibility with some Leviton scene/zone controllers using 100/200 series chips

87. Prevent heal from aborting if there's lots of activity going on

88. Fix so you can create custom luup handlers for actions with the same name and service file, but separate service id's, like heat and cool.

89. Add the option of switching to the 3.20 (aka 4.52) branch of Z-Wave firmware

90. Allow for manual routing when using 3.20

91. New heal routine that tests and optimizes Z-Wave routes.

92. A basic heal will be performed automatically at night if Vera has lost communication with some nodes.

93. Advanced users can now specify routes to nodes

94. Fix deleting devices not showing up in the UI.

95. Heal will auto-resume if it's aborted due to a crash or power outage

96. Add support for meter table class (Kamstrup power meters)

97. Do not discover UPNP devices by default anymore, unless the user requests it on the Add Device page.

98. Fix mantis #1391: Cannot add control over another UPnP device

99. Remove the 'Logs' for a device in the UI4 dashboard. Now go to cp.mios.com and choose Events.

== Old, archived release notes ==

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

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

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

4. Fix compatibility with the Fortrezz water valve

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

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

7. Fix one Vera controlling other UPnP devices.

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

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

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

----

After 996

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

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

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

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

15. Fix a crash while logging DHCP requests

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

17. Migrate to the new server structure with redundannt servers

18. Add ability to do ZWave multi-cast.

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

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

21. Don't set or restore default names that have been set with ZWave node naming get (ie starting with _).

22. Add ability to specify custom device types and names for products based on the ZWave manufacturer and product ID's and an xml file, including default names and variable settings.

23. Some ZWave chips seem to have trouble going into 'add node' mode when the commands are sent fast, so added some delays.

24. Add handling for more alarms from door locks, like when new user codes are added and removed, and low battery alarms.

25. For slow IP cameras there is now a timeout setting that can be increased to allow more time to return the JPEG. Also, the engine won't block the browser if the camera takes more than 3 seconds to respond. It will continue to retrieve the image in the background return it with the subsequent request.

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

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

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

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

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

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

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

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

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

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

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

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

11. Add default free dns servers: OpenDNS.org

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

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

'''Fixes:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Glossary]]

Release Notes

2012-01-21T01:23:01Z

OTi: Add links to Mantis

== UI5: 1.5.276 - January 20, 2012 ==

Resolved issues in 1.5.276:

#Remove 2 variables for the yale
#do not consider time successfully synced if year is not between 2012 and 2020
#use a function (get_server) to get a certain server value from servers.conf file
#force a reboot in max 15 minutes if the previous scripts don't do it faster
#start force reboot in background to be sure we don't get stuck by reboot command and wait 1 minute before forcing a reboot.
#read the wan/lan ifname from /var/state first, in case the type or proto is not standard the interfaces name will be different than the one defined in the /etc/config/network
#for units with rtc : update RTC on success sync time and update system time at boot from it
#fix firewall/dhcp in client mode for Vera3 
# allow only one network restart at a time
#Correct last field received in FORM_timezone in file /etc/TZ
#prevent php 5.3.x to lighttpd bug by stripping dirs from FORM_file_name variable
#read language and language_id directly from files 
#use main server if servers.conf file is messed up 
#log each server which is not defined
#req OpenWRT ver 74 for Vera3 and Lite
#fix time in NetworkMonitor
#fix camera relay
#fix record scene
# fix multiple room
#add custom require function
#fixes to danfoss living connect
#mantis [http://bugs.micasaverde.com/view.php?id=1978 1978], [http://bugs.micasaverde.com/view.php?id=1957 1957]
#delete wrong plugin 5 and 188
#strip independently bin and lib
#removed duplicate dir
#Fixed bug [http://bugs.micasaverde.com/view.php?id=1967 1967]
#Menu changes to have separate controls for help buttons.
#add support for SWITCH_MULTILEVEL_STOP_LEVEL_CHANGE
#mantis [http://bugs.micasaverde.com/view.php?id=2047 2047] and [http://bugs.micasaverde.com/view.php?id=2079 2079]
#fix creation of IR devices in UI5
#mantis [http://bugs.micasaverde.com/view.php?id=2054 2054]
#Swapped two strings for polling settings description
#Added alerts legend
#Mantis [http://bugs.micasaverde.com/view.php?id=2007 #2007]
#Mantis [http://bugs.micasaverde.com/view.php?id=2011 #2011]
#Mantis [http://bugs.micasaverde.com/view.php?id=2008 #2008]
#Mantis [http://bugs.micasaverde.com/view.php?id=2024 #2024]
#Mantis [http://bugs.micasaverde.com/view.php?id=2012 #2012]
#Mantis [http://bugs.micasaverde.com/view.php?id=1970 #1970]
#Mantis [http://bugs.micasaverde.com/view.php?id=1686 #1686]
#Mantis [http://bugs.micasaverde.com/view.php?id=1934 #1934]
#Fixed [http://bugs.micasaverde.com/view.php?id=2021 #2021]
#Moved help urls outside tabs.
#added help button
#Archive fix for reseting page on filters change.
#Added note about auto-updating timezone. 
#Hided manually timezone set when there is internet.
#Mantis [http://bugs.micasaverde.com/view.php?id=2045 #2045]
#Mantis [http://bugs.micasaverde.com/view.php?id=2033 #2033]
# Added offline mode for UI. 
# Added cameras reported as accessories.
#Mantis [http://bugs.micasaverde.com/view.php?id=2025 #2025]
#Mantis [http://bugs.micasaverde.com/view.php?id=2005 #2005]
#Mantis [http://bugs.micasaverde.com/view.php?id=1953 #1953]
#Mantis [http://bugs.micasaverde.com/view.php?id=1889 #1889]
#Added Alerts tooltip
#Mantis [http://bugs.micasaverde.com/view.php?id=2075 #2075]
#Mantis [http://bugs.micasaverde.com/view.php?id=2015 #2015]
#Mantis [http://bugs.micasaverde.com/view.php?id=2004 #2004]
#Fixed help urls.
#Fixed accessories to allow update only for owned devices.
#Mobile phones/av gear formatting.
#Fixed missing location box
#Added validation for set date fields

 

== UI5 : 1.5.255 (Vera2) & 1.5.254 (Vera3) - December 23, 2011 ==

New features in UI5:

1. Devices are organized and displayed in separate tabs by category: lights, sensors, cameras, etc.

2. You can pin the most often used devices and scenes on the Dashboard for quick access. The devices and scenes that are not pinned won't be displayed on the Dashboard.

3. The Add Device Wizard is now included in UI.

4. You can view and manage all the existing triggers (events) and schedules (timers) on Vera without opening any scene.

5. Creating scenes is easier and more intuitive with the new scene creator wizard.

6. You can now see the scene commands in the Advanced scene editor.

7. The MiOS Marketplace (now called MiOS Apps) functionality is now included in UI. You can:

*View app information
*Install apps
*View and Add reviews

8. The MiOS control panel (CP) functionality is now included in UI, but only if the user is authenticated. You can:

*Connect to one of your other Veras
*Add new or existing users to your Vera
*Remove users from your Vera
*Change your MiOS account password
*View alerts
*View available backups
*Change unit settings, like the Vera name and the number of SMSes and e-mails per day
*View camera archives

9. Energy monitoring using the ERGY plugin by EchoLabs, which is included in UI.

10. Real-time camera video streaming and video recording.

 

 This documents the changes since the first public beta release of UI4, 1.1.1047

== UI4 : 1.1.1338 - July 29, 2011 - RC ==

1. Use the Z-Wave double send (without ACK then with ACK) for lights only, not other devices, since its purpose was to eliminate the popcorn effect and creates unnecessary traffic otherwise.

2. Add special handling for devices made by Fibar for 2 way feedback

3. Fix NetworkMonitor so it will always reset the time if it doesn't get set at boot

4. Fix a bug in a script in the prior beta that made it incompatible with Vera 1

5. Add the pulse variable to the sdata request for energy meters

6. Fix a problem where changes saved got lost because luaupnp got a reload and the watchdog timer kicked in before it had finished flushing the files to disk.

7. Add support for Schedule Entry version 3 command class and locks by Assa Abloy

8. Tweak to the timing of the squashfs mounting to improve reliability

== 1.1.1323 - July 13, 2011 - beta ==

1. Fix a problem where a configure job could get stuck and not finish due to a race condition between multiple jobs

2. Fix problem where zwave frame collission resulted in failed job

3. Reduce incidence of EEPROM corruption in Z-Wave 4.52 where it mistakenly thinks there is a suc and gives "Failed to go into learn mode" errors when adding nodes.

4. Automatically correct situation #3 if the user has not already added devices.

5. Synchronize deleted devices with the central server

6. Add subcategory to identify types of security sensors

7. Add circulate fan mode support (not in the UI yet, but coming in UI5)

== 1.1.1298 - June 21, 2011 - beta ==

The primary reason for this release is that there was a bug in 1.1.1245 that prevented Z-Wave 'reset network' from working, and some users got stuck with a "failled to start z-wave" error.

1. Add default values for sensors as not-tripped so it appears correctly in the UI when the sensor hasn't been used yet.

2. Add support for multi-channel association

3. Add support for Danfoss thermostat

4. Fix for X10 devices that have 2 digit numeric ID's

5. Add support for Everspring motion sensors

6. Add support for Aeon 4-in-1 sensors

7. Minor enhancements to the wakeup procedure to support devices with short wakeup times

8. Fix support for the gc-100

9. Add support for the PolyControl door lock

10. Change the default PIN for locks to 8 characters instead of 4

 

== 1.1.1245 - April 20, 2011 - release ==

Most notably this release includes a new version of the Z-Wave firmware in the Z-Wave chip, and this new version allows Vera to optimize the routes the Z-Wave mesh network uses. This should improve reliability. See [[MigrateTo452]] Also Vera will no longer scan for UPnP devices unless you choose 'Add Device' and at the bottom check the option to scan for UPnP devices.

1. The energy plugin is now built into the engine. It will be removed on upgrade. Energy events are logged to your mios.com account automatically.

2. There is an option with Vera2 (Currently not working with Vera1) on Advanced, Logs to enable logging to a USB stick. This frees up quite a bit of memory, so if you have a lot of devices or plugins and your Vera is running slow or crashing because it's running out of memory, this is a solution. Note that after you check the box it can take up to 30 minutes to format the USB drive, and bootup will take a couple minutes longer with the USB drive installed. It will continue to boot up fine without the USB drive connected, just don't remove it while Vera is running. '''IMPORTANT: Use a new USB drive that hasn't already been formatted. In particular, don't use a USB drive that is already formatted for Mac.'''

3. There is a fix to prevent the main engine from starting before Vera has synced the date/time, which previously had caused sunset/sunrise timers to trigger unexpectedly. There is no battery-backed up clock in Vera. It needs to get the date/time from the internet at each boot.

4. This fixes a bug causing high CPU load and reboot when certain UPnP devices are detected on the network, such as Sonos.

5. The DSC plugin, and possibly others that use serial ports, did not work because the engine was trying to open the port twice.

6. Add some extra info in the heal process, and report the health rating and heal date to our tech support server along with ZWave node info, so, when a customer calls in for support, we will know what types of devices he has and how healthy they are to make better recommendations about improving ZWave reliability.

7. Some startup messages weren't displayed properly in the info panel.

8. Bad UPnP devices on the network that constantly report themselves every 1 second with a new UUID would eventually consume all the memory causing a crash. Now the software filters these rogue devices.

8. There's a new lu_sdata request that makes it much simpler to develop third party user interfaces to control the system. See: [[UI Simple]]

9. Store a counter of all polls (PollOk) with the number that failed transmission (PollTxFail) or failed to reply (PollNoReply). All counters are reset whenever you do a heal network. The counters are visible as extra variables in the device's advanced tab. This is for troubleshooting ZWave problems.

10. Add support for viewing live, streaming video. [[Remote Camera Streaming]]

11. Fix that sometimes variables across multiple bridged MiOS systems weren't being synchronized all the time.

12. Increase the timeouts for some internet operations so it works on super, super slow connections like satellite.

13. Fix for thermostats always showing fan as 'On' when it's in auto.

14. Add support for Fortrezz WMA-02, with new 'Leak alarm' event

15. Add support for Alarm Command Class version 2

16. Fix a crash caused by wakeup interval set to the minimum value

17. Fix problem with Insteon not starting when there are a lot of existing devices.

18. Fix problem with a LuaUPnP process not cleanly exiting, causing the UPnP port to remain stuck for 2 minutes and slowing down reload.

19. Implement a new Infrared learning, identifying, transmitting engine.

20. Fix toggle state with Insteon.

21. Add basic support for Zigbee lights with a SimpleHomeNet ZBPLM and Luup Plugin

22. Fix crash when adding new A/V devices

23. Reduce the delay between Z-Wave commands to solve startup problems on large networks

24. Add support for Yale/Assa Abbloy locks

25. Fix to handle Luup plugins staying locked to the right serial port when they're unplugged/reconnected.

26. Prevent Insteon module from taking over a serial port

27. Upgrade the ftdi_sio driver to support new infrared blaster

28. Fix intermittent crash when receiving a wakeup command

29. Add attribute set to the Luup API

30. Add Sleep to the Luup API

31. Reduce number of retries for download files/plugins

32. Use separate worker threads for slow processes like downloading vs fast processes like Z-Wave response to speed up the response to time sensitive tasks.

33. Don't execute timers if time jumps, caused by a new sync to the ntp server

34. Increase wait time for Luup plugins from 45 seconds to 90 to resolve some slow plugins that take a long time to initialize.

35. Add logging for the last time the battery level was reported and show the battery icon as a ? if it's been more than 7 days.

36. Fix problem with variableset Luup command not setting value always.

37. Don't repoll or reconfigure battery operated devices that wakeup constantly. At most re-poll every 10 minutes.

38. Add new scene recorder feature for easier scene creation.

39. Fix problem with the UI4 dashboard getting out of sync with the engine.

40. Fix problem with creation of 2 cameras using the same plugin.

41. Always write user_data when child devices change in case the reload doesn't work, causing a never ending cycle

42. Log uptime and track memory leaks.

43. Add crossdomain.xml so ActionScript clients can poll

44. Fix deadlock problem when aborting an existing send data command

45. Rewrite the watchdog function so it catches threads that don't exit after the main one closes

46. Add a tracking and reporting of 'tardy' tasks that run more than 3 seconds after they should.

47. Add decoding of infrared signals to extract the protocol, device and button codes from a learned i/r signal

48. Toggle the CPLD chip if the Z-Wave module stops responding to try to wake it up.

49. Allow scenes to control A/V devices

50. Fix for Leviton ZRCS4 id=2050 for 0-3 buttons

51. Increase timeout of http fetches for slow satellite internet connections

52. Allow Luup plugins (SQRemote) to remotely turn on features with a provision flag.

53. Don't treat superceded jobs as an error.

54. Fix issue with bridged systems not syncing state changes

55. Fix issue with bridged systems and deep nested trees of devices more than 3 layers deep (ie 3-in-1 sensor)

56. Re-write bridging code to reduce memory usage.

57. Prevent UPnP devices from being marked offline if the luup plugin doesn't load.

58. Add timestamps for all stages of the Z-Wave heal

59. Add support for measuring KWH and resetting the cumulative measurement

60. Add support for new Z-Wave metering classes

61. Add buttons for streaming and still camera images

62. Fix to prevent some messages from getting lost in the info panel

63. Fix when adding/removing multiple devices with a timeout and not doing anything that it showed it stayed in 'add/remove' mode.

64. Add filter when UPnP devices broadcast constantly to prevent bogging down the system.

65. Few minor Z-Wave changes required to pass Sigma certification. Engine is now certified.

66. Re-order the on/off buttons in UI4.

67. Keep a log of polling history and success/fail, report to central server to assist tech support.

68. Filter duplicate nonce's from secure devices.

69. Fix scenes not updating from bridge's systems

70. Add an auto purge of excessive ip and/or upnp requests so the user_data file doesn't grow bigger than the memory supports.

71. Add a watchdog to the remote access tunnels to ensure access through cp.mios.com stays alive

72. If the Z-Wave network doesn't start stop resetting the Insteon network too

73. Change default poll interval on FLiRS devices to 10800 seconds instead of 60 to conserve the battery

74. Fix mantis #1293 - Can't add notification for a device if no Scene is added previously

75. Fix mantis #1275 - Add options in Scene to show all devices in all rooms or filter by their type

76. Fix mantis #1317 - Replace Archive old logs on findvera with Archive old logs on mios.com

77. Fix mantis #1238 - Wizard through cp.mios.com displaying a 404 Error.

78. Fix mantis #1115 - text tweak on the 'add camera' page in the setup wizard

79. Fix mantis #1356 - Enable mod_expire in lighttpd, have it "cache" images directories to avoid constant reload.

80. Fix mantis #1207 - be sure the 4 buttons that remove devices have ok/cancel popups

81. Fix mantis #1213 - if a device is imported, the 'wrench' setup icon should be grayed out

82. Fix mantis #1251 - easier to use cameras

83. Fix mantis #1314 - Empty Scene name

84. Fix mantis #1360 - Don't update database fields with empty strings

85. Fix scheduling user codes with a Schlage lock

86. Fix compatibility with some Leviton scene/zone controllers using 100/200 series chips

87. Prevent heal from aborting if there's lots of activity going on

88. Fix so you can create custom luup handlers for actions with the same name and service file, but separate service id's, like heat and cool.

89. Add the option of switching to the 3.20 (aka 4.52) branch of Z-Wave firmware

90. Allow for manual routing when using 3.20

91. New heal routine that tests and optimizes Z-Wave routes.

92. A basic heal will be performed automatically at night if Vera has lost communication with some nodes.

93. Advanced users can now specify routes to nodes

94. Fix deleting devices not showing up in the UI.

95. Heal will auto-resume if it's aborted due to a crash or power outage

96. Add support for meter table class (Kamstrup power meters)

97. Do not discover UPNP devices by default anymore, unless the user requests it on the Add Device page.

98. Fix mantis #1391: Cannot add control over another UPnP device

99. Remove the 'Logs' for a device in the UI4 dashboard. Now go to cp.mios.com and choose Events.

== Old, archived release notes ==

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

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

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

4. Fix compatibility with the Fortrezz water valve

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

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

7. Fix one Vera controlling other UPnP devices.

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

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

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

----

After 996

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

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

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

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

15. Fix a crash while logging DHCP requests

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

17. Migrate to the new server structure with redundannt servers

18. Add ability to do ZWave multi-cast.

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

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

21. Don't set or restore default names that have been set with ZWave node naming get (ie starting with _).

22. Add ability to specify custom device types and names for products based on the ZWave manufacturer and product ID's and an xml file, including default names and variable settings.

23. Some ZWave chips seem to have trouble going into 'add node' mode when the commands are sent fast, so added some delays.

24. Add handling for more alarms from door locks, like when new user codes are added and removed, and low battery alarms.

25. For slow IP cameras there is now a timeout setting that can be increased to allow more time to return the JPEG. Also, the engine won't block the browser if the camera takes more than 3 seconds to respond. It will continue to retrieve the image in the background return it with the subsequent request.

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

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

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

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

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

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

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

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

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

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

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

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

11. Add default free dns servers: OpenDNS.org

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

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

'''Fixes:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Glossary]]

Aeon MiniMote

2011-12-11T13:00:22Z

OTi: Add user experience

Note: Users report this is working with UI5 build 1.5.233, but not UI4. Associated forum topic: http://forum.micasaverde.com/index.php/topic,2488.msg55580.html#msg55580

----

You need to have version 1.17 or later in your mini-mote. To determine what version you have for a mini-mote you've already included, go to our UI and in the Advanced tab in the device settings, and look for the variable "VersionInfo". There are 5 numbers, and the last 2 are Aeon's firmware version. So for example: 3,2,78,1,10 means you're running version 1.10 and need to upgrade your minimote. You can download a Windows program at aeon-labs.com to update your remote.

You should reset your mini-mote before including by holding down the associate and learning buttons, both at the same time, for 10 seconds until the LED's stop blinking.

To add the device, put Vera into include mode, and press the Learn button on the remote.

Next you can assign scenes to the 4 buttons by clicking the wrench button in our UI for the MiniMote, and picking the scenes. You can also pick 4 scenes to run when each button is turned off. On the mini-mote, tap a button to run the 'activate' scene for that button, and hold the button for a second to run the 'deactivate' scene the button.

UI5 Issues

2011-09-02T12:18:20Z

OTi: Added comments.

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

UI5 Issues

2011-09-02T12:10:29Z

OTi: Added comments.

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

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

Luup Devices

2011-08-24T22:26:34Z

OTi: http://forum.micasaverde.com/index.php?topic=7515.msg48498#msg48498

[[Category:Development]]
== Home Automation Device ==
The generic device type that all MiOS devices implement.
===Service===
*urn:micasaverde-com:serviceId:HaDevice1
===Variables===
===Actions===
== Switch ==
A binary switch, for an appliance, florescent light, or a relay.
===Service===
*urn:upnp-org:serviceId:SwitchPower1
===Variables===
====Status====
The state of the device. 1 is on, 0 is off.
===Actions===
====SetTarget====
Sets the target state of the dimmer

'''Arguments:''' NewTargetValue(Integer)

NewTargetValue: 1 for on, 0 for off.
== Dimmer ==
A dimmable light.
===Service===
*urn:upnp-org:serviceId:Dimming1
===Variables===
newTargetValue: an integer between 0 and 100 indicating the desired % of lighting.
===Actions===
====SetLoadLevelTarget====
Sets the desired brightness or load level for the dimming device.

'''Arguments:''' newLoadlevelTarget(Integer)

newLoadLevelTarget: an integer between 0 and 100 indicating the desired % of lighting/load.
== Sensor ==
A security sensor, or any device that can be "tripped"
===Service===
u*rn:micasaverde-com:serviceId:SecuritySensor
===Variables===
====Armed====
An integer. 1 for armed, 0 for disarmed. This is an internal state variable of the MiOS engine and has nothing to do with the state of the sensor.
====Tripped====
An integer. 1 for tripped, 0 for not.
====LastTrip====
An integer with the UNIX timestamp of the last trip event that the MiOS engine recorded.
===Actions===
====SetArmed====
Sets the armed state of the sensor.

'''Arguments:''' newArmedValue(Integer)

newArmedValue: 1 for armed, 0 for disarmed.
== HVAC/Climate ==

=== Service ===

*urn:upnp-org:serviceId:HVAC_UserOperatingMode1
**For action SetModeTarget
*urn:upnp-org:serviceId:TemperatureSetpoint1_Heat
**For action NewCurrentSetpoint
*urn:upnp-org:serviceId:TemperatureSetpoint1_Cool
**For action NewCurrentSetpoint
*urn:upnp-org:serviceId:HVAC_FanOperatingMode1
**For action SetMode

=== Variables ===

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

One of Off, HeatOn, CoolOn, or AutoChangeOver depending on the User operation mode of the thermostat.

==== urn:upnp-org:serviceId:HVAC_FanOperatingMode1 -- Mode ====

One of Auto, ContinuousOn, or PeriodicOn depending on the fan mode of the thermostat.

==== urn:upnp-org:serviceId:TemperatureSensor1 -- CurrentTemperature ====

An integer value representing the temperature that the thermostat is reporting.

==== urn:upnp-org:serviceId:TemperatureSetpoint1_Heat -- CurrentSetpoint ====

An integer value representing the heat setpoint for the thermostat

==== urn:upnp-org:serviceId:TemperatureSetpoint1_Cool -- CurrentSetpoint ====

An integer value representing the cool setpoint for the thermostat

=== Actions ===

==== SetModeTarget ====

Sets the desired operation mode for the thermostat.

'''Arguments:''' NewModeTarget(String)

NewModeTarget: One of Off, CoolOn, HeatOn, or AutoChangeOver.

==== SetCurrentSetpoint ====

Sets the desired setpoint. User serviceId urn:upnp-org:serviceId:TemperatureSetpoint1_Heat for heat and urn:upnp-org:serviceId:TemperatureSetpoint1_Cool for cooling

'''Arguments:''' NewCurrentSetpoint(Integer)

NewCurrentSetpoint: An integer value between 0 and 100 specifying the desired heat or cooling setpoint.

==== SetMode ====

Sets the fan operation mode for the thermostat

'''Arguments:''' NewMode(String)

NewMode: One of ContinuousOn or Auto, depending on the desired mode of operation for the HVAC system's fan.

=== Examples ===

Set Thermostat #4 to Cool: veraIP:3480/data_request?id=lu_action&DeviceNum=4&serviceId=urn:upnp-org:serviceId:HVAC_UserOperatingMode1&action=SetModeTarget&NewModeTarget=CoolOn

Set Thermostat #98 cool setpoint to 70: veraIP:3480/data_request?id=lu_action&DeviceNum=98&serviceId=urn:upnp-org:serviceId:TemperatureSetpoint1_Cool&action=SetCurrentSetpoint&NewCurrentSetpoint=70

== Lock ==
Lorem ipsum dolor sit amet, ultricies ligula ligula maecenas, sed laboriosam erat.
===Service===
urn:micasaverde-com:serviceId:DoorLock1
===Variables===
====Status====
1 for locked, 0 for unlocked
===Actions===
====SetTarget====
Sets the desired lock state of the door lock

'''Arguments:''' newTargetValue(integer)

newTargetValue: 1 for lock, 0 for unlock
== Window Covering ==
Blinds and shades.
===Service===
*urn:upnp-org:serviceId:WindowCovering1
*urn:upnp-org:serviceId:SwitchPower1
**Supports the same actions and variables as a switch. On is closed, Off is open.
===Actions===
====Up====
Moves the covering up.
====Down====
Moves the covering down.
====Stop====
Stops the covering moving.
== Sensor - Humidity ==
A humidity sensor.
===Service===
urn:micasaverde-com:serviceId:HumiditySensor1
===Variables===
CurrentLevel(Integer): The current humidity level that the sensor is reporting.
== Sensor - Temperature ==
A temperature sensor.
===Service===
urn:upnp-org:serviceId:TemperatureSensor1
===Variables===
CurrentLevel(Integer): The current temperature in degrees the sensor is reporting.
== Sensor - Light ==
A light sensor.
===Service===
urn:schemas-micasaverde-com:service:LightSensor:1
===Variables===
CurrentLevel(Integer): The current light level that the sensor is reporting.
== Power Meter ==
A power meter or a device that can display power usage.
===Service===
urn:micasaverde-com:serviceId:EnergyMetering1
===Variables===
Watts(Integer): The energy draw the meter is recording, in watts.

Supported Hardware

2011-08-20T03:16:25Z

OTi: Typos

This is a page for Supported Z-Wave devices.

Alternative hardware pages exist for

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

In general, any device with the Z-Wave logo should work with Vera. A list of tested Z-Wave devices is below, with specific notes for each type of device. This is a wiki, so feel free to add to the page. To learn about Z-Wave routing and fixing routing problems see: [[Heal Network]]

== Hardware Reported to Work ==

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

 

----

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

----

 

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

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

 

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

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

 

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

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

 

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

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Frequency
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added by User
! Notes
|-
| ACT
| Motion Sensor
| ZIR000 / ZIR010
| 
| EU (ZIR010) or US (ZIR000)
| 
| Indoor
| [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR000_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR000_instr.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZIR010_spec.pdf Link] [http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZIR010_instr.pdf Link]
| 
| 
| Remove the cover, pair to Vera's dongle by using the push-button on the left of the circuit board. Vera must configure it to work, and it can only be configured within less of a minute (30 sec best) of inserting the batteries. With Vera's dongle removed, remove/reinsert the batteries, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page
|-
| Aeon Labs
| 3-in-1 sensor (light/humidity/temperature)
| MultiSensor
| 
| EU or US
| 
| Indoor/Outdoor
| [http://www.aeon-labs.com/site/public/lib/download.php?type=s&f=29 Specs]
| 
| 
| Pair to Vera by using the push-button. Vera must configure it to work, and it can only be configured within 10 minutes of inserting the batteries.
|-
| Express Controls aka HomeSeer
| 3-in-1 sensor (light/temperature/motion)
| HSM100 / EZMotion
| 
| EU or US
| 
| 
| [http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf Link]
| 
| 
| See [[ExpressControls3in1]] If the motion sensor does not work right after inclusion and configuration, remove the batteries for a few seconds.
|-
| EverSpring/Hawking/Home Manageables
| Door/window sensor
| SM103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=355&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110873R01_SM103_-ECR.pdf Link]
|  
| Ap15e
| Pair using the intrusion button. The sensor will accept configuration within a few minutes of the initial pairing, or of pressing the intrusion button on the back even after it's paired. Pair the device, or if it's already paired, press the intrusion button, and within 30 seconds insert Vera's dongle. Within a few minutes confirm the "configure" icon for the device is green on Vera's setup page. NOTE: There is some confusion about the orientation of the sensor. The main sensor body has a back (where the intrusion is), a front (where the logo and LED is), and the 2 other surfaces, one of which has a curved edge, and the other is flat. The magnet needs to go against the flat surface. And the flat surface on the magnet should be as close as possible to the flat surface on the sensor, lined up in the middle so the line which passes through the LED lines up with the sensor.
Note: In case the inclusion/exclusion fails you should remove/reinsert the batteries from the sensor and within a few seconds the sensor should be automatically detected.

|-
| EverSpring/Home Manageables
| Humidity + Temperature sensor
| HM-TS001
| 
| 
| Jan 2010 (requires version 1.1.0 or greater)
| Indoor
| [http://www.asihome.com/ASIshop/product_info.php?products_id=3946 Link] [http://www.homeseer.com/pdfs/guides/HM_TD001.pdf Link]
|  
| micasaverde
| Pair or unpair the device by tapping the CF button 3 times very quickly. Once it's paired and shows up in the UI as a generic device, press the CF button 3 times again quickly to make it wakeup and get configured. Then it will correctly be identified as 3 devices (combo device + temperature + humidity).
|-
| Everspring
| Motion Detector
| SP103
| 6,2,9,1,0
| EU or US
| Apr 2009
| Indoor
| [http://www.everspring.com/Products/Home_Automation_Detail.asp?parentUID=83&UID=354&CateUIDList=0,83 Link] [http://www.everspring.com/Archive/Image/File/A501110874R01_SP103_%20-%20ECR.pdf Link]
|  
| Ap15e
| Works well
|-
| Fortrezz
| Water /Freeze
| WWA-001
|  ??????
| US
| Apr 2009
| Indoor
| [http://www.Fortrezz.com Link] [http://www.fortrezz.com/resources/WWA_manual_01May2009.pdf Link]
| 
| Zmistro
| Works great I would place a few in your house. Bathrooms, laundry , kitchen , basement. Great product!
|-
| Intermatic
| Motion Sensor
| CA-9000
| 
| US
| 
| Indoor
| 
| 
| Aaron
| This device has limited functionality as a sensor. It can only be used to turn on and off a light directly by setting an association, which Vera supports. It does not fire events, so you cannot use it as an event on a scene.
|-
| Merten
| 4-gang radio transmitter, flush-mounted
| 506004
| 2,2,27,1,4
| EU
|  
| Indoor
| [http://www.merten.de/download/DL_doku/V5060_581_02_web.pdf Link]
|  
| Ap15e
| Note: There is proprietary functionality here. Support will be added soon.
Quite complex device; partially supported by Vera; can be used as a window/door sensor (as of firmware 1.0.900) ...
|}

 

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

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

 

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

{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Specs
! Product Review
! Added By User
! Notes
|-
| Electronic Solutions
| Drape/Blind Motor Controller
| DBMZ
| V2+1
| 
| Indoor
| For 12-24VDC Motors
| [http://www.elec-solutions.com/products/dc_mot_ctrls/z-wave/dbmz/dbmz.html Link]
| Shady
| 2-Wire Motors
|-
| Electronic Solutions
| Drape/Blind Motor Controller
| ABMHZ
| V2+1
| 
| Indoor
| For 110-230VAC Motors
| [http://www.elec-solutions.com/products/int_ac_mot_ctrls/z-wave/abmhz/abmhz.html Link]
| Shady
| 4-Wire Motors
|-
| Lagotek / RSSceneAutomation
| Drape/Blind Motor Controller
| DC1-ZW
| 
| 
| Indoor
| For 12-24VDC Motors
| [http://www.lagotek.com/blindspdf/AC1-ZW%20Cut%20Sheet.pdf Link]
| Shady
| 2-Wire Motors
|-
| Lagotek / RSSceneAutomation
| Drape/Blind Motor Controller
| AC1-ZW
| 
| 
| Indoor
| For 110-230VAC Motors
| [http://www.lagotek.com/blindspdf/DC1-ZW%20Cut%20Sheet.pdf Link]
| Shady
| 4-Wire Motors
|}

 

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

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

 

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

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

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

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

|-
| Duewi
| Radio roller shutter push-button
| 054368
| 6,2,51,1,0
| EU
| Jun 2009
| Indoor
| [http://www.duewi.de/index.php?productid=37344 Link]
|  
| Lutz
| Open/Close buttons work well, but slide bar does not work. Some additional observations by Ap15e (Vera V1, firmware 1.0.979):
*GUI button 'Stop' and corresponding UPnP service does not work.
*GUI button 'Up' moves the shutter down, GUI button 'Down' moves the shutter up ...
*After adjusting the running times even the slide bar seems to work!
*I got a report from a user that the düwi device may fail due to interference from the shutter motor. In this case an additional filter is required (costs about 25 €/direction).
*More information is available at [http://forum.micasaverde.com/index.php?topic=3359.msg16142#msg16142 Link]
|}

 

=== '''Cameras that work''' ===
See [http://wiki.micasaverde.com/index.php/IP_Cameras IP Cameras] for a more comprehensive and up to date list
{| cellpadding="2" border="1"
|-
! Manufacturer
! Device Type
! Model no.
! Version
! Date Purchased
! Location (indoor/outdoor)
! Path for JPEG image
! Product Review
! Notes
|-
| Linksys
| IP Camera
| WVC54GCA
| all
| 2009
| Indoor
| img/snapshot.cgi
| 
| An inexpensive camera with moderate image quality. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address.
|-
| Linksys
| IP Camera
| WVC210
| all
| 2009
| Indoor
| img/snapshot.cgi
| 
| A more expensive camera with good image quality and pan/tilt ability. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address. Pan/tilt controls will not work with Vera.
|-
| Linksys
| IP Camera
| WVC80N
| all
| 2009
| Indoor
| img/snapshot.cgi?size=2&quality=1
| 
| A more expensive camera with good image quality and wireless N. Use the Linksys setup wizard for initial setup, then copy IP address and path into Vera setup fields. Use a static IP address. Pan/tilt controls will not work with Vera.
Size can be (160 x 120 = 1,320 x 240 = 2,640 x 480 = 3) and Quality can be (Very High= 1,High= 2,Normal= 3,Low= 4,Very Low= 5)

|-
| iCamView
| IP Camera Server
| iCV-22, iCV-32
| all
| 2009 
| Indoor/Outdoor
| pda.cgi?user=admin&password=1234&page=image&cam=1 pda.cgi?user=admin&password=1234&page=image&cam=2 
| 
| Feature-rich IP camera server, suports up to two compatible USB cameras, optional WiFi support, USB storage, USB hubs, motion; works with range of cameras, see icamview.co.uk. Excellent modular solution. They do ship to North America.
|-
| SmartHome.com.au
| IP Camera
| Z~Series Wireless Camera
| all
| 2009 
| Indoor
| tmpfs/auto.jpg
| 
| Inexpensive IP security camera designed for the Australian and New Zealand Z-Wave users, but shipping world wide.
|-
| [http://global.level1.com LevelOne]
| IP Camera
| WCS-2030
| all
| 2010
| Indoor
| cgi-bin/video.jpg
| [http://reviews.cnet.com/search-results/levelone-camcon-wcs-2030/1707-5_7-31972011.html CNET review]
| An inexpensive IP camera with good image quality. Can be connected wired or wirelessly. Most LevelOne cameras use the same path for the JPEG image, so most of their line (both low and high end) should be compatible. Video and audio also stream over RTSP, which can be customized through the camera's web interface.
|-
| Asante
| IP Camera
| Voyager I
| firmware 2.02 and above
| 2010
| Indoor
| image.cgi
| 
| An inexpensive IP camera that is very feature rich, has good image quality, night vision capabilities, motion detection, two-way audio, video streaming over TCP, UDP, or HTTP, and other configurable features. In firmware version 2.02, Asante added the capability to retrieve an image via a URL (however, it is delayed by 3 seconds). Offers a full-featured web interface in IE using an ActiveX plug-in (limited capabilites in other browsers).
|}

 

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

Scripts for scenes

2011-08-19T20:21:19Z

OTi: Minor rewording / resolve rendering issue

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

 

== Scene that runs only if a security sensor hasn't been tripped in a set period of time ==

1. Create a new scene. In that scene: 

2. Create a timer and set it to run every minute. 

3. In the Luup Code section put the following code:

<source lang="lua">local deviceNo = 22
local period = 15

local SS_SID = "urn:micasaverde-com:serviceId:SecuritySensor1" -- Security Sensor Service ID

local armed = luup.variable_get (SS_SID, "Armed", deviceNo)
if (armed == "1") then
local lastTrip = luup.variable_get (SS_SID, "LastTrip", deviceNo) or os.time()
lastTrip = tonumber (lastTrip)
if ((os.difftime (os.time(), lastTrip) / 60) >= period) then
return true
end
end

return false</source> ''deviceNo'' is the sensor's device number, which you can get by going into its Toolbox, in the Advanced tab. 

''period'' is the time (in minutes) the sensor hasn't been tripped before running the scene. 

'''Note:''' The sensor must be armed for this to work, but this can be easily changed. 

 

== Scene that runs only if a security sensor has been tripped for a set period of time ==

1. Create a new scene. In that scene:

2. Create a timer and set it to run every minute.

3. In the Luup Code section put the following code:

<source lang="lua">local deviceNo = 22
local period = 15

local SS_SID = "urn:micasaverde-com:serviceId:SecuritySensor1"

local armed = luup.variable_get(SS_SID, "Armed", deviceNo) or "0"
if armed == "1" then
local tripped = luup.variable_get(SS_SID, "Tripped", deviceNo) or "0"
if tripped == "0" then
luup.variable_set(SS_SID, "TripPeriod", "0", deviceNo)
else
local tripPeriod = luup.variable_get(SS_SID, "TripPeriod", deviceNo) or 0
tripPeriod = tonumber(tripPeriod)
tripPeriod = tripPeriod + 1
luup.variable_set(SS_SID, "TripPeriod", tripPeriod, deviceNo)
if tripPeriod == period then
return true
end
end
end

return false</source>

''deviceNo'' is the sensor's device number, which you can get by going into its Toolbox, in the Advanced tab.

''period'' is the time (in minutes) the sensor has been tripped before running the scene.

'''Note:''' The sensor must be armed for this to work, but this can be easily changed

 

== Scene that runs once at dawn and once at dusk ==

1. Create a new scene. In that scene: 

2. Create a timer and set it to run every hour (set a different time interval depending on the desired accuracy).

3. In the Luup Code section put the following code:

<source lang="lua">local LOW_LEVEL = 20 -- the light level threshold for night
local HIGH_LEVEL = 40 -- the light level threshold for day
local DEVICE_NO = 13 -- the light sensor device number
local LS_SID = "urn:micasaverde-com:serviceId:LightSensor1" -- the LightSensor service ID

local currentLevel = luup.variable_get (LS_SID, "CurrentLevel", DEVICE_NO) or 0
currentLevel = tonumber(currentLevel)

if currentLevel <= LOW_LEVEL then
local timeOfDay = luup.variable_get (LS_SID, "TimeOfDay", DEVICE_NO) or "Day"
if timeOfDay == "Night" then
-- It's night, so the scene has run once.
return false
else
-- It's sunset, run the scene.
luup.variable_set (LS_SID, "TimeOfDay", "Night", DEVICE_NO)
return true
end
elseif currentLevel >= HIGH_LEVEL then
local timeOfDay = luup.variable_get (LS_SID, "TimeOfDay", DEVICE_NO) or "Night"
if timeOfDay == "Day" then
-- It's day, so the scene has run once.
return false
else
-- It's morning, run the scene.
luup.variable_set (LS_SID, "TimeOfDay", "Day", DEVICE_NO)
return true
end
end</source>

== Scene that runs only in a user set time interval ==

Add this code in the Luup Code section:

<source lang="lua">local startTime = "22:30"
local endTime = "05:30"

local hour = tonumber( startTime:sub( startTime:find("%d+") ) )
local minute = tonumber(startTime:sub(-2))

if hour and minute then
startTime = hour * 100 + minute
else
luup.log("ERROR: invalid start time")
return false
end

hour = tonumber( endTime:sub( endTime:find("%d+") ) )
minute = tonumber(endTime:sub(-2))

if hour and minute then
endTime = hour * 100 + minute
else
luup.log("ERROR: invalid end time")
return false
end

local currentTime = os.date("*t")
currentTime = currentTime.hour * 100 + currentTime.min

luup.log("startTime = " .. startTime .. "; currentTime = " .. currentTime .. "; endTime = " .. endTime)

if startTime <= endTime then
-- Both the start time and the end time are in the same day:
-- if the current time is in the given interval, run the scene.
if startTime <= currentTime and currentTime <= endTime then
return true
end
else
-- The start time is before midnight, and the end time is after midnight:
-- if the current time is not outside the given interval, run the scene.
if not (endTime < currentTime and currentTime < startTime) then
return true
end
end

return false</source>

This code allows the scene to run only between 22:30 and 5:30.

== Scene that turns on the light when it detects movement and turns off the light when it doesn't detect movement for a while ==

1. Create a scene to turn on the light when a sensor is tripped.

2. Add this code in the ''Luup code'' section:

<source lang="lua">local sensorDeviceNo = 16 -- Motion Sensor device number
local lightDeviceNo = 13 -- Light device number
local period = 10 -- Seconds

local SS_SID = "urn:micasaverde-com:serviceId:SecuritySensor1" -- Security Sensor Service ID
local SP_SID = "urn:upnp-org:serviceId:SwitchPower1" -- Switch Power Service ID

function checkLastTrip()
local lastTrip = luup.variable_get (SS_SID, "LastTrip", sensorDeviceNo) or os.time()
if (os.difftime (os.time(), tonumber (lastTrip)) >= period) then
luup.call_action (SP_SID, "SetTarget", {["newTargetValue"] = 0}, lightDeviceNo) -- Turn off the light.
else
luup.call_delay ("checkLastTrip", period) -- Check when the sensor was last tripped every <period> seconds.
end
end

luup.call_delay ("checkLastTrip", period)

return true</source>

== Scene that runs only if the light level is below a user set threshold ==

1. Create a scene to turn on the light when the sensor is tripped.

2. Add this code in the ''Luup code'' section:

<source lang="lua">local LOW_LEVEL = 20 -- the light level threshold for night
local DEVICE_NO = 33 -- the light sensor device number
local LS_SID = "urn:micasaverde-com:serviceId:LightSensor1" -- the LightSensor service ID

local currentLevel = luup.variable_get (LS_SID, "CurrentLevel", DEVICE_NO) or 0
currentLevel = tonumber(currentLevel)

if currentLevel <= LOW_LEVEL then
return true
else
return false
end</source>

Polling Settings

2011-07-14T02:44:21Z

OTi: Additional tweaks and text. Reviewers added.

== Introduction ==

Polling is the process where Vera requests information from a Z-Wave device about its current status, such as on/off, dim level, temperature, and so on. 

Depending on the device, polling may not be necessary, as the device will report any status changes to Vera autonomously. Those devices are not normally polled, but only when Vera starts up. These are devices that support associations, such as a Leviton dimmer.

Other devices, such as many battery operated sensors for example, will be in a low-power state most of the time and therefore are not listening to the network and cannot be polled at all. An example would be a portable controller, such as the GE 45601. Another example is a motion sensor, such as the HSM100; it will autonomously report motion to Vera, but cannot be polled for temperature and light level readings until it 'wakes up' and notifies Vera that it is awake. However, frequently listening, but battery operated devices such as a door lock can be polled. 

The polling mechanism and the parameters that control it are described below. 

== Settings ==

The highlighted section in this screenshot shows the poll settings for the entire system. They apply to all devices, unless specified differently for a specific device. 

[[Image:UI4-1.1.1245-Polling1.jpg|System-wide poll settings]]

*'''Poll nodes''' 1 Master switch to enable or disable polling. 
*'''Number of seconds to wait to start polling <#>''' 2 Number of seconds after Vera / the Luup engine has (re-)started before the polling mechanism begins. 
*'''Only poll a node if the Z-Wave network is idle at least <#> seconds''' 3 Number of seconds Vera must not have transmitted any non-poll command before the next poll command is sent. 
*'''Poll a node every <#> seconds.''' 4 Number of seconds between poll commands. 
*'''Unless specified otherwise, poll each node at most once every <#> seconds.''' 5 Minimum number of seconds between poll commands to the same node. 

The highlighted section in the screenshot below shows the poll settings per device. 

[[Image:UI4-1.1.1245-Polling2.jpg]]

*'''Poll this node at most once every <#> seconds''' 6 Minimum number of seconds between poll commands to this node. Putting a '0' will disable polling for this node. Leaving the field blank indicates the default value from the system-wide settings will be used. (See 'Unless specified otherwise...' above.) 

== Operation ==

If polling is enabled 1, Vera will begin polling when the Luup engine has restarted and the specified wait time 2 has elapsed.

The nodes are polled in sequence, starting with the lowest device number. The Z-Wave network must have been idle for the specified time 3, before the node is polled.

Once the node has been polled successfully, Vera waits the specified number of seconds 4 before polling the next node.

After all the nodes have been polled, the process repeats, taking into account the maximum poll rate 5/6 for each device.

 

Devices that report their status autonomously and battery-operated devices that do no listen are skipped by default during normal operation.

 

To limit the amount of polling in a given time interval, the mechanism only allows to specify a maximum poll rate for each device, but not the actual poll rate for each device.

The actual poll rate per device depends on the size of the network and the type of devices in it.

== Example ==

Typically, with the default settings and more than 2 'pollable' devices, a poll command will be sent every 30 seconds (not 60, see Bug section below). For 3 'pollable' devices: 
<pre>00:00 - Poll device #1

00:30 - Poll device #2

01:00 - Poll device #3

01:30 - Poll device #1

...
</pre>
== Bug  ==

Currently (1.1.1245) the labels '''Poll a node every <#> seconds.''' and '''Unless specified otherwise, poll each node at most once every <#> seconds.''' are reversed. So:

*The default value for '''Poll a node every # seconds.''' is 30; change this number to change the poll interval.
*The default value for '''Unless specified otherwise, poll each node at most once every <#> seconds.''' is 60; change this number to limit the poll rate of a single node.
*Bug# 1526.

== Change Log ==

2011/07/13 - oTi - Replace old info with updated UI4 description. Reformat page. Reviewed by mcvflorin and JOD. [1.1.1245 / 3.20]

[[Category:User_Instructions]]

Polling Settings

2011-07-13T19:57:40Z

OTi: Extra text based on feedback; some typos.

== Introduction ==

Polling is the process where Vera requests information from a Z-Wave device about its current status, such as on/off, dim level, temperature, and so on. 

Depending on the device, polling may not be necessary, as the device will report any status changes to Vera autonomously. Those devices are not normally polled, but only when Vera starts up. These are devices that support associations, such as a Leviton dimmer.

Other devices, such as many battery operated sensors for example, will be in a low-power state most of the time and therefore are not listening to the network and cannot be polled at all. An example would be a portable controller, such as the GE 45601. Another example is a motion sensor, such as the HSM100; it will autonomously report motion to Vera, but cannot be polled for temperature and light level readings until it 'wakes up' and notifies Vera that it is awake. However, frequently listening, but battery operated devices such as a door lock can be polled. 

The polling mechanism and the parameters that control it are described below. 

== Settings ==

The highlighted section in this screenshot shows the poll settings for the entire system. They apply to all devices, unless specified differently for a specific device. 

[[Image:UI4-1.1.1245-Polling1.jpg|System-wide poll settings]]

*'''Poll nodes''' 1 Master switch to enable or disable polling. 
*'''Number of seconds to wait to start polling <#>''' 2 Number of seconds after Vera / the Luup engine has (re-)started before the polling mechanism begins. 
*'''Only poll a node if the Z-Wave network is idle at least <#> seconds''' 3 Number of seconds Vera must not have transmitted any non-poll command before the next poll command is sent. 
*'''Poll a node every <#> seconds.''' 4 Number of seconds between poll commands. 
*'''Unless specified otherwise, poll each node at most once every <#> seconds.''' 5 Minimum number of seconds between poll commands to the same node. 

The highlighted section in the screenshot below shows the poll settings per device. 

[[Image:UI4-1.1.1245-Polling2.jpg]]

*'''Poll this node at most once every <#> seconds''' 6 Minimum number of seconds between poll commands to this node. Putting a '0' will disable polling for this node. Leaving the field blank indicates the default value from the system-wide settings will be used. (See 'Unless specified otherwise...' above.) 

== Operation ==

If polling is enabled 1, Vera will begin polling when the Luup engine has restarted and the specified wait time 2 has elapsed.

The nodes are polled in sequence, starting with the lowest device number. The Z-Wave network must have been idle for the specified time 3, before the node is polled.

Once the node has been polled successfully, Vera waits the specified number of seconds 4 before polling the next node.

After all the nodes have been polled, the process repeats, taking into account the maximum poll rate 5/6 for each device.

 

Devices that report their status autonomously and battery-operated devices that do no listen are skipped by default during normal operation.

== Example ==

Typically, with the default settings and more than 2 'pollable' devices, a poll command will be sent every 30 seconds. For 3 'pollable' devices: 
<pre>00:00 - Poll device #1

00:30 - Poll device #2

01:00 - Poll device #3

01:30 - Poll device #1

...
</pre>
== Bug  ==

Currently (1.1.1245) the labels '''Poll a node every <#> seconds.''' and '''Unless specified otherwise, poll each node at most once every <#> seconds.''' are reversed. So:

*The default value for '''Poll a node every # seconds.''' is 30; change this number to change the poll interval.
*The default value for '''Unless specified otherwise, poll each node at most once every <#> seconds.''' is 60; change this number to limit the poll rate of a single node.
*Bug# 1526.

== Change Log ==

2011/07/13 - oTi - Replace old info with updated UI4 description. Reformat page. [1.1.1245 / 3.20]

[[Category:User_Instructions]] [[Category:Incomplete]]

Polling Settings

2011-07-13T05:24:19Z

OTi: Initial version

== Introduction ==

Polling is the process where Vera requests information from a Z-Wave device about its current status, such as on/off, dim level, temperature, and so on. 

Depending on the device, polling may not be necessary, as the device will report any status changes to Vera autonomously. Those devices are not normally polled, but only when Vera starts up.

Other devices, such as many battery operated sensors for example, will be in a low-power state most of the time and therefore are not listening to the network and cannot be polled at all.

 

The polling mechanism and the parameters that control it are described below. 

== Settings ==

The highlighted section in this screenshot shows the poll settings for the entire system. They apply to all devices, unless specified differently for a specific device. 

[[Image:UI4-1.1.1245-Polling1.jpg|System-wide poll settings]]

*'''(1) Poll nodes''' Master switch to enable or disable polling. 
*'''(2) Number of seconds to wait to start polling <#>''' Number of seconds after Vera / the Luup engine has (re-)started before the polling mechanism begins. 
*'''(3) Only poll a node if the Z-Wave network is idle at least <#> seconds''' Number of seconds Vera must not have transmitted any non-poll command before the next poll command is sent. 
*'''(4) Poll a node every <#> seconds.''' Number of seconds between poll commands. 
*'''(5) Unless specified otherwise, poll each node at most once every <#> seconds.''' Minimum number of seconds between poll commands to the same node. 

The highlighted section in the screenshot below shows the poll settings per device. 

[[Image:UI4-1.1.1245-Polling2.jpg]]

*'''(6) Poll this node at most once every <#> seconds''' Minimum number of seconds between poll commands to this node. Putting a '0' will disable polling for this node. Leaving the field blank indicates the default value from the system-wide settings will be used. (See 'Unless specified otherwise...' above.) 

== Operation ==

If polling is enabled (1), Vera will begin polling when the Luup engine has restarted and the specified wait time (2) has elapsed.

The nodes are polled in sequence, starting with the lowest device number. The Z-Wave network must have been idle for the specified time (3), before the node is polled.

Once the node has been polled successfully, Vera waits the specified number of seconds (4) before polling the next node.

After all the nodes have been polled, the process repeats, taking into account the maximum poll rate (5)/(6) for each device.

 

Devices that report their status autonomously and battery-operated devices that do no listen are skipped by default during normal operation.

== Example ==

Typically, with the default settings and more than 2 'pollable' devices, a poll command will be sent every 30 seconds.
<pre>00:00 - Poll device #1

00:30 - Poll device #2

01:00 - Poll device #3

01:30 - Poll device #1

...
</pre>
== Bug  ==

Currently (1.1.1245) the labels '''Poll a node every <#> seconds.''' and '''Unless specified otherwise, poll each node at most once every <#> seconds.''' are reversed. So:

*The default value for '''Poll a node every # seconds.''' is 30; change this number to change the poll interval.
*The default value for '''Unless specified otherwise, poll each node at most once every <#> seconds.''' is 60; this this number to limit the poll rate of a single node.
*Bug# 1526.

== Change Log ==

2011/07/13 - oTi - Replace old info with updated UI4 description. Reformat page. [1.1.1245 / 3.20]

[[Category:User_Instructions]] [[Category:Incomplete]]

Polling Settings

2011-07-13T04:32:19Z

OTi:

File:UI4-1.1.1245-Polling2.jpg

2011-07-13T03:34:37Z

OTi: Poll settings highlight in Settings tab of device

Poll settings highlight in Settings tab of device

File:UI4-1.1.1245-Polling1.jpg

2011-07-13T03:27:54Z

OTi: Poll settings highlight in Z-Wave device > Options

Poll settings highlight in Z-Wave device > Options

Migrate To Z-wave version 452

2011-07-03T01:38:28Z

OTi:

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

# 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

Main Page

2011-05-31T13:10:31Z

OTi:

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

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