hspindel

I am sending the commands from a program running on my EISY. I have no idea what it's doing under the hood other than the log entry I posted. There's no way to add a pause between address and bright. If I don't send the dim at all, it still doesn't work. I have no other X10 devices.

I've tried the siren in an outlet on the same wall as the PLM. No help.

It's trivial, but it doesn't help. Moving the X10 siren doesn't help. Perhaps that's true, but it's not the solution here. If I send only the bright command it still doesn't work.

I controlled an X10 siren from my ISY for years. Sometime after I upgraded to an EISY it stopped working. I don't know if that was related to the upgrade or if some change to my home's electrical system caused an issue. Anybody know the status of X10 support from EISY? Is there something I have to enable? If there's an A10/X10 module that needs to be added, I don't see how to do that - can't find any way to purchase modules. Help/Manage Modules just tells me all my modules are up to date. On the ISY, I had a program which issued the following: Send X10 "H6/Bright (7_) This caused the X10 siren to chime. I've also attempted to verify X10 functionality without using an EISY program by opening an ssh shell into the EISY and trying: send_x10 bright H6 but the shell reports that the send_x10 program is not present. I could not find out how to install the send_x10 program. It may be relevant that I had to switch the cable to the PLM when I upgraded to EISY. Any pointers on the above would be greatly appreciated. A bit more info after reading these forums: I triggered the EISY program to make the X10 siren chime. I can see in the Event Viewer that the PLM sent the X10 commands, and also received an X10 response. But the X10 device made no noise. I've tried two different X10 sirens and neither one worked. Sun 04/05/2026 23:49:39 : [ X10] H6 Sun 04/05/2026 23:49:39 : [ X10] H6/Bright (7) Sun 04/05/2026 23:49:39 : [ X10] H6 Sun 04/05/2026 23:49:39 : [ X10] H6/Dim (15) Sun 04/05/2026 23:49:39 : [X10-RSP ] 02 63 D9 00 06 Sun 04/05/2026 23:49:40 : [X10-RSP ] 02 63 D5 80 06 Sun 04/05/2026 23:49:41 : [X10-RSP ] 02 63 D9 00 06 Sun 04/05/2026 23:49:42 : [X10-RSP ] 02 63 D4 80 06

Yes, my old X10 chime was perfect. Disappointed that it stopped working. Even bought a second one as a test in case the first one had gone bad. No joy. It had two tones, I could make it go Ding or DingDong. I triggered it from my ISY to announce arm/disarm of an ISY program.

Thank you for that link. It is informative. Sounds like it won't quite do what I want: It doesn't have two different chime tones that I could separately trigger. There are warnings that make it sound like it is too loud for my purposes. I suppose I could buy one to test it out...

It is possible that my X10 chime stopped working when I switched from ISY to eISY. I haven't been able to figure out from available documentation how I would tell that siren module to make a ding dong noise from eISY.

I was using an X10 siren module which supports a high/low chime, but it mysteriously stopped working. Could be related to some electrical work on my house. I've looked for an Insteon chime, but can't find one. Someone suggested an on/off plug: InsteonOn/Off PlugControls plug-in lamps, space heaters, fans and other small appliances up to 15 Amps or 1800 Watts. Works with Amazon Alexa for voice control when paired with an Insteon Hub 2.but I don't see a way to connect to a chime. Important features for me: Trigger a brief chime noise from eISY. Preferably have two different pitched tones available. Any recommendations?

@Techman: Okay, thank you very much!

I don't see a Replace Modem function. Where is it? I used the Restore Modem function found on the File menu.

For anyone following this discussion... I just stumbled on the solution. In the Config section of the eisy, somehow the Insteon support radio button was not checked. Since this used to work, it must have gotten "magically" unchecked. I didn't even know that button existed until I just accidentally stumbled upon it. I checked the button, rebooted the eisy, and it's now working fine using the 2413S PLM. So, sadly, I unnecessarily purchased a 2413U. At least now I have a spare. But I was unable to get the eisy to work with the 2413U. The eisy sees the 2413U as connected, but I was unable to use the eisy to control any of my devices (even after trying Restore PLM). Don't think I'll pursue that right now because it would mean messing with a working system, but if anyone has further suggestions please post.

@jdm5 Very interesting. I think I've proven that this is an eisy problem, but waiting to hear more from Michael.

eisy version is 5.9.1. I've already opened a support ticket. Initial investigation said my PLM was bad. But I've now proved that not to be the case, since the PLM works fine with isy.

I followed that procedure exactly. The eisy sees neither PLM, while the isy sees the 2413S. The eisy worked for a year with the 2413S and its serial cable before failing.

I bought a replacement PLM (a 2413U this time). The eisy still does not recognize it, nor did it recognize the 2413S. As a test, I found my old isy994 and tried using it instead of the eisy. The isy works fine with the 2413S, so that PLM must be good. I am unable to test the 2413U with the isy as I don't have a cable that connects them. Anybody know if one is made (isy end is RJ45 and PLM end is USB-B)? Any further suggestions to fix the eisy? Seems like it has the problem, not the PLM.