| Author |
|
kenbr
Newbie
Joined: July 17 2007
Online Status: Offline
Posts: 33
|
| Posted: November 20 2009 at 15:56 | IP Logged
|
|
|
i need to set up detection for basement flooding and i have an ezsnsrf wireless sensor receiver along with dakota water sensor..
anyone have one of these working with powerhome? any quick tips?
thanks
ken
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: November 20 2009 at 23:45 | IP Logged
|
|
|
I had an EZSnsRF back when I started with Powerhome 1. I had to define a Type entry for the device as PH did not have a predefined Type for the EZSnsRF. You cannot configure the device specific options using PowerHome. You can use the Set button method to establish the RF signal and any device links you want to establish. There is also a free Simplehomenet Utility Suite that can be used to set the EZSnsRF specific options. The SHN Utility requires a PLC or EZServe to act as the powerline interface. You can manage the link database with PH. The EZSnsRF sends standard Insteon Group messages when it receives a Dakota Alert RF signal so PH Triggers can be defined to fire on those conditions.
__________________
Lee G
|
| Back to Top |
|
| |
kenbr
Newbie
Joined: July 17 2007
Online Status: Offline
Posts: 33
|
| Posted: November 21 2009 at 00:48 | IP Logged
|
|
|
Thanks Lee, This is pretty much what i figured out and I do have the sensor and ezsnsrf working together to fire a trigger... But, I think the ezsnsrf is hosed up. initially, i was able to talk to it with the simplehomenet program/plc combination, but that stopped working. the logs (from that program) show that the ezsnsrf receives the commands and replies but from 2 addresses: xx.xx.DA and xx.xx.DB (the unit is marked as xx.xx.DA). This confuses that program and it times out. Doing a manual reset doesn't help that problem, though it does clear out the links as far as i can tell.
So, though I don't get the commands out of it that I'd like, it does send a state change when the water sensor shorts and I can trigger my macro on that. I'll replace it after the holidays.
Thanks for the help.
ken
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: November 21 2009 at 06:35 | IP Logged
|
|
|
I'm surprised you still get an indication after doing a factory reset as that should have cleared not only the link database but also the RF Code Record (Virtual Input) information such that it no longer knows the RF frequency/zone combination to respond to. The scrambled Insteon address may be a powerline noise or PLC problem. My PLC started returning bad information including device address and eventually stopped working altogether. The EZSnsRF does not send Group commands if there are no links for the particular RF Code Record Group number. Restoring the link between the EZSnsRF and the PowerHome PLC/PLM for that Group number should restore Insteon Group In command flow. The SHN Utility can write the EZSnsRF link record but it cannot write the PLC side if you are using the PLC as the Powerhome controller. The PLC has a linked list link database format which the SHN Utility cannot read or write.
__________________
Lee G
|
| Back to Top |
|
| |
kenbr
Newbie
Joined: July 17 2007
Online Status: Offline
Posts: 33
|
| Posted: November 21 2009 at 11:44 | IP Logged
|
|
|
when i did the reset (unplug 10 sec, hold the button for 10 while plugging it in) i did relearn the wireless flood sensor and used powerhome to link it to the plc. i'm not getting any other errors on my plc, though i do know that they're failure prone having replaced 2 now. i've got a plm for this system, but have not installed it yet... i've also manually linked it with an appliance module just to see if the output changes, but it doesn't. i did try clearing and reloading the plc too.
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: November 21 2009 at 12:17 | IP Logged
|
|
|
You sure have done a good job covering the bases. If you are getting the broadcast status change message instead of the Group On message check the Group number in the RF Code Record against the links in the EZSnsRF database. Also if you linked the ApplianceLinc module manually with the Set button, that the link does appear in the link database Display. Some time ago the new PLMs with the larger memory size started appearing in the SHN products being shipped. This means that links created by powerhome could be written in a location that is valid for the older PLM that supports 417 link records but is in the incorrect location for a PLM that supports 2000+ links. The EZSnsRF has an internal PLM. If the ApplianceLinc link was done with the Set button and it does not display using the SHN Utility, try changing the Links Database Size parameter from Small to Large and repeat the Display request. A Set button created link will be written by the PLM based on the actual size of its memory. A powerhome written link is written with Peek/Poke commands at where it thinks the correct location is based on the Type definition database size column.
This has nothing to do with the wrong device address appearing in messages but could explain why there are broadcast status change messages rather than the expected Group messages even thought PH wrote link records.
__________________
Lee G
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: EZSnsRF
