shunsader

"The only way to get rid of bad links in ISY is to delete the devices that have bad links." How would one be able to determine if there are bad links on a device. I have a PILE of devices in my home. - Steve

"why are you needing to rebuild after a power outage? I literally do nothing after a power outage. And what specifically do you mean by "rebuild"?" I did a "Restore PLM"....my version of rebuild, since Michel mentioned that doing so removes duplicate links. I made the assumption that to get from 981 links to 330 something, that perhaps the PLM is writing a new table when there's a power outage, which would result in duplicate links. It's pretty clear from the above comments that I've got some work to do to get a real link count. What I DO KNOW is that once I rebuilt the PLM the first time (a couple of weeks ago), my addition of leak and motion sensors all report back. Another topic: My home is not complete yet, due to break ground on a large addition next year. If I'm having link limits, what would you suggest that I do to 'finish' my home installation? Should I be considering a second device? I had no idea that I could be running a second device until Michel mentioned it last month. I bought a backup ISY and needed to test some switches. It's possible to structure the build so that one device handles mission critical leak and motion sensors while the main ISY runs the lighting and comfort aspects. - Steve

Thanks for the feedback. Out of town for a week. I'll try the factory reset first on the new device. Hoping that'll solve the issue. I DO have a Pro unit, and initially had 981 links. After Michel suggested I rebuild, I now have 330 something. What worries me is that I had a power outage a few days later (go figure), and needed to rebuild again. The number was quite different than that value...like 190, which doesn't seem like enough for the 106 switches, 21 dimmers, 20 motion sensors, and handful of water sensors. - Steve

Forum Wizards, I've been running a large home installation for years, and have NEVER come across anything even remotely as bizarre as this: I've installed NEW 8 button keypad. I've added the device, to my ISY 994, and have not even had the chance to do any linking. It was DESIGNED to turn on/off a motion sensor in a room by switching power. Never got that far. I noticed in the morning that Button 1 (power button) was turned off. When I turned it on, I noticed the guest bathroom light was on, but only one of 2 circuits/switches necessary to turn on the bathroom completely (another story). When I turn off the bathroom switch, the new keypad button 1 also turns off. It's as if they've been linked right out of the box. ZERO controls/programs have been added to this NEW, out of new BOX device. This is Event Viewer, Level 3 when I turn ON the keypad, address 53.B2.24: Tue 05/31/2022 03:05:00 PM : [INST-SRX ] 02 50 53.B2.24 00.00.01 C7 11 00 LTONRR (00) Tue 05/31/2022 03:05:00 PM : [Std-Group ] 53.B2.24-->Group=1, Max Hops=3, Hops Left=1 Tue 05/31/2022 03:05:00 PM : [D2D EVENT ] Event [53 B2 24 1] [DON] [0] uom=0 prec=-1 Tue 05/31/2022 03:05:00 PM : [ 53 B2 24 1] DON 0 Tue 05/31/2022 03:05:00 PM : [INST-SRX ] 02 50 53.B2.24 21.20.9C 41 11 01 LTONRR (01) Tue 05/31/2022 03:05:00 PM : [Std-Cleanup ] 53.B2.24-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 05/31/2022 03:05:00 PM : [INST-DUP ] Previous message ignored. Tue 05/31/2022 03:05:00 PM : [INST-SRX ] 02 50 53.B2.24 21.20.9C 42 11 01 LTONRR (01) Tue 05/31/2022 03:05:00 PM : [Std-Cleanup ] 53.B2.24-->ISY/PLM Group=1, Max Hops=2, Hops Left=0 Tue 05/31/2022 03:05:00 PM : [INST-DUP ] Previous message ignored. Tue 05/31/2022 03:05:00 PM : [INST-SRX ] 02 50 53.B2.24 11.01.01 C7 06 00 (00) Tue 05/31/2022 03:05:00 PM : [Std-Group ] 53.B2.24-->11.01.01, Max Hops=3, Hops Left=1 Tue 05/31/2022 03:05:00 PM : [INST-INFO ] Previous message ignored. This is Event Viewer, Level 3 when I turn OFF the bathroom light switch (the one that behaves as if it's linked), address 51.3F.38: Tue 05/31/2022 03:06:06 PM : [INST-SRX ] 02 50 51.3F.38 00.00.01 CB 13 00 LTOFFRR(00) Tue 05/31/2022 03:06:06 PM : [Std-Group ] 51.3F.38-->Group=1, Max Hops=3, Hops Left=2 Tue 05/31/2022 03:06:06 PM : [D2D EVENT ] Event [51 3F 38 1] [DOF] [0] uom=0 prec=-1 Tue 05/31/2022 03:06:06 PM : [ 51 3F 38 1] DOF 0 Tue 05/31/2022 03:06:06 PM : [D2D-CMP 00CE] CTL [51 3F 38 1] [DOF] op=is --> true Tue 05/31/2022 03:06:07 PM : [ Time] 15:06:13 4(0) Tue 05/31/2022 03:06:07 PM : [INST-SRX ] 02 50 51.3F.38 13.01.01 CB 06 00 (00) Tue 05/31/2022 03:06:07 PM : [Std-Group ] 51.3F.38-->13.01.01, Max Hops=3, Hops Left=2 Tue 05/31/2022 03:06:07 PM : [INST-INFO ] Previous message ignored. Tue 05/31/2022 03:06:07 PM : [INST-TX-I1 ] 02 62 00 00 16 CF 13 00 Tue 05/31/2022 03:06:07 PM : [INST-ACK ] 02 62 00.00.16 CF 13 00 06 LTOFFRR(00) I need to read up on command structure, but see no reference to either device in the above events. I looked at link tables, and don't see any cross reference either. It should be noted that I've had recent problems with too many links in my PLM, and needed to rebuild more than once so that I could get my LEAK SENSORS TO REPORT (may have seen my post...yes, too many links kept them from posting data). I'm usually pretty good at solving 'typical' problems, but this one feels like a ghost....how in the world could a device right out of the box start turning on a single device, which is already part of another scene??? - Steve

