tome

Actually, you probably are not going out over the internet, the router is probably issuing a redirect for the dyndns address which it knows is local but in any case.... I will assume that you didn't create a SSL cert for the ISY and that it is using the default cert for now... To take port forwarding out of the picture...what happens when you go to: https://10.0.1.196 in a browser window while on your local network? Tome

First, in regards to iLinc... I have iLinc configured with my local address and my remote address. It will use http (local address) when it is on the local lan via wifi. It will use the remote address via https when off my local net. I don't understand why you say you want two http addresses? Also, iLinc allows multiple profiles, so if for some reason you really do have/want two local addresses you could set up the other in a different profile. Regrading not being able to connect via https... You have not created a SSL Certificate from a MacOS device have you? There is a problem with certs created and installed from MacOS X at the moment. If not, then make sure the ISY in the Configuration tab is set to port 443 for https and that you have SSL Port on iLinc Pro set to 443 as well. Also, in iLinc the Connect Method should be set to Auto. Tome

Hmm, perhaps I am beginning to learn something... I looked at the Links Table for all the devices. The non-dimming switchlincs had A2 and E2 links for all the other devices. The dimmer did not, it had 62 and 22 links for all the other devices. From this page: http://www.universal-devices.com/mwiki/ ... Tools_Menu I see that 22 is "deleted" whatever that means, and 62 is not there so I don't know what that is. Anyway, I decided to do a restore device on the dimmer and now the Links Table shows A2 and E2 links like the others and it works!

I have a (high wattage) Switchlinc Dimmer tied to a load of outdoor incandescents (11 75W floods). In addition I have 3 other Switchlincs (non dimmers) at various locations. I want it to be a 4-way circuit, such that when I press any of the switchlincs it causes the dimmer to go on. I create a scene called OutdoorLights and put the four devices into it (all as controllers) and it doesn't work. Behavior is: 1) When I turn on a switchlinc (non dimmer) the ISY indicates all devices in the scene are on. In actuality, the non-dimmers go on, but the dimmer does not. If I tell the ISY to then query the dimmer it shows it's true state of Off. 2) When I turn on the dimmer, all the switchlincs go on and so do the lights. If I then turn off one of the non-dimmers, the scene indicates off but it doesn't really go off. Again, causing a query in the ISY then shows the true state of the dimmer (which is on). I just installed these switches so I don't know if this is something I am doing wrong, a bug in 2.7.9, or what? All the Switchlincs (dimmer and non-dimmers) show as version v.37 in the ISY display. All were factory reset before I added them to the ISY. Tome

