paulbates

You can manually enter a url that incudes the IP address of the policy into the ISY finder. Can you give that a try? Is there a chance that the IP address of the policy and eisy are identical? Depending how you use DHCP, eg router assigned IP to a MAC address, that could be one explanation.

There are a few moving parts and I think it's down to one of these: The switch is old and losing functionality.. how old is the switch? turn on the event viewer level 3 and double tap the switch, does iox have a record of that? The mechanical part of the switch could have failed due to frequent, vigorous double tapping. If yes to the above, something happened in iox. Does the program turn green when the double tap occurs? It would help to post the program If none of the above, probably something happened between eisy and homeseer and its plugin. Has it ever worked with eisy?

I forget and leave it open. The main thing I've seen, with both ISY and eisy, on different computers at 2 houses is: clicking the mouse causes the old windows to "blong" sound, with no visual change in the interface. Other times some things will work and some won't... then I remember... 🤪😂

The Admin Console/iox is not designed to be left running 24x7. It's the java app on the computer that freezes, not the ISY/eisy. Different users have different experiences with how long the AC/iox runs before freezing.

I haven't used the i3 keypad, but having used the PS-01, some surprising behavioral tweaks are under the flags 'node' associated with each device. The out-of-the-box flags can vary and odd sometimes. Out of my ~20 PS-01s, a number of them were set to 'Disable RF'(???). I also had to factory reset a couple initially because of behavioral problems, but have been fine since. Note that my experience is that ,'Restore Device' does not put flags back on the device.

Let's start with the basics: Where is your PLM plugged in, to the EISY? Sometimes Insteon devices get "confused" after long periods (years) of use. If your PLM is connected to the EISY, Factory reset the 2477D Pull out the tab, wait a few seconds Press in all the way and hold until it beeps Restore old settings from EISY: Right click on the device Pick "Restore device" Retest If that doesn't help, then the PLM might be in question

It was a number of years ago, but I had a keypad that had random key behaviors: individual keys, the middle 4 of an 8 key keypad flashing on and off.. sometimes a random beep. It didn't happen very often and I seemed to be the only one that noticed.

Did you try 'restore device' to a few of the problem devices? If you look at tools/diagnostics/plm links, how many links are there in the list?

A first step would be to pick a problematic device, right click and then restore device. Repeat on several more problematic devices. How did that go? It sounds like your PLM is old... How old? There's a white sticker on the back with 4 numbers, what are they? Old PLMs can slowly die and need replacing. Restores can seem like they're helping, but if the PLM is old, it's just a matter of time and you should plan on replacing it before things get worse.

Did you specifically state you'd like a return/replacement?

Assuming you're migrating from a previous ISY99xx controller, you'll back up what you have and restore on eisy... switches, scenes and programs. I moved houses and started with a new eisy, but it's fundamentally what you're used to

I've only used the i3 paddle and outlets; they are both smaller switch packages than previous insteon switches and I've had an easier time installing

I would submit a ticket asking how you can change the logfile size on eisy

SSH client in. It should be in the wiki

What is the specific application? Does the switch simply turn the fan on and off? An Insteon on/off switch will work. I have an eisy and control 2 bathroom fans with a PS1 Insteon switches

That's how I did it when I removed nodelink

The post you're quoting is from the ISY29/99 = a very long time ago. It travels completely unencrypted. The eisy doesn't support telnet

I'd suggest going into the plug-in and logging back into ring.

The iolinc is single band, meaning that it only communicates via powerline. The gate motor(s) will create powerline noise, with the added complication of likely being far away from the rest of the Insteon network in terms of wire feet, which is how long the iolinc's signal has to travel Some direct remediation things to try an Insteon plugin filter on the gate motor if that's possible. It will block the motor's noise If your gate is relatively close to the house and insteon RF signals might make to other Insteon dualband devices in your house, plug a lamplinc or other dualband module into the back of the iolinc. Plug one in the area by the gate temporarily as a test. Another programming idea in addition to Guy's is to create a program that you set to "Run Then" on startup. This will cause the program to automatically run and it will keep running until eisy is shutdown or rebooted: IF - No conditions Then Repeat Every 15 minutes Set 'Gate device name' Query When in programs, go to the summary tab and right click on the program on the Run at Startup column and click "run Then". For the very first time after you write that program, you'll also need to go back to the Details tab, right click on it and click "Run then" to get it going There are a couple of complications with using query. I don't believe that the query will resend the scene to sync the keypad buttons, so a program will be needed to detect and resend the scene "on" or "off": If 'gate device' status is on Then wait 3 seconds set 'gate switch scene' on Else wait 3 seconds set 'gate switch scene" off 3 second waits are recommended because this program will also run when the gate operates and the iolinc catches it, there's a chance of the program and the iolinc traffic banging into each other. The program will only run when there is a change. The query could return an error, so program to trap that might be needed, depending on how the above works that might be another step

If that didn't fix it, sometimes java needs more memory to run the admin console / iox: - Close the admin console / iox - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: -Xmx512m - Press Ok to close the window, then Press Apply to save the changes

Yes, all insteon dual-band devices, including plugin-in modules repeat insteon traffic. It's repeated on the powerline too, and the LED light may be reacting to that. Insteon sells a 2 capacitor pack to try and avoid this problem

Ok, I see what you're saying. I use one of these in a box with hardware store lamp post photo cell for a dusk sensor.. but I've capped off the load and use iox programs to control the lights and avoid unwanted behavior like car lights reaching the sensor. The only way I can think of to do it is to add hardware like another micro module or switch to control the lights. The yellow lead in the micromodule is expecting a hard on/or off voltage, kind of the equivalent of dry contacts, and it looks like there are fluctuations in what the sensor is sending the micromodule. I know for my dusk sensor app, I have to use an iox program to send it an "off" in the afternoon this time of year in my northern latitude as there were days it wouldn't work simply because the photocell never reset it back to off for similar reasons.

Don't want to be a broken record, but you need to take control of the lights' off away from the sensor and let a program do it

It's going to help to see the program. What you're describing could happen its totally controlled with a scene What I do in these situations is: Use a scene where the sensor is the controller to turn the light on fast Set the "off" time of the detector to the longest time possible if possible Use a program to detect it "switched on" and use a wait of my choosing and have the program switch it back off If you can;t set the off time on the sensor to be long, do the whole thing program only with no scene

The rebuild comment was meant for the scene. Take a picture of or write down the current scene in the ISY. Create a new scene, under the link menu, on eisy and drag the related devices in