Michel Kohanim

HAS, What did you enter for your DNS server IP address? With kind regards, Michel yes -50000,null,null,null I left the IP Address, NetMask and Gateway settings, but removed the DNS Server (0.0.0.0) and no longer have the -500000,null,null,null message. The new message is: Failed to send message to: (my email address) I tell ya, I think all the settings in my router are correct. The ISY should have access to the internet / email

sloop, You will always get the Internet Gateway Not Found error since ISY cannot communicate with your router. This, however, has nothing to do with the ability for ISY to communicate with the internet. For the gateway, you should still enter your router's IP address. For DNS, you should enter the DNS server address in ISY's config shell. Please send me an email and we'll walk through it and get it resolved one way or another. With regards, Michel

sloop, But you didn't get the 50,000 error which means that ISY couldn't communicate with our mail server. Can you please try TM one more time? Thanks so very much, With kind regards, Michel P.S. I cannot believe the Verizon people. It just doesn't make sense.

HAS, Please see my comment to sloop (previous thread). Thanks so very much, With kind regards, Michel yes -50000,null,null,null

Hi HAS and sloop, Here's the issue: ISY cannot get the IP for our mail server; the reason, DNS (Domain Name Server/Service) is not available to ISY. If you remember correctly, for the DNS server, we used your router's IP address which is really not a DNS server. What we have to do is to figure out what is your ISP's DNS address. You can find this in your router; something along the lines of: Domain Server 1: Domain Server 2: Then, all you have to do is to go back to ISY's shell, issue CT (configure TCP/IP) and enter the DNS server IP as found in your router. I hope this helps and please do let me know of the outcome. Thanks so very much and with kind regards, Michel

HAS, I am so very sorry to hear this. 1) You don't have to do anything with your modem/router to send a NOTIFY as long as you're on DHCP (i.e. your router assigns the DNS address). So, let's try to resolve this issue before anything else. a. Do you have the right email address in your Configuration page? b. Please try logging with telnet to our box (telnet your.isy.ip 126) and issue TM (test mail). Please let me know what you get. With regards, Michel

GPG, Would you be kind enough to PM me your external IP address/ISY port? Let me see if I can get to it from here and, if so, then we know it's a firewall issue on the computer you are using to access your ISY. Thanks and with kind regards, Michel

The code is completely modular and can be made into an application within a day. In short, yes it is possible but not in the current incarnation. With regards, Michel

sloop, Thanks so very much for the detailed instructions. I really do appreciate it. With kind regards, Michel

GPG, I am so very glad that we could resolve it and thanks so very much for giving us the opportunity to resolve it remotely! Please don't hesitate to contact us if you have any other issues with ISY. With kind regards, Michel

GPG, Thanks so very much for taking it upon yourself to do this. Shortly, I will send the instructions to your private mailbox. Again, with sincere apologies for the inconvenience, With kind regards, Michel

GPG, Unfortunately, I think you have a corrupt file system. Do you have a recent backup of your configuration? In short, we can do two things: a. We'll gladly pay for the shipping and have you send us the unit to fix b. If you feel up to it, I can guide you through fixing the issue. It would be great if you have an extra SD card ( Sincere apologies for the inconvenience, With kind regards, Michel

Sloop, Wow! Thanks so very much. Here are my comments: Any for the source port is not correct. In effect, what you are doing is creating a "DMZ" device out of ISY; this means that all requests to any ports on your router will be directed to ISY's port (16618) which, of course, cannot handle any other requests except those that it understands! So, in short, the source port should be = destination port = the ISY's port (16618 in your case). Protocols should be: Application - TCP 16618 -> 16618 -7029 means that ISY tried to configure mail service but you don't have any recipients -80000 means that although your router furnished a URL throughwhich we can configure UPnP, but when we tried to get the description, it returned 404 (not found). If you have a static ip address and port forwarding setup, then you can ignore all errors starting at 80,000 -2 means Device communication Error with the device at the given address; so, ISY starts querying all your devices at startup. In your case, two of your devices did not respond: 7 D7 19 and 7 E7 1B Do you know why these devices fail to communicate? We finally found a "hidden" workaround to resolve McAfee issues which doesn't require you to disable the Redirector Service. Please checkout this topic The only issue I see is using Any as your source port (in port forwarding). You do not need to register but we do surely appreciate it if you did.

