Revision History

• 2.4.0 (December 3, 2009)
  • Fixed issue with DooMotion not ignoring X10 All Lights On/Off when option was selected.
  • Fixed listing of action items when editing events.
• 2.3.5 (March 25, 2009)
  • Security Breach event triggers should fire first time motion is detected when in Security Mode. However, there was a problem with the trigger not occurring again when Security Mode was deactivated/reactivated. This has been corrected.
  • Fixed problem with Activation/Deactivation status changes via Web Options Page not being saved in settings file.
  • Fixed a problem with the DooMotion script file that is created with new installs.
  • Fixed "Unable to set DooMotion Plugin Mode. Error occurred within HSPI.SetPluginStatus " error.
• 2.3.4 (March 6, 2009)
  • Fixed Ignore X10 All Off setting not being restored as startup.
• 2.3.3 (March 3, 2009)
  • Fixed creation of DooMotion scripting file for new installs.
• 2.3.2 (February 28, 2009)
  • Fixed problem with installer that corrupted plug-in.
• 2.3.1 (February 21, 2009)
  • View Sensors Only broken on Sensors List Web Page.
  • Fixed problem with saving Options.
  • Fixed Activate/Deactivate buttons within Web Options Page.
  • Fixed problem with Security Mode.
  • Fixed problem with testing CAC via web page.
  • Removed extra Options... menu item from web page menu bar.
• 2.3.0 (January 17, 2009)
  • Changes to CAC are not lost after Testing.
  • Fixed problem with Web Options not saving settings changes reliably.
  • Fixed problems with viewing Sensor Activity Web Page.
  • Added ability to ignore X10 All Off commands within Options.
  • Added ability to disable CAC execution within Sensor Properties.
  • Added debug log entries for when DooMotion is telling HS to set device status.
• 2.2.115 (November 18, 2008)
  • Fixed installer to recognize HS 2.3+.
• 2.2.114 (February 26, 2008)
  • Fixed a potential looping error when a sensor is deleted via HS rather than through DooMotion.
  • Fixed nuisance error message at shut down referring to object not being initialized.
• 2.2.113 (February 13, 2008)
  • Fixed a problem where DooMotion could cause HS to hang at shutdown.
• 2.2.112 (February 12, 2008)
  • Fixed problem with FailSafe Feature not being used at startup.
  • Improved some other timing functionality at startup.
• 2.2.110 (January 25, 2008)
  • Fixed data file converter issues.
  • Fixed sorting issue with Web Sensors List Page.
  • As was the case with earlier builds, events related to occupancy sensor status are now only triggered upon a status change to the occupancy sensor. Custom Action Code still fires repeatedly as well as events for motion sensors (unless the For motion sensors, do not re-trigger within Normal Elapsed Time (min.) option is checked).
• 2.2.109 (January 12, 2008)
  • Fixed Windows bar charting error.
  • Data and script file conversions are now handled by an external application.
• 2.2.108 (January 3, 2008)
  • Fixed intermittent problem duplicate entries within Web Sensors List Page.
• 2.2.107 (December 24, 2007)
  • Some device string and general operational fixes related to operating in Away Mode, Sleep Mode, and Security Mode. Device string timers should be fully functional without affecting the functionality of these modes.
• 2.2.106 (December 23, 2007)
  • Web Sensors List Page has been improved to display faster. Also fixed some errors with displaying Web Sensors List Page that resulted from sensors that had their sensor type changed.
  • Security Mode no longer ignores dusk/dawn sensor changes during its initial stage of ignoring commands for Away Time minutes.
• 2.2.105 (December 20, 2007)
  • Finally fixed stuck device string timers.
  • Added ability to ignore OFF commands for motion sensors that send a nearly immediate OFF after motion is detected making DooMotion quickly show "no motion" after "motion detected". This feature is set within the sensor's properties. To force an OFF after a much later time than the hardware produces, you can use Fail Safe Time. Note that this only works for motion sensors that have a different trigger code otherwise HomeSeer will respond to the immediate OFF before DooMotion would have a chance to ignore the OFF.
  • DooMotion will no longer warn of a missing underlying device which can happen if devices are deleted within HomeSeer but the DooMotion sensor is not removed from DooMotion. DooMotion will now recreate the underlying device. To remove sensor and underlying device, DooMotion should be used.
  • Help menus are now working within Windows interface.
  • Changes to default chart time now apply to current chart.
  • Fixed problem with deleting the "Default" favorite.
  • Fixed Windows Chart Dialog Page Setup error referring to a string not being a valid boolean value.
  • Disabled ability to zoom bar charts as this feature was not planned to be available. This functionality may be added back in the future.
