MiOS - User contributions [en]

How to connect 3G modem to Vera

2013-04-13T06:51:01Z

Cj: /* Instructions */

This guide applies to Vera units with firmware version starting with 1.5.622 and works only when the WAN port is not connected, and the modem is manually set to connect. When the wire is plugged back, the WAN becomes the default gateway.

 Supported 3G Modems : 
<pre>Huawei E153
ZTE MF180
ZTE MF667F </pre>
== Instructions ==

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

1. Disable network-autoconfigure 
<pre>rm /etc/cmh/fresh_install</pre>

1.2. Add 3G support in /usr/bin/GetNetworkState.sh script 
<pre>
wan)
[[ "$(uci -P/var/state/ get network.3g.up 2>/dev/null)" == "1" ]] && { echo "UP"; exit; }

ip_wan)
[[ "$(uci -P/var/state get network.wan.up 2>/dev/null)" != "0" ]] && [[ "$(uci -P/var/state get network.3g.up 2>/dev/null)" == "1" ]] && {
uci -P/var/state get network.3g.ipaddr 2>/dev/null
exit
}

</pre>
1.3 Add 3G support in /usr/bin/Report_AP.sh
<pre>
#TODO - report if unit is in WifiClientMode
WanIP="$(GetNetworkState.sh ip_wan)"
if [[ "$WanIP" == "" ]]; then
</pre>
2. Plug in USB Modem in Vera 

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

 

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

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

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

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

 

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

 8. Stop and start 3G

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

==  Possible issues : ==

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

'''Cause ''': 

USB port miss-configuration 

'''Resolution ''':

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

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

'''3.''' Remote access doesn't work anymore :

Certain providers block the remote access port, so the unit can't connect anymore to the remote access server.

A possible solution would be to check "FailSafe Tunnels" from Setup > Net&Wifi page on the user interface.

Firmware Flash Vera2

2012-02-16T10:05:59Z

Cj: /* Prerequisites */

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

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

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

* Make sure your computer is connected to your network through an Ethernet cable. Make sure to disable any wireless networking interfaces before continuing.
NOTE: Failure to disable your wireless network before continuing could result in an unusable unit.
* Please deactivate all Firewall and Antivirus software which is running during the upgrade process.

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

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

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

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

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

== Begin the process for flashing the firmware ==

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

== To do after the restoration has finished ==

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

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

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

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

Firmware Flash Vera3

2012-01-24T16:47:16Z

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

== Prerequisites ==

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

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

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

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

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

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

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera3 Firmware Recovery Tool]
*[http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware]

==  Setup your computer to connect to Vera 3   ==

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

== Begin the process for flashing the firmware ==

#Use a network cable (CAT5e) and plug the cable from your PC into Vera's '''LAN1 port'''.  
#Unplug Vera from the power cord.
#Holding down Vera's '''ZWAVE button''' whilst pluging in the power cord back in. Wait about 3s after you plugged the power cord back with the ZWave button pressed. When releasing the ZWave button, '''USB1 LED''' should be blinking.  
#If the '''USB1 LED''' is not blinking, turn Vera off and try again'''(PLEASE doublecheck FIRST!!! The LED blinking can be very faint!).'''
#Start [http://download.mios.com/firmware/vera3_recovery_tool.zip Vera3 Firmware Recovery Tool].
#Click "Browse target" button.
#Vera should appear in targets list.
#Click on "*UN*checkPID" radiobox
#Select "EraseALL" from dropdown box. (<- this will update your unit bootloader also)
#Click the [Files] button.
#Download the file: [http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware] and save it on your computer.
#Select the file [http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware]
#Click the [Open] button to get the file.
#Click on the [OK] button on the BIN File Information dialog box.
#Click on the [Upgrade] button. File will be flashed, and you will see a dialog box saying success - close Upgrade Tool.
#Put your computer's IP back to DHCP (Automatically Configure) and Vera will assign an IP like 192.168.81.xxx
#Please wait until Vera ''automatically'' reboots and the '''WAN led''' starts double blinking or it's solid (this can take 10 to 30 minutes).  
#When you see the ZWave led solid, you are done. 

== To do after the restoration has finished ==

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

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

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