My pleasure. Very much looking forward to resolving this issue. With kind regards, Michel

GPG, Hello and I am so sorry to hear that you are having trouble with ISY. I don't think what you did has anything to do with double solid lights. But, before you do factory reset, please reboot ISY and look at your hyperterminal for any startup failures. Would you please let me know what you see. Thanks and with sincere apologies, Regards,

Mark, Yes but with the pre-condition that you cannot use KPL buttons to do an All On/All Off if the KPL load itself for those buttons is going to be part of that scene. So, if you want an All on/All off scene using your KPL buttons, you have to use the KPL load button as the controller for that scene. If you want to control only the load for that KPL, then simply do a Synchronized Group between the KPL load button and another button which is going to control only the load; i.e between KPL button A and KPL button 1/load. The effect is that from now on every time you click on the load button, the whole scene turns on/off. When you click A, only the load for the KPL turns on/off. I hope this makes sense. With kind regards, Michel

HAS, You are right! I think sloop has already tried this so he might be better able to help you with the gizmos and scary things! As far as the port, you don't have to assign a port to ISY. ISY already has its own port: a. Right mouse click on My lighting b. Click on Properties c. Look at the Device Address you will see something like: http://192.168.0.105:16872/0/p.html In the example above 16872 is ISY's port for my device. I hope this helps a little. With kind regards, Michel

Mark, We are trying to figure out what we can do to alleviate these scenarios. As of right now, there are a couple of "ugly" workarounds that we are considering! I shall keep you all updated with the progress. With regards, Michel

Hi Sloop, Long time no see! EI in the shell is equal to File->Enable Internet Access. If I may, I would like to explain the sequence of events at ISY start up: a. Start Network Services (make sure we are on the network and an IP has been assigned) b. Initialize Filesystem (make sure we can get access to the file system on our SD card) c. Initialize Device/Nodes (make sure we can communicate with all the devices configured in ISY) d. Start Logger/UPnP/HTTP/D2D ... (low level services) e. Look for an Internet Gateway: i. This issues a UPnP Search Request for all the UPnP Gateway devices on the network ii. If one is found, and if Enable Internet Access has been issued at some time before ISY startup, then try to communicate with the router and get the necessary information to create a port forwarding rule in the router. This may fail if the router does not want to give out that information in which case the status of Internet Access becomes Disabled iii. If one is not found (i.e. the router never responded to the UPnP search request), then the status of Internet Access becomes Disabled When you get "null", it means that the router did not want to supply "port forwarding" information in step ei. Now, I have to emphasize that not being able to enable/disable internet access has no bearing whatsoever on the operations of ISY. As far as your router not being able to assing an DHCP address, that's quite strange because that function has nohting to do with UPnP. If your other devices on the network can be assigned a DHCP address, then we surely have to get one of these ActionTec routers and figure out why that is the case. With regards, Michel