• 2.2.102 (October 13, 2007)
  • Fixed SelectMenu error when attempting to access Windows bar charting.
• 2.2.101 (October 12, 2007)
  • Windows bar charting is now functional. Windows timeline and web charting are still under (re-)development.
  • Fixed problem when OccupancyElapsedTime was set to zero.
  • Some general performance improvements.
• 2.2.99 (September 7, 2007)
  • Fixed some update issues.
  • Added more default custom device status/value relationships that are now contained within custom.xml file in DATA\DooMotion folder.
• 2.2.98 (August 19, 2007)
  • Improvements to performance.
  • Fixed some shutdown errors occurring with non-English regional settings.
• 2.2.97 (July 18, 2007)
  • Fixed problem with setting Location2 via Web Sensor Properties Page.
• 2.2.95
  • Fixed CheckTriggerObject.Go error that occurred when Debug Mode is enabled.
  • Fixed problem with disabling Debug Mode.
• 2.2.94
  • Fixed shutdown problems introduced with 2.2.92.
• 2.2.93
  • DooMotion now restarts in same Plug-In Mode (Active, Away, Sleep, Security, Inactive) that was being used during previous shutdown. If for some reason the mode is incorrect (plug-in device value was manipulated by other means), then Active Mode will be assumed.
  • Attempted to fix CheckTrigger error.
  • Fixed some code samples errors in documentation involving DateDiff function.
• 2.2.92
  • Attempted to fix memory issues by limiting log files to 1Mb. Previous log file will be saved and will need to be deleted manually by user.
  • Fixed an HSEvent error occurring with some hardware interface plug-ins.
  • Fixed and improved the Web Sensor Activity Page (/DooMotion/Activity.aspx).
  • Fixed SysTrayIcon error.
  • Fixed potential DooMotion database problem with new/migrated installs.
• 2.2.89
  • Fixed some double sensor triggers occurring approximately one update cycle apart. Problem was introduced in 2.2.83.
• 2.2.83
  • Reincorporated the value change callback while still providing similar versatility with HS versions prior to 2.2.0.3 that do not support the value change callback.
  • Duplicate event are now ignored if they occur within less than 250 milliseconds rather than the original 1 second.
  • Fixed debug log entries to not show error as log type unless it is an error.
• 2.2.80
  • Fixed lingering issues with proper occupancy sensor handling.
  • Fixed errors with GetSensorByXXXX scripting commands when used with VBScript.
  • Some work completed with charting features.
• 2.2.74
  • Fixed bugs with settings status of some sensors.
• 2.2.73
  • Some fixes related to the changes for supporting HS 2.2.0.3.
• 2.2.71
  • When using HS 2.2.0.3 or greater, status changes are ignored if user specifies custom device status/value expressions. Similarly, value changes are ignored if user does not specify custom device status/value expressions.
• 2.2.70
  • Now takes advantage of separate value change callback in addition to status change callback. Requires HS 2.2.0.3 or greater.
• 2.2.69
  • Altered strategy for handling device status/value changes which may improve integration of DS10a/MS10a devices with DooMotion when using ACRF Plug-in.
• 2.2.67
  • Fixed a problem displaying Web Sensors List Page when user is not tracking dead sensors.
• 2.2.65
  • Fixed problem with removing associated sensors via Web Sensor Properties Page.
  • Fixed problem with OccupancyElapsedTime set to blank (or < 0).
  • Added WebHelp link for new HomeSeer help page. Requires maintenance release of HomeSeer after 2.2.0.0.
• 2.2.64
  • Fixed some problems with Windows Sensor Properties Dialog.
  • Fixed some lingering issues with occupancy sensors firing CAC.
  • dm.RunEx scripting command has been deprecated. Use hs.RunEx instead.
• 2.2.62
  • Fixed inability to use image selector within Windows Sensor Properties Dialog.
• 2.2.61
  • New release Build!
  • Fixed problem with occupancy sensors not updating in a timely manner.
