Michel Kohanim

HAS, Don't throw in the towel yet. We'll figure it out. So, let me get it right: You are on DHCP You can access your ISY remotely But, email notifications don't work If so, please do me a favor: 1. Click on configuration 2. Remove all recipients 3. Add a regular email address 4. Click on save 5. Create a simple trigger with Notify as the response I'd appreciate your feedback, With kind regards, Michel email failing / no gateway issue

Rand, I am glad your fears are alleviated ... unless, of course, I've been given the wrong information by SmartLabs. I've sent an email to get a confirmation and I will let you know if I am told otherwise. Thanks so very much and with kind regards, Michel

sfhutchi and Mark, We are working on it and should have a work-around in the next release. With kind regards, Michel

Hi Mark, This is "the workaround" for now but the main issue is that the status of the load is not reflected in ISY using this method. We are looking for a another workaround (in the code) to update the status of the load when a synchronized button attached to the load button is on/off. This is going to be very ugly but we think it's a needed feature. With kind regards, Michel

Rand, Hello. You are correct! PLM is supposed to allow for 417 links. So, I don't think you will run out of PLM links any time soon. Does this answer your question? With kind regards, Michel

Rand, Wow, I just realized that this submission of yours had remained unanswered. My sincere apologies (can't trust the auto notificiation). In case you exceed 255 nodes (device/scene), you will have to get a our new product which handles 512. I've yet to see anyone going beyond the 210 devices (for a 12000 sq feet house) and 45 scenes. With kind regards, Michel

HAS, Please try the Any for source port ( I was wrong ... it has to be Any since we tested it with Sloop and it didn't work any other way). We will figure this out one way or another since out of the 3 clients with ActionTec/FIOS, yours is the only one that seems to be causing problems. Please let me know if you wish me to call and get this resolved quicker. With kind regards, Michel mine too! Did ya see that by clicking on the Globe? I saw my Gateway was 71.180.***.* I've tried ALL those....blah LoL

sloop, Thanks so very much. We can cautiously assume that all Verizon customers use the same DNS. And, YES, I read your instructions to another one of our customers and BOOM: it all worked! With kind regards, Michel

HAS, 192.168.1.1 is your routers IP; I am not sure this would work. Would you like me to call you and walk you through this? Thanks to sloop's instructions, another one of our customers with ActionTec/FIOS modem was able to configure his ActionTec/FIOS modem and it all works. 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

evarsanyi, The issue with triggers in 2.3 is that they work based on "state change" and not "button press". As such, if you have a non-toggle button, the state never changes (always off) and therefore the trigger is not run. Our new enhanced trigger/scheduler functionality rectifies this issue (2.4). With kind regards, Michel

evarsanyi, The Replace function (very similar to Replac Modem) will be available in our next release (2.4). I'd appreciate your patience. With kind regards, Michel

Rand, Excellent idea. The only issue is that I don't think most people would want to buy an extra InlineLinc for every KPL they have. In short, we have to find a workaround no matter how ugly it looks. Wouldn't you think? With regards, Michel There is no way to change the load button. It does not change going from 6 to 8 mode, only that links are created when in 6 button mode that are not present in 8 button mode. An option would be to use an InlineLinc for the load you have now and put no load on the KPL. Rand

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.