AnonymousMay 14, 2007 at 2:15 amPost count: 8
I am using the EzSnsRf on my insteon network run by Homeseer 2.2. I have the EzSnsRf turning on button A on a Keypadlinc. I was hoping that a change in state of button A could be used to trigger a whole sequence of lights (in this case the ExSnsRf is activated when someone drives down my driveway). Unfortunately I haven’t been able to make it work completely. EzSnsRf does turn on button A. However, it doesn’t trigger the sequence of lights (while physically turning on button A does). I think the problem is that the EzSnsRf is not crosslinked with button A.
One of the challenges with EzSnsRf is that Homeseer can’t add the insteon address manually and there is nothing in the instructions about crosslinking. Has anyone come up with a solution using EzSnsRf to activate a series of events using Homeseer?
The instruction sheet from Simplehomenet references some other documentation (other than the quick start guide). Can someone point me to where that is located?
ThanksAnonymousMay 14, 2007 at 5:13 pmPost count: 408
We are completing the other docs. Sorry for the delay. As far as controlling links, we are creating an EZSnsRF utility (free download) that will allow for link management. You can also do a group command, and have the lights you want controlled connected to the group.
Finally, I also encourage you to look at the ezbridge. It can respond to data and issue other commands (macros). It also has timers, etc…AnonymousMay 29, 2007 at 8:01 pmPost count: 9
i pinged the guy who writes the insteon v2 plugin for homeseer about this specific device. I’ll post back here with his feedback. My concern is how to link the ezsnsrf against the PLC/PLM — right now as you’re aware homeseer doesn’t see it as a device even when you attempt to pair it manually while it’s in “learn” mode.
If you really need support for the change events then you’ll need to enable polling on your keypadlinc. Unfortunately, the shortest duration possible is 1 minute and even that’s iffy given how much time is spent polling each key status through the PLC.
I’m looking forward to the software that allows us to define links in software, though I’m curious exactly how that information will make it into the ezsnsrf. Got any ideas for us, Paul?
-tAnonymousJune 1, 2007 at 8:47 pmPost count: 256
The EZSnsRF links database behaves the same as our other PLM-based devices. Additionally, there is another database of learned codes that stores the timers for the inputs. Both databases will be alterable through our upcoming utility sometime in June.AnonymousJune 11, 2007 at 8:09 pmPost count: 9
I’ve got the basic structure down on the SNSRF I/O in and out of homeseer’s insteon plugin, and am seeing the following messages for the single dakota RF module paired with the SNSRF, Device ID 08.9E.01:
01 08 9E 01 00 00 01 C7 11 00
01 08 9E 01 00 00 01 C7 13 00
Field 0 is always 01 for status messages.
Field 1-3 indicate the device ID
Field 4-6 are (so far) always 00 00 01 — I’m not sure what this indicates — device ID? Dakota ID?
Field 7 consistently appears as either C3 or C7, which I’m assuming indicates some kind of group id or device id.
On seems to consistently appear as hex 11 in Field 8, and off as hex 13.
Given that there’s currently a lack of developer documentation for these devices, can you elaborate a bit on my observations? Specifically, what the content of these fields is and how I might best interpret it to observe on and off states for multiple sensors?
-TomAnonymousJune 12, 2007 at 6:56 amPost count: 256
Tom, sorry we are late releasing the expanded document on the EZSnsRF (we are actually busy bringing out an X10 version). But we were not planning to cover the group messages sent in response to a sensor input. Your observation is that of a standard group command that the EZSnsRF sends in response to a sensor signal being received.
Perhaps if you tell us more of what you need to see, or what application you are developing, we can then figure out what additional documention to release.
Sorry if we are not addressing your need quickly enough!!AnonymousJune 12, 2007 at 6:27 pmPost count: 9
No worries — I’m familiar with being a garage developer and all the insanity that results.
I’ve been somewhat successful in creating a vb.net script for HomeSeer’s Insteon Plug-in that interfaces the ezsnsrf with homeseer. I’m at least able to detect (with a PLM) distinct on and off signals from distinct dakota alert modules and have them trigger events in homeseer. I personally use it to detect motion on various parts of my property and have homeseer turn certain groups of lights on as long as motion has been detected within the past 30 minutes. It’s working reliably so far, but I’m unfamiliar with the actual insteon command structure and pretty much hacked the script together. I’m sure it’s missing support for device status query, and wasn’t certain if this was supported by the module.
If you’d like to take a gander, the code’s pretty readable. It’s posted on homeseer’s Insteon forums, currently located at the following URL:
I’ll keep that URL current with script updates as they come to be.
[/url]AnonymousNovember 29, 2009 at 5:29 amPost count: 16
I just bought anEZSnsRF. It picks up the dakota alert inductive driveway sensor fine. I am not having any luck getting Homeseer to trigger on it. I need to have it send me an email.. and only at night turn on the insteon controlled driveway lights.
For the longest time I had an X10 interflash module wired direct to he Dakota alert reciever relay contacts and it worked fine for a couple of years. Then X10 reliability declinded and finally it stopped working altogether and this is why I purchased the EZSnsRF.
I linked it to trigger an insteon switch link module which it does fine. When the driveway sensor is tripped it turns on the linked module (called Driveway sensor indicatior) for a second or so then shuts it off. So I set up an event that is to trigger on the state change to “on” of Driveway sensor indicator insteon module. if I use the Homeseer status screen and turn on the switchlink module, the event triggers fine. The event never triggers when the EZSnsRF turns the module on so it wont trigger at all when I trip the driveway sensor. I cant add the EZSnRF to homeseer as a device or on input device such as a remote or keypad link button. I see the earlier threads fom 2007 with similar concerns from others but no conclusion. Also what this about a utility to set up linking that is mentioned on the sheet that came with it? I can’t find anything on the simple home net website.
So Simple home net, can the EzSnsRF be used with Homeseer? Please confirm. if not I need to return it to Aartech for a refund .
ThanksAnonymousNovember 29, 2009 at 5:42 amPost count: 8
I use it with homeseer. Here is how
http://board.homeseer.com/showthread.php?t=121595&highlight=ezsnsrfAnonymousNovember 29, 2009 at 6:00 amPost count: 16
Hi Jono, Thanks. I have downloaded your script. I will give it a try. I have not played with scripting yet on homeseer so now is my need to start. have you made any changes to it since you posted it on Aug 31 2007?AnonymousNovember 29, 2009 at 8:41 amPost count: 1001
I know nothing about Homeseer but it sounds like you do not have the EZSnsRF linked to the powerline controller being used by Homeseer. You can trigger from an Insteon message being sent from the SwitchLinc I assume because that device is linked to the Homeseer powerline controller. The EZSnsRF will send messages only to the devices that have been linked to it. The SwitchLinc is linked to the EZSnsRF as it is responding to the Insteon message generated by the receipt of the Dakota Alert RF signal. If Homeseer will not trigger from the same condition it is likely that the Homeseer powerline controller is not linked to EZSnsRF so it does not “see” the Insteon messages being sent to the SwitchLinc. Again just from an Insteon perspective, without that link the only way Homeseer would know if the SwitchLinc is On or Off from another device would be to Query the SwitchLinc on some time basis.
The Simplehomenet Utility Suite is a free download available on the Downloads section of the SHN web site. The Utility requires a PLC or EZSrve device to interface to the powerline. The Utility does not support a standalone PLM as a powerline interface.AnonymousNovember 29, 2009 at 1:58 pmPost count: 8
Hi Jono, Thanks. I have downloaded your script. I will give it a try. I have not played with scripting yet on homeseer so now is my need to start. have you made any changes to it since you posted it on Aug 31 2007?
I have not made any changes to the script. I didn’t develop it, but like you was trying to use EzSnsRf with homeseer. The script was developed to allow non HS supported devices to be used.
As an alternative, the HS Insteon Plug in is currently being worked on again. Mark Sandler is doing a great job on it. You could request direct support for the EzSnsRf and once written, not need the script.AnonymousNovember 29, 2009 at 2:23 pmPost count: 16
Thanks folks. This helps. I have some EZIO modules still in the box waiting for garage door control and I assume will have the same issue with homeseer. Jono, is mark with homeseer or SHN? I’m surprised on the lack of SHN plugins. I have a mutl I/O shn module that’s been sitting in the box for a couple of years now because of this..AnonymousNovember 29, 2009 at 2:35 pmPost count: 8
Mark is writing the plug in for Homeseer. You can find the latest here:
I believe you can use the external script for the I/O units but that may also be something Mark has on his list. Insteon is tough to support because each new product has to be coded separately. For 18 month HS decided they couldn’t support a dedicated person to it as HS is trying to support many different interfaces and they couldn’t dedicate a full person just to Insteon. Mark has picked up the ball but I don’t know if he is compensated by HS or not.AnonymousNovember 29, 2009 at 8:03 pmPost count: 16
Jono, Really appreciate the quick replies and the info.
I checked out the link and couldn’t find a thread specific to the EzSnsRF HomeSeer plugin so I started a thread..
I’m sure like I did… most people order these modules thinking HS will support them right out of the box. I’m suprised SHN would not insist on having HS plugins available for all of thier inteon modules. I would think this would pay dividends in the resulting product sales and reduced product returns.
Ok, off to take my first go at working with HS scripts…
I’ll post my outcome..
- You must be logged in to reply to this topic.