== References ==

http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera3 Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

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

Release Notes

2012-01-21T09:01:18Z

Cj: /* UI5: 1.5.276 - January 20, 2012 */

== 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], [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]]

Firmware Flash Vera3

2012-01-16T15:25:55Z

Cj:

== Prerequisites ==

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

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

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

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

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

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

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera3 Firmware Recovery Tool]
*[http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware]

==  Setup your computer to connect to Vera 3   ==

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

== Begin the process for flashing the firmware ==

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

== To do after the restoration has finished ==

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

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

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

== References ==

http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera3 Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

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

Firmware Flash Vera3

2012-01-16T15:24:55Z

Cj:

== Prerequisites ==

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

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

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

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

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

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

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera3 Firmware Recovery Tool]
*[http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware]

==  Setup your computer to connect to Vera 3   ==

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

== Begin the process for flashing the firmware ==

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

== To do after the restoration has finished ==

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

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

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

== References ==

http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera3 Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

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

Firmware Flash Vera3

2012-01-16T15:18:15Z

Cj: Created page with " == Prerequisites == *The upgrade tool is only tested in Windows XP, it will not work with Windows Vista. In Windows 7 the applications should be run in Windows XP SP3 co..."

== Prerequisites ==

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

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

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

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

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

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

*[http://download.mios.com/firmware/vera3_recovery_tool.zip Vera3 Firmware Recovery Tool]
*[http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware]

==  Setup your computer to connect to Vera 3   ==

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

== Begin the process for flashing the firmware ==

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

== To do after the restoration has finished ==

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

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

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

== References ==

http://download.mios.com/firmware/latest-vera3-recovery-firmware.bin Vera3 Recovery Firmware http://download.mios.com/firmware/vera3_upgrade_tool.zip Vera3 Firmware Recovery Tool http://www.simplehelp.net/2008/09/10/how-to-install-a-tftp-client-in-windows-vista/ 

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

Release Notes

2012-01-09T16:20:26Z

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

== 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-09T16:19:18Z

Cj: /* 1.1.1338 - July 29, 2011 - RC */

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

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

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

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

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

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

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

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

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

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

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

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

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

11. Add default free dns servers: OpenDNS.org

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

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

'''Fixes:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Glossary]]

Release Notes

2012-01-09T16:19:02Z

Cj: /* 1.5.255 (Vera2) & 1.5.254 (Vera3) - December 23, 2011 - beta */

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

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

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

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

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

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

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

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

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

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

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

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

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

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

11. Add default free dns servers: OpenDNS.org

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

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

'''Fixes:'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Glossary]]

Install NTP

2012-01-09T11:55:06Z

Cj: /* Introduction */

[[Category:User Instructions]]
[[Category:How To]]
'''HOWTO install NTP on your Vera.'''

==Prerequisites==
* Vera 2 hardware
* Root acces to your OpenWRT

==Introduction==
Heres a short manual on how to install NTP to your Vera 2. Out of the box your new Vera 2 does not use NTP (Network Time Protocol) for its timer updates, but uses the less commonly used Rdate. However, NTP support and personalisation can be added after market. Here is how: 
Note:
 1) this is not fully supported by MiCasaVerde firmware and you should also leave rdate installed and configured
 2) this is not required if everything is working fine with your Vera unit
 3) if your unit time is with X hours (or X*30minutes for Australia) before/after your correct time, the issue is related to your TIMEZONE and not to the sync time client. Check if your timezone is correctly stored in /etc/TZ.