Can the ISY tell me if communications to each device is excellent, good, bad? I understand I can watch the Event Viewer when I do something and see if the command sequence is right, but that requires me to know what the sequence is (I know basically but not details yet), and to be able to see a missed command. Is there another way? Seems like the ISY knows if it had to repeat a command or got no response, etc. and could present this information in a clear format. It would be nice if the ISY kept for each device either an overall grade (E, G, or better, a percentage of successful commands (100%, 80%, etc). Tome

I installed the existing certs and that didn't change anything. I will send email. Tome

Yes, it is set for 443. PS: I just set it again to be sure and it rebooted the ISY. I am sure the port is right as I can see packets in and packets out to/from the isy local ip address and port 443. Tome

No, if I try https://192.168.X.X:443 on a local machine I do not get anything either. I can get to http://192.168.X.X:80 though.... Tome

Mine are jibberish. Below is one partial example. Yes, I know I shouldn't post a cert, but I have created new ones since this one and this is only partial but goes on like this... No matter how many times I create certs they look similar to this and I still cannot get access to the ISY remotely... MTI5OjM6MTI5OjY1OjY1OjY0OjY1OjY1OjYwMwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI6cpGkuOS+SlA1jDDgo9g2vVhknerAIbc3SzjBvUlR0Wmyi/FRTfZUgiJsp/8m5LuZ7wettP7FH a8VukANscbiTdGEBHJRv0nyPv2cHzt7tHiMpU/jlE5bht8dz01jmauWbbkgX2ClZQ/eA1VrIMwuN eBWhajjOBEsyOw5UMmeVAQABAIwWcSZk4oXJradsyV8NVY5h0uiIsGrlDL+nOSW45J3TYdPfUpCfJvhraeVJn1sPjnOX1AioW22Q Y9wf3FWQnC+kz44Ysmn98+N3BYcPMymfy/9odYo7Vcj61ueWgH25jWXUBaQcCXG43SCsTjdhlfko 1R7+6Z1P49IW6QHIYeVhAMh28Cw9WojlBqFCF+7HMdEXpnLJRTGWq2QNZnOe+Id+GgAcgRBZUHq9u+eqwNzEIkutbB8Ig3qK /erk6E6MkW0=ALYewcIAR9zDkNdo00e86tN6a1+VDuV8Qi6FLSUHAb10pURScObjrJa+aGJ/NEJhMWefqP8GZrkb S7N2lCbafck=Nz+AZdDq+LuWHi9nBSnk8ul/uDb8WPRbfBGtYMQ5Xq5EYC966pSS96D+/pQy3yU3BoBfQhZIlidk X66Cz9Mx6Q==AIiV0pzr1vlz1monXOWdgsQuON8LjIuBwKThDnWJpr1vAQ+XgMM5F1RK40CTxB7Qg9wCex0gsOO8 JPQ1bAbb6qs=MIICVzCCAcCgAwIBAgIEYq1XcjANBgkqhkiG9w0BAQUFADBwMRowGAYDVQQDExFlYm91bmQuZHlu ZG5zLm9yZzEMMAoGA1UECxMDSVNZMQwwCgYDVQQKEwNVREkxFDASBgNVBAcTC0xvcyBBbmdlbGVz MRMwEQYDVQQIEwpDYWxpZm9ybmlhMQswCQYDVQQGEwJVUzAeFw0xMDAxMDUyMDMxNTVaFw0xNTAx MDUyMDMxNTVaMHAxGjAYBgNVBAMTEWVib3VuZC5keW5kbnMub3JnMQwwCgYDVQQLEwNJU1kxDDAK BgNVBAoTA1VESTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxEzARBgNVBAgTCkNhbGlmb3JuaWExCzAJ

Can someone look at their ssl certificate that was saved and see if there is any readable information in it? Other certs I have on my mac have clear text info in them showing the host they are for and a few other bits of info, the rest is jibberish. The cert that the UDI app created is pure jibberish. Is that normal? Tome

I have a static address on the ISY, and as I said I can see the ISY responding to the connection request. Remote access has worked fine for weeks. It was only after installing the SSL Cert that it broke. This has to be a problem with the ISY rejecting the connection for some reason or other. Tome

Yes. In fact, I turned on logging and watch the packets come in to the ISY and port 443 and go out from the ISY to my iPhone (or computer)... Tome

So, it turns out I cannot access the ISY at all remotely. This isn't just iLinc, even from my laptop I am getting no response. Something is wrong with the ISY related to SSL Certs. What can I do to resolve this? Tome

1. From the Admin console on my Mac, I select 'Request/Manage SSL Certificates' from the Help Menu. 2. A window opens and I have to log in again. 3. I select 'Generate & Install New Self-Signed Certificate' 4. In dialog I enter: myhostname.dyndns.org (not really myhostname, but the one I have registered) select 512, or 1024 (did both) checked save ISY reboots after each cert creation. Same result. If I connect via wifi (local ip address and port 80) iLinc works fine If I turn off wifi, using myhostname.dyndns.org and port 443, I get the failure to connect error. I looked at the logs on my router and I see the requests coming in and being directed to the correct ip address and port, and I see the packets going out from the ISY (local ip address) and port which are the refusal (I assume - since I cannot look into the packet). How do I check this? When I look at the saved cert files in a text editor they are gibberish, there is nothing readable in them... I do know that after I created the 512 byte cert and went to create the 1024 byte cert the ip address in the dialog box was automatically filled in correctly (though I changed it back the dydns hostname before saying OK). PS: I also removed and reinstalled the iLinc app on the iphone but that didn't help... PPS: Just for grins I used the external ip address rather then the dyndns hostname when generating the certs, but that didn't help either... Tome

Thanks for the tip, Michel! I will give it try. Tome

How does one remove previous certs from the iphone?

I was talking with the iLinc developer and he says iLinc Pro should be able to handle any cert the ISY gives them. I wonder if 2.7.8 has a bug in it in regards to SSL certs...? Basically I cannot connect at all to the ISY from iLinc if off my local network...

I generated a self-signed cert and installed it today as I was getting the warning about the default cert when off my local network. However, after I did this I realized that now I cannot access the ISY though iLinc Pro application on my iPhone. I keep getting "Failed to Connect" errors and I assume it is due to the new cert that is in the ISY but not in my phone. I don't think iLinc allows me to install a cert (I don't see that as an option anywhere). So my question is...How can I remove my self-signed cert from the ISY and go back to the default? Thanks, Tome

