wrj0

This technique also works to update 2852-222 Leak Sensors. Set program to watch for the heartbeat, wait 1 second, then have the program do the Update Device. Sure beats running around to all leak sensors after a PLM update; especially for those in hard to reach places like beneath the dishwasher.

New capacitors from Mouser arrived and were installed today. The failed PLM has been restored and is now back in full operation. Whu hoo! Thanks to all who provided details on the cause of the failure and the fix - much appreciated!

Another 2+ year PLM failure to report. My PLM #2412S V1.B failed after running for 2 years and 3 months. Fortunately, I still had the pre-dual band version in the spares box and was back in operation quickly, thanks to the wiki procedure. Replacement parts listed above have been ordered from Mouser to attempt to resurrect the failed PLM. It's rather amazing how frequently these PLMs seem to fail just after operating for two years.

Years ago 'burakk' posted a program "It may snow." http://forum.universal-devices.com/topic/1793-weather-module/?do=findComment&comment=14248 Based on that post, the following has worked fairly well as a snow predictor for my system located in central NC. If Module 'Climate' Dew Point < 32 °F And Module 'Climate' Humidity > 80 % And Module 'Climate' Temperature <= 40 °F Then Run Program 'Snow Probable' (Then Path) Else - No Actions - (To add one, press 'Action') The program 'Snow Probable' provides message notifications

Sure seems like it's adding Rain Today and Rain Yesterday. My ISY shows Rain Today = 0.6" while my PWS reported 0.4" Yesterday and 0.2" Today.

It seems my Total Rain Today value is also the sum of yesterday's and today's values. My ISY is showing Total Rain Today = 1.62 inches. My PWS reported 1.57" yesterday and 0.05" today.

Thank you, sir! Station info has been sent as requested.

My PWS currently shows RainDay=0.4289 in. PWSweather shows it as 0.43. My ISY shows Total Rain Today 5 inches. My PWS currently shows Baro=29.85 Hg. PWSweather shows it as 29.86. My ISY shows Pressure 0 psi. What's up docs?

Yes, indeed. I've copied the degree symbol from Character Map and pasted it into the Custom Notification Body after the variable name. But, I'm allowing Climate Module to provide the degree symbol for the current temperature variable. Perhaps a screen shot may help with my previously poor attempt at an explanation. If I leave out the 2nd line with {mod.weather.temp.current}, the degree symbol in the 1st line of the body presents properly.

Thanks, again, Michel. I tried following your instructions with the results below - still getting the strange characters. Created new custom email notification “Char Test†with HTML option selected: Subject: @webpage:@append:myDir/testlog.htm Test4 Body: WC Temp1 = ${var.2.33}° Wx Out Temp = ${mod.weather.temp.current} Program: Send Notification to ‘wrj email’ content ‘Char Test’ When Run Then is selected, the resulting email content is: Subject: Test4 Body: WC Temp1 = 90° Wx Out Temp = 47.3 �F When sent to Prowl, the body displayed is: WC Temp1 = 90ð Wx Out Temp = 47.3 °F The ISY file /user/web/mydir.testlog.htm contains: WC Temp1 = 90° Wx Out Temp = 47.5 °F You have far more important issues to address and I have other means of getting the degree symbol in notifications, so please use your time and efforts to better advantage than on this small issue. Thanks.

Thanks for your reply, Michel. Do you *ever* take a day off? It appears that both HTML and Text content type return similar results with the à character, at least in my tests. Thanks for noting this has been logged for a possible fix in a future release. It's not really a big deal, as two separate notifications can be sent that eliminates the undesired symbol. Here's wishing you and the staff of UDI a very successful 2014!

