One2ManyLights

Thanks!

Thanks for the reply Michel, My Safari is on both an iMac & MacBookAir. The same issue happening on both computers. Creating a 1024 certificate did not change anything. I am not really too sure how to use the "Send Certificate Request to CA and then Receive Certificate" functions and form. My web address is an xxx.dyndns.org type, so would this apply in my situation? It seems like this problem is solely a Mac OSX and/or Safari issue. Something has changed on the Apple side. The following process improved things a little: - I delete the ISY99 certificate from the Mac OSX "Key Access App" (this is where Macs stores all of their certificates and passwords. - Used Firefox to access my Https://xxx.dyndns.org address. This then lets Firefox put the self generated ISY99 certificate into the Key Access App rather then Safari. This now makes Firefox work perfectly and Safari only gets one warning rather than two. The warning that Safari still gives is "Safari can't verify the identity of the website". I must acknowledge this each time before I can continue to the big blue Universal Devices screen were I enter my name and password. Next, if I select the "Admin Console" I am taken straight to the Java app log-on with no warning messages. Using Firefox to add the certificate to system eliminated the second Safari warning, which would appear just before the Java app log-on screen. Anyways, this crazy little annoyance has eaten up way too many hours. Hopefully, this information might somehow assist another user or at least stop them from beating it to death. Thanks for the help! Mike

I am running the following: ISY99i with firmware v3.2.1 Mac OSX Lion v10.7.4 Java for OSX v1.6.0 Safari v5.1.7 My SSL certificate has been generated with 512 strength and is installed. When Safari is used to log into the ISY99 via my ddns web address locally I get the message: "Safari can't verify the identity of the website" So next I chick on "Show Certificate" and check the box "Always Trust". The problem is that the box will not stay checked and I always get the warning message. FireFox v13 for OSX has accepted my self generated certificate with no trouble. Could my certificate strength have been set too low for Safari? Has anybody else seen this issue? Any help would be greatly appreciated! Mike

Thanks very much LeeG! The solution you provided worked. I have read similar posts where you addressed basically the same issue, however this time I finally understood. As a new user my confusion came from not fully understanding Scenes, Controllers, and Responders. Just thought that a Scene was a group of lights that could all be controlled at the same time by the ISY99. In my case there is a table lamp that can be controlled by two different controllers (Icon switch or Lamplinc plug-in). By creating a scene and adding both the Icon & Lamplinc (defined as controllers). The current state of the table lamp can now be both known and controlled by either the Icon switch or Lamplinc via the scene. In other words the scene creates the ISY99 connection that I needed. When I first began, a stand alone link was created between the Icon switch (controller) and the Lamplinc (Responder). Given that I am now controlling everything though the scene this link was not needed and is now just redundant?

I have a LampLinc plug-in dimmer (2457D2X) controlling a table lamp through my ISY99. This works fine. Next, I added a wall switch (2876SB) to control the same table lamp and this also work well. This switch has no load attached, it is just linked as controller of the Lamplinc. So, my table lamp can be controlled from the ISY99 or the wall switch. ISY99--->LampLinc 2876SB--->Lamplinc Question: When the wall switch is linked to the ISY99 why can't I send a command to the wall switch from the ISY99 and control table lamp? The wall switch receives the command and clicks on or off, but the table lamp only responds if I physically tap the wall switch button. ISY99--->2876SB--->Lamplinc Any help on this would be greatly appreciated!