I am experimenting with programming lights reacting to a motion sensor. I have one condition that creates a problem in the logic I used. That is, if someone physically turns on the switchlinc during the day, my lights go on and stay on - Good. If they turn on the switch in the evening, my lights go on and stay on - Good. But, if they turn on the lights before evening, and evening comes (sunset on the ISY), the lights will go off.... I want to keep track if someone turns on a switchlinc before "evening" (aka prior to sunset) and if so, use that fact in an If statement after sunset. I have a program named ControlStatus: If From Sunrise To Sunset (same day) And ( Control 'Foo' is switched on Or Control 'Bar' is switched on ) Then - No Actions Else - No Actions This will be true if someone switches on a light before sunset but will get re-evaluated and be false after sunset. How can I prevent it from being re-evaluated so that I know the switch was turned on earlier?

I believe it is actually 15 minutes after the MS has sent the Off command, or 20 minutes minimum since last motion, because the Off command causes 'Last Run Time' to increment. Gotcha. I guess you could add the 'And Program Evening is True ' to limit it to evening only. Thanks for the info. From a little bit of playing around, I don't think it makes any difference to the 3 variables that the ISY is able to control. My speculation is that Smarthome with Houselinc is able to manage all the other jumper settings based on the setting of jumper 5, but the ISY isn't able to (yet?). Tome

Hi Michel, Thanks for the response. I can think of several reasons that one might want to have the ISY run during a power outage and to know the status of the PLM... 1. I will have an ISY at a remote site that has UPS (and generator) for some circuits including my phone system, internet access equipment, and LAN gear. I will remotely monitor the ISY (and other equipment). 2. If I am using Insteon thernostats to control/monitor my HVAC system, which is backed up by generator) and the ISY is unreachable, then so is my HVAC system. 3. I would view it as a feature for the ISY to be able to log power interruption events by being in communication with the ISY. 4. The UDI network module supports running a web server on the ISY. If I was using it for that purpose I would certainly want it on UPS! I think you (UDI) need to think outside your current box on what the ISY is and what it's capabilities are. Thanks for listening! Is it under My Programs or is it hidden in the ISY? If the former, I must have deleted it... Tome

Ok, so to see if I understand what is going on (and to see if you understand what is going on )... You can set the timeout ONLY to be as short as the Off timeout on the MS, right? That is, if you set the 'For 15 minutes' to 'For 1 Second', the lights will go out at 5 minutes (which is what you have your MS timeout configured for) +1 second. You can configure it any number of seconds/minutes/hours longer then 5 minutes but not shorter, am I right? With the off program above, anytime (day or evening) someone is in the room you will be sending Off commands for the scene every time the MS is tripped then times out, won't you? Tome

And what about jumper 5? Thanks Tome

So here we are nearly two years since the last post in this thread and 2.7.8 is in testing. I am curious what the expected behavior now is if I put my ISY on a separate power supply? Does the ISY know when the PLM reports a power outage, or that the PLM is not reachable due to a power outage (or other problem)? Does it stop executing programs in that case? Does it know when the PLM becomes reachable and will it sync the status of devices and resume programs? Is there still a 3am query in the ISY? Thanks, Tome

I like your approach. Out of curiosity, what is your Timeout set to? Also, what are your jumper settings on the MS?