@Geddy, I've opened a ticket per your advice, and following that, realized that since I have a 2nd ISY, I should put it to use. Here's my follow up post to the ticket: I have installed a 2nd ISY994 PRO with another PLM, and installed one of the motion sensors I was having trouble with on the 'production' ISY. It installs and works as expected. I can touch the set button and get On and Off commands broadcasting across the Event Viewer (Level 3), without issue. Because of this, I expect that the problems are associated with my production ISY. I DID run a PLM Link report, and is just shy of 1000.... 991 links. There is 1728 Mb of free memory (System Status). Summary of issue: Production ISY can register devices, (as shown in menu, can talk to them, change settings), but when a sensor is triggered, NOTHING comes across the Event Log (Level 3). This started when working with a Leak Sensor....able to get Wet/Dry, but no Heartbeat. Adding additional Leak Sensors...NOTHING across Event Log when pressing Set, or getting wet, although I can see the LED flash when it should be sending data. - Steve

I've recently been having problems adding sensors (4 leak, and today, a motion sensor) that can be added to the ISY, but when testing to see if a signal is generated when triggering (looking at the Error Log, level 3), nothing happens, for the last 4 devices added. I decided to see if perhaps maximum memory, programs, etc. were the limitation, so as mentioned, tried generating a topology, and when doing so, immediately got HUNDREDS of errors like this "[FileOpen ] Open failed for [/CONF/410.PRP] (r)". Attached is the Logfile during this process, with intermittent motion sensor commands (women baking in kitchen). Additional Info: I installed a Z-Wave module somewhere around the time that I was adding these new devices, but do NOT have Z-Wave hardware installed. UNLIKELY that this could be the culprit, but trying hard to isolate the issues...thus, removed module and rebooted, with no new news. 1. Any chance these 2 issues are related? Why can device be added (written to) without any issue, but when it comes time for the sensor to fire/trigger, NOTHING crosses the event log? 2. I've read in another thread that it might be a memory card issue. Why would the memory card only have issues with new devices, then fail when trying to read everything else...when trying to generate a topology report? I'm at a loss as to where to go from here. FEELS like some type of limitation issue, but need help evaluating by the experts. See attached for the LogFile. - Steve GeneratingTopologyReportERRORS.txt

Thanks for the video link. I suspect that today's firmware might present just a bit different. Units 2 and 3 NEVER transmit anything, even though they register on the ISY just fine. The first does NOT show an On/Off until I've taken the unit out of discovery mode, and then push the set button. I've NEVER seen the same input do an ON/OFF toggle. Is it possible that all 3 units, from 3 different sources, could all have some issue? It's hard to believe. May sound stupid, but all I need is these to be around a dual BAND device, right? all my motion sensors work, scattered around the home. OR, am I supposed to have some type of receiver I haven't read about yet?