GPG, Apologies for tardy reply. Mr. Sanctuary tried automatic configuration with BEFSR81. Have you tried Enable Internet Access with the new release of ISY (2.3). If so, are you still having issues? You are 100% correct vis-a-vis remote access 101. In short, you would have to create a Port Forwarding rule in your router. This said, however, if your ISY is being assigned DHCP addresses by your router, then you might run into an issue where ISY is assigned a different IP address (at some point) and thus your port forwarding will no longer work. So, here are the instructions: a. Make ISY use a static IP address: i. In the Run dialog, type: telnet your.isy.ip 126 ii. type CT (configure TCP/IP) iii. enter the desired IP address for ISY iv. enter the mask (usually 255.255.255.0) v. enter the gateway IP (usually the IP address of your router; i.e. 192.168.1.1) vi. enter your DNS IP (you have to look at your router's configuration page for this address) vii. you are done; wait for the system to reboot b1. For Linksys, open up the router's adminstrative page i. Go to Applications and Gaming ii. Go to Port Forwarding (sometimes, it's under UPnP) iii. Create a rule such that all TCP (not UDP) traffic directed to ISY's port is handled by ISY's static IP address b2. For DLink i. Go to Firewall tab (under Advanced) ii. Follow steps ii and iii in b1 (above) Please let me know if you run into any issues. With regards, Michel

HAS, Excellent question! The best option would be for us to get one of these routers and figure out what it takes for us to do it automatically. As far as I remember, the router is an Actiontec (MI424-WR). Do you know where we can buy one since the last time I checked it was a discontinued model and we couldn't buy it. To enable internet access manually, you have to do Port Forwarding. Unfortunately, in the case of sloop, ActionTec did not allow Port Forwarding for devices which were not issued an IP address by the ActionTec (DHCP). Have you tried port forwarding? In short, what you have to do is: a. Have your ISY use a static IP (if it's DHCP, then since ISY is not taking care of the forwarding, then when ISY gets a new IP, your port forwarding will not work) b. Go to the firewall configuration page in your router c. Forward all the TCP traffic directed to ISY's port, to ISY's IP address This should do it. I would sincerely appreciate receiving your feedback and experiences in this regards. Thanks and with kind regards, Michel

HAS, It makes perfect sense and quite elegant. Thanks so very much for the feedback. With regards, Michel Thanks for the understanding. My suggestion (i guess in a round about way) is to NOT put the bath fan (exhaust fan aka **** fan) on any sort of automation. Just replace the standard wall switch with a wall switch timer, llike the Intermatic I mentioned. As fun as automation is...some things don't need to be automated.

HAS, Not only you are not stepping on any toes but also we consider all suggestions and feedback invaluable. Here are some minor issues with the configuration as you suggest it: a. If your timer cuts power to your Insteon device, then you will receive "Device Communication Error" in ISY especially if there are some other functions (schedules/triggers) which need to communicate with that device b. There's probably not an easy way for ISY to figure out whether or not that device is on/off. You may decide to create a schedule to query the device every n minutes, but even that will fail if the timer cuts power to your device (see "a" above) So, in all likelihood, ISY's state will be out of synch with the actual state of the device being controlled by the timer. In short, you have an excellent suggestion if: a. You are not concerned with ISY being in synch with the actual state of your device b. You don't have any schedules/scenes/triggers which reference that device c. You have an extra space for a timer next to your device Thanks and with kind regards, Michel

Greetings HAS, Thanks so very much for your willingness to try this suggestion. Yes, you are 100% correct; there's collision and we should add a "wait" between the requests. We are working hard to release our trigger/scheduler functionality very soon so that we can get the scenario also resolved. Thanks again for the feedback and your support, With kind regards, Michel Greetings, I tried the above, and it kinda/sorta worked. It seems as if the signals are crashing into themselves, only allowing this "work around" to work intermittently. I worked on this "ALL OFF" scenario for many hours now, using various triggers and the conclusion is always the same; will not work 100% of the time. I think some 'delay' options need to be added before we (at least in this case) can control KPL button lights, with buttons on the same KPL, to eliminate the collision.

HAS, Would you be kind enough to try the following: a. Create a scene called whole house b. Drop in all your devices in there as responders c. Drop in D as the controller Next: a. Create a scene called KPL All Off Scene b. Drop in all the KPL buttons in there as responders c. Create a trigger such that when D is off, KPL All Off Scene is turned off With regards, Michel Works! Yippie! OK, how to make the A,B and C KPL lights go off when D (all off) is pressed?