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.

slcasner

Members
  • Joined

  • Last visited

Everything posted by slcasner

  1. Just to close this out: I have purchased and installed the Smart Meter Module in my 2012 ISY994i and connection to the meter has been enabled by the utility. There are a few funny numbers that I'm trying to investigate with support on both sides, but it is basically working.
  2. Thanks for confirming compatibility. Is there a User Guide for the Smart Meter Module that would tell me how I can use it (e.g., what methods are available to access the data).
  3. I bought an isy994i in 2012 to control my INSTEON devices. I just heard about the Zigbee Smart Meter Module. Would my isy be compatible? I suppose there may have been some evolution over the past 9 years. Is there a User Guide for the Smart Meter Module? (I don't see a Documentation link on the website.) I would like to automatically pull meter readings for my records. I've been reading my meter visually on a daily basis for years, but it would be nice to do that automatically.
  4. Sadly, I have to conclude that my capacitor replacement repair was not a complete success, but that may be because the problem with the PLM was not a failure of the power supply in the first place. This PLM never got into the state where the LED was red or dark. I replaced it with a new one in 2016 because programs were occasionally failing to do what they were supposed to do, that is, the ISY was sometimes unable to control some devices. Power cycling the PLM seemed to help for a while. Now, after replacing the capacitors in the unreliable PLM it seems to mostly work, but after a time the admin console was popping up error messages about being able to communicate with one or another device. When I swapped back in the newer PLM, it was able to communicate with all devices. Going back to the repaired one, it took multiple executions of the Restore Modem operation to get through to all the devices, and there still was one that it could not reach. I tried this with the PLM plugged into outlets in two different rooms (but not sure if they were on different halves of the panel) to try to make sure I could get through to all the devices so they would be linked to the PLM. So, even though this repaired PLM mostly worked in my system (all the timed lights still worked), it could not communicate as reliably as the newer one. Perhaps some component other than the capacitors has failed or degraded. Perhaps RF is not working well (I did put the antennas back into their original positions after the repair). I have more sets of capacitors, so if the newer unit fails I will try again.
  5. Thanks for your help. You hit on the right answer, although I coincidentally found it myself earlier that day after searching the forum for information about PLM replacement. I had not powered off the ISY because I did not realize that was required (it has been a while since I replaced this PLM before). That is why the devices had the wrong PLM ID and why the Restore Modem operation finished at only 7% on the progress register. When I did the full recommended procedure (#1) then the Restore Modem operation took much longer to rewrite all the devices. I have relied on the User's Guide document as my primary reference. Why doesn't it describe the PLM replacement procedure? It doesn't even explain the Restore Modem command. Better yet, why doesn't Restore Modem cause the ISY to go read the PLM ID first? The repaired PLM has now been operating fine for a day, so it looks like the capacitor replacement was successful. I'll leave it in place to see if there are any indications of the instability that caused me to replace it before.
  6. Hmmm, the suggestion to check the device like table is a good one, except that ISY can't read the device link table, either, which I guess is not surprising. After putting in the questionable PLM and doing Restore Modem, I get the following when trying to read the keypad's link table: Fri 02/02/2018 05:05:44 PM : [iNST-TX-I2CS] 02 62 1E 02 E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 02/02/2018 05:05:44 PM : [iNST-ACK ] 02 62 1E.02.E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 02/02/2018 05:05:45 PM : [iNST-SRX ] 02 50 1E.02.E7 1E.47.4F AB 2F FF (FF) Fri 02/02/2018 05:05:45 PM : [std-Direct Nack] 1E.02.E7-->1E.47.4F, Max Hops=3, Hops Left=2 Fri 02/02/2018 05:05:54 PM : [iNST-TX-I2CS] 02 62 1E 02 E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 02/02/2018 05:05:54 PM : [iNST-ACK ] 02 62 1E.02.E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 02/02/2018 05:05:54 PM : [iNST-SRX ] 02 50 1E.02.E7 1E.47.4F AB 2F FF (FF) Fri 02/02/2018 05:05:54 PM : [std-Direct Nack] 1E.02.E7-->1E.47.4F, Max Hops=3, Hops Left=2 Fri 02/02/2018 05:06:03 PM : [iNST-TX-I2CS] 02 62 1E 02 E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Fri 02/02/2018 05:06:03 PM : [iNST-ACK ] 02 62 1E.02.E7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Fri 02/02/2018 05:06:04 PM : [iNST-SRX ] 02 50 1E.02.E7 1E.47.4F AB 2F FF (FF) Fri 02/02/2018 05:06:04 PM : [std-Direct Nack] 1E.02.E7-->1E.47.4F, Max Hops=3, Hops Left=2 I should make clear that the problem is not just this keypad; there are several devices I can't control with the problem PLM. If I compare the event logs for the Restore Modem operations on the good and bad PLMs, they are identical. Is there some other step that is supposed to be done to tell all the modules about the new PLM?
  7. I mentioned that the output of Show PLM Links Table was identical for the two PLMs. Is your suggestion to check the PLM's ID shows up in the Device Link Table for the devices that are failing to be controlled? Is there a reference to tell me how to interpret the logs in the Event Viewer and the Links Tables? BTW, I bought an inexpensive LCR tester that tells me the EKXM500ELL101MHB5D caps I bought for C7 and C13 are low ESR as claimed: 0.02 ohms. One of the two 10uF 35V originals that I removed shows an ESR of 41 ohms, but I don't know how much damage may have been caused by the desoldering process.
  8. I have done my first PLM capacitor replacement repair, on a 2413S V1.7 1222 that wasn't communicating reliably but still showed a green LED, with mixed results. I ordered from DigiKey: Digi-Key PN Mfr Part Number Manufacturer Description 399-6538-ND ESG106M400AH4AA KEMET 10uf 400v replaces 6.8uf 250v 493-3276-ND UTT1E101MPD Nichicon 100uf 25v replaces 100uf 25v 565-1598-ND EKZM500ELL101MHB5D United Chemi-Con 100uf 50v replaces 10uf 35v 493-10390-1-ND UTT1C100MDD1TP Nichicon 10uf 16v replaces 10uf 16v The assembly process was relatively straightforward. The 10uF 400V cap is much larger than the original but actually fits the hole spacing on the PCB whereas the original cap's spacing was narrower. I put in the larger 100uF 50V caps lying down, as Smarthome does in the newer revs, but I observed that I needed to push C7 to be parallel to the bottom edge to avoid hitting the modular connector for the cable (photo below). I think these caps might fit better standing up. When I put this repaired PLM in place of the operational one to test, the green LED still lights. After doing Restore Modem I can control some devices but not others. In fact I got a "can't communicate" for one keypad that I tried; resetting the keypad restored communication, but I still could not control it. In the log I see: Mon 01/29/2018 01:35:17 PM : [iNST-TX-I1 ] 02 62 1E 02 E7 0F 11 FF Mon 01/29/2018 01:35:17 PM : [iNST-ACK ] 02 62 1E.02.E7 0F 11 FF 06 LTONRR (FF) Mon 01/29/2018 01:35:17 PM : [iNST-SRX ] 02 50 1E.02.E7 1E.47.4F AB 11 FF LTONRR (FF) Mon 01/29/2018 01:35:17 PM : [std-Direct Nack] 1E.02.E7-->1E.47.4F, Max Hops=3, Hops Left=2 This Nack is sent right away every time I try to command the keypad on or off, so it is not a timeout problem. What does this mean? When I did the Restore Modem operation I was concerned because the progress register advanced only to 6% before the popup disappeared. But when I switched back to the working PLM and did Restore Modem again, the behavior was similar (perhaps 7%). But the log of the restore operation is identical and the result of Show PLM Links Table was identical for the two PLMs. Since I can successfully control some devices and not others, perhaps the repaired PLM is only able to communicate with RF or powerline but not both, and the devices that I can't control were depending on the other mode? Is there a way to investigate that hypothesis? Other debugging suggestions welcome.
  9. Brian, thanks for the advice. Here's a picture showing my old 1.7 and new 2.4.
  10. I'm about to do this capacitor replacement on a 2413S V1.7 1222 that didn't fail all the way (the LED still goes green) but programs would fail to execute. Power cycling seemed to help, but the problems repeated. I replaced it with a spare in 2016. Not all of the original replacement capacitors are still available. Mouser shows the ESX106M400AH4AA 10uF 400V in stock, but KEMET does not show that as a current product (the ESX series does not go up to high voltages) so DigiKey does not have it and I can't find a datasheet to compare. (I prefer DigiKey because I have an account.) Is there a recommended alternative? DigiKey has KEMET's has ESU106M400AH4AA at 10000 hours for "electronic lighting and power" applications and ESG106M400AH4AA at 5000 hours for "electronic ballast, power supplies and long life" applications. Does either application suggest a preference? The ripple current at 120Hz is 90ma for the ESU and 100ma for ESG; the ESU has no ESR spec while ESG is 2.9ohms, while both specify and impedence ratio 5. The ESG is rated 350V / 400V surge rather than just 400V like ESU. The physical size for both is 10mm diameter, 20mm length, and 5mm lead spacing. This is 1mm longer than the ESX, but it looks like there is room. I see several posts upstream that cdragon chose the Nichicon UPW2G100MHD1TO from Mouser instead. Also, is it a good idea to replace the original 10uF C7 and C13 in an older 2413 with 100uF as in the newer revisions, and if so, is the recommended part still in the KY series (EKY-500ETD101MHB5D)? I wondered if there was any other component value change that would need to be coupled with the capacitor change. I just bought another spare 2413 (prompted by the 30% off offer from Smarthome) and I see it has the 100uF capacitors still mounted lying down on the board even though it looks like the board layout was changed to allow at least C7 to be installed standing up. I can't tell if the inductor is the same, though; it looks the same as in the old unit but there are no markings I can see on either one.
  11. I have downloaded the american.zip file from the wiki that contains the american.isy file containing programs to import. These programs contain schedule conditions for some common American holidays for the next several years. I'd like to creates some similar program conditions using other programming tools to then import into the ISY. Is there an XML schema available to describe the format of a program import file?

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.