• 2.2.59
  • Finished a series of overall performance improvements.
  • Fixed inability to access the MotionSensors, Dusk2DawnSensors, and OccupancySensors collections via scripting.
• 2.2.54
  • Performance improvements for systems that use DooMotion triggered events and/or systems with large numbers of events.
• 2.2.53
  • Fixed remaining issues with SysTray functionality.
• 2.2.52
  • Fixed problem with removing devices/sensors.
  • Fixed potential issue where DooMotion would incorrectly report that a sensor data file could not be found for current HomeSeer configuration even though the sensor data file had been created/updated for the current HomeSeer configuration.
• 2.2.51
  • Fixed problem with Windows Sensor Activity Dialog and Web Sensor Activity Page not allowing DooMotion database to be located in a folder other than C:\Program Files\HomeSeer 2\DATA\DooMotion\DooMotion.mdb.
  • Fixed problem with testing Custom Action Code.
• 2.2.49
  • Fixed more issues with upgrading from much older DooMotion builds.
• 2.2.46
  • Fixed problem saving a change to device codes of sensors.
  • Fixed a problem displaying Web sensors list page when device strings of some devices contained embedded
  • carriage returns.
  • Some changes to overcome issues with conversion of ini configuration file to xml.
  • Some changes to overcome issues with conversion of sensor data file from much older versions.
• 2.2.45
  • Release version!
  • Cycling protection scheme has been removed until it can be revised to include easily configurable options (including disabling it).
  • Made more progress with charting. Release build has not been held up for this feature.
  • Fix for "InsertActivity" error was determined to be a corrupted database that is easily fixed by performing a compact and repair either through the plug-in or by using Microsoft Access with HS/DM shut down. If error occurs, a log entry will indicate this solution.
  • Issues with certain SysTray functions have not been fully resolved. User will be notified when a function is not working correctly. This is another issue that should not hold up the release version.
• 2.2.42
  • Fixed problem with saving some options and sensor properties via web interface.
  • Fixed problem with updating dead sensor count device.
  • Trigger codes are no longer case-sensitive.
  • If there are problems with reading sensor datafile, DooMotion will shut down rather than continuing with the possibility data loss.
  • The installer will now maintain an extra backup of previous version of DooMotion and associated files in DATA\DooMotion\backup folder. There will now be a batch file (restore.bat) in the BIN\DooMotion folder that will allow user to easily restore that previous version. Run file when HomeSeer is shut down.
  • Fixed bug with displaying Web Sensors List page in "Sensor Only" view when no sensors have been defined.
• 2.2.40
  • When changes to HomeSeer configuration file name is detected, DooMotion will now check device references before declaring that configuration file has changed.
  • Fixed problem with saving global device status/value relationships. Individual device status/value relationships that follow HomeSeer X10 conventions will be set to empty strings.
  • When in Away Mode, Security Mode, or InActive Mode, dead sensor timers will be disabled for sensors whose Dead Sensor Time is greater than zero.
• 2.2.39
  • Fixed problem with competing threads attempting to set status of occupancy sensors leading to unpredictable results.
  • Fixed intermittent problem report at startup regarding Dead Sensor Count device.
• 2.2.37
  • Fixed devices not being listed in Windows Sensors List Dialog or Web Sensors List Page when no DooMotion sensors have been created.
• 2.2.36
  • Fixed a problem with occupancy sensor status logic.
  • Fixed sensors not showing up in sensors list of Web Sensors List Page when only one sensor defined.
  • Fixed problem with creating plug-in devices with new installs.
• 2.2.35
  • Improved protection scheme for sensor status cycling and eliminating rapidly repeating commands.
  • Fixed a problem with reading sensor lists from previous versions of sensor data files.
• 2.2.34
  • Fixed problems with maintaining lists of assigned sensors.
  • Fixed a bug with new protection scheme for sensor status cycling.
  • Fixed error referring to inability to access to sensor data file.
  • Fixed NoMotionTime/NoOccupancyTime properties returning negative values. Values should always be postive.
  • Some further performance improvements related to accessing collections of sensors.
  • Improvements to sensor initialization.
• 2.2.33
  • Fixed excessive occupancy sensor logging introduced in 2.2.32.
• 2.2.32
  • For Custom Action Code, Sensor.LastOn/Sensor.LastOff are not updated until after code is executed so you can use the properties to determine the time of the previous ON/OFF.
  • More performance improvements.