Hi All, and Happy New Year! I'm looking for advice on how to correct a display problem with the degree symbol in custom email notifications. The following custom notification correctly displays the degree symbol on both windows email client and iPhone prowl push: Body: WC Temp1 = ${var.2.33}° ° (Courier 0xB0) ° Times New Roman (U+00B0) However, when the body includes a Climate Module Temperature variable, the received message displays other symbols, as follows. Body: WC Temp1 = ${var.2.33}° ° (Courier 0xB0) ° Times New Roman (U+00B0) Wx Out Temp = ${mod.weather.temp.current} The above body content returns this in the windows email client: WC Temp1 = 92° ° (Courier 0xB0) ° Times New Roman (U+00B0) Wx Out Temp = 42.1 �F ...and the below image on the iPhone Prowl app. When the variable ${mod.weather.temp.current} is omitted, the degree symbol displays fine on all devices. Two different fonts have been included for the degree symbol for testing. The Body is in Text format, but HTML returns the same result. What should I do to eliminate the undesired symbol presented in place of the degree symbol when a Climate Module variable is included with other variables in the notification? Thanks.

As you suspected, Michel, Network Resource ID=116 is the one I'm trying to get to mimic the curl command. Thanks for your reply and suggestion to look further at network issues. I'll keep poking at it. Thanks. edit: Michel, I subsequently found that the curl command works only if run from the same PC that is running the application that I am trying to control. If the same curl command is run from another PC on the same subnet, it returns: curl: (7) Failed to connect to 192.168.3.105 port 1178: Timed out So, you nailed the problem. Think I'll sleep on this one and try again tomorrow. Thanks again for your advice and assistance. edit again: It turns out this was was a Windows Firewall issue on the PC running the application being controlled. Enabling a firewall rule to open port 1178 allows the curl command to return the desired response from any device on the local network, including the ISY's Network Resource. The body for the rule that is now working is: {"password":""} Thanks Michel and Xanthros for your input. I'd still be banging my head without the benefit of your comments.

Thanks, Michel. Yes, it is indeed on the same subnet. Other ISY Network Resources access other applications on that PC just fine, e.g, WCLink.

Sadly, no - it cannot.

Thanks, Xanthos. I've tried that but can't seem to properly omit the username when entering the PW in the Authorization header. I'll keep poking at it for a while. Appreciate your input!

I’m having trouble implementing a Network Resource based on a curl command and would appreciate some help. With curl installed, the following works from a command line, immediately returning an appropriate response from the (InControl Pro) application on port 1178: curl -X PUT -H "Content-Type:application/json;charset=utf-8" -d "{\"password\":\"\"}" http://192.168.3.105:1178/zwave/getScenes But, my attempts to translate the above into an ISY Network Resource fail, returning “Error: Request Failed,†and “N/A†in the ISY Resource Response window. Error Log shows: [TCP-Conn] -1/-140002, Net Module Rule: 116 Bumping the Timeout to 9000 returns the same result. I’ve tried various permutations of PUT, POST, modes, Encode URL, {} and "", all with the same result. Suggestions on what to try next will be greatly appreciated. Thanks.

Hey apostolakisl, Thanks for another one of your brilliantly simple solutions. After seeing your timed light program method, I had another one of those "man...that's a slick way to do it" moments. Keep 'em coming.

I have to agree with Xanthos' observations; my T1800 Venstar adapter has been working great for the past year. The initial version installed did have some communication problems, but after providing some diagnostic information to Smarthome, they provided a replacement adapter (rev 2.4 "FWD5") that has been working flawlessly. It manages temperatures and modes several times a day without any problems at all.

Plau, Launch the ISY Dashboard and login, then under settings (the wrench icon), you should see the Verify checkbox under the section "HTTPS Server Settings."

I have also had positive experiences dealing with Smarthome. Recently, a 2413S dual-band PLM failed, two months inside the warranty. (My luck is normally on the other side of the warranty calendar!) With a single call to Smarthome describing the problem (suddenly, all device querys returned ERR), they provided a pre-paid return shipping label, and a week later I received a notice that the replacement device had been shipped. No complaints here.

Weatherbug seems to have their Backyard server back on line. WB data for my station has been available for the past few hours and is now being pulled successfully by the ISY.

They (sort of) did. http://backyard.weatherbug.com/notes/Backyard_Station_Outage_Again

WB status update indicates backyard stations are still out. My station is publishing, just can't pull the data from WB. http://backyard.weatherbug.com/

My station also reports raw data, but for the past few days has been unavailable on the backyard station list. It seems all backyard stations stations are still unavailable on the site below. http://weather.weatherbug.com/USA-weather.html