LeeG

Sounds like the battery may be low with it being On all the time. This could also simply the result of the motion sensor being configured for On Only (no Off commands sent). Suggest a new battery and be sure it is near a Dual Band device. If there are tstat adaptors installed are any of them 2.1? They are known to cause RF issues. Double check the Insteon address and be sure to select the Motion Sensor from the Device Type pulldown. If it still does not work run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Run New INSTEON Device entering Address, Name and Device Type as motion sensor. Put the motion sensor into linking mode before clicking Ok on New INSTEON Device. Post the event trace. That will show why the device will not add.

The relay and the button LED respond as one. The button LED and relay operation cannot be separated. There is no problem with the relay operating even though there is no load connected to the Red load wire. The buzz is not related to not having a load attached. Once the cover plate is on the buzz does not seem to be audible when not standing alongside the switch. Both KeypadLinc button .1 should be Controllers of the Scene to keep the button LEDs in sync. It sounds like that is the way you have the Scene defined.

Try deleting the Scene again. If that is not successful run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Delete the Scene with the event viewer running and post the event log. That will show the device address that is causing the problem and perhaps how to resolve it. What ISY firmware is running?

The Help | About confirms running the correct Admin Console. The variable file error might be fixed by going to Programs | Variables tab (under Admin Console) and add an Integer and State Variable. That should create the variables file Ajax is looking for. What level of ISY firmware was being used before updating to 3.1.17? nstein should be able to help with the other Ajax questions.

Under the Admin Console check Help | About. Does the Firmware line and the UI just below it both show 3.1.17?

IM Great catch! Thanks. That is what I did wrong back on the 24th. I coded a different test Program for todays test which of course does have the Repeat and Wait. Explains why I see 120 seconds today. Really appreciate that find. I would have spent hours tonight trying to recreate a mistake. Lee

It was run on the test bed. I now have two ISYs, one that manages the house and the other that runs the test bed. Although I have very little unexpected Insteon traffic from the house devices I found it easier to manage the test bed devices when they are on an ISY by themselves. Power cycle of ISY made no difference. The Event trace is showing a clean 2 second cycle between Beeps. Thought it might have something to do with the If statement reevaluation but I deleted all If conditions with the same 2 second result. I’m right clicking on the Program and running the Then. Very strange. Just need to think about what I have done in the last 3 days. Now that is a challenge.

These results are fascinating. I saved the Event log file from the 24th when I ran the test here which ran in exactly 60 seconds. Went back to the event file to confirm I had not miss calculated the time between the first and last beep, 60 seconds. Today it takes 120 seconds +/-. Will try rebooting the ISY and power cycling the PLM to see if that makes any difference.

Don't know if the Program holds on the Beep until the ACK is received or the next Beep is held until the ACK for the previous Beep is received. Either approach works. Probably others that don't immediately come to mind. The HouseLinc trace has a specific entry for waiting between events to throttle PLM commands.

The PLM can be over driven by the application so all applications (including the ISY) have a delay built in to insure the PLM is not driven faster than it can handle commands. Other Insteon activity during the 60 second once per second beep loop could slow the loop.

Looking at the pictures of the probe it shows a three pin plug. The sales page spec says the I/O Linc jack has GND and Sense which seemed odd compared to the pictures. Opened one of my I/O Lincs and found the jack is a three pin jack with GND, Sense, +5V. Looking forward to what you find Brian. I also offer my thanks for going the extra mile on this one.

Does sound that way and the probe should protect itself from inadvertent polarity error. Although this is very interesting from the technical side, adding more data points to what the I/O Linc Sense needs to turn On, I'm afraid it is not getting any closer to a solution. For whatever reason the probe does not pull the Sense voltage to GND. The last series of measurements of S relative to GND show the probe cannot turn the I/O Linc Sensor On. I think either of the two alternatives, the ELK board or an external AC relay, will provide what you are looking for. Brian has used the ELK board so that is a tried and working solution.

There is a polarity to the input side of the probe. Not applicable where AC is input such as the door bell but would make a difference when the input to the probe is DC.

Change to a low DC scale when measuring the Sense input. That is a 5v DC digital circuit. Not AC.

