GDavis01

A double tap (or click) in ISY Finder, on the http:// addresses of the remote ISY, does nothing!

The remote ISY is not on a Beta. It is currently on version 4.2.18. My local ISY is on version 4.3.1. Am I supposed to be using different ISY Finder applets for these two versions? The ISY Admin Console icon opens up the ISY Finder and my local ISY Admin Console. When I go to the actual ISY Finder and try to add in my remote ISY's DDNS address https://mycottage.ddns.net:443(not my real address!) or the actual address (https://xxx.xxx.xxx.xxx:443) I get a series of errors as follows: XML Parse Error https://address/desc Socket Open Failed javax.net.ssl.SSLHandshakeException:Remote host closed connection during handshake Not Found However I am able to add the same addresses using http://! Any ideas on why the https:// addresses are not recognized? I am still able to log into the remote ISY using the https:// addresses when I go the browser route! With respect to the ISY Finder... how do I actually launch the remote Admin Console once I have an address added? The Admin Console for my local ISY is automatically launched when I click on the Admin Console icon on my desktop but I haven't figured out how to launch the remote ISY's Admin Console from the ISY Finder (even using the http:// addresses)!

I am using Safari! What do you mean by this? Is this the admin.jnlp file? If so how do I set this up for a remote ISY connection? Whenever I run the file it opens up my local ISY Admin Console!

I am on an iMac running Yosemite. As I understand it the older versions issue is a Windows issue. However, I did delete Java from the iMac and then I reinstalled it. I am no longer getting the error saying that Java is out of date... but I am still not able to get to the Admin Console! After I click on the Admin Console button a browser page opens which shows the Universal Devices logo and the message "Please Keep This Windows Open!". Normally I see the Java logo below and the progress of it loading before the Admin Console opens. However, now instead of the Java logo I am getting a box with "Error. Click for details". When I click I get another box: Application Error ClassNotFoundException com.univeraldevices.client.ui.UDClientApplet.class

I have two installations (home & cottage) and up until a few minutes ago I was able to log into the cottage ISY, from my home computer, and then startup the Admin Console. However now when I try, I can still log into the remote ISY but when I try to open the Admin Console I get the message that "Your Java version is out of date." I had already updated my Java version on my home computer to version 8 Update 51 just prior to this problem starting! This is the same version that the message is suggesting that I should update my computer with! I have also confirmed that my computer is in fact running this version of Java! Any thoughts?

Here is the table (Thanks for the explanation on how to attach the file)

Is there a way to attach a spreadsheet table in this forum? If so can someone please direct me to the procedure...

