If you would, open a ticket on the trac site at http://www.cfreeze.com/trac/stormsiren. The problem is that the current version does not automatically create certain files like the 1.x version. You need to create a ~/.StormSiren/StormSiren-log.conf file. An example exists as log.conf. You can also run it from the command line with "--logconf log.conf" to avoid the error. Another ticket could be opened on this for a check to be made an appropriate status given to the user.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just uploaded a new version 2.0RC2 that should fix the problems that you mentioned. It should also remove the dependency requirement of python-xmppy. Thanks for your input and trying the new version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry--wanted to do this on Trac, but didn't get verification mail. Checked spam box, etc.
I am using Ubuntu 8.04. So, I thought the deb package would be fine for me. No good. Package installer says it cannot open it. Possible corruption, etc.
D/l'ed the tar.gz and put in place fine. Looks like you have a version buried within the version. I ran the 'deepest' siren--not sure if I'm running the right executable.
I can get a test message using sendmail on this box. Luckily, Gmail accepts it!
I am not sure I have the program properly configured. I have enclosed my config file. I want ALL of CT to feed me. I enabled all types of data only to give myself a better chance of getting something.
For locations, I see you are using towns. I listed our 8-counties. Will that work? Must I list every town?
There are a few short term forecasts in effect now, but they were not sent. Also, nothing is written to the history file. In fact, that file wasn't created, so I did manually and then made it 777 (local machine--no worries).
Attached is my conf file:
[main]
states = CT
watchers = 1
history=100
[smtp]
host = localhost
port = 25
from = me@geofffox.com
#user = user (real one on actual file)
#password = password (real one is on actual file)
[jabber]
host = www.example.com
port = 5223
user = weatherbot
password = **********
The way StormSiren currently works is that the state list in [main] is a hint for what weather lists to download. Then each device is given the chance to filter the list to a subset of that list. The only way to get all weather in CT is to add each county/city to the areas list. The one problem I see with your aeras list in device 1 is that yhou have Litchfield without a state. Hopefully it gave you an error stating that the list had a problem. I will run it locally with your config and see what happens.
Also you shouldn't have to create a history file or set it 777. The file is created automatically after the first alert is issued.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The one thing that I did notice is that you have the areas specified backwards. It should be City,State or County,State. You have specified your areas as State,Location.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is it now correct? I would think that will give me full state coverage, since the counties are always mentioned.
Also, it looks like 'short term forecast' is not parsed by StormSiren, which is why I still see nothing. But are forecasts, which is one of your parameters ever seen in the CAP files?
All the best,
Geoff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
[1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory,watch,warning
areas = Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT
This configuration alerted on three weather alerts that included a short term forecast.
CTZ003.BOXNOWBOX.070500
CTZ004.BOXNOWBOX.070500
CTZ002.BOXNOWBOX.070500
I probably need to go back and add trim calls that will take care of spaces in the areas definition...
I installed the debian package without problems. Can you give me the full terminal dump of the install that failed? Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got the Hartford, Tolland and Windham forecasts twice - 2:13 and 2:21 am. The cron is running every minute and the forecasts didn't change (I think).
Did not get Litchfield County--and I assume I have to split it (and te other four counties) into north and south as per NWS zones.
Not sure how to get you the terminal dump you need. Was running the GUI to unpack the .deb.
I only know enough to be dangerous!
BTW - am also running MythTV on the Ubuntu machine. Really like it a lot. Have had it up well over a year. Have two PVR-150s. Use MythTV Player to play video back on my Windows machines from the Myth box.
Geoff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got on Trac--finally. Have not posted my probs because of this ongoing conversation. Took email forever to reach me. Your site is somewhat sluggish to me in normal ops as well.
Geoff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The extra alert could have come from me. Check the email headers as I was using your configuration file for testing. I would not expect you to have to do anything other than specify the "Location,State" in your 'areas' defintion. The current ct.cap file from weather.gov does not include any alerts for Litchfield,CT. Have you been able to use the MythTV alert device yet? The information from it is very terse and I would like feedback.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It does seem to want Northern and Southern, since it sent the Litchfield forecast as soon as I added that. There are two Litchfield County entries in the CAP file.
currently: [1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory, watch,warning
areas = Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT:Southern Litchfield,CT:Northern Litchfield,CT:Northern New Haven,CT:Southern New Haven,CT:Northern Fairfield,CT:Southern Fairfield,CT:Northern Middlesex,CT:Southern Middlesex,CT:Northern New London,CT:Southern New London,CT
I have not had a chance to play with the Myth functionality. Not sure how that works nor where it goes.
You are correct. The second set did come from you "freezefamily.net"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I didn't realize that there was actually two different counties with the same name. You can take a look at the wiki for how to configure a MythTv device.
No--it's one county, but it's split into two NWS forecast zones. This is very common in some parts of the country, especially where elevation changes over a short distance or the county is adjacent to a large body of water.
Saw the new version and tried to get StormSiren up and running. My attempt was on a Ubunutu 8.04 machine.
The docs made it look like XMPPPY was an option--the software required it to operate. No problem. I installed.
It also needed dnspython to be installed. Again, no problem.
Now the software is choking with: "No handlers could be found for logger "Config"" So, I'm lost again.
Can you provide any help?
Thanks for keeping the project alive.
All the best,
Geoff Fox
geoff.fox@gmail.com
If you would, open a ticket on the trac site at http://www.cfreeze.com/trac/stormsiren. The problem is that the current version does not automatically create certain files like the 1.x version. You need to create a ~/.StormSiren/StormSiren-log.conf file. An example exists as log.conf. You can also run it from the command line with "--logconf log.conf" to avoid the error. Another ticket could be opened on this for a check to be made an appropriate status given to the user.
I've just uploaded a new version 2.0RC2 that should fix the problems that you mentioned. It should also remove the dependency requirement of python-xmppy. Thanks for your input and trying the new version.
Sorry--wanted to do this on Trac, but didn't get verification mail. Checked spam box, etc.
I am using Ubuntu 8.04. So, I thought the deb package would be fine for me. No good. Package installer says it cannot open it. Possible corruption, etc.
D/l'ed the tar.gz and put in place fine. Looks like you have a version buried within the version. I ran the 'deepest' siren--not sure if I'm running the right executable.
I can get a test message using sendmail on this box. Luckily, Gmail accepts it!
I am not sure I have the program properly configured. I have enclosed my config file. I want ALL of CT to feed me. I enabled all types of data only to give myself a better chance of getting something.
For locations, I see you are using towns. I listed our 8-counties. Will that work? Must I list every town?
There are a few short term forecasts in effect now, but they were not sent. Also, nothing is written to the history file. In fact, that file wasn't created, so I did manually and then made it 777 (local machine--no worries).
Attached is my conf file:
[main]
states = CT
watchers = 1
history=100
[smtp]
host = localhost
port = 25
from = me@geofffox.com
#user = user (real one on actual file)
#password = password (real one is on actual file)
[jabber]
host = www.example.com
port = 5223
user = weatherbot
password = **********
[media]
player = mplayer
forecast = alert.wav
statement = icemag.wav
advisory = lightmag.wav
watch = onscreen.wav
warning = spinout.wav
[1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory, watch,warning
areas = Litchfield, CT:Hartford, CT:Windham, CT:Tolland, CT:Fairfield, CT:New Haven, CT:Middlesex, CT:New London, CT
Thanks again for working on this project.
Geoff Fox
ps - I am a meteorologist.
The way StormSiren currently works is that the state list in [main] is a hint for what weather lists to download. Then each device is given the chance to filter the list to a subset of that list. The only way to get all weather in CT is to add each county/city to the areas list. The one problem I see with your aeras list in device 1 is that yhou have Litchfield without a state. Hopefully it gave you an error stating that the list had a problem. I will run it locally with your config and see what happens.
Also you shouldn't have to create a history file or set it 777. The file is created automatically after the first alert is issued.
The one thing that I did notice is that you have the areas specified backwards. It should be City,State or County,State. You have specified your areas as State,Location.
Here's what I had: Litchfield, CT:Hartford, CT:Windham, CT:Tolland, CT:Fairfield, CT:New Haven, CT:Middlesex, CT:New London, CT
I had a space between the counties and state. I take it the ":" is the separater between differen locations. I have removed the spaces-- so
Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT
Is it now correct? I would think that will give me full state coverage, since the counties are always mentioned.
Also, it looks like 'short term forecast' is not parsed by StormSiren, which is why I still see nothing. But are forecasts, which is one of your parameters ever seen in the CAP files?
All the best,
Geoff
It works!!!!
With the changed conf file, it's sending the forecasts!
I ran with a slightly modified configuration file that looks like the following.
[main]
states = CT
watchers = 1
history=100
[smtp]
host = mail
port = 25
from = me@geofffox.com
#user = user (real one on actual file)
#password = password (real one is on actual file)
[jabber]
host = http://www.example.com
port = 5223
user = weatherbot
password = **********
[media]
player = mplayer
forecast = alert.wav
statement = icemag.wav
advisory = lightmag.wav
watch = onscreen.wav
warning = spinout.wav
[1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory,watch,warning
areas = Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT
This configuration alerted on three weather alerts that included a short term forecast.
CTZ003.BOXNOWBOX.070500
CTZ004.BOXNOWBOX.070500
CTZ002.BOXNOWBOX.070500
I probably need to go back and add trim calls that will take care of spaces in the areas definition...
I installed the debian package without problems. Can you give me the full terminal dump of the install that failed? Thanks
OK -
Got the Hartford, Tolland and Windham forecasts twice - 2:13 and 2:21 am. The cron is running every minute and the forecasts didn't change (I think).
Did not get Litchfield County--and I assume I have to split it (and te other four counties) into north and south as per NWS zones.
Not sure how to get you the terminal dump you need. Was running the GUI to unpack the .deb.
I only know enough to be dangerous!
BTW - am also running MythTV on the Ubuntu machine. Really like it a lot. Have had it up well over a year. Have two PVR-150s. Use MythTV Player to play video back on my Windows machines from the Myth box.
Geoff
Good glad to hear that you have had success. Have you been able to get on the Trac instance as well?
Got on Trac--finally. Have not posted my probs because of this ongoing conversation. Took email forever to reach me. Your site is somewhat sluggish to me in normal ops as well.
Geoff
The extra alert could have come from me. Check the email headers as I was using your configuration file for testing. I would not expect you to have to do anything other than specify the "Location,State" in your 'areas' defintion. The current ct.cap file from weather.gov does not include any alerts for Litchfield,CT. Have you been able to use the MythTV alert device yet? The information from it is very terse and I would like feedback.
It does seem to want Northern and Southern, since it sent the Litchfield forecast as soon as I added that. There are two Litchfield County entries in the CAP file.
currently: [1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory, watch,warning
areas = Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT:Southern Litchfield,CT:Northern Litchfield,CT:Northern New Haven,CT:Southern New Haven,CT:Northern Fairfield,CT:Southern Fairfield,CT:Northern Middlesex,CT:Southern Middlesex,CT:Northern New London,CT:Southern New London,CT
I have not had a chance to play with the Myth functionality. Not sure how that works nor where it goes.
You are correct. The second set did come from you "freezefamily.net"
Ok, I didn't realize that there was actually two different counties with the same name. You can take a look at the wiki for how to configure a MythTv device.
http://www.cfreeze.com/trac/stormsiren/wiki/MythTvDevice
No--it's one county, but it's split into two NWS forecast zones. This is very common in some parts of the country, especially where elevation changes over a short distance or the county is adjacent to a large body of water.
So: http://www.weather.gov/wwarss-tst/ct.php?x=2
Meanwhile, do you know about this:
"It is expected these CAP 1.1 feeds will replace the current feeds by December 2009."
http://www.weather.gov/alerts-beta/
http://www.weather.gov/wwarss-tst/us.php?x=0
http://www.weather.gov/wwarss-tst/us.php?x=1
This might be an easier parse?
Geoff