Skip 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.

Brian H

Members
  • Joined

  • Last visited

Everything posted by Brian H

  1. Did you power cycle the Eisy also? The PLM is most likely only checked for a boot up. Is the LED on the side of the PLM on at about its normally brightness? Sounds like the PLM has failed or is almost completely failed. How old is it? Sticker on the back should give you information.
  2. Brian H replied to hspindel's topic in eisy
    Thank you for the update.
  3. Brian H replied to hspindel's topic in eisy
    The SH10A is receive only and will not send an acknowledge back. You probably are seeing the PLM acknowledging the command. Since the PLM sends the command back to verify it was valid and sent.
  4. Brian H replied to hspindel's topic in eisy
    The X10 commands require a short delay between commands. Like the address has to be sent and then a short (not much but don't have exactly known) time the bright or dim command. I am not a programing type so if the slight delay maybe needed. I can't say how to do it. That maybe but not for sure your problem. The ISY controller that worked maybe running slower than the eisy that doesn't work. With the short delay long enough with the ISY controller.
  5. Brian H replied to hspindel's topic in eisy
    The small siren. Need the X10 address sent and then the bright or dim command. Did you send the address than a small pause to the dim or bright? Do you have any other X10 devices that are still OK? If others also stopped working then I would suspect something changed power line problems.
  6. Brian H replied to hspindel's topic in eisy
    I saw your question on the X10 forum and I agreed. In my post there. Try moving the module to different places to see if you have a power line signal issue.
  7. I have one of the early released Insteon Siren modules and I believe X10 was not supported.
  8. 5.3.4 was the last ISY994i firmware. If you have a Z wave card. Depending on which version you have. Series 300 or 500. 5.3.4 was only for series 500.
  9. Yes it has failed. Power cycling and working again for a short time is one of the failure modes we see. If the eisy behaves like the older ISY994i. It will only check for a PLM at boot time. It may have to be rebooted to again check for a PLM. If it thinks it is not communicating.
  10. I have also used similar devices to sense when a device is drawing current.
  11. Does the eisy still have a Replace PLM function? When you install a replacement PLM and then reboot so the controller knows you have a new PLM. You had to use the Replace PLM function. To go out to all the modules and replace the old PLMs six digit ID with the replacement PLMs six digit id. If the replacement PLM sends commands with the new id to a module with the old PLMs id It will not respond.
  12. I also found my 2440 original RemoteLinc. Would not link if close to the PLM. I had to put it into the linking mode located at the other end of the home. So the PLM had use a different Insteon dual band device using that devices RF.
  13. Battery data from old Smarthome site. The part where I thought there was no protection board was incorrect. It did have a protection board on the battery. Battery.pdf
  14. FCC Database: https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm Grantee SBP: Product Code: 23422 Details.
  15. Yes there was a post on the old Smarthome forums on changing the battery. I may have a archived copy. If memory is correct. The exact battery was not available when I looked. There are internal and external photos and original users manual in the FCC Database web site.
  16. I feel it is more like the battery is near end of life and the charger is preventing over charging. As I believe the red led was never flashing in a remote even the original units. The finding that if you use it for awhile and then try charging it and the red led is not flashing but then again flashing again. Sounds like the battery is above the normal full charge voltage and the charging circuit is stopping an over charge voltage. Try Insteon support. They should have a more definite answer. https://support.insteon.com/#gsc.tab=0 Forum. https://forum.insteon.com/forum
  17. v1.7 is an older revision. The date code looks like week 50 of 2014. My 2342-232 (4 scene) is a v2.05 date code 1631 week 31 of 2016. My thoughts are the battery is getting weak and the charging circuit is not seeing the battery voltage high enough to trigger the fully charged sensor. So its always trying to charge the battery. The battery has an over charge & over current circuit so it should not be effected too much. As a test. Try seeing how long the remote works after a few hours charging. To see how long the remote works before needing a refresh charge.
  18. I use a 5VDC 1000mA(1A) cell phone charger. After checking your chargers ratings. You may want to see if a different charger may give you different results. As I have seen some of the new ones have multiple outputs and hand shake with the device being charged for it's output. Though it should default to 5VDC. Remote chance the remote is is defective or near end of life. After many charge discharge cycles we occasionally see battery failures or diminished capacity. The label on the back of the remote. Could give you something to check on its revision number and maybe age.
  19. Charge LED on the lower right side inside the case. On mine near the USB charging port. Is solid red when charging and turn off when charged. Is this a newly purchased remote? I doubt they changed the way it works. Maybe see what other have found for a better understanding if it is changed or defective.
  20. One thing I forgot. The PLM both 2413S and 2413U. Use a HEX message for receiving and sending data. Get Version should get a reply back with the PLMs information. 02 60 Cartridge return. Should send back 02 60, the PLM's data and end in an 06 ACK. The serial 2413S also had serial port interface chip problems occasionally. Rev 2.3 changed the chip for one with better ESD protection. V2.4 and above. Have a new serial port daughter board that also has a protective on the serial in and out signals from the PLM.
  21. Wrong serial settings. 19,200 8 Bit No Parity 1stop bit. Bad caps frequently. Caused things like 0 or few links in it. Restoring it so the link count is more normal but then eventually is again 0 or very low link count. Runs for a short while after a power cycle. Are you running windows and a serial port? There are a few programs to access it but are more for folks that can use the low level commands to see what it is doing.
  22. If you want to use the2413S serial PLM on an EISY you need the UDI USB to serial cable they sell. The EISY does not do serial communications to the PLM. If you try a USB to Serial port adapter. It will not work. The serial signals are not correct for a standard adapter.
  23. Powered down for awhile and working for a short time after power up. Was one of the known problems when the PLM was failing. The ISY994i only checks for the PLM Status Info. When it is booting up. If you disconnected the PLM and the ISY994i was not rebooted. It will still be reported as connected. Even though it is not connected or has gone off line.
  24. It did a Query of all the modules in the setup. To find their status and see if any of them where not reachable. Mine was 3:00 AM. I do not know how important it is these days of almost all dual band devices. Can't say about Eisy as I am still on an ISY994i.
  25. Brian H replied to matapan's topic in ISY994
    Glad you got it working. The information may assist someone with similar issues.

Account

Navigation

Search

Search

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.