• 2.2.31
  • Fixed multiple dusk/dawn log entries.
  • Improved strategy for guarding against repeated device status changes in a short period of time.
• 2.2.30
  • Fixed Dead Sensor Device not updating.
  • Fixed problem with conversion of DooMotion 2.0 INI configuration file to DooMotion 2.2 XML.
  • Added additional checks to prevent devices from cycling status as a result of user defining an problematic custom device status/value relationship.
• 2.2.29
  • Fixed HSEvent errors resulting from changes in 2.2.28.
• 2.2.28
  • Inactive status now stops almost all processing except for the ability to add sensors, view data, and view charts.
  • Due to problems accessing Windows Custom Functions Dialog from SysTray, access has been removed from the SysTray menu and you must use HS console instead. When solution is determined, access will be returned.
  • Fixed problem with adding new motion and dusk/dawn sensors.
  • Fixed NoMotionTime property for motion sensors so that it correctly shows how long a motion sensor has/had not detected motion.
  • General processing improvements that should provide some performance benefits.
• 2.2.27
  • Earlier builds of DooMotion did not actually allow user to disable Occupancy Elapsed Time for motion sensors. You can now disable by clearing it (or setting it to -1). This effectively causes motion sensor to be used for determining occupancy but not for determining vacancy. If you wish the motion sensor to not determine occupancy, then do not assign it to the occupancy sensor.
  • Another attempt to fix ProcessPendingEvents error.
  • Fixed problem with importing system settings from DooMotion 2.0.
  • Fixed problem with switching to/from .NET scripting.
• 2.2.26
  • Fixed occupancy sensor status not changing as a result of attempted fix in 2.2.25.
  • Fixed SetStatus/GetStatus error occurring when custom device status/value expressions are incorrectly specified.
• 2.2.25
  • Fixed incorrect reporting of dead sensors at startup.
  • Fixed "Less than x seconds after" event trigger.
  • Fixed problem with occupancy sensor status cycling.
  • Removed some debug statements left from prior beta build.
• 2.2.23
  • Improved performance of Away, Sleep, and Security mode timings.
  • Fixed problem with occupancy sensor event triggers.
  • Fixes to some minor issues with Fail Safe and Dead Sensor handling.
• 2.2.22
  • Improved Fail Safe and Dead Sensor handling.
  • Fixed missing DooMotion Actions when creating events.
  • Debug logging now includes subsecond timestamp to better troubleshoot.
• 2.2.19
  • NoMotionTime/NoOccupancyTime scripting properties now return a more accurate time representing the number of minutes between when sensor first detected an ON (Sensor.FirstOn) and when sensor first detected an OFF (Sensor.FirstOff). Previous DM versions used a slightly different time span.
  • Documentation examples changed to reflect recommendation to use If DateDiff("n",Now,Sensor.LastOn) > Sensor.NormalElapsedTime Then ... (or If DateTime.Now.Subtract(Sensor.LastOn).TotalMinutes > Sensor.NormalElapsedTime Then ...) rather than If Sensor.NoMotionTime > Sensor.NormalElapsedTime Then ...
• 2.2.18
  • Installer now provides the noscript.gif image.
  • NoMotionTime/NoOccupancyTime Properties now return non-zero values indicating how long motion sensor/occupancy sensor has been/had been detecting no motion/vacancy.
  • Custom device status/value expressions now use .NET scripting engine which should be faster and should also fix lingering GetStatus issues.
  • Fixed inability to reset a device, delete a device, or remove a sensor via Web Sensors List Page.
  • Fixed unable to check trigger error.
• 2.2.17
  • Finally fixed multiple SysTray icons.
  • Finally fixed SysTray-related ActiveX errors.
  • Fixed potential problem with Custom Action Code not being triggered properly if PC was not restarted for quite some time.
• 2.2.16
  • Fixed HSEvent error resulting from an HSEvent that should have been ignored by DooMotion. There should have been no log entries for when that occurs.
  • Fixed ActiveX error resulting from performing operations using Systray icon menu.
  • Fixed problem with editing custom action code via web interface (clsActionCode2.GenPage error).
  • Added grayscale icon/image to Window Sensors  List Dialog/Web Sensors List Page for depicting that no CAC defined for a given sensor.
