gschoffstall

Thanks for that. I don't have any programs at this point that I trust. None of them were very complicated anyway- sensor > light> time> on/off. You get the point. I do have some old X10 hardware- Powerhouse remote controllers HR12A, which I really like for manual control. I won't get on a soap box about the Insteon remotes, but I have nothing good to say about them. Thanks again for clear instructions. I'll let you know either way.

Yes, Paul, I did. But in my flailing about, I can't remember exactly what happened. To the best of my knowledge, I seem to remember the results being that the device I was trying to link ignored me. I want to test each module and make sure it works where I need it to. It might be an advantage to use a range extender, but there wasn't any need for one before. I don't see any new ones for sale, and I don't want to buy a used one and end up with more trouble. But then I've been at this for over two weeks intermittently and I am afraid I need to get serious and zero everything out to start fresh. I could use some suggestions to that end. I've seen suggestions to put things in "Test mode", Use a range extender (which I do not have), remove links (for which there are no clear instructions). Simply: How can I make sure ALL the links are disabled/ deleted to start clean?

All good information, of course. I am still confused about the 2456S3, which all of my on/off modules are, not being dual band. The pdf file sent by Brian says the module uses the A.C. line and RF communication. Is this not Dual Band? I have never heard of the 4 tap test, and I never heard of an Insteon range extender. So I do not have one. What I do have is a phase coupler sold to bridge X10 signals on my split phase system. My home is a small 850 sq ft ranch with a basement. I don't have any new devices with chokes to kill the X10 powerline signals. In my efforts, I deleted devices and programs that were ineffective, left those that functioned. I saw no correlation with phase or distance from the PLM. I did encounter warnings to remove links from those removed devices. Exactly how does one accomplish that. I never saw anything mentioned about the how to, just the warning. Other than a factory reset (holding the set button while powering on the PLM) was the only sure way I knew to clear out the PLM links. I never saw an official procedure for replacing a PLM. Is there a way to do it piecemeal? And how about the EISY? It took 3 tries just to reset it (the press the multifunction button 10x). The devices I have are: 3 Appliance Linc 2456S3, 4 Lamplinc 2844-222 (which are not in service), 1 2457 D2, 1 2634-222 outdoor , 2 2842-2 motion detectors, 1 2844-222 motion detector. Most of this stuff has been around a while, and once set up, has worked reliably. Until now. I can honestly say i never had trouble like this until I upgraded to the EISY.

According to the Insteon manual for the ApplianceLinc, it is a dual band device, using powerline and RF to communicate. I didn't mention before that I started with an X-10 system and do indeed have a powerline bridge for my two phases. With the Insteon modules replacing X-10 modules, I figured that issue was resolved, but alas.... I decided to start from scratch, factory resetting the PLM and EISY. I believe the (decidedly old) PLM did what it should and is now devoid of links. The EISY, however did not respond as expected. When the multifunction button was pressed 10x (starting when it was on), and held for some 20 seconds, it came back with a red light. Waiting the obligatory 10 minutes, it was still on and red Pressing the button once restored the light to blue. When the console ran, it found the ISY still had a program. I only work with these things when they break, so not a lot of troubleshooting experience. SO when I follow directions and get conflicting results, it's beyond aggravating. What's up with it this time, please?

Ok, continuing my epic journey, now another ApplianceLinc that HAD been working went the route of the other two - cannot determine Insteon engine. I'm thinking there's no hope and ready to abandon ship. I never had this issue with the ISY-994. Yes, other problems - but this may be the end of the story for UD. I see no other avenue except for a total rebuild, factory reseting everything. Failing that HomeAssistant may be worth a try. Suggestions? Comments? I'm wide open.

Guys, I have reconstructed some of my system, but I am stuck on getting 2 ApplianceLinc modules - #2456S3 to communicate. I tried the usual factory reset - holding the Set button while powering the module. Then relinking, both with removing existing links and finding and adding them. Same result - they're not talking. When I try to link on either problem module, the status light blinks 4 fast blinks before going to the normal slow link mode blink. I never noticed that before. When trying to link, I get the standard Cannot determine Insteon engine. Any ideas?

Guys, I have another PLM, and its' date code is 1123. Actually it looks newer than the current one. I have been alternating them, seeing as they just seem to go nuts on their own. After I factory reset and sitting on the shelf a while, they seem to work fine again....until they don't. Right now, I have a sensor and light module working and I am rebuilding. I'll keep plugging away at it. Thanks.

Techman, Here is the PLM backplate. Maybe you can make out the date code- 1222? I have already started factory resetting the battery devices. I have a variety of saved files, so I can try. I'll let you know. Thanks.

Gentlemen, I had a reasonably reliable system until recently. The first issue was a power outage that caused my HUE equipment to not be seen by the EISY. Next, in trying to recover, I found an Insteon Appliance linc wasn't recognized. Well, from bad to worse, and I want to wipe the system and start rebuilding from scratch. My question: Is there a sure way to clean up the devices and start fresh? I have an older PLM, Insteon 2842-2 motion sensors, motion sensor II's, Remote linc 2440's, mini remote 2342-2, lamp linc's, and of course, the HUE bridge and lights. I am guessing I need to clear out any old links on the PLM and EISY, and factory reset all the components. I've already tried restoring the PLM and EISY with no success. Thanks for suggestions.

