wrj0

Those were my tired old eyes. Prowl's still working fine, thanks.

TJF1960, try this link that worked for me. http://isy.universal-devices.com/99i/3. ... board.jnlp

Thank you, Michel. Anything I can do to capture the 2xx response?

OK, thanks. The router is a Linksys WRT160Nv2 that's worked well for the past few years - no changes to it during the time period when the Internet connection test quit working. Port forwarding is in use to connect to the ISY, and both UDP & TCP are enabled for that rule. From a remote PC, this works fine: "https://my.dyndns.org:443/rest/vars/set/1/99/1" (Also works fine from the local PC) So, wouldn't that indicate the router is doing it's job properly? Wonder if the way I have configured the Client Certificate on the ISY could be an issue? Generation of the required SSL certificate for the 994 is the only related change that I can find in my notes during the period when this problem started. I used the same procedure described in the Network Security Configuration Guide to create a self signed certificate for both the Server and Client. Regardless of the Authorization parameters used in the Network Resource (correct user/pw, wrong user/pw, no user/pw), the response is the same. Network Resource Test returns: "Error: Request failed." And "N/A" in the Resource Response window. Event Viewer, Level 3 returns: "Net-Resource: Failed connecting to my.dyndns.org" Thanks again for your input, Xanthos. Edit: posted while TJF1960 was posting - seems we both came to a similar conclusion.

The ISP's DNS server: dns-comm-cac-lb-02.southeast.rr.com

From both the local PC connected to my ISY-994, and from a remote PC on another network, nslookup resolves the TLD for my dyndns name to the DHCP ip address assigned by my ISP.

No router changes on my side. I did try a couple of other DNS servers in the ISY, but with the same result. Thanks again for your thoughts.

Xanthros: I tried 8.8.8.8 with the same result. DNS was setup identically in both the old ISY-99 and the new ISY-994. And both are (were) set to the same static ip address. Guess I'll keep playing with this occasionally as it is a nice to have function, but not critical. TJF1960: Sure. If I manage to get it working again, I'll certainly post the changes made. I'd really like to find out exactly what changed to stop this from working. Thanks for the ideas, guys!

Thanks, Xanthos. I've tried it both with and without the Connection Close header - same result. Can't seem to find a configuration that does work. The DNS entry in my ISY points to my router which in turn uses the ISP's recommended DNS servers. Good idea, though - I'll do some more playing. Curiously, this was working a day or so after your initial post on how to configure this setup. But, since then I've upgraded from an ISY-99 to an ISY-994, and upgraded revisions in both. So, I don't really know when the response quit working. I do appreciate your input.

Thanks, Lee. The intent is to use an external path to test Internet connectivity, per this post: http://forum.universal-devices.com/viewtopic.php?f=26&t=9201&hilit=check+internet

Hi. I‘m experiencing a problem with a Network Resource entry in my ISY994i/IR PRO, ver 3.3.8. This works fine from a browzer: "https://my.dyndns.org:443/rest/vars/set/1/99/1" But, this Network Resource entry fails from the Network Resources Test or when called from an ISY program: http://dl.dropbox.com/u/46376739/NetResErr.jpg Network Resource returns: "Error: Request failed." and "N/A" in the Resource Response window. Event Viewer, Level 3 returns: Net-Resource: Failed connecting to my.dyndns.org Integer Variable #99 does not change from 0 to 1. (Actual Host name and authorization have been changed above, but fail when the identical parameters are used successfully with the REST command. User/password has been verified to be identical to that used to log into the ISY.) Suggestions on what I am doing wrong will be greatly appreciated. Thanks.

Updated to 3.3.8 without any problems. mms.att.net messages are working great. Thanks Michel!

Michel: Will there be an option for others of us with ATT devices to be able to support MMS? Perhaps in a future ISY code release? mohansen: I agree, UDI support is truly remarkable.

Thanks for you efforts, jmed999. It would be great to have WeatherBug light data available in ISY programs. The only thing better would be to be able to read data directly from a Davis weather station on ISY's network.

A recent upgrade to an ISY994i/IR PRO (thanks UDI!) has been working well except for my Prowl network resources. Several other network resources are working fine; only my Prowl resources seem to have problems. After the upgrade to the 994 running 3.3.5, no prowl notifications are being received. A Test on the prowl network resource returns a popup message: "Error: Request Failed , along with 'Network Response: N/A" and the Event Viewer shows: "Net-Resource: Failed connecting to api.prowlapp.com" The prowl API key tests OK from the prowl site and the prowl resources configurations are the same as in the old ISY99. A test configuration example is shown below, with the Body content: apikey=&application=ISY&event=TEST ONLY&description=Test Notification\n The resources in the new ISY994 were copied from the ISY99 using the Restore ISY operation from the 99 backup file. All other resources, except Prowl, seem to be working properly. Suggestions on what to look at to identify the problem will be greatly appreciated. Thanks. edit: after careful examination of the Dashboard Network settings, my tired old eyes noticed a faint, grey check in the HTTPS Verify checkbox. After UNchecking that box and rebooting the ISY994, all is well now - Prowl is working fine once again.