• 2.2.15
  • Fixed problem with plug-in devices not updating.
  • Fixed potential problem with DooMotion using a base code (plug-in house code) of another plug-in.
  • Fixed "Unable to process pending events" error.
  • Fixed potential problem that could result in duplicate sensors.
  • Fixed problems with Web Sensor Properties Page.
  • Fixed GetStatus error.
  • Fixed "Unable to check trigger" error.
  • Fixed multiple icons in SysTray.
  • During shutdown, plug-in status device is now set to "Inactive" with date/time of shutdown.
• 2.2.14
  • Fixed "Unable to EXECUTE InsertSensorActivity" error

• 2.2.13
  • Fixed dm.NightTime scripting function.
  • Fixed testing of Custom Action Code using VB.NET scripting.
  • Fixed problem with sorting of Web Sensors List Page.
  • Fixed database errors by enabling row-level locking.
• 2.2.12
  • DM can now be disabled and re-enabled within HomeSeer setup without restarting HomeSeer.
  • Web Sensors List Page now features column sorting as it did in DM 2.0.
  • Windows Sensors List Page now features right-click context menu as it did in DM 2.0.
  • Fixed inability to change sensor type with Windows and Web interfaces.
  • Fixed problem with new sensors not showing up in Windows Sensors List Dialog and Web Sensors List Page until a restart.
  • Fixed synch sensor lists error.
  • Fixed Dusk2DawnSensorClass.GetStatus error.
• 2.2.11
  • Fixed inability  to add a new sensor within Windows interface.
  • Fixed inability to add a new sensor with Web interface.
  • Fixed HS events with DooMotion triggers.
  • Fixed Occupancy Elapsed Time exceeded error.
  • Fixed inability to process custom device status/value relationship (EvaluateCode error).
  • Fixed problem with testing CAC.
  • Fixed problem with Windows Options Dialog not recognizing changes to form data which subsequently resulted in not being able to save changes.
  • Fixed Web Preview in Windows Options Dialog not working reliably.

• 2.2.10
  • Sensor Activity can now be viewed and edited via web interface by using the following url: http://homeseerweb:port/DooMotion/Activity.aspx. The link has been added to the DooMotion menubar. Database can also be compacted. Ability to purge records will be available in a future version.
  • Added Location2 to Windows Sensor Properties Dialog and Web Sensor Properties Page.
  • Fixed problem with setting associated sensors lists within Windows Sensor Properties Dialog and Web Sensor Properties Page.
  • Fixed problem with Windows Sensor Properties Dialog not allowing changes to be saved. Issue resided within code for determining whether form data was changed.
  • Fixed problem with sensor data file not being created for new installs.
• 2.2.9
  • Fixed problem with NewNoMotionDelayedEvents.
  • Fixed TriggerAction error mentioning "Subtract" function.
• 2.2.8
  • Sensor activity data is now viewable. Editing capability to be added later along with a web interface version.
  • Fixed problem with hs object not being added to VBScript scripting engine.
• 2.2.7
  • Fixed problem with changes to Add Icon to SysTray needing a restart to work.
  • Fixed problem with VBScript custom action code file (DooMotion.txt) being populated with System.String[] entries that caused code execution errors.
• 2.2.6
  • Fixed repeat listings of sensors on Web Sensors List Page.
  • Some general fixes with web interface bugs.
• 2.2.4
  • Fixed problem with installation of code editor.
  • Some improvements in reporting of errors in user's custom action code.
• 2.2.3
  • Fixed Init.InitSettings error.
• 2.2.2
  • Fixed "Add Icon to SysTray" setting.
  • Fixed ability to compact DooMotion database (Sensor Activity|Tools|Compact Database). Note that Sensor Activity display is still not finished.
  • Converted database routines from ADO to ADO.NET.
  • Fixed problem with upgrading assigned sensor lists from earlier versions.
  • Fixed problem with No Motion Delayed Events.
  • Fixed problem with loading VB.NET scripting code.
• 2.2.1
  • Fixed problem with multiple Interface settings entries being stored in settings.xml file.
  • Fixed problem with web interface where form data (such as slashes within image paths) were not being processed correctly.
  • Fixed problem with setting the status of dusk/dawn sensors.
  • Errors are now logged with version number in log entry to facilitate debugging.
• 2.2.0
  • Added "Fail Safe Invoked" event trigger.
  • Initial beta release of .NET 2 version for HomeSeer 2.1/2.2.