Edit... the pasting of a spreadsheet didn't work at all!! I have removed the table and will have to figure out how to put it in correctly! No I do not have the latest units with dual LED's. Until you raised the issue I didn't realize that the 4-tap test could be applied to any dual band module! Very interesting... below is a table of tests (hopefully the table copies in properly!) that I ran through doing the 4-tap test on different units and how I determined which devices were on which phase. I started with the premise that the PLM is on phase 1. Note that I was able to conclude on which phase each device was on only after going through the various tests and then determining that the results of specific modules from the earlier tests were in fact anomalies caused by the devices presumably not receiving the RF signal or hop. I put bold boxes around the devices that had anomalies. As an example, the Family room (3) module stayed Solid White when I tapped the PLM and also when I tapped the Lamplinc, which I had already confirmed was on the opposite phase to the PLM... so my next test was to tap that particular module (test D) which caused the Lamplinc to blink green. This allowed me to conclude that it was actually on phase 1, despite the fact that it did not blink when I tapped the PLM! Similarly the two back stairs modules (6 and 7) initially appeared to be on phase 2 but were probably simply out of range. Test D,E and F confirmed that they are on phase 1. Tests A and B allowed me to conclude that there were other units on opposite phases and therefore the Lamplinc wasn't really needed to bridge the phases, since the results were exactly the same for all other devices. Test F, where I tapped the Back Stairs bottom wall dimmer seems to suggest that this module is having the most problems with communications, judging by the 6 anomalies! That module is a 3-way switch controlling one set of lights with the Back Stairs Top switch, so I ran test G by tapping the other switch in the 3-way (Back Stairs Top) and the results are a bit different in that the communications seem to be much better with the exception of 1 module (Soffits Side # 12). The Back Stairs bottom wall dimmer is in a gang box with 2 other dual band dimmers (Bar Accent and Bar Main)! Shouldn't the other two devices strengthen the communications of that device? Aside from now having a pretty good idea on which phase each of my dual band modules are on, I am also concluding that, if there are sufficient communications, then when the 4-tap test results in Solid White or Green Flashing devices then those modules are on the opposite phase; whereas a White Flashing or Red Flashing means that the modules are on the same phase.

Unfortunately I am back home and won't be back to the cottage for a week. Hopefully I will have the Filterlincs by then. I didn't think to try looking at the outdoor module when I did the 4 tap test! I will try it next time. I assume you mean by doing the same test in reverse, that I should 4 tap the outdoor module and then check other modules... right? (see below for my at home test) I decided to do some testing on my home installation and it has raised some questions in my mind! When I set my system up a few years ago I used a Dual Band Lamplinc to bridge the phases with the PLM. I have been assuming all along that I had to keep that Lamplinc in place to ensure that bridging. However when I look at the PLM's Quick Guide is see the statement Does this mean that my dual band wall dimmers which are a solid white after I press the set button on the PLM 4 times are confirming that I have bridged the phases? The only problem I see with this is that they are also solid white before I do the 4 tap test! Interestingly the Lamplinc now stays solid red when I do the 4 tap test from the PLM, which suggests to me that it is not on the opposite phase!! I'm almost certain that when I set it up I was getting a reaction from the Lamplinc that confirmed that it was on the opposite phase!! So... to see if I was encountering any phase issues, I removed the Lamplinc and ran a query all from the Admin Console (35 devices and 18 sprinkler zones on 3 controllers). The only communication error I received was for the disconnected Lamplinc! So I am assuming that I have successfully bridged the phases with something other than the Lamplinc. Does this make sense? Doing that same 4 tap test from the PLM I see that 4 dual band wall dimmers right next to the PLM are blinking white, whereas every other dual band device had no change (e.g. wall dimmers remained solid white). I also tried to do the reverse 4 tap test using another outdoor module, which I plugged into an outlet in my kitchen. The results were mixed in terms of which Dual Band devices reacted to the test: (note the devices below are only dual band) - 3 wall dimmers were blinking white; - 1 wall dimmer was solid red - 1 Lamplinc did nothing (remained solid red) - 4 wall dimmers did nothing (remained solid white) - 4 wall dimmers remained solid white... but occasionally dimmed - about every 10 seconds - 1 wall dimmer was blinking green, but every 10 seconds it would turn white and then go back to blinking green - PLM remained solid green How should I interpret these results?

As explained in an earlier post, I did verify the proper bridging using the 4 tap test. I think that you are probably right and that it is the transformer that is sucking the signal!! I disconnected it from the transformer and it does communicate! I guess I will have to figure out another way to deal with the landscape lights! I still think that I have noise issues because I am experiencing other communication issues from time to time. So the hopefully the Filterlincs will help.

As a test, I unplugged everything except the router, PLM and the ISY. I have another computer on another circuit. Using the Admin Console I am still not able to query the outdoor module!

Thanks... I have ordered 3 Filterlincs.

Interestingly, in my other installation (home) I have no Filterlincs and I haven't had any problems. My PLM is not on a dedicated circuit and I have a ton of electrical / sound equipment right next to it!! Lucky so far, I guess, with that installation!

I have started researching Filterlincs. Looking at the Aartech site (Canada) I see that they only sell the 10 amp model (1626-10). Is this the recommended model (Manual shows a 5 amp model)? Here is an excerpt from the manual... I don't have an appliance module so I will be using my Dual Band Lamplinc... what do they mean by a transmitter? I would assume that I would need to use the ISY which means that I need a computer and my home network (router) also running... correct? Another excerpt... Do they still make those? lol I haven't seen one in many years!! Just looked it up and they do still sell them!! I think I will buy one $14 and try that route too.

Thanks for the replies. My PLM is currently on the same circuit as my router, a distributed sound system, a plugged in laptop, a battery charger for my drill, a powered switch and the ISY... so based on the comments it appears that this may be my issue! I now have to find a new place to locate the PLM where I can connect it to the ISY, and the ISY to the home network! This might prove to be a temporary challenge. When I do I will post the outcome.

I used the 4 tap test on the PLM to verify that a dual band device was on the other leg (i.e. the Lamplinc). So when I do the tap test I see the Lamplinc blinking green. Despite this the ISY cannot communicate with the Outdoor Module.

I have a new ISY994i installation and I seem to be having problems accessing certain devices at times! I have 6 dual band Switchlinc Dimmers (2477D), 2 LampLincs (B2457D2), 1 Leak Sensor (2852-222) and 1 Outdoor module (2634-222). In terms of electrical set up within the house there are 3 sub-panels off the main panel. I used one of the Lamplincs to bridge the 2 phases. Am I correct in understanding that bridging the 2 phases only has to be done once despite the number of panels? Here is an example of a problem I am having... I linked the ISY and Outdoor Module using a plug within the house and it worked as expected. I then went outside and plugged my landscape lights into the module. Then sitting outside, using Mobilinc on my iPhone, I did a Sync with the ISY. Once again all went well and I could now see the Outdoor Module on Mobilinc. I then was able to successfully turn on the landscape lights with Mobilinc. Happy with this set up, I went to my indoor computer, linked to the Admin Console, to start programming the Module... however the ISY could no longer see the module and shows with a red exclamation point on the console! Any suggestions on how to debug this?

Yes, thanks, I saw that. I had a quick look at it and it felt like I was going to have to bare my soul to them in order to set it up! I generally am very distrustful of cloud services, so I try to avoid them when possible. However I will admit that it was only a 5 minute look at their offer... I will look closer when I have the time.

As I understand it, when I look at 'My URL' (Help -> About) it shows the manner by which I accessed the system. When I access it locally it shows the LAN IP address but when I access it remotely it shows the URL I used to access it. I too am surprised that the ISY would be able to see the No-IP Host name... is it possible that the ISY is simply showing a field that is picked up from the computer I am using to access the system?

Yes I was spelling the URL correctly. In fact, I was just copying and pasting from the No-IP site. My problem was the way I had set up the host within No-IP. I originally selected the Host Type as Port 80 Redirect whereas I believe that I should have selected DNS Host (A). I changed the Host Type to DNS Host (A) and now when I enter mycottage.ddns.net (not the real host name!) I can login into the ISY. When I look at 'My URL' (Help -> About) it shows "http://mycottage.ddns.net".So I realize now that I should always use the syntax https://mycottage.ddns.net:443 when l login. Am I correct in assuming that if my router does support DDNS and specifically No-IP then I would not need to have the No-IP app running on a computer 24/7 updating the Wan IP address every 5 minutes? So if I understand correctly, you do not keep port 443 open to the outside but instead have a 5 digit port open which is routed internally to 443... right?

If I understand your question, I see the respective addresses when, on the Administrative Console, I go to Help--> About (as I explained in an earlier post) On my cottage ISY 'My URL' shows the current external WAN IP address http://xxx.xxx.xxx.xxx and 'Internet Access' showed an old external WAN IP address https://xxx.xxx.xxx.xxx. I have now disabled the Internet Access so there is nothing there. However the WAN IP address continues to show under 'My URL'. Whereas on my home ISY 'My URL' shows the local network address. My understanding is that 'My URL' should show the LAN IP address as it does on my home ISY. I am just trying to understand why there is a difference. Just a thought... given, that I am accessing my cottage ISY remotely is it possible that 'My URL' simply shows the address I am using for access? So if I logged on to the Cottage ISY, while at the cottage and through the cottage network it would then show the local LAN IP address.

No I don't have uPnP turned on for either ISY. I have now turned off the Internet Access for the Cottage ISY but still have the WAN IP address showing for My URL. It doesn't seem to be affecting anything so far...

I only use https to access the ISY. The No-IP app sends the WAN IP address to No-IP and so I can find the address by logging into my No_IP account from anywhere. Since my ISP changes the IP address often I need the revised address to gain access to the ISY remotely. I would like to see if I can figure out how to run that app on a Raspberry so that I don't have to keep a computer running 24/7 at the cottage. I have a new Asus router which I believe is supposed to handle No-IP but I simply haven't had the time at the cottage to play with it enough. I want to have a DDNS service because eventually I will want access to my IP cameras / NVR. For the time being I am testing out the access with the free version but I will probably end up with a headache-free (!!) pay version. Interestingly I can access the ISY with the https://xxx.xxx.xxx.xxx:443but not with https://mycottage.ddns.net:443 (the No-IP host name). Perhaps it's the way I have set it up on my router... I will try to turn off the Internet Access and see if it impacts anything I do... Any ideas on why the cottage ISY 'My URL' shows the current external WAN IP address whereas my home ISY shows the local address?

Thanks for the reply. On my home ISY the 'My URL' shows my internal IP address 10.0.x.xxx and the 'Internet Access' as Disabled. I am guessing that I disabled it at some point to get around the certificate messages I was getting! It doesn't appear that I need it. I currently use Mobilinc to access this network. On my cottage ISY 'My URL' shows the current external WAN IP address http://xxx.xxx.xxx.xxxand 'Internet Access' shows an old external WAN IP address https://xxx.xxx.xxx.xxx I have been trying to setup up a DDNS service (No-IP) to access my cottage but accessing my network using the 'host' name has not been successful so far! (I suspect that I haven't mastered the port forwarding for this!!) However by logging in to my No-IP account, from my home, I am able to see the cottage's updated IP address, and then, using a browser, I can access the ISY with https://xxx.xxx.xxx.xxx:443. Can I just disable the Internet Access like my home set up and still get remote access? Why does the cottage ISY show the external WAN IP address whereas my home ISY shows it's internal IP address?

I recently installed a new ISY994i at my cottage. My ISP changes my IP address often (daily or more!). I noticed that when I check the ISY (Help -> About-> Internet Access) the address is not updated! Why would this not happen automatically? Am I correct in assuming that if the ISY has not updated the IP address then accessing the ISY remotely would not work? Edit: I'm using Firmware v.4.2.18