Can you please dumb this down a little for someone that doesn't mess a whole lot with router configurations? Thanks. For reference, the router is a Netgear AX1800 RAX10. And here's a new one. When trying to add back a previously working Insteon Appliance module that it "Forgot it had", here's what it reports

The issue with the security cert was my fault. Duck Duck Go doesn't have a bailout like Chrome. I got past it with Chrome but I still need to resolve the rest of the mess. I "lost" one of the modules now. It shows up on the main screen with an ! . I tried a restore of both PLM and ISY, then a program restore with no success. And the link with the HUE system never came back. I'll keep fooling with it and report back. Thanks.

Gentlemen, I'm back again with EISY/Hue issues. We experienced a power outage as a result of a storm. Everything came back except my link from the Hue bridge to the EISY. I can see and manipulate both devices and their controlled lamps and switches. The issue is that I cannot connect to Poyglot to re-up the link as I have done before. I downloaded the latest start.jnlp, I have rebooted everything and I get this when trying to connect : NET::ERR_CERT_AUTHORITY_INVALID when trying to get into Polyglot via the EISY interface that points here: https://eisy.local:3000/ Oh yeah, my router, EISY, and HUE bridge are on a UPS. Unfortunately the controlled lights are not. Any ideas? Thanks

Yes, after all the fiddling around and everything but the 3 related Hue programs was working, I tried power cycling the EISY. This cleared the "Not loaded" "Out of Memory" messages, but the EISY and Hue bridge were previously power cycled. As regards to this configuration, it seems very fragile and subject to guessing which hardware wants what and when. More prominent and descriptive error messages would sure help. And, yes, now the EISY, Insteon interface, router, and Hue bridge are all on a UPS. ISY994i and Insteon stuff was never this touchy. To me, it seems to have more to do with how the Hue bridge talks to the EISY. It would be nice if EISY talked directly to the HUE devices, but unfortunately the add-on module that does Zigbee doesn't do HUE. But thanks for your response.

Also I found this and I have no clue:

Gentlemen, I previously posted when having trouble integrating the Hue lights and bridge with the EISY controller. With your help and suggestions, I got it functioning using a Hue bridge through Polyglot. That is until a power failure causes the system to just lose its' mind. After the power is restored, everything I have programmed on Insteon devices works. The system sees the Hue hardware, and I can see and manipulate the Insteon and Hue lights. But the Hue automation refuses to work. Eventually, if I reset, repower, restart the EISY and Hue bridge in the right order, it MIGHT start working. But it's really starting to wear on me. Why does it have to be so hard to recover from a power failure? Is there a way to get things restarted in the right recovery order without all the drama? Thanks in advance.

Thank You!!!

Hey gang, I see a way to trigger events based on time, but I don't see a way to set a time window. What am I missing?

Thanks guys. The lights are Philips Hue, so a percentage is settable. @Andy P, it seems like your solution would work best. I'll have to figure out how to configure both programs so they don't interfere or cause one of those infinite loops that I am so prone to create.🤪

Here's the subject program as it is currently working. Problem is, at night the 100% command is jarring. I want to modify the action of the motion detector to only set the Bedroom 2 level at 20% between, say 10:00 pm and 6:00 am. I just don't know how to fit that in with the current structure. Any suggestions are welcome. Thanks.

A program acts to turn on a set of lights. It has IF commands to check if a motion sensor is on, a remote switch has been pressed, or if an X10 command has been issued. I need to make the program time sensitive to make the lights come on dim within a time range, but leave the rest of the functionality alone. Can this be done within the same program? If not, how? Thanks.

@Geddy Painful as it was, the result is: There was a reboot, a delete and reinstall of the plugin, and several presses of the Hue button, in no particular order. I've learned a LOT. Thank You, Thank You, Thank You!

You've been great. Thanks for your input. I have started a ticket.

AAARRRRG. I have restarted the Admin console and nothing has changed. I deleted what I had entered. I closed the Admin console and went back to the store and reloaded the plugin over top of where it was (slot 1). I restarted the Admin console and, again, nothing had changed. Here's what reloading accomplished: Selecting Node Servers and Hue, This is what I get: Selecting Configure gets me this: And Selecting [01] to [20] gets me this: Sorry, I am so confused. Thanks for any suggestions. Nothing was added to my network display after the Hue plugin was loaded, even though it appeared to have loaded successfully - Both times it was tried. The only thing that has changed is that Hue was added to the Node Server list. And Query does nothing.

@ Geddy. thanks for bearing with me. I have one more question. I have configured the node for slot 1 (Since I have nothing else). Is there a "How to" on configuring the lights that are already found by the Hue Hub in the EISY Admin Console? In the console, I went to node servers > Configure and made Hue Network 1. To add lights as nodes, it looks like it wants the light's node address. Just where is that? When the hub finds them it doesn't share that information and I can't find it in the Philips mobil app.

@Geddy YAY!!! That was indeed the issue. I signed up for the free trial. There was never a need for me to have portal access because I always did everything locally. Does the fact that it could not see the portal mean I need to pay for portal access for this plugin to continue to work? Sigh.....