jspoon Posted March 10, 2014 Posted March 10, 2014 I pushed the button just before I did the Add Insteon device, so it should be active. I have the one Keypad dual band device and I assume the ISY also has the RF receiver. I also placed the sensor within a few feet of both. I do not have any access points since the devices are so close. Since it said it was an unsupported device, I assume the ISY is communicating with it... This is strange, sounds like most other folks got things running by updating firmware.
LeeG Posted March 10, 2014 Posted March 10, 2014 Click help | About. What is displayed for Firmware? What is displayed for UI? It sounds like the UI (Admin Console) is not at 4.1.2.
jspoon Posted March 11, 2014 Posted March 11, 2014 Help does say both firmware and UI are: Insteon_UD994 v.4.1.2 (2014-01-13-23:20:00)
shannong Posted March 11, 2014 Posted March 11, 2014 Have you tried holding the Set button until the green light begins blinking and then manually adding it?
LeeG Posted March 11, 2014 Posted March 11, 2014 The Hidden Door Sensor is in the list of supported devices on 4.1.2. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Put the Hidden Door Sensor into linking mode with its Set button and attempt to add using new INSTEON Device. Post the event trace.
shannong Posted March 11, 2014 Posted March 11, 2014 I assume the ISY also has the RF receiver. The ISY does not have an RF Insteon transceiver. That's why it has to be mated with a PLM to provide an interface to the Insteon network. The newer 2413 PLMs are dual-band and thus RF-enabled. The older 2412s and 2414s are powerline only.
tandar Posted March 11, 2014 Posted March 11, 2014 jspoon, I had similar difficulties linking the door sensor. I moved the sensor 10 feet closer to an Access point and that made the difference. After linking, the device works fine at the original distance and further. It seems that linking requires a stronger signal?
jspoon Posted March 12, 2014 Posted March 12, 2014 LeeG: Tue 03/11/2014 07:25:19 PM : [2b b 6b ] Added to list of devices to link to ISY Tue 03/11/2014 07:25:19 PM : [iNST-TX-I1 ] 02 62 2B 0B 6B 0F 0D 00 Tue 03/11/2014 07:25:19 PM : [iNST-ACK ] 02 62 2B.0B.6B 0F 0D 00 06 (00) Tue 03/11/2014 07:25:20 PM : [iNST-SRX ] 02 50 2B.0B.6B 13.24.2B 2B 0D 02 (02) Tue 03/11/2014 07:25:20 PM : [std-Direct Ack] 2B.0B.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/11/2014 07:25:20 PM : [iNST-TX-I1 ] 02 62 2B 0B 6B 0F 10 00 Tue 03/11/2014 07:25:20 PM : [iNST-ACK ] 02 62 2B.0B.6B 0F 10 00 06 ID-REQ (00) Tue 03/11/2014 07:25:21 PM : [iNST-SRX ] 02 50 2B.0B.6B 13.24.2B 2B 10 00 ID-REQ (00) Tue 03/11/2014 07:25:21 PM : [std-Direct Ack] 2B.0B.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/11/2014 07:25:30 PM : [iNST-TX-I1 ] 02 62 2B 0B 6B 0F 10 00 Tue 03/11/2014 07:25:30 PM : [iNST-ACK ] 02 62 2B.0B.6B 0F 10 00 06 ID-REQ (00) Tue 03/11/2014 07:25:30 PM : [iNST-SRX ] 02 50 2B.0B.6B 13.24.2B 2B 10 00 ID-REQ (00) Tue 03/11/2014 07:25:30 PM : [std-Direct Ack] 2B.0B.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/11/2014 07:25:39 PM : [iNST-TX-I1 ] 02 62 2B 0B 6B 0F 10 00 Tue 03/11/2014 07:25:39 PM : [iNST-ACK ] 02 62 2B.0B.6B 0F 10 00 06 ID-REQ (00) Tue 03/11/2014 07:25:39 PM : [iNST-SRX ] 02 50 2B.0B.6B 13.24.2B 2B 10 00 ID-REQ (00) Tue 03/11/2014 07:25:39 PM : [std-Direct Ack] 2B.0B.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/11/2014 07:25:43 PM : [2B B 6B 0 ] Cannot determine device type Tue 03/11/2014 07:25:43 PM : [2B B 6B 0 ] Failed to add device, reason 2 Tue 03/11/2014 07:25:43 PM : [All ] Writing 0 bytes to devices Tue 03/11/2014 07:26:32 PM : [ Time] 19:26:33 1(0) One thing to note, is that my PLM is older and not dual band. So, the Keypad is the only Dual Band device I have. The sensor was only about a foot away... Thanks to everyone for your help. Jay
LeeG Posted March 12, 2014 Posted March 12, 2014 The Hidden Door Sensor is not completing the sequence that is asking for the type of device. There should be an Extended message that is not being received or not processed by the PLM. Tue 03/11/2014 07:25:20 PM : [iNST-TX-I1 ] 02 62 2B 0B 6B 0F 10 00 Tue 03/11/2014 07:25:20 PM : [iNST-ACK ] 02 62 2B.0B.6B 0F 10 00 06 ID-REQ (00) Tue 03/11/2014 07:25:21 PM : [iNST-SRX ] 02 50 2B.0B.6B 13.24.2B 2B 10 00 ID-REQ (00) Tue 03/11/2014 07:25:21 PM : [std-Direct Ack] 2B.0B.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 There should be an Extended message here with the device type information. Comm looks good as the Standard message from the Sensor has a Hops left=2 (as good as it gets). How old is the PLM? What does Tools | Diagnostics | PLM Info/Status display?
jspoon Posted March 12, 2014 Posted March 12, 2014 It is pretty old... is there a way to update it? 13.24.2B v92 / Connected
LeeG Posted March 12, 2014 Posted March 12, 2014 A PLM cannot be updated. A new PLM would be a 2413S Dual Band PLM.
jspoon Posted March 12, 2014 Posted March 12, 2014 That is expensive, but I certainly appreciate everyone's help. Ordering a new PLM and that will be another dual-band device, so guess that helps too. thanks again!
jspoon Posted March 13, 2014 Posted March 13, 2014 When I get the new PLM, what steps do I need to take to swap them out? I assume a current backup and then do I just need to "Restore Modem (PLM)? Any other steps? Thanks.
LeeG Posted March 13, 2014 Posted March 13, 2014 The Wiki covers the process of replacing a PLM, under 6.1 http://wiki.universal-devices.com/index ... _.28PLM.29
jmed999 Posted March 14, 2014 Posted March 14, 2014 I use these with the ELk. I inserted them into the top of the door so they are completely hidden... http://www.smarthome.com/79463/GE-Security-TX-1510-01-1-DesignLine-Recessed-Door-Window-Sensor/p.aspx
jspoon Posted March 14, 2014 Posted March 14, 2014 Thank you again to all, you are a great group. I now have a working Door Sensor.
MikeD Posted March 20, 2014 Posted March 20, 2014 I just upgraded to 4.1.2 Beta and installed a 2845-222 Hidden Door Sensor. Does it broadcasts it's status every x number of hours? Only one node showed up when I added it unlike the 2852-222 Leak Sensor.
Xathros Posted March 20, 2014 Posted March 20, 2014 It only broadcasts status changes as they happen (Open/Close) just like a Triggerlinc. No heartbeat. -Xathros
shannong Posted March 20, 2014 Posted March 20, 2014 It can be used as two nodes: 1 for Open and 1 for Close. Use the "Options" to change it. You'll need to activate it (open/close it) or use the set button for changes to be written.
MikeD Posted March 20, 2014 Posted March 20, 2014 Funny how the manual misleads: Adjust Heartbeat Interval Customize the duration of time between sensor check-ins; by default, the sensor will broadcast it’s state once every 24 hours. Low Battery Warning Enable or disable a low battery broadcast that can trigger events with software. Disappointed to say the least. ~Mike
Xathros Posted March 20, 2014 Posted March 20, 2014 Mike- I could be mistaken. I have not yet installed mine yet and have no direct experience yet but was under the impression that these were just Triggerlincs in a different package. I will dig deeper but I have not seen anyone else indicate more than one/two nodes depending on configuration on these. It is possible that Smarthome added heartbeat and low battery nodes and the ISY just does not support them yet. -Xathros
MikeD Posted March 20, 2014 Posted March 20, 2014 Xathros, I was going to drill and install it today but will wait a day to see if it sends an update. This program should fire true if in fact it does not send activity, correct? If Control '2845 - Door Sensor' is switched On And Control '2845 - Door Sensor' is not switched Off Then Wait 25 hours Resource 'DoorSensorNotResponding' Else - No Actions - (To add one, press 'Action') It is currently in the 'On' state so I am hopeful that it will send another 'On' Command as a confirmation within the next 24 hours. ~Mike
Xathros Posted March 20, 2014 Posted March 20, 2014 Mike- I think this would be better: If Control '2845 - Door Sensor' is switched On Or Control '2845 - Door Sensor' is switched Off Then Wait 25 hours Resource 'DoorSensorNotResponding' Else - No Actions - (To add one, press 'Action') This way and action from the sensor will re-trigger the 25 hour wait open or close. If you have a startup program, you would also want to add a runThen of this program to your startup to start the countdown after a system startup otherwise you could miss a failure of the sensor. -Xathros
MikeD Posted March 20, 2014 Posted March 20, 2014 Oh, good catch! I do want to always make sure it displays Running 'Then' in the Summary tab. Thank you, ~Mike
shannong Posted March 20, 2014 Posted March 20, 2014 You'll need to wait somewhere between 24 and 48 hours for this to render a decision.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.