Curious that MobiLinc reports Total kWh, as well as Power, Current and Voltage from the iMeterSolo. And, these vary appropriately as the load is turned on and off. Perhaps its an I=P/E calculation by MobiLinc?

Thanks for the reference to the wiki article. It indicates that these variables are available in custom email definitions: CV, CC, PPW, TPW, and PF. I’m able get TPW (total power used) from an iMeter Solo (19.89.d4) into an email notification: TPW=€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€14040 (in kWs). But, the other variables don’t seem to work for me. Using this statement in an email customization: CV=${sys.node.19 89 D4 1.CV} Returns: CV=CV Should I be able to get CV, CC, PPW, and PF from the iMeter Solo in an iSY-99i email customization? Thanks.

Having support for Variables in Network Resources would be very useful.

Brian, You'll just need to register with Prowl to get your own email address, then enter that into your ISY under Configuration | Email Notifications | Settings/Groups. Then in your ISY program(s) use the Notify operation to 'Send Notification To' and select your Prowl entry to send the message content that you have selected.

I've been using Prowl to receive both ISY and ELK notifications since last October, and have been very pleased with its operation.

Thanks, Michel. I've been watching these discussions with interest and am looking forward to seeing what changes that you may choose to implement.

Michel, I understand from your post above that Irrigation Requirement is calculated only at Midnight and when Cycle Complete is issued. During these hot summer days, it would be great to be able to water plants in the afternoon based on an updated, current Irrigation Requirement calculation (vs. the value calculated at midnight). Would you consider adding an on-demand Calculate/Update Irrigation Requirement command to the Irrigation module? Thanks.

Thanks, Michel. The ISY was indeed in Level 1, but I found the problem: I had previously issued the telnet DON command to try to track outside ip accesses. Turning off that command eliminated the extra Error Log entries. What prompted me to look into this was the situation where I could no longer open the Error Log - I had to clear it, then I could open the Error Log and see the entries previously provided, at least for a while. A couple of days later, I could no longer open the Error Log. Tools, Error Log, would causes the Windows wait hourglass to display for ~20 seconds, then the hour glass would disappear - no "Save log to..." was presented. After Clearing the Error Log, the "Save Log to..." was once again presented. All's well now.

Thanks for the response, Lee. Event Viewer is set for Level 1. Only began seeing this after upgrading from v3.2.5 to v3.2.6.

It seems I have a similar issue with the error log after upgrading to v3.2.6. I have a CAI WebControl board and am running WCLinc on a PC at 192.168.30.104. The ISY Error Log fills up pretty quickly with the polls from WCLinc as shown below. Didn't see this in v3.2.5 Error Log. Shutting down WCLinc stops the entries in the Error Log. Suggestions, please. Time User Code Message Fri 2012/05/11 15:43:31 System -170001 [HTTP] 192.168.30.104:2481->80 Fri 2012/05/11 15:43:31 System -170001 0: GET-->/rest/vars/set/2/19/1 Fri 2012/05/11 15:43:31 System -170001 [HTTP] 192.168.30.104:2482->80 Fri 2012/05/11 15:43:31 System -170001 0: GET-->/rest/vars/set/2/19/1 Fri 2012/05/11 15:43:32 System -170001 [HTTP] 192.168.30.104:2483->80 Fri 2012/05/11 15:43:32 System -170001 0: GET-->/rest/vars/set/1/65/32 Fri 2012/05/11 15:43:32 System -170001 [HTTP] 192.168.30.104:2484->80 Fri 2012/05/11 15:43:32 System -170001 0: GET-->/rest/vars/set/1/65/32 Fri 2012/05/11 15:43:42 System -170001 [HTTP] 192.168.30.104:2487->80 Fri 2012/05/11 15:43:42 System -170001 0: GET-->/rest/vars/set/2/19/-1 Fri 2012/05/11 15:43:42 System -170001 [HTTP] 192.168.30.104:2488->80 Fri 2012/05/11 15:43:42 System -170001 0: GET-->/rest/vars/set/2/19/-1 Fri 2012/05/11 15:43:52 System -170001 [HTTP] 192.168.30.104:2491->80 Fri 2012/05/11 15:43:52 System -170001 0: GET-->/rest/vars/set/2/19/1 Fri 2012/05/11 15:43:52 System -170001 [HTTP] 192.168.30.104:2492->80 Fri 2012/05/11 15:43:52 System -170001 0: GET-->/rest/vars/set/2/19/1 Fri 2012/05/11 15:43:52 System -170001 [HTTP] 192.168.30.104:2493->80 Fri 2012/05/11 15:43:52 System -170001 0: GET-->/rest/vars/set/1/65/33 Fri 2012/05/11 15:43:52 System -170001 [HTTP] 192.168.30.104:2494->80 Fri 2012/05/11 15:43:52 System -170001 0: GET-->/rest/vars/set/1/65/33 Fri 2012/05/11 15:44:03 System -170001 [HTTP] 192.168.30.104:2497->80 Fri 2012/05/11 15:44:03 System -170001 0: GET-->/rest/vars/set/2/19/-1 Fri 2012/05/11 15:44:03 System -170001 [HTTP] 192.168.30.104:2498->80 Fri 2012/05/11 15:44:03 System -170001 0: GET-->/rest/vars/set/2/19/-1