Teken

If your physical speaking location is fixed a simple method to try is cut a small piece of paper and wrap just the back side of the case. It will look like a collar on the unit and will focus the sound to the multi point far field microphones. This simple trick will negate the direct / reflection of reverberation from impacting the system.

Please try to add in another Insteon device and report back success / failure in that task.

Well, since the I/O Linc is only a single band device and you plugged it into the same outlet as the 2413S PLM not sure why its having such a hard time finding it. For the sake of asking please ensure 2413S PLM is plugged into dedicated outlet void of any other electronics. Have you tried to add the device using both methods one being the *whirling 2 colored arrows* and pressing the set button? Along with entering the Insteon ID using the *New Insteon* using both methods of auto vs manually selecting the hardware. Last but not least try to follow the full users manual and hard reset the I/O Linc and try again. Failing to complete any of the above at all your only recourse is to submit a service request with UDI here: http://www.universal-devices.com/contact-support/ Please reference this thread so they can document this issue has been resolved . . .

How many devices do you have in your Insteon network does it exceed 100?

Can you please reboot the controller and try again . . .

That would be highly unlikely - can you please reboot the controller and try again. If you could also try both methods to add the I/O linc and provide the level 3 error logs for both attempts that would be great. Please plug the I/O Linc in the (same) outlet as the PLM and report back success / failure.

1. What controller are you using 99 vs 994? 2. What firmware and UI is indicated in the Help - About? 3. Have you tried to plug the I/O Linc next to the 2413S PLM?

Was the device in fact purchased as refurbished and does it have a ® at the end of the product number? Have you taken the unit and plugged it in next to the 2413S PLM to see it makes a difference?

First, what a beautiful bar you have down stairs - must be really tough on you when your sent to the basement by the wife! LOL . . . To be clear when you left the leak sensor on the top of the counter after the customary 24 - 26 hour wait the system didn't update correctly? If so given the pictures offered here I would submit a RMA and have the item crossed docked. Meaning Smarthome will charge your CC first while you ship back the defective product. Meanwhile they will ship out a replacement immediately instead of waiting for the returned product. If time isn't an issue than just submit the RMA and ship it back to them and sit back and wait for the warranty replacement unit.

What is the bar made of and is there any metal surrounding the sensor? Can you offer any pictures of the actual placement?

Your device was produced on the 47th week of 2014 and is revision 2.3 of the hardware. When looking at the ISY Admin Console for the device it will list the firmware for the leak sensor and recall you said it was v.43. Lets try a few simple things and reply back what you observe, OK? 1. Take one of the bad sensors while viewing the admin console place it in a dish of water. Does it change state for both wet and dry? Yes / No? If it changes state I want you to carefully look at the green LED on the top of the unit. Is it blinking every XX seconds or is kind of fluttering / flickering? 2. Taking the unit out of water dry the unit and press the set button. Does the status change in the admin console at this point? Yes / No? 3. I am going to assume your office is no where near the final placement is, correct? If so I want you to do the same two tests listed above (at the final location) and go back to the admin console and report back if the signal is received and reflected in the admin console. If it is this generally means RF is fine - if it doesn't you need to add in another plug in dual band device near the leak sensor.

This has been a long time feature support issue that UDI must provide. I would suggest you submit a service request to ask this basic feature be offered. The Trigger Linc / Open-Close sensor has been hobbled like this for more than a year. Not sure why its taking so long to include this feature. Perhaps Smartlabs is still dragging their feet in providing the API?

For the benefit of others could you please indicate the production date, revision, and ISY firmware for this unit. This information will help others in the future and provide context when they compare their hardware / behavior. Let us know if the 26 hour heart beat test pasts . . .

Well, it looks like your in good shape now - Rock On . . .

Smartlabs changed the behavior in the latest firmware where the end user *must* press the set button to make the unit send out the dry on command. There is a use case (like / dislike) for this new behavior vs the old . . . I personally don't mind either so long as you know how the sensor is going to react and what the person needs to do in the future moving forward.

Now, if you watch the Admin Console do those two problem leak sensors (variables) change state as expected?

In that case you will need to place the device in a dish of water. Once it trips you should see it reflected in the Admin Console for wet on, when you wipe it dry and press the set button it should go back to dry on. Please confirm that behavior is seen . . .

Hello Dean, Before you go through the whole ordeal of hard resetting the one sensor. Please bring it next to a Insteon dual band device and perform step 2. If the Admin Console does not reflect the correct state you can hard reset the unit per the full users manual. As a reminder once you hard reset the leak sensor you need to do a restore device so all the links are associated to the program(s) you have at hand. Should the above steps not resolve the issue - I would press forward and initiate a RMA via cross dock with Smarthome. They are very good about in warranty returns so keep us all updated to the outcome.

Hello Dean, Lets keep this simple and do the following when your able to do so. 1. Reboot the controller and validate they return to a status 1. If it does your code is solid - if not you need to review. 2. Manually change the value from 2 to 1. Press the set button on one sensor and toggle it from wet to dry. The system should reflect the two states. The device will also send a heart beat to the controller. Verify that all of the above come in as expected if not you have a communication issue, device needs to be hard reset, removed, added, or defective product.

@Larry, With out more information from the OP as to how he intends to use the *Heart Beat* in his specific application. I would have gathered its intent would be to keep him aware the device was *Alive / In Range*. As all other Insteon devices already provide immediate feedback whether it be leak, motion, open / closed. For me if this was not a Insteon product but some kind of 3rd party product that you wanted to monitor for what ever reason the over all scope needs to be defined.

I had assumed you were talking about a Insteon product, no? [emoji848] If this is for some 3rd party device than yes a fixed heart beat would be the preferred method. Makes audit / tracking predictable for long term trouble shooting. ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

Not really sure what your after but no two devices send their heartbeat at the same time interval. So don't know what you mean by fixed vs variable?!? [emoji848][emoji53] ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

Login to the Admin Console: Programs -> Summary -> Variable Control 2 for those leak sensors. What is the last run / last finish time recorded in the summary log? If the logs show they haven't changed for example 2-3 days or what ever. It could mean the sensor is too far from a RF to power line device or the battery is low. Even though the batteries have been spec'd for 10 years of service Smartlabs has indicated a few batches released in the wild came with less than fresh batteries. 1. Measure battery voltage for both units ensuring they are with in specs. 2. Verify your Insteon RF to Powerline mesh is adequate in those areas.

Answers in line . . .

Answers in line . . .