Jump to content

IndyMike

Members
 View Profile  See their activity

  • Posts

    1581

  • Joined

  • Last visited

 Content Type 

Everything posted by IndyMike

  1. IndyMike
    @CoolToys, Have a look at your motion sensor for the guest area. It can disable/interrupt your bedtime program if it fires at the wrong time. I just recently replaced batteries on two MS I sensors that were behaving badly (no low battery set). Aside from that, when programs fire without a trigger or re-enable themselves I start thinking about SDcards and the like. A program should Never spontaneously enable itself (you can enable a program with another program). I have no experience with the Eisy, so I will bow to others who do.
  2. IndyMike
    @gempro, not sure if you have been able to resolve your issues. Your event log did show an interesting detail that was not part of the scene test. After the test completed, the ISY attempted to write an update to your 46.2F.CA device (RemoteKP.F). This update failed with a Nack response from the KPL. The Nack indicates that your new PLM is not currently linked to this device. It looks like with update may have been automatically triggered after you performed the scene test. In a system that is having communication issues, that can complicate things. Try turning OFF the automatic writes (screen capture below) and restoring this device. If the restore completes successfully, perform a link table read/compare to double check. Continue in this manner with your other devices. If the restore does not work, come on back and we can develop a plan B. <html><font color="red">----- Keypad LED F Test Results -----</font></html> <html><font color="red">[Failed]</font> KeypadF (44 7D D7 6)</html> <html><font color="red">[Failed]</font> RemoteKP.F (46 2F CA 6)</html> <html><font color="red">----- Keypad LED F Test Results -----</font></html> Wed 10/23/2024 07:18:32 PM : [INST-TX-I1 ] 02 62 00 00 12 CF 13 00 Wed 10/23/2024 07:18:32 PM : [INST-ACK ] 02 62 00.00.12 CF 13 00 06 LTOFFRR(00) Wed 10/23/2024 07:18:32 PM : [Ext MH ] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Wed 10/23/2024 07:18:32 PM : [46 2F CA 1 ] Link 27 : 0F20 [A22A711973FF1F01] *Failed Writing [A22A711973FF1F01] Wed 10/23/2024 07:18:32 PM : [All ] Writing 8 bytes to devices Wed 10/23/2024 07:18:32 PM : [INST-SRX ] 02 50 46.2F.CA 71.19.73 AB 2F FF (FF) Wed 10/23/2024 07:18:32 PM : [Std-Direct Nack] 46.2F.CA-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 10/23/2024 07:18:32 PM : [D2D EVENT ] Event [46 2F CA 1] [ERR] [1] uom=0 prec=-1 Wed 10/23/2024 07:18:32 PM : [ 46 2F CA 1] ERR 1
  3. IndyMike
    @CoolToys, the program you posted above has the variable $sOccupied_Guest_Edit is 0 as a qualifier. I'm not sure where this is controlled, but if it is altered it could cause your program to exit prior to completion. The waits in your program will allow this. Some lights could be left in the incorrect state, and the variable $sBedtime = 1 might not be set.
  4. IndyMike
    @CoolToys, as others have indicated, a program that uses ONLY the condition "Time is XXXX" will show true until it triggers false. Unfortunately, it will Never trigger false. As a result, you can't use the program status as an IF condition in another program (it will always be true). As a workaround, you could use the "From XX to XX" clause that would evaluate to a false after the time period. The following program will evaluate to false 1 minute after sunset. This becomes difficult if you have embedded "waits" within your program (which you do). You wind up with a race condition between the program and the If statement. It's far better to separate the Trigger (if statement) and program (then clause) into two separate programs so the IF statement won't terminate your running program. Outside Sunset - [ID 0015][Parent 0002] Outside Sunset - [ID 0015][Parent 0002] If From Sunset For 1 minute Then Set 'Outdoor / SC Outside Sunset' On Else - No Actions - (To add one, press 'Action') I'm not sure that's the answer to you issues as nothing that you've posted above would results in your variables both being true ("sEarly_Morning" and "sNight") Please do review your code for any programs that use a program "true" status as a condition.
  5. IndyMike
    @SimonK, thanks for taking the time to post back the results of your ticket with UD. It sounds like this problem may have been frustrating users for some time. Curious whether it applies to the Polisy and possibly the ISY994. In the meantime, celebrate by spinning up some Queen "another bug bites the dust"
  6. IndyMike
    @Guy Lavoie, thanks for the clarification. Looks like I added 2 + 2 and came up with 22. One question regarding your eisy/Zstick configuration - does it support S2 security? The link that I referenced above (@lilyoyo1) indicated that S2 security was only supported for the Zmatter board. Wasn't sure if that had changed.
  7. IndyMike
    Ouch! When did UD UNSUPPORT the Zooz 700 stick? That's a rather major new item and a big departure from previous statements. Did I mis-understand? https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/
  8. IndyMike
    @ELA, Nice Photo. That's a failure that I have yet to encounter. I am worried that you may have voided your warranty 😉. Like you, I am on the fixed income plan. When Smartlabs closed their doors I began playing with Z-Wave devices. When Insteon restarted. it was their prices that kept me away. For future planning, you may want to visit the Zooz site (Zen51 Dry contact). They have a number of innovative products that make some financial sense. Unfortunately, if you are still using a ISY994, you will need to upgrade to take advantage of the 700/800 series Zwave features. Zooz plusses: Inexpensive relays, dimmers, and embedded (typically 50% less) Select relay and dimmer devices can be used in N-way configurations with standard mechanical switches (additional cost savings). EX - I had a 5 way insteon setup (4 insteon switches) that I replaced with 1 Zen77 and 3 mechanical switches. Very nice rocker feel. As good or better than Insteon. Smooth dimming performance. I replaced some 2477D's I had controlling 2 chandeliers. The 2477D's produced "herky jerky" dimming with the 45W candelabra LED bulbs. The Zen77's were very smooth even with a slow ramp rate. Responsive customer support - reported an issue with what I termed "excessive communication" using a power monitoring plug-in. Customer service responded, we conversed, and 3 months later they informed me of a firmware update that they had developed to address the issue. OTA firmware updates of devices. No issues with all-on (Insteon issue that still plagues some devices). Full disclosure - I really like these guys. I want to make sure they stay afloat.
  9. IndyMike
    I'm thinking that the IF clause is re-evaluating to false after you have run the "Then section" of the program. Your 20 second waits will allow the program to exit. Try separating into two programs (1 program for IF and 1 for Then).
  10. IndyMike
    You are correct that you cannot see KPL secondary button status in Home Assistant by istself. If you create a scene with the secondary button as member, Home Assistant will create a "Switch" using the scene name. You can track the KPL button status and control it (On/Off) through the scene name. As an example, I had an unused button C on one of my KPL's (BSMT KPL Game - C). I created a scene (SC BSMT KPL Game - C) with the KPL button as the only member. Re-loaded the ISY integration on Home Assistant, and the Scene (SC BSMT KPL Game - C) shows up as a Switch. It is both observable and controllable.
  11. IndyMike
    @larryllix, I was unaware (or forgot) about the psudodevice using the Alexa interface. It appears that similar triggers can be accomplished by publishing variables through the portal. Not my cup of tea. I understand that this is my issue. I started with the ISY26 in the way back because it was a local solution to home automation. I've managed to stick with that for most of my ISY994 and Home assistant implementation. Not willing to go to the Dark Side (pun intended) of internet automation. As stated earlier, I have a very different view of scene status. I wan to know if ANY device in a scene (bsmt, 1st floor, 2nd floor, outside) is on so I can display it on a keypad and turn All Scene Members off. My thing - but that's what home automation is, right?
  12. IndyMike
    @gschoffstall, I've lost track of what you are trying to accomplish. Are you attempting to fix Insteon problems, X10 problems, or both? It looks like you are trying to track down a signal absorber. You've mentioned a number of plug in devices that you've eliminated. Don't forget about hardwired devices (heat pump, etc) that activate on their own. Something as simple as a failing photocell on a post lamp can wreak havoc on powerline communication. You mentioned that your 4-tap test was inconclusive. What did it show you about your insteon components? Did they all flash either red or green? The information provided by @Brian H is spot on. In addition to the plug in filters, Jeff Volp has developed a XTB-ANR active noise reducer. I have not tried the ANR and can't say for certain that it's compatible with Insteon. In the past, Jeff did develop his products making sure that they were compatible with Insteon. I would recommend contacting him directly if you're interested. Jeff does sell these in pairs so you can place one on each phase near the electrical panel. https://jvde.us/xtb/xtb-anr.pdf
  13. IndyMike
    @EJones01, The device that you linked to is a Zigbee device. Not sure what UD device you are using to talk to it. My experience is with the ISY 994I which will NOT talk to a Zigbee device. If you have a Polisy or Eisy that supports the Zigbee protocol, please post back. There are other forum members than can assist.
  14. IndyMike
    This is precisely the thinking that led to where we are now. We could never agree on what constituted the status of a scene. In trying to please everyone, UD did nothing - and pleased no one. If they had tried something, it would have been a starting point that could have been built upon... I am quite pleased by the scene status that HA currently gives me. If I upgrade my ISY994, I will try the Virtual plugin. I'm quite sure I could find applications for it.
  15. IndyMike
    @Guy Lavoie, nice find and good job realizing the possible applications. This is what happens when a new set of eyes looks at an old problem. Rather than enumerating all the ways the problem can't be solved, the new eyes provide a solution. If I could figure out a way of running this on my ISY994, I'd be all over it. I guess it's one more vote for upgrading to the Eisy...
  16. IndyMike
    I'm thinking that the V.38 device is a powerline only model. It should still function fine if it gets enough signal (I have several older devices still in use). Strange that you have 2 micro dimmers on the same circuit. I would think these would boost the signal to an acceptable level. I hate firing the parts cannon at unresolved problems. Upgrading to a newer micro-dimmer would bring in some newer capabilities (dual band, i2CS, different repeating), but they are expensive. Z-wave brings it's own issues with establishing a good mesh. Impossible to recommend without knowing your installation, ISY model, and how many z-wave devices you have. I personally would not use anything less than a 700 series z-wave device for reliability. Before you swap out this device, please try a few last things: Try changing your communication mode to "device reported" (/link management/advanced options/device reported). This should force the ISY to use I2 communication during link table reads. Perform a link table read and compare to make sure the device is properly programmed. If the compare shows errors, restore the device and perform the link table read/compare again. Power cycle the InlineLinc (may require cycling the breaker) then retry scene communications. This should eliminate any learned AGC settings. Improvements may be temporary. Try a factory reset/restore on your InlineLinc - retry scene communications. There are some settings that can only be eliminated by a factory reset (X10 programming is one). Take a hard look for other devices on this circuit. It sounds like your "extractor fan" is a range hood in a kitchen. Kitchens are loaded with appliances that can absorb Insteon signals (Microwaves, Air fryers, toaster ovens, Kuerig's). See what you can unplug to try increasing signal level. When you are done with the above, you may want to switch your communication mode back to "automatic". Most devices function fine with "device reported". I have one old Icon switch that doesn't like it.
  17. IndyMike
    @EJones01, the method of writing to the device should not cause the problems you are seeing. It's just slow and antiquated. You indicated that your InlineLinc is new. Unfortunately, the address in the event viewer (17.7A.03) and the antiquated link writing style indicates this is an old device. Did you happen to get this off Ebay? I looked at the database (http://www.madreporite.com/insteon/Insteon_device_list.htm) and there were some I1 (non dual band) devices made. Could you post the firmware revision the ISY is showing for this device? Have you checked to see what else is on this circuit?
  18. IndyMike

    Link Confusion

    IndyMike replied to JoelW's topic in eisy

    The links for 33.D7.B7 are showing a mismatch, but they are probably OK. The LSb is being set to 1 for some reason, but probably won't cause any harm. A restore will correct this, but it's likely to return. Device 34.E7.8B is a controller for group 00. It's very likely your PLM. The links for 33.10.4F look valid. Your deck lights are listed as a responder to the 33.10.4F switch. There should be in a scene on the admin console showing 33.10.4F as a controller and your 34.09.80 as a responder.
  19. IndyMike
    It's listed as a "beacon test" in the full device manual (not the quick start guide). Not all that easy to find these days. Here's one for a 2477D - https://cache.insteon.com/documentation/2477D-en.pdf If you perform this on your PLM, it will signal all the devices in your home that are within range. Devices will flash: Green - opposite phase Red - same phase Nothing - out of range or doesn't support function
  20. IndyMike
    @Techman, very interesting. Wasn't aware the ISY994 supported Zwave 700 series dongle's. Which manufacturers are compatible?
  21. IndyMike
    That sounds like a definitive result. Built in microwave replacement definitely NOT recommended. I'm looking for a "what changed" item. Unlikely that your microwave suddenly started absorbing more signal. You mentioned constriction and power outages. Is it possible that one or more of your phase coupling devices got damaged/upset? You may want to try the 4-tap phase test on your PLM to see if things are still coupled. Easier than installing an XPF filter.
  22. IndyMike
    @gschoffstall, a passive X10 coupler is close enough to Insteon frequency that it can be used. A X10 BOOSTER may couple Insteon signals (depends on the model). X10 boosters will NOT boost Insteon signals. Some will actively interfere with Insteon. LampLincs will NOT bridge X10 RF.
  23. IndyMike
    @EJones01, your communication during the link table read looks rather good. Takeaways: When your InLineLinc communicates back to the PLM, it is responding with 2 of 3 hops remaining. That's rather good. When the device hears the PLM, it responds well. During a link table read the PLM requests that the device respond with an acknowledge. The is the [INST-SRX] entry in the event viewer. If none is received, the PLM will re-try the communication to the device up to 5x. This is invisible to the ISY and event viewer. In other words, we can't tell how good the signal level is from the PLM to your device (it will be different than the reverse direction). The PLM may be re-trying commands multiple times. If the PLM re-tries 5x and doesn't receive an acknowledge, a device timeout occurs. For certain commands (query, link table read), the ISY will re-try the command up to 2x (3 total). These are the RED highlighted entries I showed above. You are not seeing these - that's a good thing. A scene command does not do any of the above checking. If you have marginal signal level from the PLM to the device, it's entirely possible it will not hear the scene command. The ISY will assume that it did. Questions: "Extractor fan" sounds industrial. Is this a dust collector or other large motor driven device? Does your scene fail only when the load is on or off - trying to determine is the load could be absorbing signal. Try to determine what else is on this circuit. You may have devices that are absorbing the Insteon signal. Unplug devices to see if the scene performance improves. Remember that you are looking for better communication from the PLM to the device. You can use the scene test for this (tools/diagnostics/scene test). Alternatively, you can activate your device scene and follow with a query to see if the device responded correctly. In my case above, I was able to improve the signal levels by installing a On/Off module upstream from my 2477S (closer to the electrical panel). 2477S downstream from refrigerator - poor signal levels Panel -----------------------------Frige-----2477S Adding On/Off module upstream of the refrigerator improves signal level. Panel -------On/Off Module -----Frige-----2477S Edit: Realized you are using a 2475D on your extractor fan. Dimmers are not normally compatible with fan motors. Your event viewer log is showing Peek/Poke communication during the link table read. This is an old (I1) method mode that is extremely slow and has been deprecated for most newer devices. Please check your settings under "Link Management/Advanced Options" to make sure that "Automatic" is selected. It would appear that you have "I1 Only" selected.
  24. IndyMike
    Other switches, and the Admin Console (not sure about Alexa) communicate via Insteon Direct commands. These commands interrogate the target device (your Inlinelinc) to determine if it received and properly acted on the command. The PLM and "other switches" will also re-try sending the command if it does not get the correct response. Scenes do not confirm the target response, nor do they re-try commands. They are open loop "send only" and assume that the target has responded correctly. Your inlinelinc likely has marginal communication with the PLM. The 2475D is dual band, but inlinelincs tend to be installed in areas where they may not have good RF communication. Powerline communication may be affected by the load or other devices on the same circuit. You can try to improve RF comms by installing range extenders or Lamplincs. You can try improving powerline comms by inspecting/filtering signal absorbing devices or again installing powerline devices on the same circuit to repeat the Insteon signal. If you wish to assess the quality of you communication, try running a link table scan with your event viewer on level 3 (right click on the device, select "Diagnostics/Show Device Link Table". A link table read will generate a lot of communication with the device. With each device acknowledge, the ISY will display the Max Hops and Hops Left. Having them equal is perfect. The larger the disparity, the worst the communication. I'm betting that your Hops Remaining on the 2475D will show it's having problems. You can also compare with other devices for a relative quality factor. If you have a question on the event viewer information, post yours and we'll have a look. Link table scan for a good communication: dual band KPL 2 floors up at other end of my house: Fri 09/20/2024 05:45:40 AM : [INST-TX-I2CS] 02 62 58 D0 2B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 09/20/2024 05:45:40 AM : [INST-ACK ] 02 62 58.D0.2B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 09/20/2024 05:45:41 AM : [INST-SRX ] 02 50 58.D0.2B 53.BC.3A 2F 2F 00 (00) Fri 09/20/2024 05:45:41 AM : [Std-Direct Ack] 58.D0.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 09/20/2024 05:45:41 AM : [INST-ERX ] 02 51 58 D0 2B 53 BC 3A 15 2F 00 00 01 0F FF 20 A2 49 53 BC 3A FF 1F 02 4E Fri 09/20/2024 05:45:41 AM : [Ext-Direct ] 58.D0.2B-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Fri 09/20/2024 05:45:41 AM : [INST-TX-I2CS] 02 62 58 D0 2B 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Fri 09/20/2024 05:45:41 AM : [INST-ACK ] 02 62 58.D0.2B 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Fri 09/20/2024 05:45:42 AM : [INST-SRX ] 02 50 58.D0.2B 53.BC.3A 2F 2F 00 (00) Fri 09/20/2024 05:45:42 AM : [Std-Direct Ack] 58.D0.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Link table scan for a problem 2477S in my basement (20' from the PLM). Device is powered by a GFCI circuit and includes a refrigerator with inverter cooling. I have a LampLinc on this circuit to "improve" communication to the 2477s. Communication below is good. Fri 09/20/2024 05:59:48 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 09/20/2024 05:59:48 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 09/20/2024 05:59:49 AM : [INST-SRX ] 02 50 20.73.18 53.BC.3A 2B 2F 00 (00) Fri 09/20/2024 05:59:49 AM : [Std-Direct Ack] 20.73.18-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 09/20/2024 05:59:49 AM : [INST-ERX ] 02 51 20 73 18 53 BC 3A 11 2F 00 00 01 0F FF 00 AA 00 39 01 76 FF 1C 01 4C Fri 09/20/2024 05:59:49 AM : [Ext-Direct ] 20.73.18-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 09/20/2024 05:59:49 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Fri 09/20/2024 05:59:49 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Fri 09/20/2024 05:59:50 AM : [INST-SRX ] 02 50 20.73.18 53.BC.3A 2B 2F 00 (00) Fri 09/20/2024 05:59:50 AM : [Std-Direct Ack] 20.73.18-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 2477S with no helper installed (red items are ISY re-tries). Without the LampLinc "helper" installed communication exhibits multiple ISY re-tries after time outs. Fri 09/20/2024 06:07:33 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 09/20/2024 06:07:33 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 09/20/2024 06:07:42 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 09/20/2024 06:07:42 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 09/20/2024 06:07:44 AM : [INST-SRX ] 02 50 20.73.18 53.BC.3A 2B 2F 00 (00) Fri 09/20/2024 06:07:44 AM : [Std-Direct Ack] 20.73.18-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 09/20/2024 06:07:44 AM : [INST-ERX ] 02 51 20 73 18 53 BC 3A 11 2F 00 00 01 0F FF 00 AA 00 39 01 76 FF 1C 01 4C Fri 09/20/2024 06:07:44 AM : [Ext-Direct ] 20.73.18-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 09/20/2024 06:07:44 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Fri 09/20/2024 06:07:44 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Fri 09/20/2024 06:07:53 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Fri 09/20/2024 06:07:53 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Fri 09/20/2024 06:08:02 AM : [INST-TX-I2CS] 02 62 20 73 18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Fri 09/20/2024 06:08:02 AM : [INST-ACK ] 02 62 20.73.18 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Fri 09/20/2024 06:08:05 AM : [INST-SRX ] 02 50 20.73.18 53.BC.3A 2B 2F 00 Fri 09/20/2024 06:08:05 AM : [Std-Direct Ack] 20.73.18-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
  25. IndyMike
    @SHM, I'm a little surprised that your microwave is causing a problem when it is off. Is this a built-in model or countertop? I ask because a countertop model would be on a GFCI and could be shared with other outlets while a built in would not. If your lamplincs were on the same circuit, I could absolutely believe that the microwave would absorb the insteon signal and prevent them from communicating. If your devices are on a different circuit from the microwave, I would suggest that you saw a "false positive" in your testing. It's unlikely that the microwave could absorb signals on a different circuit. Try unplugging the microwave to see I the devices still communicate. If the microwave is indeed causing interference on a different circuit when it's off, it may be time for a new microwave.
×
×
  • Create New...