UPDATE: Check below for a new version of this script!
All:
Here's my first stab at a script to add support for the EZsnsRF module from simplehomenet to the Homeseer Insteon Plug-in. If you aren't aware, the EZsnsRF module sends Insteon events when it receives RF-based triggers from Dakota Alert sensors. The system has a remarkable RF range (I use it for 400' runs personally, and they claim it can send signals as far as 3000') and is only mildly painful to setup.
I have this working (for me) to the point where it recognizes on and off events from 2 of my Dakota Alert outdoor motion sensor modules. There's a lot of work to be done on the code still, and I'm waiting on simplehomenet to furnish me with documentation on exactly what the module sends, but this appears to work for the first 2 sensor groups in the device (I've currently set it up for a maximum of 8 but I understand it internally can recognize up to 20 -- I'll fix this in future updates)
I've only tested this against the first PLM beta, and have no idea what it does w/ the PLC. [UPDATE: I can confirm it works with my PLC, too.]
In order for this to work:
1) You will need to manually pair your RF module with the sensors per the Quick Start guide, and then set the RF module to send updates to a module in your home. I used an unused PLC module as the target.
2) Back up your current Insteon_ExtDevSupport.vb file in the homeseer 2 scripts directory. Keep it someplace safe since you're taking your life in your own hands by using this code.
3) Download the attachment. You will need to rename this script Insteon_ExtDevSupport.vb and place it inside your homeseer 2 scripts directory.
4) Edit the script and insert the ID of your RF module. Change the House Code if you have X10 or other modules using E already.
5) Restart Homeseer 2. It should create 8 new devices, E40-E47. E40 will react to the first sensor you paired against the EZsnsRF. E41 will react to the second paired sensor, and so on.
6) Test the module by watching the logs. Note that by default the EZsnsRF sends on followed almost immediately by off, so it's almost impossible to see a sensor in the on state in Homeseer's status screen (unless you've specifically programmed the ezsnsrf to delay sending the off signal). Watching the logs will show you the data as it goes by. When it works, you should currently see (in debug mode) something like this:
That's it. You can either directly define trigger events based on status change to the devices E40-E47 to have homeseer take action based on the motion sensors, or you can use a third-party plugin like DooMotion (which I love) to handle groups of sensors by setting E40-E47 as motion sensors.
Good luck -- feel free to PM me with questions!
-Tom
UPDATE: Check below for a new version of this script!
All:
Here's my first stab at a script to add support for the EZsnsRF module from simplehomenet to the Homeseer Insteon Plug-in. If you aren't aware, the EZsnsRF module sends Insteon events when it receives RF-based triggers from Dakota Alert sensors. The system has a remarkable RF range (I use it for 400' runs personally, and they claim it can send signals as far as 3000') and is only mildly painful to setup.
I have this working (for me) to the point where it recognizes on and off events from 2 of my Dakota Alert outdoor motion sensor modules. There's a lot of work to be done on the code still, and I'm waiting on simplehomenet to furnish me with documentation on exactly what the module sends, but this appears to work for the first 2 sensor groups in the device (I've currently set it up for a maximum of 8 but I understand it internally can recognize up to 20 -- I'll fix this in future updates)
I've only tested this against the first PLM beta, and have no idea what it does w/ the PLC. [UPDATE: I can confirm it works with my PLC, too.]
In order for this to work:
1) You will need to manually pair your RF module with the sensors per the Quick Start guide, and then set the RF module to send updates to a module in your home. I used an unused PLC module as the target.
2) Back up your current Insteon_ExtDevSupport.vb file in the homeseer 2 scripts directory. Keep it someplace safe since you're taking your life in your own hands by using this code.
3) Download the attachment. You will need to rename this script Insteon_ExtDevSupport.vb and place it inside your homeseer 2 scripts directory.
4) Edit the script and insert the ID of your RF module. Change the House Code if you have X10 or other modules using E already.
5) Restart Homeseer 2. It should create 8 new devices, E40-E47. E40 will react to the first sensor you paired against the EZsnsRF. E41 will react to the second paired sensor, and so on.
6) Test the module by watching the logs. Note that by default the EZsnsRF sends on followed almost immediately by off, so it's almost impossible to see a sensor in the on state in Homeseer's status screen (unless you've specifically programmed the ezsnsrf to delay sending the off signal). Watching the logs will show you the data as it goes by. When it works, you should currently see (in debug mode) something like this:
Code:
6/11/2007 5:15:49 PM Insteon_ExtDevSupport.vb Received Insteon Data 01 08 9E 01 00 00 01 CB 11 00 6/11/2007 5:15:49 PM Insteon_ExtDevSupport.vb SNSRFDebug: 0:01, 1:08, 2:9E, 3:01, 4:00, 5:00, 6:01, 7:CB, 8:11, 9:00 6/11/2007 5:15:49 PM Insteon_ExtDevSupport.vb SNSRFDebug: GroupNum:1 6/11/2007 5:15:49 PM Insteon_ExtDevSupport.vb ProcessEZSnsRFGroupCmd: 1, 11 6/11/2007 5:15:49 PM Insteon_ExtDevSupport.vb Turning device E40 on 6/11/2007 5:15:51 PM Insteon_ExtDevSupport.vb Received Insteon Data 01 08 9E 01 00 00 01 CB 13 00 6/11/2007 5:15:51 PM Insteon_ExtDevSupport.vb SNSRFDebug: 0:01, 1:08, 2:9E, 3:01, 4:00, 5:00, 6:01, 7:CB, 8:13, 9:00 6/11/2007 5:15:51 PM Insteon_ExtDevSupport.vb SNSRFDebug: GroupNum:1 6/11/2007 5:15:51 PM Insteon_ExtDevSupport.vb ProcessEZSnsRFGroupCmd: 1, 13 6/11/2007 5:15:51 PM Insteon_ExtDevSupport.vb Turning device E40 off
Good luck -- feel free to PM me with questions!
-Tom
UPDATE: Check below for a new version of this script!
Comment