==Instructions==
01.Gain ssh access to your vera2 (root) and use the password that is provided on the bottom of your vera2. More info on how to can be found here:[http://wiki.micasaverde.com/index.php/Logon_Vera_SSH] 
02. Then run the following commands: 

''opkg update''

''opkg install ntpd''

''/etc/init.d/ntpd enable''

''/etc/init.d/ntpd start''

03. To edit the ntp.conf file without using and editor like VI use the echo command like this; 
''echo "server "your servers ip or dns name" prefer" >> /etc/ntp.conf''

04. (important to remove ONLY the quotes before and after your and name) To view the current entries in your ntp.conf type: 
''cat /etc/ntp.conf''

05. To remove obsolete IP's or server names from the ntp.conf files type: 
''cat /etc/ntp.conf | grep -v "lines to remove" > /etc/ntp.conf.new''

06. Check the newly created file using this command: 
''cat /etc/ntp.conf.new''

07. Overwrite the existing file if all checks out using: 
''mv /etc/ntp.conf.new /etc/ntp.conf''

08. Double check the newly created ntp.conf file by typing: 
''cat /etc/ntp.conf''

09. Restart the NTP service 
''/etc/init.d/ntpd restart''

10. OR reboot/powercycle your vera

==References==
please find more info here: http://forum.micasaverde.com/index.php?topic=5591.0 
For logging on to your Vera using SSH read this [http://wiki.micasaverde.com/index.php/Logon_Vera_SSH]

Update Firmware

2011-07-16T12:05:13Z

Cj: /* References */

[[Category:How To]]

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

==Prerequisites==

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

==Introduction==

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

===General Notice===

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

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

The current workaround is to disable the authentication, upgrade and then re-enable the authentication from cp.mios.com after the update was succesfull.

===Create a backup!===

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

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

To restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

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

==Manual updates==

'''Manually upgrading the firmware'''

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

Vera automatically checks connectivity to the download server (download1.mios.com or download2.mios.com). 
Then Vera shows you the current firmware version and provides info if this firmware is up to date or not.

You can upgrade your Vera by dropping the specifick download URL for your Vera in the "URL for MiOS custom firmware" box. 
Please contact MiOS for the correct URL first.

----

===Automatic Updates===

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

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

You can automatically update your Vera by accepting the pop-up notice that a new firmware is available, asking you if you want to upgrade. 
Also you can go to this url: 
http://micasaverde.com/vera2

From there you can follow the steps to automatically update your Vera to the latest official firmware release.

==Known Issues==
* Vera 1 upgrading to 1.1.1245 directly from a version older than 1.1.1062 does not work. Please contact tech support at MiOS and ask them to help you install intermediate release 1.1.1062.

* Sometimes an upgrade makes Vera go back to her default locale settings (USA). For users in the EU their devices do not work anymore. As for the locale issue mentioned in this thread, please refer to: http://forum.mios.com/index.php?topic=6652.0

==References==
please find more info here: 
Update url for your Vera | http://micasaverde.com/vera2 
Recovery procedure : 
- for Vera 1 hardware | http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera_1 
- for Vera 2 hardware | http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2 
Note: To be done only if you vera unit doesn't boot anymore!!! See in each link how the leds should blink if this is the case !!!

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

Update Firmware

2011-07-16T12:01:00Z

Cj: /* Advanced manual upgrade */

[[Category:How To]]

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

==Prerequisites==

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

==Introduction==

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

===General Notice===

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

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

The current workaround is to disable the authentication, upgrade and then re-enable the authentication from cp.mios.com after the update was succesfull.

===Create a backup!===

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

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

To restore a backup file, either one that you created manually with 'Create Backup', or an automatic backup at MiOS.com, click 'Browse' to find the backup file, select it, and click 'Restore'.

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

==Manual updates==

'''Manually upgrading the firmware'''

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

Vera automatically checks connectivity to the download server (download1.mios.com or download2.mios.com). 
Then Vera shows you the current firmware version and provides info if this firmware is up to date or not.

You can upgrade your Vera by dropping the specifick download URL for your Vera in the "URL for MiOS custom firmware" box. 
Please contact MiOS for the correct URL first.

----

===Automatic Updates===

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

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

You can automatically update your Vera by accepting the pop-up notice that a new firmware is available, asking you if you want to upgrade. 
Also you can go to this url: 
http://micasaverde.com/vera2

From there you can follow the steps to automatically update your Vera to the latest official firmware release.

==Known Issues==
* Vera 1 upgrading to 1.1.1245 directly from a version older than 1.1.1062 does not work. Please contact tech support at MiOS and ask them to help you install intermediate release 1.1.1062.

* Sometimes an upgrade makes Vera go back to her default locale settings (USA). For users in the EU their devices do not work anymore. As for the locale issue mentioned in this thread, please refer to: http://forum.mios.com/index.php?topic=6652.0

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

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