Sunday at 08:29 PM1 day I'm just getting used to EISY-UI after using Admin Console for 20+ years. It seems really nice.But how do I add X10 devices? I still have a few old ones I would like to continue to use if possible since Insteon no longer sells equivalents, but it looks EISY-UI has moved on?If I go to Protocols > Insteon and start a linking process, I can drop down a list of hundreds of old devices to choose from, but there's no mention of X10. I swear Admin Console had a "Generic X10 Device" option or something like that that I've used in the past, but it is no longer on the list.I have three existing X10 Universal Module devices I set up years ago (in AC) and they appear in my nodes, but they all say "Unknown type:113.2". They do turn on/off as expected in EISY-UI, which is good.So how can I add a X10 Powerflash PF284 or any other X10 device to EISY-UI?
Sunday at 09:00 PM1 day As far as I know, X10 devices don't need to be added to the device tree to use them with ISY.You can address them directly in programs using their house and unit codes.For example, Send X10 A1/On or A1/Off to control a device. You can also use an X10 Received condition to react to signals from something like the Powerflash PF284.The old optional A10/X10 module allowed you to create named X10 devices in the device tree, but that wasn't required for basic X10 operation.I haven't verified where the newer eisy-ui exposes the X10 programming options, though. If those options are missing, that may be an eisy-ui interface limitation rather than removal of X10 support.-Mike2545
Sunday at 10:04 PM1 day You can add them as you manually add Insteon devices: Go into Insteon -> New Insteon Device, and key in the X10 address directly, eg: A1 and give it a name.
Sunday at 10:52 PM1 day From AISteps to Add an X10 Device in eisy-uiLog in to eisy-ui. Open a web browser and navigate to http://eisy.local (or access it through your ISY Portal account) and sign in with your portal credentials. Open the Devices / Link Management Menu. Navigate to the Devices management section in the web interface where new Insteon, Z-Wave, and Zigbee devices are added. Select Manual Device Addition. Choose the option to Add an Inste / X10 Device manually (rather than scanning a QR code or starting auto-linking). Enter the Device Name and Type. Give your X10 device a descriptive name and select the X10 device category/type from the device type dropdown list. Input the X10 Address. Enter the combined House Code and Unit Code without spaces or punctuation (for example, enter I9 for House Code I, Unit 9). Save and Test. Confirm to create the node in your device tree, then test turning the device On and Off directly from its tile or device page in eisy-ui. Important Limitations to Keep in MindAdmin Console Fallback. While Universal Devices announced full device-management parity in eisy-ui ahead of retiring the Java Admin Console in December 2026, if an older legacy A10/X10 module type does not appear in your browser dropdown, you can still add it via Link Management > New INSTEON/A10/X10 Device in the IoX Launcher Admin Console.
Yesterday at 04:53 AM1 day What a GREAT product and forum user group.Its good to know that some of the hardware that I have stored away in boxes somewhere can still be used.Its also good to know that there are folks on this forum willing to help make it useful again.Thank you EISY and forum users! 1980 hardware still functional, UNBELIVEABLE in any other place but here!
17 hours ago17 hr Author 18 hours ago, Techman said:'m From AISteps to Add an X10 Device in eisy-uiLog in to eisy-ui. Open a web browser and navigate to http://eisy.local (or access it through your ISY Portal account) and sign in with your portal credentials.Open the Devices / Link Management Menu. Navigate to the Devices management section in the web interface where new Insteon, Z-Wave, and Zigbee devices are added.Select Manual Device Addition. Choose the option to Add an Inste / X10 Device manually (rather than scanning a QR code or starting auto-linking).Enter the Device Name and Type. Give your X10 device a descriptive name and select the X10 device category/type from the device type dropdown list.Input the X10 Address. Enter the combined House Code and Unit Code without spaces or punctuation (for example, enter I9 for House Code I, Unit 9).Save and Test. Confirm to create the node in your device tree, then test turning the device On and Off directly from its tile or device page in eisy-ui.Important Limitations to Keep in MindAdmin Console Fallback. While Universal Devices announced full device-management parity in eisy-ui ahead of retiring the Java Admin Console in December 2026, if an older legacy A10/X10 module type does not appear in your browser dropdown, you can still add it via Link Management > New INSTEON/A10/X10 Device in the IoX Launcher Admin Console.None of these steps work for me. There is no Devices/Link Management Menu or any of the steps below that that I can find in my EISY-UI.The UDI Wiki page describes Zwave, Insteon, and Matter devices in EISY-UI but nothing about X10.
17 hours ago17 hr Author 12 hours ago, Walt N said:What a GREAT product and forum user group.Its good to know that some of the hardware that I have stored away in boxes somewhere can still be used.Its also good to know that there are folks on this forum willing to help make it useful again.Thank you EISY and forum users!1980 hardware still functional, UNBELIVEABLE in any other place but here!I'm not convinced X10 hasn't been abandoned based on my limited experience so far.Fortunately I only use a few legacy X10 devices and won't be too upset if I have to resign them to the bin of defunct toys. Edited 17 hours ago17 hr by IndyUDIuser
16 hours ago16 hr Inclusion has not yet been implemented in eisy-ui, will likely be worked in the next week or two. Until that time please use the Admin Console to Add x10 devicesIt will be in the insteon menu when implemented, similar to Admin.
16 hours ago16 hr 44 minutes ago, IndyUDIuser said:None of these steps work for me. There is no Devices/Link Management Menu or any of the steps below that that I can find in my EISY-UI.I tried following these instructions as well, and also found the third step elusive. Having said this, the suggestion above from @Guy Lavoie seems to work for me. In different words...from the menu, go to protocols>>Insteon>>add new Insteon device. Give it a name, and X10 control in the address field (such as A1). Leave the third "auto discover" field as is. Choose "OK". If your experience is like mine, you will get an orange banner advising you that it is saving the device. After the popup menu asking whether you want to rename the device or not, it shows up under nodes as an unknown device with an address something like ff XX XX 1. The address format matches some of my old X10 devices created many years ago using the x10 module option and admin console. (see attached image where the last device is my newly-added x10 and all others before it were carry-overs from the admin console).Reminder: the original ability to create an X-10 node and name it was only an option if one purchased the X10 module and added it to the ISY and the admin panel. Otherwise, the only way to transmit an x10 command was via a program. The ability to transmit x10 codes appears to currently remain available in the EISY-UI in programs as well. While I have not tested this (currently don't use X-10), it appears to me that X10 capability still exists fully in the current EISY-UI world. Edited 16 hours ago16 hr by oberkc
16 hours ago16 hr Author 8 minutes ago, Javi said:Inclusion has not yet been implemented in eisy-ui, will likely be worked in the next week or two. Until that time please use the Admin Console to Add x10 devicesIt will be in the insteon menu when implemented, similar to Admin.Would it be possible to add an X10 protocol of its own, alongside Insteon, Zwave, etc? X10 predates Insteon so mixing it in with Insteon would be sub-optimal. Just my opinion.
16 hours ago16 hr Author 12 minutes ago, oberkc said:I tried following these instructions as well, and also found the third step elusive. Having said this, the suggestion above from @Guy Lavoie seems to work for me. In different words...from the menu, go to protocols>>Insteon>>add new Insteon device. Give it a name, and X10 control in the address field (such as A1). Leave the third "auto discover" field as is. Choose "OK". If your experience is like mine, you will get an orange banner advising you that it is saving the device. After the popup menu asking whether you want to rename the device or not, it shows up under nodes as an unknown device with an address something like ff XX XX 1. The address format matches some of my old X10 devices created many years ago using the x10 module option and admin console. (see attached image where the last device is my newly-added x10 and all others before it were carry-overs from the admin console).Reminder: the original ability to create an X-10 node and name it was only an option if one purchased the X10 module and added it to the ISY and the admin panel. Otherwise, the only way to transmit an x10 command was via a program. The ability to transmit x10 codes appears to currently remain available in the EISY-UI in programs as well. While I have not tested this (currently don't use X-10), it appears to me that X10 capability still exists fully in the current EISY-UI world.I did purchase the X10 connectivity with my old ISY994i and then the EISY that replaced it. I have a few devices I set up years ago that are still in service and working. These are X10 Universal Modules used for low-voltage controls.I'll play around with setting up a new device in the near future to see if it works.I will note that the Status column (not shown in my screenshot) is nebulous. It is blank until I turn the device on or off. Just mentioning this for the developer.Also the device type on the right isn't useful (FF 02 03 1). It would be nice if that showed the X10 house code and device number. Those don't seem to appear anywhere in the UI. Edited 15 hours ago15 hr by IndyUDIuser
15 hours ago15 hr Author Also noticed the detail screen for those devices has buttons for ON, OFF, BRIGHTEN, DIM, QUERY. Universal Modules are simple on/off devices that cannot be brightened or dimmed. I'm guessing can't be queried either. Edited 15 hours ago15 hr by IndyUDIuser
14 hours ago14 hr I'd be curious to know how many of us went with our UDI controller because it supported X10. It allowed a progressive migration. Count me as one.
13 hours ago13 hr 1 hour ago, Guy Lavoie said:I'd be curious to know how many of us went with our UDI controller because it supported X10. It allowed a progressive migration. Count me as one.Count me as two, although all of mine have long since been retired. 😎 Edited 13 hours ago13 hr by Athlon
12 hours ago12 hr Author Count me as well. I still use a few X10 Universal Modules just because they work for what I need. I don't miss all the struggles with line noise and such on X10. Edited 12 hours ago12 hr by IndyUDIuser Edit to remove attachment I didn't paste.
12 hours ago12 hr 1 minute ago, Guy Lavoie said:The old geezer club showing through!lolI remember buying some X10 stuff at Radio Shack - I think they were marketed under the Black & Decker name. I believe there was an outdoor unit that came with that bundle at a very low price.Most of what I had was regular X-10 stuff though.
10 hours ago10 hr Me too. X10 compatibility gave me the confidence to buy my first automated device, a KPL to replace a dead rotary dimmer. Second purchase was a used ISY26 off eBay, and then I was off to the races.My first X10 devices were somewhat later, and were primarily for controlling Xmas lights. They’re still great for that as long as your power line noise level permits. Plug them back in at the start of the season and everything works again. No network healing like Z-Wave requires. Unplug them at the end of the season and there are no nagging messages about unresponsive or missing devices. Silver lining of one-way communication.-Tom
10 hours ago10 hr 2 hours ago, Athlon said:lolI remember buying some X10 stuff at Radio Shack - I think they were marketed under the Black & Decker name. I believe there was an outdoor unit that came with that bundle at a very low price.Most of what I had was regular X-10 stuff though.Radio Shack's house brand for X10 devices was Plug 'n Power.
8 hours ago8 hr 1 hour ago, Guy Lavoie said:Radio Shack's house brand for X10 devices was Plug 'n Power.Ahh yes. I remember those blister packs. Not sure where I found that Black and Decker pack now.
8 hours ago8 hr 7 hours ago, IndyUDIuser said:Also the device type on the right isn't useful (FF 02 03 1Well, not totally useless. I observed that there seemed to be a relationship between the device type and X-10 code. It appears that the 02 represents house code B. 01 represents house code A, 03 represents house code C, etc...6 hours ago, Guy Lavoie said:I'd be curious to know how many of us went with our UDI controller because it supported X10I am one of those.On 11/15/2026 at 4:00 PM, mike2545 said:I haven't verified where the newer eisy-ui exposes the X10 programming optionsIt does
8 hours ago8 hr Even IBM sold X10 devices, under the Home Director brand. I remember seeing live demos at the Comdex shows in Las Vegas. It really was the future, and suprisingly affordable.You can see the whole list of companies that sold X10 devices under their own name:https://en.wikipedia.org/wiki/X10_(industry_standard)
Create an account or sign in to comment