Brian H

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.

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.

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.

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.

I have one of the early released Insteon Siren modules and I believe X10 was not supported.

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.

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.

I have also used similar devices to sense when a device is drawing current.

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.

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.

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

FCC Database: https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm Grantee SBP: Product Code: 23422 Details.

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.

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

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.