I now have 3 sensors installed. ONLY the first sends any data when I push the SET button, and I can clearly see DON 1 in the event viewer. NOTHING is transmitted with the other 2 units. When dipping in water, first sensor SENDS DON 2 command, software picks it up, and sends an email. The other 2 do NOT send any data, but I CAN see the LED flicker the moment it hits the water, and again each 15 seconds, like the first sensor. It's as if I haven't enabled something on the device to transmit. Even though these are new devices, I'm doing a factory reset before adding them to the ISY. Procedure: Remove battery, wait 5 seconds, add battery WHILE holding reset button on until the LED has gone on, then off again, release set button...should be Factory at this point. The event log CLEARLY shows when adding to ISY that the part is being written to. WHY is nothing being transmitted by the 2 new devices? I'm looking at Event Viewer, which should see all traffic. FYI, I have a motion sensor less than 10 feet away, and it triggers 100% of the time, as it should. (trying to identify whether it's an RF thing...NOT). It's as if all 3 are working, but only the first one sends WET and DRY signals when necessary. Still NO heartbeat since I initiated it more than 10 days ago. NONE of these devices have been added to any scenes, but that shouldn't have anything to do with me not seeing any transmission traffic when something on a device is triggered. I'm at a loss. Any other ideas? - Steve

Guys....FACTORY batteries. I've simply pulled the plastic tab, and expected it to work. Incidentally, factory batteries are labeled "Huiderui Lithium", but are only measured at 1.764V....not sure how one gets to that number if it's really a lithium battery. Duracell Alkalines beep out to 1.611V. I found a Lithium-ion Sulfur battery white paper written in 2015 that talks about a lithium chemistry that boasts 1.7V. Perhaps that's it. FYI, changed both sensors to alkaline batteries...same results....DRY when pressing SET on one sensor, and nothing on the other. I'll do a wet test after this writing to see if they trigger as they should. Thanks.

Larry, I DID, I waited a whole week, not a single email, nothing on the counter, and programs are still red, indicating they've never been run....except for the DRY, on ONE UNIT. AND, even when I push the SET button, I get nothing from one of the units. I DO get a green light when I press set, and instructions were written from ISY just fine.

Mr Bill, I'm hoping that the post above was intended for me. I'm pretty code savvy, and was only trying to get some feedback on what I might be doing wrong in regards to installation.... First sensor: ONLY get DRY trigger when pressing SET button. Second sensor installed: NO HEARTBEAT, NO WET, NO DRY triggers when pushing the SET button. I currently have 20 motion sensors installed at home, and initially spent a considerable time understanding its functions before installing at the home. Wanting to do the same for the Leak Sensor, but having mixed results when trying to test signals. Just looking for a way to CONFIRM that all 3 outputs of the sensors work (DRY, WET, HEARTBEAT), and data comes back uniformly (I've read that when pressing SET, all 3 outputs should be triggered, but can't even make that work). Yes, I agree that I'd get a barrage of email messages, but that's what I was counting on. I configured the sensor a day before a 1 week trip, and didn't get anything for the whole week I was gone....no heartbeat at all. In addition, I wanted to understand how the alarm system worked, and whether it alerts just once, or repeated times. ANSWER: 9 or 10 alarms when the Wet sensor is triggered, approx. 15 seconds apart. After that, it goes silent. I'm just a geeky engineer who wants to thoroughly understand how a product works before installing a large deployment. Can any of you think of a reason why pressing the SET button gives mixed results OR why I haven't seen a single heartbeat from either unit? - Steve

I'm also having issues with Leak Sensors. Now that Insteon product has hit a dead end, I've stockpiled all sorts of sensors and product. What's different about this product though is that much of it has probably been sitting on shelves for quite some time. Batteries might be suspect, and older versions may be dusted off and sold to those who still want to use Insteon product. Yes, I've read the "Leak Sensor and Heartbeat Messaging", and although this software probably works great once one confirms that everything works, it's not very good at seeing and testing the signaling that's supposed to be happening. Thus, Instead of going that route, I created 3 simple programs, each triggered by an On OR Off for each of the 3 'outputs'. I DID NOT create State Variables since I'm not doing any triggering off of those variables. Instead, I'm just using Integer variables to keep track of how many times a trigger has occurred. Installation should be as simple as any other RF sensor, holding the set button until if flashes, and then adding the device with the Address and providing a name. I always turn on the Event Viewer on Level 3 to ensure communication flows regularly. The typical test for each of these signals is shown here: For this 'test', I'm just looking for anything that happens with the heartbeat. From this thread: It was mentioned that I should be able to get things to trigger by pressing the SET button. But when doing so, ONLY the DRY sensor program triggers. When I look and read the data coming through on the Event Viewer, I only see the DRY being sent across the line. Thinking something might be wrong with that sensor, I installed a second...and this one does NOTHING, when pressing the button, even though the light flashes when I press the SET. I DID change batteries between the 2, thinking it might be a battery issue. Still, NOTHING from the Newer one, and ONLY a DRY trigger when using the first, regardless of which battery is used. Unsure of what to try next. It's probably something stupid, which is typically the issue for me. I HAVE also upgraded firmware to V5.3.4, and do not have any Z-Wave hardware installed. It's an old, but reliable box....but now have 3 spares in case something should fail. Has anyone interrogated the device like this before assuming that all signals are firing the way they should be? Steve

Looking everywhere for a link to any of the versions of Firmware. I've secured a number of back up units now while working on finding enough insteon products for the next 15 years. Having great difficulty figuring out what's the latest firmware needed for each unit. Here's what I'm planning to do... 1) If the unit has Z-Wave 300 series, it needs 4.9.0. I FOUND that version and installed on first unit, which has external LED, making it a 300 Series Z-Wave supported system. 2) If unit has Z-Wave 500 series, it needs to have 5.3.4. It currently has 5.0.16C, and would really like a back up copy of that firmware in case something goes wrong, but can't find a link to that firmware either. Why is a table of all the firmware version SO ELUSIVE??? Really....I'm a pretty talented and intelligent guy, but working with this stuff gets my blood boiling.

