wrj0

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

Along with adjusting the 2420M Dusk/Dawn light level, programs such as offered in the UDI Wiki allow transient light level changes to be ignored. Please refer to this Wiki Article.

Tim, Some weather stations may submit only limited weather data, depending on their capability. Also, for those of us submitting data to Weatherbug, they limit the data that they accept from certain Backyard stations, for example, they don't currently accept light levels (among other data) from my Davis weather station. (At the risk of raising Michel's blood pressure , I should probably avoid asking again for local network Davis weather station support in the ISY. But it sure would be a nice addition.)

Michel, My results are similar to that of TJF1960 for my Earthlink email address, for example using emailaddy@earthlink.net From with just my email address works fine. Received email shows it was From emailaddy@earthlink.net From <:emailaddy@earthlink.net> works, but the received email From field is blank. From fails, or at least the stuff I have tried before the : has failed to delivery any email. Thanks.

Thanks, Michel. I was indeed testing the Mobilinc portal and have returned SPU back to the default setting.

Could someone please advise the default setting for the 'SPU - Set Portal' command in the ISY Shell? I have changed the URL for testing and would like to return to the default URL. Can't seem to find any documentation regarding the default SPU setting. Thanks. edit: Found 'DPU' will reset Portal URL to default setting.

Upgraded from 3.1.10 to 3.1.12 and installed Elk module without any issues. ISY correctly sees Elk areas and zones. New ISY programs to monitor and report Elk zone changes seem to be working just fine. Thanks UDI! Santa came early this year.

"Does your startup program call a series of programs to start watchdog timers desired each time the ISY is restarted?" For the case of the Motion 1 Detect program, an init program calls its ELSE at startup to kick off the 24 hour timer. Really shouldn't be necessary if the detector senses motion or Dawn/Dusk conditions each day.

Here's one method to monitor your motion sensors: First setup a program that looks for any activity from your motion sensor. Program: Motion 1 Detect If Control 'Motion 1-Sensor' is switched On Or Control 'Motion 1-Sensor / Dark' is switched On Or Control 'Motion 1-Sensor / Dark' is switched Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Detects Motion Sensor, so we can monitor battery with Verify Motion Sensor pgm. Then setup another program to watch for that activity every day. This program will reset each time the motion sensor is activated, but if 24 hours elapse without any activity detected, it will send out a notification. This program is also called by an Init program at ISY startup so it is triggered to start monitoring. Program: Verify Motion 1 Sensor If Time is Last Run Time for 'Motion 1 Detect' + 24 hours Then Send Notification to 'wrj0 email' content 'Motion Sensor 1 Fail' Else - No Actions - (To add one, press 'Action') If no motion detected for 24 hours, then battery may be dead. Send notification. Set up similar programs for the rest of your motion sensors. Hope this helps.

My first 2420M Motion Sensor, Rev 1.1, "4908" provided a single low battery report on the second battery installed (running ISY rev 2.7.12). I changed out the battery before finding out if multiple reports would have been received. The first (original) battery in the same MS (with ISY rev 2.7.0) did not provide a low battery report - I found the battery dead after noticing motion sensor enabled lights were not turning on. Programs now run once every day to notify when no MS activity has been received in the last 24 hours.