NOAA Weather Plus discussions

[nsheldon]

Thank you for looking into it. I removed the plugin then reinstalled it, and haven't gotten an error since.

Excellent! Let me know if it shows up again. If it does, enabling debug logging (Plugins menu -> NOAA Weather Plus -> Configure) to capture the data just before you get the error again would be helpful to know as well.

[CraigM]

Nathan,

The plugin has been really stable. Good Job

FYI, I got this today:

Code: Select all

Nov 29, 2012 10:05:33 AM
  Weather [NOAA Plus]             Warning: Error parsing weather station list XML from NOAA: not well-formed (invalid token): line 24944, column 42
  Weather [NOAA Plus]             Warning: Error parsing weather station list XML from NOAA: not well-formed (invalid token): line 24944, column 42

[nsheldon]

Glad to hear it's been working well.

There's not much that can be done about the warning message. If the NOAA Weather Plus plugin finds that the current weather information for a NOAA Weather Plus device's latitude and longitude are incomplete, it downloads a list of NOAA weather stations and attempts to find the station closest to the NOAA Weather Plus device's latitude/longitude values. If it finds a match in that list, it then grabs the current condition information from that NOAA weather station's web page directly (rather than from the GPS-based NOAA source). That warning message means that the list of NOAA weather stations, which is provided by NOAA, is formatted incorrectly. If you're not seeing the warning any longer, it means that

1. NOAA Weather Plus was able to get your "Weather [NOAA Plus]" device's current condition information based on its entered GPS coordinates (thus not needing to find an alternate station source).
2. OR... It did need to locate the alternate NOAA weather station info, but NOAA has fixed the error in the weather station list.

So, if you don't see that warning every time NOAA Weather Plus updates your weather information (every 15 minutes), things are working as they should.

[nsheldon]

Patch update 1.1.9 released:

Download here.

Changes Since Version 1.1.8

Added Water Temperature device states for NOAA weather stations located at sea.
Improved Data interpretation from NOAA weather stations located at sea.

[eme jota ce]

Patch update 1.1.9 released:

Added Water Temperature device states for NOAA weather stations located at sea.
Improved Data interpretation from NOAA weather stations located at sea.

Wow! Thank You!

Appreciate your monitoring of my question to Jay and Matt regarding water temperature data on the NOAA Plugin ("nonplus" version).

Updated the NOAA Weather Plus plugin and can now see the water temperature for that station. Very helpful display item for our home control page, and will be helpful in making home control decisions in the future.

[nsheldon]

Glad I could help.

[hamw]

I've enabled the plugin and all the states seem to be working fine. How do I enable a refreshing icon on the control page to reflect current conditions?

[nsheldon]

I've enabled the plugin and all the states seem to be working fine. How do I enable a refreshing icon on the control page to reflect current conditions?

The best way to do this is the same way you would with the Perceptive Automation's included "NOAA Weather" plugin.

1. On your control page, create a new object by clicking the New button (or select an existing object).
2. Configure it with the following settings:
   • Display: Device State For: (your NOAA Weather Plus device), Current Condition Icon
   • (selected) As image: NOAA Condition+.png

[automaton]

Hi Nathan,

I'm receiving an error message in the logs regularly (every 15 minutes) from NOAA Weather Plus. Here is a snippet of the debug log:


NOAA Weather Plus Debug Getting forecasted hazardouns weather advisory elements.
NOAA Weather Plus Debug Getting the time layout for hazardous weather advisory elements.
NOAA Weather Plus Debug Looking through time layout for weather advisory layouts.
NOAA Weather Plus Debug Found matching layout in time layout list for 1st weather advisory.
NOAA Weather Plus Debug Found matching layout in time layout list for 2nd weather advisory.
NOAA Weather Plus Debug Looping through each hazard (weather advisory) element.
NOAA Weather Plus Debug updateDeviceState called.
Error script is not valid
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug Weather advisory 1: Frost Advisory
NOAA Weather Plus Debug Start time: 2013-01-12 08:00:00, End time: 2013-01-18 18:00:00
NOAA Weather Plus Debug updateDeviceState called.
Error script is not valid
NOAA Weather Plus Debug updateDeviceState called.
NOAA Weather Plus Debug updateDeviceState called.

