paulw

Michael, All is well. I was able to stay with 443. Turned out to be some type of issue with an air card which was on the client computer. Thanks for all your help.

Some progress. I'm able to remotely get past the router, installed the certificate and eliminated that error. Now it just sits there spinning it's wheel getting no response. (looking for a response from the ddns site, ddns service is via no-ip.com) FYI ISY-99 13.1.17 https port = 443 ISY set to port 443, accessing via https://ddns.name.xxx

Verizon can be a royal pain, and their support usually much worse. I'm just going to set it in bridge mode to a real router and be on with life. Will let you know if I have any other issues after doing that. Paul

Michael, Greetings, I appear on on that count. Just tried yougotsignal.com which reported both 443 and 8443 are open ports at my address. Paul

Sort of swallows you right up! Finding their commercial dsl at work is not the same as residential here at home!!! Anyone have any success in getting through to the isy from a Verizon Westell 7500? Generated certificate. Set the isy for port 8443 (suspect verizon has 443 blocked) Tried the 7500 forwarding 443 > 8443, and also 8443 > 8443 with the isy as the target. No joy. Tried actual dynamic address:8443 no joy. Tried no-ip host name set to redirect port 80 to 8443, no joy. No problem with internal ip:8443. Am I missing something?

Mine is the old 2412s. However, like I said the Lamplinc which is sandwiched in, has an extremely light load.

I have a PLM plugged into a Lamplinc, plugged into a Filterlinc. Been that way for a couple of years without any issues. The Filterlinc feeds my computer, the Lamplinc has a very light load of only a window candle.

Lee, Many thanks again! My last resort was going to be a power down. It did the trick.

I’m running 2.8.16. I inadvertently clicked an icon (no idea which one) and got a “linking in progress†screen with three options and a “Finish†button. Tried to close the screen via “X†but nothing, never pushed “Finishâ€. Appeared to be locked there with no way out. Closed down explorer and tried to go back into the isy. I keep getting a “Discovering nodes; retry†error, goes away in a couple of seconds, the “linking in progress†screen flashes up and then it goes to a blank explorer screen. There appears to be no traffic on the network, just a power light on the isy, no flickering on any modules. Anyone with any thoughts?

FYI, have had no issues with a Kohler whole house generator (non inverter). It does provide a delayed start for the AC, and I use the isy to shut down the electric water heater after a power failure.

Michael, Thanks.

Michael, A nudge in the direction of the many work arounds would be appreciated.

I ran my EZflora in parallel with the existing controller without any problems. I just removed the programming from the rainbird controller. It was easier, at the time, for my wife to do some quick watering from the rainbird. We pump from a creek which is fresh water, but is also tide effected so I can't irrigate on a fixed schedule as at low tide my pickup is out of water. The old controller in time died, so now the EZflora is the one and only. Have had no issues with it. If you don't have the manual for your existing system, look around on on-line. That should help you identify the wiring. Once you have that, you should be able to match it up to the documentation for the EZFlora. Paul

I'm also interested in the answer. Paul

If I have a program with no if condition and set it for 'startup' will it run the 'then' after a power failure. And, do the 'startups' run before or after the schedule catchup?

With our layout, the only way I could have good x10 communication was with the use of Smarthome boosterlinc's which gave me solid performance. However, as I added more Inseton devices, (at about 25-30) I did start to see bright / dim issues with x10 which I attributed to signal absorbtion . At that point I just made the decision to move more quickly to insteon.

Have you checked to see if any of your devices are v35. I had considerable problems similar to yours until I had them all replaced. Since then, life is good.

Just a side note. I have at least 10 magnetic transformers on insteon dimmers and have never had any issues. Many of them are used daily, and have been in use for years. Paul

Changing link mgt mode made the difference for me! It is a 2486D v36 6 button unchanged. Appreciate the help from you both!

Well, here is my level 3. I had reset all to toggle before starting the log. This was from just setting "c" to toggle off. Tue 11/30/2010 06:22:16 PM : [12 C1 31 1 ] Memory : Write dbAddr=0x0249 [10] Tue 11/30/2010 06:22:18 PM : [12 C1 31 1 ] Memory : EPROM Refreshed I should also note that at this time I do not have any links to the c button.

Lee, Thanks, will post the results when I get home tonight.

OK, back in the AM. A reset and restore of the device did not correct the problem. My question now is this a possible firmware issue, or a device problem? Or, something else...

Possibly time for me to upgrade firmware. Yes, I selected the button before changing mode, and bringing up the popup again reflects the "change". Have to move along for tonight, will report back tomorrow with the restore, and or upgrade effects.

Lee, It is a 2486 v36. Tried the 30 second power down, no change. LED still toggles on and off. ISY shows it as non-toggle off (set via ISY). If there are no know issues, I will do a factory reset and restore. ISY 2.7.15

I have set up a button on a kpl to non-toggle off. I am still seeing the led turn on and off with each push, and the following events for a double push. Mon 11/29/2010 06:19:37 PM : [ 12 C1 31 5] DON 0 Mon 11/29/2010 06:19:37 PM : [ 12 C1 31 5] ST 255 Mon 11/29/2010 06:19:39 PM : [ 12 C1 31 5] DOF 0 Mon 11/29/2010 06:19:39 PM : [ 12 C1 31 5] ST 0 I was expecting no led, and an off for each push. Am I expecting wrong?