No Pressure Posted May 9, 2013 Share Posted May 9, 2013 Hi all. New to ISY and Insteon having a great experience for the most part. But I am struggling with a brand new EZsnsRF (Model 5010E, 2233-233 v1.7 1226which I would like to use with a wireless pushbutton, a driveway sensor and a motion detector (all Dakota). Originally the pushbutton and motion sensor worked fine but after they were deleted, linked, deleted, linked, etc, because of issue with the driveway sensor then they started having issues. The problem with the driveway sensor is that they EZsnsRF does not see it. The current situation is that the push button can be added to the system normally but it doesn't respond once added. The motion sensor can be added but its status does not appear and the system doesn't recognize when it changes state. Here's as much information as I can think to give as background - 1. The sensors have been added according to the directions. Click on add ezsnsrf sensor in the admin console, hold button down for four seconds (slow flash), activate the device (fast flash), press OK in the admin console, wait as directed, hold the button for four seconds, hold the button for four seconds. The LED does not respond as the manual suggest for the last 2 button pushes. a. I tried adding the sensors without adding the EZsnsRF as an Insteon device. 2. I've tried the frequency address 2 ways - setting them all the same per the Dakota directions, setting them all differently per other directions. The batteries were removed between changes. 3. I clear the java cache with all browsers closed between attempts, I have cycled power on the 994 (always 2x with 30 seconds between cycles), I have factory reset the EZsnsRF multiple times, etc, etc per the various things I found on the WIKI and forum. 4. The firmware and gui have been upgraded to 4.04 RC. All of the equipment is new. Original firmware was 3.3.1. 5. I have switches, dimmers and EZIO8SAs around the house. There's 240v load controller in another portion of the house. I have the device which connects the two phases installed at the main breaker panel... I don't think communications in the house are the problem. Type 3 events from a query of the push button - Thu 05/09/2013 04:17:28 PM : [iNST-TX-I1 ] 02 62 1E 7F 44 0F 4F 02 Thu 05/09/2013 04:17:28 PM : [iNST-ACK ] 02 62 1E.7F.44 0F 4F 02 06 IOCTL (QUERY) Thu 05/09/2013 04:17:29 PM : [iNST-SRX ] 02 50 1E.7F.44 22.83.0E 27 4F 02 IOCTL (QUERY) Thu 05/09/2013 04:17:29 PM : [std-Direct Ack] 1E.7F.44-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 05/09/2013 04:17:29 PM : [ 1E 7F 44 1] ST 0 Thu 05/09/2013 04:17:29 PM : [iNST-TX-I1 ] 02 62 1E 7F 44 0F 49 00 Thu 05/09/2013 04:17:29 PM : [iNST-ACK ] 02 62 1E.7F.44 0F 49 00 06 RINPUT (00) Thu 05/09/2013 04:17:29 PM : [iNST-SRX ] 02 50 1E.7F.44 22.83.0E 27 49 00 RINPUT (00) Thu 05/09/2013 04:17:29 PM : [std-Direct Ack] 1E.7F.44-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Any guidance would be greatly appreciated. ISY-Events-Log.v4.0.4__Thu 2013.05.09 04.17.38 PM.txt Link to comment Share on other sites More sharing options...
LeeG Posted May 9, 2013 Share Posted May 9, 2013 The delete/add sequence has likely gotten the Group numbers out of synch. Delete the EZSnsRF from the ISY, then factory reset the EZSnsRF and add back to the ISY using one Dakota Alert device with a unique code. If all the devices have the same code you will not know which Dakota Alert device is sending the signal. May have to tap the Set button on the EZSnsRF more than the instructions indicate. Depends on what PLM is inside the EZSnsRF. Do not attempt to add other Dakota Alert device until the first is working. If the first one does not work more analysis of the link database and perhaps some information from the EZSnsRF itself will be needed. Adding more Dakota Alert devices makes the analysis more complex. Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 LeeG Thanks for the quick reply. I tried the code switch because the Dakota brand receiver apparently uses a different method for detecting the differences between devices. I understand that the EZsnsRF picks ups the signals on different frequencies to distinguishing which one is which. I've read this site, dakota's site and every one that has a shred of info before I posted. And I have even tried the test you describe, now multiple times with the two sensors that were working (individually of course). But am going to go through it again now. And I will post the result. Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 LeeG Actually one question...Should I add the EZsnsRF through the Insteon Autodetect and then add the sensor? That leaves me with a 1e.7f.44 0 and a 1e.7f.44 1. Or should I just proceed to adding the sensor. When the system worked it was with the former configuration - a 0 and a 1. Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 LeeG, Tried it both ways with the push button and the motion detector. No luck. However the motion detector does get a status box indicating off when it is added by itself. Unfortunately the status never changes. Thanks again. Link to comment Share on other sites More sharing options...
LeeG Posted May 10, 2013 Share Posted May 10, 2013 How old is the EZSnsRF? Does it have a plain face without a passthru outlet? Run Tools | Diagnostics | Event Viewer at LEVEL 3, do a Show Device Links Table and post the event trace. Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 LeeG, I tried adding the sensor solo without adding the EZsnsRF as an insteon device. Then I did it with the EZsnsRF as an insteon device. Both link tables are attached and the version is noted in the filename. Where can I read more about what the information in that event log means? You're help is greatly appreciated but I would have kept digging into this on my own if I knew where to look. Thanks ISY-Events-Log.v4.0.4__Fri 2013.05.10 06.14.47 AM_motion_detector_added_solo.txt ISY-Events-Log.v4.0.4__Fri 2013.05.10 06.14.47 AM_motion_detector_added_ezsysrf_first.txt Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 I forgot to mention that I just bought it about 2 weeks ago. No pass through. Model 5010E, 2233-233 v1.7 1226. Link to comment Share on other sites More sharing options...
LeeG Posted May 10, 2013 Share Posted May 10, 2013 Next step is to run the SHN Utility Suite (free download from Simplehomenet/Smartenit web site). This requires a PLM connected to a PC. Invoke the Utility, Connect to a PLM, select EZSnsRF tab at top of window. Enter Insteon address of EZSnsRF (added this step) Set Code Number to 1, click Read button. The values are read 1 byte at a time so the Read process takes several seconds. What is displayed in the "Settings for RF code records" fields. Set Code Number to 2, click Read button. What is displayed in the "Settings for RF code records" fields. I am assuming the sequence of Delete EZSnsRF, factory reset, add to ISY was not followed for these latest trace files. The link record for the only Dakota Alert device the ISY is aware of is using Group 01. I suspect when the Motion Sensor was added to the EZSnsRF again it was the second device the EZSnsRF is aware of and used Group 02 for the definition. Displaying the “Settings for RF code records†information will provide the Group information. Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 LeeG, You wrote, "I am assuming the sequence of Delete EZSnsRF, factory reset, add to ISY was not followed for these latest trace files" The latest Quick Start for the EZsnsRF says, "Unplug the EZSnsRF for at least 10 seconds. Press and hold the pushbutton and plug it back in while keeping the pushbutton depressed. Continue to hold the pushbutton for an additional 10 seconds and then release." I have followed that to a tee with every change of the sensors using a very slow count to 10. I also wait for a good amount of time after the reset to make any additions just in case the device is still going through the process internally. But I will do it again now. Thanks again. It's great to get such support on a forum like this. I'll follow-up shortly (hopefully with good news). Link to comment Share on other sites More sharing options...
No Pressure Posted May 10, 2013 Author Share Posted May 10, 2013 Is it safe to assume that the utilities are not compatible with the 2412N Smartlinc? Otherwise, I've got a 2413S around but I'll need to find a serial port. Link to comment Share on other sites More sharing options...
LeeG Posted May 10, 2013 Share Posted May 10, 2013 The Utility does not support the 2412N. It requires a PLM. My comment regarding the factory reset is related to the link records that are in the second trace. It appears to have the link record associated with the first effort to add a Dakota Alert device outside of the ISY along with the link record when the motion sensor was added under the ISY. Link to comment Share on other sites More sharing options...
No Pressure Posted May 11, 2013 Author Share Posted May 11, 2013 I attempted to figure this out for a couple of hours without assistance. Still no luck... Then I recreated and the actions that I took earlier and compared the files, As far as I can tell I started at the same place and then followed your guidance. Attached is the version where I added the EZsnsRF and then added a sensor. I inserted the information from the utility at the end of the file. I will repeat the exercise adding only the sensor next. ISY-Events-Log.v4.0.4__Fri 2013.05.10 08.01.03 PM_motion_detector_added_ezsysrf_first.txt Link to comment Share on other sites More sharing options...
LeeG Posted May 11, 2013 Share Posted May 11, 2013 The EZSnsRF information is not correct. The ‘Linked’ check box must be checked for Code Number 1. The Dakota Alert code “BF†and the remainder of the information looks okay. With the Linked box not checked I'm not sure the Set button sequence is correct and the ISY wrote the required link record. First do a Show Device Links Table and verify this link record exists E2 01 22 83 0E FF 00 01 Code Number Linked In Use Timer Code Group Cmd1 Cmd2 Cmd1 Cmd2 1 No Check 0.0 BF 1 11 0 13 0 2 No No 0.0 0 2 11 0 13 0 Using the Utility, Read Code Number 1, check the Linked box and click Write When the Write completes (busy goes back to Ready) Read the information back to be sure the information was not scrambled. When the information is correct try the motion sensor with the Event Viewer at LEVEL 3 to see if inbound messages are generated. Link to comment Share on other sites More sharing options...
LeeG Posted May 11, 2013 Share Posted May 11, 2013 With the Event Viewer at LEVEL 3, right click the EZSnsRF node, select Diagnostics | Query Insteon Engine and post the event trace. Extended commands are being used to write the EZSnsRF link records which is odd. Have the Link Management | Advanced Options be changed from the defaults? Link to comment Share on other sites More sharing options...
No Pressure Posted May 11, 2013 Author Share Posted May 11, 2013 Yes the line is there. 0 : 1FF8 : E2 00 22.83.0E FF 00 00 1 : 1FF0 : E2 01 22.83.0E FF 00 01 2 : 1FE8 : 00 00 00.00.00 00 00 00 The ISY sees the motion detector according to the event log and ON appears in the UI. Fri 05/10/2013 10:36:14 PM : [iNST-SRX ] 02 50 1E.7F.44 22.83.0E 41 11 01 LTONRR (01) Fri 05/10/2013 10:36:14 PM : [std-Cleanup ] 1E.7F.44-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 05/10/2013 10:36:14 PM : [ 1E 7F 44 1] DON 0 Fri 05/10/2013 10:36:14 PM : [ 1E 7F 44 1] ST 255 Fri 05/10/2013 10:36:16 PM : [iNST-SRX ] 02 50 1E.7F.44 00.00.01 C7 13 00 LTOFFRR(00) Fri 05/10/2013 10:36:16 PM : [std-Group ] 1E.7F.44-->Group=1, Max Hops=3, Hops Left=1 Fri 05/10/2013 10:36:16 PM : [ 1E 7F 44 1] DOF 0 Fri 05/10/2013 10:36:16 PM : [ 1E 7F 44 1] ST 0 Fri 05/10/2013 10:36:16 PM : [iNST-SRX ] 02 50 1E.7F.44 22.83.0E 41 13 01 LTOFFRR(01) Fri 05/10/2013 10:36:16 PM : [std-Cleanup ] 1E.7F.44-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 05/10/2013 10:36:16 PM : [iNST-DUP ] Previous message ignored. Query the insteon engine... Fri 05/10/2013 10:42:22 PM : [All ] Writing 1 bytes to devices Fri 05/10/2013 10:42:22 PM : [iNST-TX-I1 ] 02 62 1E 7F 44 0F 0D 00 Fri 05/10/2013 10:42:22 PM : [iNST-ACK ] 02 62 1E.7F.44 0F 0D 00 06 (00) Fri 05/10/2013 10:42:23 PM : [iNST-SRX ] 02 50 1E.7F.44 22.83.0E 27 0D 02 (02) Fri 05/10/2013 10:42:23 PM : [std-Direct Ack] 1E.7F.44-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 05/10/2013 10:42:23 PM : [1E 7F 44 0 ] Calibrating engine version Link to comment Share on other sites More sharing options...
No Pressure Posted May 11, 2013 Author Share Posted May 11, 2013 Advanced Options = Automatic: ISY tries to find the most suitable messaging option I don't believe it was ever changed. Link to comment Share on other sites More sharing options...
LeeG Posted May 11, 2013 Share Posted May 11, 2013 The EZSnsRF is an I2CS device which is why the ISY is using Extended commands to manage the link database. I suspect the EZSnsRF firmware is expecting the link records to be written with Peek/Poke commands. Once it sees the link record being written using Peek/Poke it would normally turn on the ‘Linked’ bit. The ISY cannot use Peek/Poke for a device that identifies itself as I2CS because Peek/Poke commands have been dropped from I2CS devices. I expect it will be necessary to turn on the Linked bit for each Dakota Alert device defined to the EZSnsRF. Link to comment Share on other sites More sharing options...
No Pressure Posted May 11, 2013 Author Share Posted May 11, 2013 That worked perfectly and I learned a bunch of things during the process. You should have a PayPal donations button somewhere on the web. The second issue from my original post remains. The EZSnSRF still doesn't see the driveway sensor during linking. Click the button on the EZ until you get a slow blink, activate the sensor, watch the red LED flash, but no response at the EZ. Is it safe to assume that's a different issue? Assuming so I'll start another thread to keep things organized around here. Thanks a million. Link to comment Share on other sites More sharing options...
LeeG Posted May 11, 2013 Share Posted May 11, 2013 That is a different problem. Make sure it has its own dip switch code and you may have to move it closer to the driveway sensor. With the EZSnsRF seeing the motion sensor but not the driveway sensor it sounds like an RF range issue. Perhaps there is something in the path of the driveway sensor that is not in the path of the motion Sensor. The Utility has the capability to display the 'Last Received RF code'. The code does not have to be linked to the EZSnsRF. It should indicate if the EZSnsRF is receiving the driveway code. When the Insteon address is entered into the EZSnsRF tab, what firmware level is display? Link to comment Share on other sites More sharing options...
No Pressure Posted May 11, 2013 Author Share Posted May 11, 2013 LeeG saved the day for me on this one as it seems he has done many other times for other problems. The thread grew quickly and the solution was buried in the middle. So for the next person who bumps into this issue… 1. Get yourself a PLM if you don’t already have one 2. Connect it to your computer through the serial port 3. Download anthe Simplehomenet Smartenit Utility Suite 4. Factory Reset the EZSnSRF 5. Add the EZSnSRF as an Insteon device 6. Add Sensor to EZSnSRF 7. In the Utility connect to PLM 8. Goto EZSnSRF tab 9. Read code Number X (where X is the sensor number) a. You have to do this with each sensor 10. Check the Linked box 11. Record the other codes 12. Click Write 13. Wait until it’s not busy 14. Make sure the codes haven’t changed 15. Wait a bit more then test the sensor back at the UDI Admin Console Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.