Test Sequence

Latest revision as of 01:21, 15 June 2013

This page is OBSOLETE

A test system is available to the public to prod around with Vera. The test system consists of Vera, a thermostat, a motion detector, a dimmable light connected to a lamp, an on/off switch connected to a fan which blows foil in front of the motion detector to trip it, and a wireless Panasonic IP camera. It can be accessed directly (like you would on the home LAN) at testvera.micasaverde.com, or on findvera.com with the username: testvera, password: myvera123. Following is our standard test sequence to confirm that all major functions are working:

Prep: In order to see all the verbose logs for several errors, edit /etc/cmh/cmh.conf and put a # in front of LogLevels and change number of copies to 100

1. Start with a new Vera unit and connect the WAN port to the network

2. Go to the 'Setup' page, and on FindVera.com, enter: user: testvera password: myvera123 and activate

3. On the 'Rooms' tab, enter a Bedroom and a Living Room

4. On the 'Devices' tab, the dimmable is "Lamp" in Living Room, the switch is "Fan" in Bedroom. Thermostat and motion are in Living Room.

5. Power on camera, wait for light to come on green. Confirm it shows up as a new device.

6. Confirm 'View Camera' works, lights can be controlled, thermostat set, etc.

7. Fill in all the options for the camera: Motion Detector, 30 seconds, Lamp, 30 minutes, 20 days, check all 4 boxes

8. On the 'Scenes' tab, create scenes: "On for 30 seconds" turns lamp on for 30 seconds and off. "Arm Home" turns lamp off and arms motion detector. "Disarm Home" bypasses motion detector.

9. Choose Location

10. Add user: vera password: vera, then set the SMS text and email addresses

11. Add timer: 30 minutes on interval 30 minutes, turn fan on and off after 5 minutes, and turns light to 75% for 15 minutes and turns it off. Add another timer that at 45 minute intervals turns the lamp on to 25% and then to 60% after 30 minutes.

12. Add timer: evening, on all days of week at "6:00pm, 20:00" turns lamp on for 10 seconds and off

13. Add event: breach, type: armed sensor, users: vera, motion detector. lamp on for 10 seconds then off

14. Add event: sunset, lamp off

15. On energy, check every option, choose every day of the week, 1 lights, a thermostat, more than 100 watts, notify the user vera, and sign up for Flex alerts.

16. Click 'Save'. Press F5 and confirm all settings stuck. Manually arm the sensor by clicking 'Arm' on the devices page. Turn on fan, which should trip the motion sensor. 30 seconds later or so the sensor should have the red "trip" icon, and you should get a notification via SMS and email about the 'breach' event.

NOTE: Manually trip a motion sensor like this: http://ip:49451/data_request?id=lu_variableset&DeviceNum=xxxx&serviceId=urn:micasaverde-com:serviceId:SecuritySensor1&Variable=Tripped&Value=0

NOTE: Manually simulate a 'door lock pin failed' event like this: http://ip:49451/data_request?id=lu_variableset&DeviceNum=xxxx&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=sl_PinFailed&Value=1

NOTE: Manually lock the door: http://ip:49451/data_request?id=lu_action&DeviceNum=xxxx&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=Target&Value=1

NOTE: Manually simulate a 'user enters a code' event like this: http://ip:49451/data_request?id=lu_variableset&DeviceNum=xxxx&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=sl_UserCode&Value=yyy where yyy is in the format of: UserID="a" UserName="b" so that a is the id of the user code (1-19) and b is the name assigned to the user code. Example: http://192.168.1.108:49451/data_request?id=lu_variableset&DeviceNum=25&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=sl_UserCode&Value=UserID%3D%226%22%20UserName%3D%22robert%22

NOTE: Manually simulate a temperature sensor reaching a certain value: http://ip:49451/data_request?id=lu_variableset&DeviceNum=xxx&serviceId=urn:micasaverde-com:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=30

17. Browser check: Open the site in IE 6, IE 7, IE 8, Firefox 2, Firefox 3, Chrome, and Safari. Confirm the site loads, you can click buttons on the dashboard, expand the devices page, and create/save a scene

18. Login to findvera.com with testvera/myvera123. Click events and confirm you can see the breach event and the notification attempts. Click Camera, Panasonic camera, and confirm you have video archive, including every time you tripped the sensor. The date/time should be correct, and the light should be on for 10 seconds.

19. Go to the 'Energy' tab and confirm you see the live usage

20. Go to 'Control' and confirm you see the Dashboard

21. Go to 'Settings' and put in your email and SMS number. Unplug the access point. Within 1 hour you should get a notification.

22. Let the access point wait for 5 hours. Confirm you can view the 'Energy' history.

23. On the devices tab confirm the thermostat is reporting the temperature.

24. Open a generic WAP browser on a mobile phone and go to testvera.micasaverde.com:3451/iphone. Confirm you can view the camera, control the lights, and execute secenes.

25. Open the browser and go to findvera.com/mo. Enter testvera and myvera123, and again confirm you can view the camera, control the lights, and execute scenes.

26. Open the Blackberry's browser, go to testvera.micasaverde.com/mo and install the Java app. Confirm you have the same control, and also that the status updates if you change devices using the web page

27. Go to: https://ra1.findvera.com/testvera/myvera123/3451/data_request?id=camera_control/16&parameters=get_video_frame and confirm you can view the camera

28. Choose 'Poll all nodes' from the Dashboard and confirm you get 'poll jobs' for all the devices.

29. Choose 'Permanently remove dead node' for one of the existing devices, and confirm it goes away.

30. Confirm the following: Every 30 minutes you should get a notification of the breach, because of the 30 minute timer. The timers and events should work properly, and after a while, you should see the energy usage history graphs showing how the energy usage is fluctuating in response to the 30 and 45 minute timers.

If this is the public Vera box, make these changes to prevent someone from breaking the network settings:

in /www/cmh/js/scripts.js, make this change:
document.getElementById("remote_access_box").innerHTML="Changes to this page are disabled because this Vera is exposed to the public";
document.getElementById('zwave_options_box').innerHTML="Changes to this page are disabled because this Vera is exposed to the public";

and in /www/cmh/index.html:
<a href="/cgi-bin/webif/info.awx" target="_blank">Advanced configuration</a> should be Changes this to page and access to OpenWRT control panel are disabled because this Vera is exposed to the public
delete this: <td id="restore_factory_defaults_box"><input type="button" class="normal_button" onClick="restore_factory_defaults();" value="Restore factory defaults"></td>
and this: <td id="restore_backup_form"></td>

and delete these 2 lines from /www/cmh/access_point.html:
<input type="submit" value="Save and Apply" class="normal_button">
<input type="button" value="Revert changes" class="normal_button" onClick="getElementById('ap_form').reset(); show_connection_details(); show_encryption_details();">

and delete this from /www/cgi-bin/cmh/upgrade_step1.sh:
<td><input type="button" name="upload" value="Download" class="normal_button" onclick="document.location='upgrade_step2.sh?firmware='+document.getElementById('firmware').value"></td>

When the box is setup, do this:
mkdir /etc/cmh.bak
cp /etc/cmh/devices.json.lzo /etc/cmh/user_data.json.lzo /etc/cmh.bak/
echo "*/* 1 * * * cp /etc/cmh.bak/* /etc/cmh/" >> /etc/crontabs/root

passwd: 95ireland