TJKintz, I agree with Mr Bill. Now that I've been doing this for about 3 months, things are stable. When I upgraded my ISY firmware, a whole heap of configuration options were now available to me, including telling the motion sensor to ONLY provide an ON/OFF during the Night. If you really want to get picky, you could change the threshold light intensity to trigger a bit earlier or later. AND, since I CONTINUE TO get an email every 5 minutes during sunset/rise to see light intensity, I think you'll find that you won't need to change that default level. Currently, I have 2 different methods of manipulating lighting... 1. INSIDE, where I have the sensor be part of a scene, tell the sensor to broadcast ON and OFF signals. I set the timeout to the minimum number of minutes that I'd like to leave the light on. For bathrooms, I make this number longer so that the light doesn't go off during a 'standard' shower. (10 minutes). 2. OUTSIDE, I make the sensor part of a SEPARATE SCENE, and tell it to turn ON ONLY, and only during the night. I set the timeout to 10 seconds, and decide myself when to turn off the lights. I have "Main Loop" that checks counters each minute to determine whether a light needs to be turned off or not. When a motion trigger (or a light switch) is turned on, I set a variable with the number of minutes I'd like the light to stay on. I also set another variable (Binary) that the light is on. (you can use a single variable for the time and whether on, but sometimes it'll miss a command, and the light will stay on all day. ONLY when I turn the light off, do I set the bLightON = 0. Why such a short timeout? Because once the motion sensor times out, if someone is still in the area, it'll trigger again. Each time I get a Motion ON command, I re-initialize the timer to the default, which is 3 minutes. I find that most of the time, I'm walking around the building, and may not come back. Thus, 3 minutes being ON is good, AND, if I come back through that area after 10 seconds, I get another 3 minutes of time. The ONLY time this method doesn't work well is if I'm standing around for awhile talking to someone. BUT, and easy fix to this is to create a quick variable called FREEZE. If Freeze = 1, then DO NOT count down the timer. AND, since I have a lot of echo devices around my home, if I'm chatting with someone, I simply say "Echo, Turn FREEZE ON", which not only sets the variable to 1, but also turns on a keypad button on a number of keypads throughout the house. By the way, when initially testing these ( I currently have 10 motion sensors, and have another 10 ready for deployment, but too busy at the moment), I tried to control everything programmatically. DELAY was the largest problem. I could be 1/2 way into a room before the lights would go on, the same outside in the darkness. The solution was to add the sensor to a scene, and tweak how one would like to get the light to turn off. INSIDE, turning off the light with a program was problematic. Outside, much easier if I control when to turn off. The COOL part of this project was that I used some of my coding to send me an email EACH TIME the light is turned off, how long the light was on, and a running total of how long that light's been on. I was VERY surprised to find how long our kitchen light was on each week. I would have thought it was about 1/4 of the time it was on. Hope this helps. Steve

I've already found the answer....Here's the new list of things to be done to ensure that there aren't duplicates.... 1. I delete the old spoken at My.ISY.IO, and create a new spoken with the same "Spoken"....for instance "Exit Front" now uses a different program than what it used to. 2. In the Alexa PHONE app, Choose "Devices", then "Scenes", find the scenes that you're replacing, choose it, then delete (trash can at top) 3. I then ask Alexa to "Re-discover my devices", and after a minute or so, it'll tell me that no new devices have been discovered (because it probably references the spoken words, and not a program number. Now Alexa finds new devices that are unique...problem solved.