Thanks Brian for asking that question. I thought the reading was with the probe in the jack. The Sense line on the I/O Linc is not an analog input that is measuring an independent voltage. The Sense input is connected to the I/O Linc 5V source through an internal pullup resister. This keeps a positive potential on the Sense line and keeps the Sensor Off. The expectation is I/O Linc GND will be applied to Sense to turn the Sensor On. For the Sensor not to be turning On the Sense line must not be at or near I/O Linc GND potential.

The ISY User Guide (page 60) indicates MEM and ERR LEDs blinking indicates the ISY is not able connect to the Ethernet network. Suggests checking cable between the ISY and the Router/Modem along with rebooting Router/Switch. In addition was a static IP address defined to the ISY and perhaps that IP address is no longer valid.

Along the lines of anything is possible it could but I really don't think so and it would not allow you to return the probe. It presents like a bad voltage level rather than a bad contact.

The I/O Linc is expecting Sense to be connected to GND through a dry contact switch to turn the Sense On. Open to turn Sense Off. The specs do not indicate how much if any tolerance there is in either state.

It is not necessary to actually do a un-link but it is preferred to use the default "erase existing links" when adding a device. That way there is no possibility of picking up a bad link. There are a few exceptions for special devices but that is spelled out in the UDI Wiki for those devices. Use an ISY Scene to link the two devices. The Motion Sensor –Sensor node would be a Controller and the SwitchLinc would be a responder. Welcome to the fun world of ISY. Hope you have as much fun as I do.

ELK has a good reputation for quality equipment. I don't have one so no direct experience. Perhaps those who use ELK and have used that particular board can provide some firsthand knowledge.

An alternative would be to connect a small 18-24V AC Relay (whatever the transformer secondary is rated at) to the same points the probe is now. Connect the new relay Com and N/O contacts to the I/O Linc GND and Sensor screw points. That will turn the I/O Linc Sensor On for as long the door bell button is pressed. That will not be long but should be long enough for the I/O Linc Sensor to send an On command to the ISY which could trigger an ISY Program. I've challenged and cross-checked the probe connections every way I know how. It should be working based on all we know at this point. Would have to take a probe apart and see what makes it tick to go any further down that path.

That is a good wiring diagram. For some reason the probe is not bringing the Sensor line down to I/O Linc GND. The jack the probe plugs into carries the I/O Linc GND and Sensor connections. The expectation is GND will be applied to the Sensor. For some reason the probe is not bringing the Sensor line down to GND. The Green LED can actually turn On (not full bright) but not trigger the Sensor to On state. Smarthome use to sell a water leak detector I/O Linc combination that never worked well because the water detector could not bring the Sensor line down to GND. The Green LED would be on which mislead many folks. It was not apparent the LED was not full On meaning the Sensor line was not down to GND.

The Restore Modem worked if the ISY is reacting to device traffic. Click on My Lighting at the top of the tree which displays all the device nodes in the right pane. Look at the Current State column. I suspect the column is blank for all the devices. If so the ISY has been unable to push device state data to the Admin Console. This can happen from time to time. It is good practice to check the Current State column whenever the Admin Console is started. Normally exiting the Admin Console and starting it again will bring it up with the Current State column populated with current device status, If Current State never shows device status something with the router/AV is stopping the ISY from pushing state change information to the Admin Console. Something to check is Help | About. It should show a Firmware line and immediately below that should be a UI line. Both lines should show 3.1.17 assuming the ISY is running the latest Official release. If on 3.1.17 but both lines are not there or they do not show 3.1.17 clear the Java cache and check the URL being used to invoke the Admin Console.

My I/O Lincs do not toggle the Sensor (Green LED) when the Set button is pressed. The I/O Linc Relay does toggle On/Off (White LED) with the Set button. It sounds like the I/O Linc Relay is operating in Momentary mode. If the Set button turns the Relay On the momentary mode will turn if Off.

The 0 volt reading does not mean the probe is on the correct secondary connection. So long as there is sustained voltage on the probe (equal to the transformer secondary voltage) while the button is pressed and held I think the probe is wired as it should be.