Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

IndyMike

Members
  • Joined

  • Last visited

Everything posted by IndyMike

  1. joefly, In a nutshell, your 2486D is not acknowledging the link write from the PLM. The ISY tried to write the link to the device EEProm 3 times. It did not get an ACK from the device for any of the attempts and timed out. The cause of the write problem could be due to noise, signal absorbtion, or a failing device. I'd try multiple restoring the device times (reset the dimmer and retry the restore) since it could have been an isolated event. If the restore does not work, you can try the normal "inspection" technique, looking for any new devices that could be absorbing signal or generating noise. Alternatively, you could remove the switch and attach it to an appliance cord and plug it in next to the PLM. If a restore does not work with the dimmer next to the PLM, you have a bad dimmer or a failing PLM.
  2. The 4827 boosterlinc will designed to repeat (amplify) X10 signals. Unfortunately, when it gets confused and corrupts Insteon signals. If you do not have X10 in your system there is no reason for the 4827 - remove it to preserve your Insteon signalling. If you do have X10 in your system there are far better amplifiers that do not step on the Insteon communication - again, remove the 4827. Jeff Volp has a line of X10 repeaters that will not interfere with your insteon signals: Jeff Volp XTB X10 Repeaters
  3. Hello pjjameso, I agree that this could be a case where the scene command from the ISY/PLM could collide with the scene clean-up commands from the Keypadlinc. I'm wondering if your KPL is flashing, indicating that it is not communicating properly with one of the scene responders? The 2 second delay that Larry suggested should have gone a long way toward eliminating this possibility. It should have allowed time for the KPL to complete the clean-up communications, unless there are communications issues which could require re-tries (extending the communication time). Paul is also correct that noise or absorption near the KPL could be causing the KPL to miss the scene command from the ISY. Why am I posting? I do not recommend your "fix" as you have posted it. If I understand your scene correctly, you are issuing a scene command to a KPL that has just issued a control action. That opens the door for possible "all-on" collisions. Have a look here: Wiki: All-on-events I would rather see you place the 2 second wait in front of the 1st scene command.
  4. Scott, I do disassemble the PLM and physically remove the antenna. I did this years back after having a all-on event. Can't say this was a solution since I made many other changes at the same time. I have had 1 all on since then. It was KPL triggered. I am a bit confused by your second statement. I was trying to point out to the OP that performing a factory reset would wipe the PLM. He has a very low link count now because he only added the motion sensors back in. It sounds like you and I agree that the PLM will ignore traffic that it does not have a link record for. That was the point that I was trying to make in my post. Did you mean to address this to the OP?
  5. Jack, You've noted several times that the device has issues at the Sunrise + 10 minute point, but functions normally otherwise. We are looking for a noise source / signal absorber that is RELIABLY active at that time. Assuming that you aren't actively turning on another device programmatically, the only other device I can think of would be a photocell. This could be outdoor or indoor, but normally the indoor night lights don't pull enough power to be a problem. I have had issues with photocells generating noise in the past (post lamp). They can generate noise due to poor design, or aging of the sensor itself. I finally removed the sensor from my post light and used an Insteon switch to activate programmatically. Other possible offenders could be timed kitchen devices (coffee pot), a setback thermostat warming the house around that time, etc.
  6. Hello GTCJ, You are correct about disabling the programs. The following is what I have done to read the link tables: 1) All programs in a folder which I disable with a $Programs_disable variable. This takes care of scheduled programs and queries. 2) Place the PLM behind 2 - filterlincs to prevent powerline communication from reaching the PLM. This does not always work. The filters are not 100% effective in eliminating the powerline signals. 3) I have removed the antennas from my PLM in an attempt to eliminate RF communication. Again, not 100% effective. My reasoning for eliminating the antenna is a bit obscure. Suffice it to say that I do prefer the PLM to operate in powerline only communication mode. Please note that I am not advocating that anyone perform the above operations. I am posting this mainly to show how difficult it can be to get a reliable PLM link count. If you cannot get a consistent link count 3 times (with nothing showing in the event viewer), I would not trust the result. Not a very useful function for most users. Since you factor reset your PLM, the ISY knows of the existence of your devices but your PLM does not. If you go to a Switchlinc and turn it on/off, the PLM will likely not register it's activity. You will need to restore the PLM before it recognizes communication from these devices.
  7. Hello GTCJ, While it is entirely possible that your PLM is having power supply issues, getting a good PLM link table read is actually quite difficult to do. Problems arise if there is ANY program or device activity while the reading is in process. LeeG posted a rather nice explanation of what happens when the read process is interrupted here : https://forum.universal-devices.com/topic/19022-cant-view-plm-links-table/?p=177734 The fact you were seeing wide variations in the link count is more likely due to the read process being interrupted. Your most recent post after resetting the PLM has me confused. Either the PLM is failing or you "FACTORY RESET" the PLM, and in doing so wiped out the Link table. If you did perform a factory reset, you will need to restore the PLM from backup to restore the Link Table. I do agree with Stu that, with over 300 devices, you are likely at or over the PLM table limit of 1000.
  8. The fact that "fast on" functions makes it sound like you may have a problem with the device ramp rate. Check to make sure it isn't set to something very long - making the device seem like it is not responding to the "on" command.
  9. Unless something has changed recently: The ISY will not request a group cleanup after turning a scene on/off. There are no retries associated with an ISY scene. The ISY reports what "it believes" the correct device status is based on the scene command it executed. While not as reliable, this is very fast and does not encounter issues when stringing multiple scene commands together. A device direct command from the ISY (clicking a device on/off from the device tree) will request a cleanup response and will retry failed communications. A button press (KPL button or switch button) will execute a scene command and request cleanup from each device in the scene.
  10. Techman, I also have the 2009 developers guide. No help there. The best information that I've seen on the subject is Lee G's post that you referenced above. Just to be clear, it isn't just the "EA" record that will show as a record mismatch. Since the hop count can increment from 0 to 3, you have three values that can create a mismatch. Better to simply mask the bits out of the comparison 0 Hop: E2 1 Hop: EA 2 Hop: F2 3 Hop: FA By the way, thank you for bringing this up. I don't have many I2CS devices and had been restoring them (incorrectly) when I noticed these mismatches. I feel a lot better now that I understand that the devices are modifying themselves.
  11. Hello Techman, It looks like you found the correct post from Lee G. As he documented I2CS controllers are capable of changing the cleanup hop count to "adapt" to their installed environment. The "EA" link record is the result of a I2CS device increasing the default cleanup hop count to 1 hop. Since the hardware device is modifying its cleanup count locally, the ISY should NOT consider this a record mismatch. I had missed this post originally an am learning along with you. To verify, I went through a series of tests with a "new" KPL. The KPL was setup to "turn off" my 1st floor scene (~ 30 devices) using a non-toggle button. As programmed by the ISY there were zero mismatches. By varying the location of the KPL (wired to a cord) I could observe how it modified the cleanup hop counts for various scene members. The KPL both increased and decreased the hop count depending on its location. 1) As programmed by the ISY - no mismatches 2) Location 1: 10 mismatches 3) Location 2: 11 mismatches 4) Location 3: 12 mismatches
  12. Hello jgcharlotte, My information may be a bit dated - most of my devices are V1.1 2420M sensors (Old). The behavior you are looking for below is exactly what I get with the "sensing mode" unchecked. I've just verified this with my spare sensor. With the "sensing mode" unchecked: 1) sensor sends an "On" at first motion, then an off after 30 seconds if no additional motion is detected. 2) sensor sends an "On' at first motion, and recognizes additional motion but does not transmit. It re-starts the 30 sec motion timer at each event. After 30 sec with "no motion", it will send an off. If this is what you are looking for, I don't believe you need any program intervention.
  13. Hello GMD99, As others have correctly posted, dimmer switches generate heat that is a percentage of the power delivered to the load. The higher the power, the more waste heat generated by the dimmer. All (95%) dimmer switches generate waste heat in this manner. This is not something that is unique to Insteon devices. Since the hot faceplate appears to be new after the rewire, I am guessing that you had traditional (non-dimming) switches installed previously. If so, these would not have generated waste heat. With dimmers installed, the temperature of your faceplate will depend on many factors that affect the amount of heat generated, and how the heat is conducted away from the switch: 1) # of active dimmers/load power 2) J box type (plastic/metal) 3) Wall type (inside/outside; insulated/uninsulated). 4) Wall sheathiing (sheetrock/plaster/wood) 5) faceplate type (plastic/metal) I made some measurements on the heat generated by a KPL dimmer VS load some years back. That information is located here: http://forum.smarthome.com/topic.asp?TOPIC_ID=6969&FORUM_ID=9 The temperature vs load information should give you an idea of whether there is something "wrong" with your installation. My guess is that there is not, but I certainly do not want to minimize any concern on your part. If you believe your temps are running higher than what I am showing in the link, you should absolutely call your electrician. If you are concerned with the heat being generated at the switchbox and/or reliability concerns with the heat in the switches, post back - there are many ways to address this.
  14. nil13, If you have the network module, you can use a program to log whatever data your heart desires (and variables support). http://forum.universal-devices.com/topic/10122-402-network-module-create-web-pages-using-programs/ I've been using this technique to log weather data for a couple of years now. Very nice.
  15. Christopher, I agree that if your program ran, you should have received both a "Program" log entry as well as "System" log entries for each device in the Scene. I have a "recirculation pump" program that runs twice daily. I've been logging entries for this program daily even though the applicancelinc that is Scene uses was removed months ago. I don't have a good explanation for why your program indicated "run" but you have no log entries. This is probably a Michel question. My only observation would be that 12:59:59 may be a rather busy time for the ISY. You could try moving the trigger time a few minutes in either direction. I've never seen the ISY "miss" a program operation. Nonetheless, I do think this needs to be investigated.
  16. IndyMike replied to jwarner964's topic in ISY994
    Brian, I believe the 4826 had issues handling "Dim" commands from the X10 CM15a (firestorm event). Being that the 4826 is labeled as a "true X10 repeater", it should have been able to distinguish between X10 and Insteon transmissions. The Boosterlinc was a real time booster. It attempted to discriminate between Insteon/X10 by the start of the waveform in relation to the 60Hz zero crossing. It would invariably get fooled into thinking a low level Insteon transmission was X10 and would transmit on top of the Insteon.
  17. Hello JSP0511, To be blunt - these are not the type of devices that I would trust to automation. Not just Insteon, but ZWave, UPB, X10, RadioRa - you name it. All of the automation protocols are subject to programming and communication errors. Think in terms of what would happen if your compressor or shop vac were to inadvertently turn on while you were away. This is not something we can answer for you - it's your application. Personally, I would not install such a system without a manual override. The problem is remembering to activate the override. If I were to vote, I would vote in favor of the "purpose built" current sensing switches that larryllix posted. I'm not sure if these are appropriate for you air compressor application - I'm unsure how you are using the compressor with your woodworking tools. My 0.02, IM
  18. Like LeeG, your comment on this being an old Commercial building caught my attention: 1) Possible that you have "true 3-phase" power. Voltage across the mains (legs) would be 208 rms rather than 240. 2) Possible that your RF communication is being blocked by fire-breaks, metal, and other construction materials not commonly found in residential construction. As LeeG indicated, check your coupling between RF devices - make sure your phases are STILL coupled.
  19. Hello smokegrub, It sounds like your program is turning off the individual switches themselves. This affects only the device addressed by the program. Try turning off the scene instead. This should turn off all devices in the scene.
  20. IndyMike replied to jmed999's topic in ISY994
    Hello Michel, KSBN received .22" of rain yesterday according to NOAA. The HAM website recorded .2" of rain - 0.02" was "missed" due to the 1 hour time offset. The ISY recorded the 0.2" of rain yesterday, but did not reset to 0 after midnight. It is currently recording 0.2" for 10/5/2014 even though no rain has fallen. The table below shows rainfall totals reported by the HAM website. The plot below shows NOAA and ISY cumulative rain for 10/4 through 10/5. The red line (ISY) should reset to zero after midnight on 10/4. Unfortunately, I'm running out of calendar to track this issue. In November precipitation will become "fluffy" around here (the bad fluffy - not Gabriel Iglesias). We had an unofficial 110" of snow last year - unofficial because the NWS at KSBN decided to discontinue measuring snowfall after 74 years. We're doing our winter tuneups on Vehicles, furnaces, snowblowers and the like. Judging by the way my pines are dropping needles, we don't have much time left.
  21. IndyMike replied to jmed999's topic in ISY994
    Hello Michel, I am having a bit of trouble interpreting HAM's response: It seems that they are implying that one hour delay on the KSBN website is an isolated case. I spot checked 3 other international airports aross the US (O'Hare, Atlanta, LAX). All showed a one hour time delay. Interesting, since a one hour delay from LAX would put you in the Pacific. They also seem to make the distinction that the website and the API are not the same. Unless I mis-understood, the API should be more accurate. I am currently tracking a minimum of 1.5 hours delay between the ISY reports and NOAA (10 minute update in my logging). I have been holding this back since I regarded it as unofficial vs the website (one issue at a time). I'm a bit concerned that HAM appears to be treating this as isolated rather than examing their "system". Also concerned that it is far more difficult to correct PWS stations since we do not have access to a "webiste" summary for them. Am I overcomplicating things? IM
  22. IndyMike replied to jmed999's topic in ISY994
    Hello Mike, I haven't received any rain here to check the updates. I have noticed that HAM data is being presented 1 hour late VS NOAA. My airport station (KSBN) is in the eastern time zone. HAM appears to be presenting for central.
  23. IndyMike replied to jmed999's topic in ISY994
    Hello Michel, Verified both firmware and UI at 4.2.8, Under 4.2.8: 1) KSBN received 0.06" of rain yesterday. The ISY reported 0.04" 2) No rain at KSBN after 16:00 yesterday and today. The ISY continued to report 0.04" until 4:50 PM when I loaded 4.2.15. 3) After loading 4.2.15 rain is at 0.0" No rain the the forcast for the forseeable future. Waiting on data on this end...
  24. IndyMike replied to jmed999's topic in ISY994
    Hello Michel, I'm on 4.2.8 (RC3). There was nothing related to HAM/Climate noted in the 4.2.10 (RC4) release notes. Did I miss something?
  25. IndyMike replied to jmed999's topic in ISY994
    That's correct Michel. I'm thinking that something was "stuck" after the changeover. Rain today was showing 0.05 again this morning. I manually switched stations and then came back to KSBN. Now correctly showing 0".

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.