I'll send you the complete debug log and also the XML feed from NOAA separately.

Any ideas?

ps. Pioneer plug-in working great!

[nsheldon]

Hey Bob.

Thanks for the report. I received your debug log info that you sent via email. That error doesn't appear to be coming from NOAA Weather Plus, but rather from a trigger action that seems to be firing whenever the Weather Advisory 1 text changes. Perhaps the action triggered is trying to execute an external script that no longer exists or whose name has changed? You're seeing the message every 15 minutes because NOAA Weather Plus has a 15 minute refresh cycle and actually clears out all the device states before putting the newly downloaded states from NOAA into the device, so even though the Weather Advisory 1 text may not have changed, it still gets reset every 15 minutes which would cause any trigger that's set to fire when that state changes to fire.

So, see if you can find any triggers in your Indigo database that are set to fire when your NOAA Weather Plus device's Weather Advisory 1 (or 2 or 3) state changes, then examine the actions those triggers take. I'll bet you find one trigger that's trying to execute a script that isn't working any longer for some reason.

[automaton]

Nathan,

I'm embarrassed again, sorry. I have a trigger, as you figured out, that triggers on the device state change of WeatherAdvisory1. It runs a script that looks at all the advisories to see if they are warnings. When I ran this trigger using "execute actions now", it works fine, so I had eliminated that as a cause of the problem. As it turns out, the Condition tab was set to "if script returns true", even thought no script was present... thus the "script is not valid" message.

OK, so your plugin is not only great, but also bug free

When you are thinking of expanding features, how about flagging the Weather Advisories by severity (Warning, Watch, Advisory, etc)? It would also be nice to be able to get the text of the advisory message as a device state.

Thanks again for the plugin and great support.

[nsheldon]

Haha. No worries man.

I doubt the plugin is completely bug-free, but thanks for the vote of confidence. (

The advisory severity as a state sounds like a good idea. I'd prefer to only create states whose data directly corresponds with a data element coming from NOAA (e.g. current temperature value, current condition text, etc) simply because such states don't rely on my ability to interpret what I think NOAA means. However, a "metadata" state like what you're suggesting does sound pretty useful. I'll seriously keep it in mind for future updates.

As for having the full text of the advisories themselves in a device state, I definitely sympathize with the desire for that. However, have you seen some of those text advisories? They can be pages long sometimes (they're very raw and generally difficult to read IMO). I'm not sure what the character limit is for device states, but if there were one, I wouldn't be surprised if NOAA weather advisories end up breaking it. If there were a short summary, that'd be much more doable for a device state. But as it stands, I couldn't find one in the XML that's provided by NOAA.

[Dewster35]

Nathan,
In regards to the plugin's calculation for windchill, is that something you're pulling directly from the NOAA location or are you doing some internal calculation? I am showing a -250F right now... and while cold... it's not that cold!

[nsheldon]

Nathan,
In regards to the plugin's calculation for windchill, is that something you're pulling directly from the NOAA location or are you doing some internal calculation? I am showing a -250F right now... and while cold... it's not that cold!

Wow! That is cold!

Wind Chill is not provided in the NOAA feed used by NOAA Weather Plus, so it's calculated by the plugin based on the wind speed and temperature (both as reported by NOAA), using the formula provided by NOAA at http://www.nws.noaa.gov/om/windchill.

I just now double-checked the formula in the plugin with the formula posted on that NOAA page and found that I'd accidentally multiplied when I should have added. That'd explain the vastly incorrect number. I've posted an update to NOAA Weather Plus that fixes it (as well as a few other bugs). See the announcement thread for the download link. Thanks for bringing that bug to my attention.

[Dewster35]

Not a problem! -12 for windchill looks more proper. Thanks for the update and awesome plugin!