You can further enhance the table with an index such as CREATE NONCLUSTERED INDEX Again the syntax varies between database systems. Its worth having an identity so there's a primary key on the table, at least in MSSQL anyways and you'd create this with ALTER TABLE. If your using Microsoft Access (JET 4.0) Then the create table would be slightly different: CREATE TABLE DXP ( This isn't INSERTed so you can leave it off or create your own name and format. In this example above I've created an identity Column named RID. If your familiar with the database then the format of the CREATE TABLE command shouldn't be that hard. The above SQL is for MSSQL, MySQL is slightly different as is Oracle, MariaDB, Interbase, JET and so on. You will need to create the table in this format: CREATE TABLE. ini file) and you need to make sure you've created this table and given the user INSERT privileges before running the plug-in. The Plug-in, using the OLE connection string establishes connection to a database (local or remote) and writes to a Table called DXP (Table name can be changed in the. Monitor_300,3600 <- Write Device 300's state every hour (3600 seconds) Monitor_200=0 <- Write Device 200's state every time it changes. Monitor_100=900 <- Write Device 100's state every 900 seconds (15 minutes) That is, if the sample period is zero, then the plug-in will write to the database every time the given device changes, whereas for non zero sample period the plug-in will write to the database every sample seconds. The format of the INI file in the section is Monitor_xxx=yyy where xxx is the HS3 Device Reference and is always an integer and yyy is the sample period or 0 for on change and is in seconds. Be sure to SAVE the config after adding devices or your changes will be lost when the plug-in restarts. INI file which resides in the Config folder under the HS3 directory, OR you can add devices via the Config Tab. In my case the plug-in exports power usage data hourly, environmental data (Temperature and Humidity) every 15 minutes and a few key zones such as movement as and when they change.Ĭonfiguration of devices to be monitored is stored in the plug-ins. Using a reasonable Server data can be selected, analysed and charted using tools like Microsoft Excel, Jasper, Crystal etc. The market for this plug-in is long term and/or large volume data analysis from Homeseer HS3 systems. Common times are something like 900 seconds for environmental, and On Change (0 seconds) for zones but its up to you to set it up as you see fit. The shortest interval we can sample data is 1 second although I'm not sure why you'd want that. For this reason there may be a small delay between device state changes and the record arriving at the database, but this should be limited to seconds. The plug-in leverages a multi-threaded architecture to ensure loading of the HS3 instance is kept to a minimum and writes to the database in the background. We use the standard OLE Connection String format to determine where to write the data. This Plug-in for HomeSeer is designed to export device data (On Change or Interval) to a wide range of databases and systems. DXP (Data Export) Plug-in for Homeseer HS3