X10 Community Forum
🖥️ActiveHome Pro => SDK => Third Party Add-Ons & Software => Topic started by: jjsalobird on January 13, 2010, 05:35:31 PM
-
Hi,
Have been using PC Companion for a few days and yesterday, it stopped getting the temperature and executing the X10 codes associated with the temperature in the triggers section. Anyone else having this issue? I can still make it get the detailed forecast by going into program options, but clicking weather either in the main interface or in the trigger section keeps saying N/A. Any help appreciated.
-
jjsalobird
PC Companion uses 2 different web locations for gathering forcasts and getting temperature.
Sometimes information for your location doesn't get loaded to the web site if that is the case you will get the N/A
I'll look into it in any case. ;)
For more reliable weather PC Companion is now capable of interfacing with personal weather stations using VWS (http://www.ambientweather.com/software.html).
>!
-
Update:
Seems the Site PC Companion was getting it's temperature and current conditions from has changed their format. B:(
Hopefully it won't involve to much coding to fix. ::) :'
It may also lead to more info that PCC can utilize ::) :'
>!
-
Thanks for looking into it so quickly, I thought that might be it. Will look forward to an update!
-
jjsalobird,
Thanks for bringing that to my attention. I have taken the PCC temp macros for granted. I'll have to keep an eye on things till PCC gets fixed.
-
UpDate:
Ok seems like this will be an easy fix! ::) :'
The web site sub folder was changed for current weather.
And looks like I'll have to rewrite the parser for that page. B:(
Should have a fix for that before the end of the week. ;)
>!
-
Up Date:
Since posting the fix for the temperature triggers in PCC Version 3.0.52
I've been able to get the display screens working correctly.
I think the Daily weather report even gives you a little more info now. ::) :'
Here is an example of what I'm able to pull off the new site so far:
Current Conditions Are: Cloudy
Temperature is: 36 Degrees Fahrenheit.
Temperature Feels Like : 31 Degrees Fahrenheit.
Wind is: From the West at 6 Miles Per Hour!
Humidity is: 75%
The Dew Point is: 28 Degrees Fahrenheit.
Pressure is: 30.14 Inches.
Visibility is: Unlimited
And the U V. Index is: 0 - Low
The small info screen still only displays current temperature and condition.
If anyone would like more info reported let me know, and I'll see what else can be added before next update.
>!
-
Hi,
Would it be possible to have greater than or equal to and less than or equal to as well. Also, would it be possible to trigger on the "feels like" temperature? Just asking. I also assume the greater than operator means exactly that, so greater than 32 means 33 and up and less than 33, means 32 and down.
I ask because right now I have two triggers, less than 33, trigger on, and greater than 32, trigger off, so that anything 32 and down turns on my heater and anything 33 and up turns it off.
Thanks
-
Hi,
Would it be possible to have greater than or equal to and less than or equal to as well. Also, would it be possible to trigger on the "feels like" temperature?
It is certainly a possible add! ;) Feels like is a combination of temperature, Wind speed and humidity.
So unless your wishing to activate something completely exposed to the elements it would mean triggering before needed.
Or turning off something before you should.
Just asking. I also assume the greater than operator means exactly that, so greater than 32 means 33 and up and less than 33, means 32 and down.
I ask because right now I have two triggers, less than 33, trigger on, and greater than 32, trigger off, so that anything 32 and down turns on my heater and anything 33 and up turns it off.
Thanks
Thats correct!
>!
-
Thanks
I may have asked this, but are you familiar with the software Weather Watcher Live? For about 10 bucks it does a great job at accurate local forecasts. For instance, right now, the info I get via PC Companion, from whatever weather service it uses, comes from about 30 miles away. The weather watcher live software has many more sites from which it gets its weather data. So it is more precise (in my case, it has data from my small town). I often see a temperature difference of 5 or 6 degrees. Anyway, since I am not a programmer, all I can do is point it out, not sure if you could use it's data legally or not, but it's worth a look. The link is http://www.singerscreations.com/Weather-Watcher-Live.asp (http://www.singerscreations.com/Weather-Watcher-Live.asp). It also has some logging capability, so I have attached a log file. Don't know if the logs are suitable for PC companion triggers. It just seems like a much cheaper solution, at least for me, and pretty darn accurate as well, compared to a personal weather station, using the virtual weather station software. Anyway, just posting for your information, may be useful.
Thanks again.
-
jjsalobird
Never heard of Weather Watcher Live but it looks like it pulls info from two sources as well.
NOAA's National Weather Service (http://www.nws.noaa.gov/) uses your Zip code to find your weather as well but is for the US only. But would be a simple add I think.
Weather Bug (http://weather.weatherbug.com) may be where your getting the most accurate info as it gathers info from personal weather stations. ::) The issue with using this is I'd have to compile another data base for Cities as it won't use codes the other sites do! :(
Setting up a personal weather station doesn't have to be expensive.
Some places like Ambient Weather include a registered base version of VWS
If your only looking at temperature monitoring you can find units that just do that.
Ambient (http://www.ambientweather.com/orems100.html) has a deal on now for one, beating prices on e-bay.
In any case if NOAA's National Weather Service reports a more accurate temp let me know and I'll look ad adding it as a info gathering site.
>!
-
Thanks again, I'll take a look at the ambient stuff, I have heard that those weather stations have issues with the USB connection and the software that uploads the data. The NOAA National Weather Service would be a nice addition, since it is always a lot closer to my local temps than whatever PC Companion now uses. As I write, PC Companion reports 49, NOAA 46, the Weather Watcher Live, which is in fact from WeatherBug, reports 44, same as my outdoor thermometers, and the weather channel reports 45. I'll look to see if the next update includes this option. Thanks again
-
jjsalobird Nice to hear NOAA is a little more accurate. ;)
I'll start at adding this option. ;)
Pc Companion doesn't report the exact temperature reading for me either but is usualy only 1-2 deg + or - from my weather station. ::)
I was looking at posting an update today but I'll look at how much work it is going to be to add NOAA to the mix and may put that off.
>!
-
Update:
Looks like adding NOAA as a temperature retrieving site is going to be more work then I previously thought. :( :'( :-[
Seems punching in your zip code doesn't always send you to a common site B:(
That's the issue I first ran into when initially setting up the forcast option. :(
I'll keep playing with this and weather bug. ;)
Looks like I may have to create a new data base for which ever looks most promising ::) :'
I'll have to do somemore tests no need coding something in if it only works for part of a Country B:( ::) :(
Should have a new update posted that fixes current weather display issues later today.
>!
-
Using the weather watcher live software I mentioned earlier, I can generate a text file identical to the temperature.txt file that PCC generates to check the temperature. If PCC is indeed using that file to check it's triggered temp events, is their an easy way for PCC to use a file generated in a different manner, as long as it has the same name. Right now it seems that if I copy my new file into PCC, it just overwrites it when it does its check.
-
Any one else seeing the same problems again today. Have not gotten any weather, temp information since this morning. In program settings I can have it fetch the forecast succesfully, but clicking the weather button on upper right of main window just gives a N/A as does clicking it in the weather triggers section. Any ideas?
-
B:( they did it to me again B:( ::) :'
Time to cut that weather site out of PCC!
Looks like Its back to the drawing board! >*<
Using the weather watcher live software I mentioned earlier, I can generate a text file identical to the temperature.txt file that PCC generates to check the temperature. If PCC is indeed using that file to check it's triggered temp events, is their an easy way for PCC to use a file generated in a different manner, as long as it has the same name. Right now it seems that if I copy my new file into PCC, it just overwrites it when it does its check.
Looks like that may be an option to add. Currently PCC generates that text file after it fetches the info I'll see about adding the option to read from it instead of reading from the net. also I'll add the option not to generate the txt so as not to over write it.
>!
-
I have attached for you two of the files from the weather watcher live program. These are examples of what it generates. The [TEMP] variable in the program is static, so it outputs 43.0 instead of 43 degrees. Also, the one called Temperature.txt is the html version which puts the degree symbol in. I can't get rid of that. You can name the files WWL generates, anything you want. In either case the only number in the file is the temperature. The Temp.txt file puts a new line in the log file everytime it checks the temperature, anywhere from real time to every 2 or 3 hours. I'd take a look at the WWL program, it seems to do a lot of the front end work for you. -:)
-
If PCC only reads the numbers in the temperature file, and does not write one, then those wanting to use http://www.singerscreations.com/Weather-Watcher-Live.asp, Weather Watcher Live, could do so. Better yet, if PCC would only read the last line of the file, then ;D idiots like me wouldn't have to do anything!! Thanks again. :)% #:) :)+
-
I should ::) be able to get PCC to read just the number from either file. :'
Pulling from the Temperature.txt file would be the easiest to code. ::) :'
-
Timetable? :D
-
Timetable? :D
How does this evening sound? ??? ;)
Just cleaning up some lose ends. ;)
I've removed the offending weather site from PCCs code. The temperature and forecast now come from the same site.
I've added code so PCC can read the temperature.txt file in the log folder which it normally writes.
If the option is selected to use a thirdparty source PCC will not write to that file.
You'll need to have the thirdparty software write it at regular intervals in order to have the temperature triggers work.
Also I've received many requests for weather support for places other then North America.
Using Yahoo weather it is now possible. Temperature triggers aren't available from this info yet! ::) :'
I may not get a post up stating that the new update is available so check using the download link in PCC or PCCs web site.
>!
-
Great, hopefully you can close this chapter for a while! ;)
-
rofl yes!
Although I constantly get weather related requests.
I'm also looking at adding a Weather Bug weather link as a back up!
I hate relying on one site for info. ::) :'
It is always handy for users to have a back up in case this happens again!
>!
-
Well thanks again. The fact that one can use a user generated temperature file now, will enable a person to at least get by in cases where PCC cannot get temp info. Many of us know enough to be dangerous and can automate the creation of text files by reading info from other text or html files, stripping the needed data and creating a format that PCC can read. In fact, I had done this, with a couple of freeware programs before I stumbled onto WWL, but then realized that PCC always wrote over the temperature file anyway. Thanks again.
-
I just realize -:)
If one could create a CSV file from a thirdparty software then it would be possible to use the personal weather station plug-in.
You could have more weather based triggers not just temperature but wind, humidity, rain.... ! ;)
Of coarse it doesn't strip text so any values you planed on using would have to be numerical only. ::) :'
>!
-
Just notice on the latest build that anytime I use my own temperature.txt file, and try to put in a trigger that says, "More than" a certain temperature (does not matter what number I use), that with temperature parameters checked, the program always tells me "Temperature did not match 3rd condition parameter :( (or first,second, fourth, etc, depending upon where I actually put it. This just happens with "More than"
Right now I have 3 parameters: 1st is less than 32, second is less than 22 and the 3rd is more than 32.
-
BTW, that behaviour (the temperature parameter failure on "More than" temps), happens on my Windows 2000 machine as well as on my Windows XP machine. I don't use it on the Vista machine.
-
The temperature paramiter checked basically is a error checking tool it isn't meant to be left on.
In your case if the temperature was less then 22 you will always get the message did not match parameter for the more then temp. If your temperature was more the 32 you should get paramiter didn't match for the other two settings.
The temperature paramiter check was originaly left in as an error. :-[
One user asked that this option be left in for checking purposes other wise it wouldn't be there.
Hope that helps.
>!
-
Ok, let me make sure I understand. Right now my temperature is 43. I have the first slot set, if less than 32 - then B4 ON, the second one says, less than 22, then B5 ON, the third is set to, if more than 32, then B6 ON. when I run the parameter check, it says the third one fails? Additionally it is turning B5 ON, not B6. I just figured that if the temperature was actually more than 32, then this one would not fail, the other 2 would. Is that what you expect? When I turn it around and uncheck the option to use a third party temp file, it reports the 1st two don't match the parameters. Sure seems like a bug, but I could be wrong.
-
Yep B:( sure sounds like A bug. ::)
Not sure why it fails with thirdparty temps it is only using the number ??? ???
I'll dig into it and see what I can find.
Can you post the actual text file your using? ???
There maybe a hidden character that is throwing things as well. ???
-
Sure, :)% attached
Thanks
-
I don't see the degree symbol were you able to remove it?
I guess you found how to remove it! ;)
-
Couple of things I see that may be causing the issue.
1: Spaces in your text
2: Another line entry even though it is blank PCC picks that up. ::)
I hadn't coded to take those into account so I'll add that stripping info and see if that fixes things before I dig deeper. ;)
>!
Update:
jjsalobird
Seems like 1 of those 2 things or both were causing the issue.
After adding code to eliminate carage returns and blank spaces the parameter test works as it should and the correct triggers are fired.
Or at least they do with your supplied txt file! ::) :'
-
Yes, I removed the degree symbol. Finally read the help file in WWL, it has a plain temp round variable that rounds it off and leaves out the degree symbol. Sorry, I was out of town today.
-
Seems to be working fine now! :)% #:)
-
jjsalobird found another weather program that generates a CSV file and it is free.
I'm Sure there are other Freebies out there! ;)
It gets information from personal weather stations and other stations.
IT generates a visible forecast and writes the CSV file to where ever you like.
The program WeatherExchange (http://www.ambientweather.com/weex1.html) from ambientweather.
I actually received this on CD with my weather station and just looked at it today :-[
I've started playing with some code and may add the ability to create a readable forecast from it's generated CSV file since it is in the same format as that created from VirtualWeatherStation.
In any case one Could use this with the extra triggers available with PCC's weather Plug-in! ;)
>!
-
??? Will the CVS file that WeatherExchange uses work as is with PC Companion's additional triggers or does it have to be formatted differently? I was unclear on this. Thanks
-
??? Will the CVS file that WeatherExchange uses work as is with PC Companion's additional triggers or does it have to be formatted differently? I was unclear on this. Thanks
It won't work with the additional triggers but does work with the PCC weather station plug-in (x10WeatherWatch).
It doesn't allow for you to edit the CSV file! :(
I may add the option for PCC to pull the temperature value so the CSV will work with the additional triggers as well in the next build. ;)
-
Hi,
In the x10weatherwatcher plug-in on PC Companion, how do you retrieve the info into the text box. ??? I only have buttons that say "Speek retrieved info" and "X-10 Triggers? Or does the program just retrieve the info for each parameter automatically. So far I have never seen anything in the white box on that screen. Also, does this automatically run when PC companion runs or do I have to open that page and minimize it to the system tray if I restart PC Companion? is it running if I close it with the X or not? Hope this makes sense. B:(
-
x10WeatherWatcher doesn't put info into the temperature text file.
I can't remember how detailed the manual is so here goes:
Open your CSV file with notepad make sure word wrap is unchecked so you can find the number spacing for your Temperature,Wind....
Set the file the path to the CSV file in the program so it knows where to look each time
Set the Time interval that the program will parse the CSV file for values.
You need to change the text that says Parameter Name: to some thing like Temperature,Wind,Humidity.....
Then in the small box beside that you scroll to the number of values in the CSV file that represents that
Say file looks like 10,20,09,1,23,0,1.5,35,48,.......... and value you need is 48 then the Paramiter value would be 8 as the program counts from 0 as first digit.
if temperature you need is 23 then value is 4.
if you want more then one temperature trigger or a different trigger like wind, add that paramiter the same way.
If you get a message box that pops up before you have settings in place don't worry.
The program is set to auto scan and just hasn't found your settings.
Once you have the values in place click the reset timer that will pull up the info faster then waiting for timer to count down (maybe I don't remember what I have the default set to). ::)
Check to see what pops up in the text box to make sure it is getting the correct values.
Now check x10 triggers each row will now have the paramiters you typed in.
Select =,<,or > then scroll to number
Select the x10 code.
Click save
From the main screen check if you wish it to load minimized or not.
Now save from main screen.
Now if you wish X10WeatherWatcher watching all the time reopen it and minimize.
If you wish it to only run at night set AHP to launch it using a windows command (batch file) or have PC Companion launch it.
>!
If you wish to use WeatherExpress for creating a CSV file I've attached a text file indicating where each value is located just remember to subtract 1 from the number indicated. ;)
-
Thanks, I just did not know how to force the info into the box so I could see it. It was working fine. Quick question, it checks all the parameters at the same time, correct? In other words if I have 4 parameters set up and 2 are met and two are outside the parameters I set, then when PCC checks, it will run the x10 triggers for the ones that are met at the same time and the ones that are outside the parameters will not be run. Think I asked this before concerning the weather triggers.
If this is the case, let's then say I have only one x10 trigger (D5ON) set up to run if any or all of my 4 conditions are met, let's also say that the trigger is a macro that sets a flag. Would there be a problem if it fired more than one D5 ON at the same time, since more than one parameter was met? (guess that is more of an AHP, question, but since I already typed it, I'll leave it and hope you answer!) :angel:
-
Well it kinda is a AHP CM15A question, and X10WeatherWatcher (SDK) question.
The Program will only sends one X10 command at a time if they have to be relayed by the CM15A they will be sent one after the other.
Now where a issue might come up is if you have two programs sending commands at the same time. ::) :'
>!
-
Thanks! :D
-
Hi,
In the latest version of the x10 weatherwatcher plugin, I am having some problems. I used to be able to set the order in which I wanted the values in the CSV file to be checked. In the version I am now using, you have apparently added a permanent wind speed, temperature and wind direction constant. These show up as triggers 1-3 and cannot be changed. That is not the biggest issue, since I just don't set these first three, but it would be better if I could get rid of them. A bigger issue is I cannot get the else part to work on the triggers. For instance, I had a trigger for Temperature that said if the temperature is less than 55, then D4 on, else D4 OFF. The off never fires if the temp is over 55. The only way I can do this is to do it with 2 temperature variables, one firing D4 ON if is it less than 55 and the other firing D4 OFF if it is greater than 55. I assume the else should fire if the condition is not met. Also, it appears that the wind speed variable is not working. Hopefully you can check this out and send some advice. My wind speed is 8 and I try a trigger that says fire D5 if it is greater than 20, and it seem to fire every time. Any help appreciated!
Thanks
Jeff
-
Thanks jjsalobird for reporting this! #:)
I'll dig into this, to morrow when my eyes are fresh.
It may just be a typo ::) :'
After the first 8 lines of conditions they start to blur rofl
>!
-
Well Tuicemen,
It may just be me too, trying to do something it was not designed to do. Here is what I am trying to do. Need to turn have my garage close automatically when the temperature is below a certain point, or when it is snowing or raining. No one can seem to remember to push the button when they come home! Anyway, I need to check 3 or 4 conditions. I used a macro that set a flag which I then used to tell the garage what to do, in this case it was flag 1. In the macro, I first cleared the flag in WWL everytime it checked conditions, I did this by checking if the month was less than 13, which it always is (there may be better ways, but bear me out!). Then it evaluated each condition, if the first one was true it set the flag if it was off (which it always was because of the month condition), all subsequent conditions were then checked as well, but the macro's condition was if the flag was already set, do nothing. This way, the flag was always set on the first true condition, and then was never cleared if subsequent conditions were false. If I recall there was not an "else" option in earlier versions. Originally, in the last version, it seemed to work fine. In this version I set up a test using 1 condition and then more than one condition. I would hit reset and see what AHP would send. Here is what seems to be happening. If I want D4 On to fire when the temp is below 60, it sends my D4 OFF (which is actually my month condition, which is first, which is alway true), then the D4 ON (the temp condition), the first time I hit the reset timer button. This is expected. After that, when it checks, if the temp is still below 60 it sends nothing on all subsequent checks. Does not fire the D4 OFF for the month condition, nor the D4 ON for the temp condition, just does nothing. (I removed all conditions in my macro for the test, and I used no else statement in WWL). If the temp then goes above 60, it will send the D4 OFF (the month check condition which is first, and ignore the D4 ON for the temperature condition, since it is not met), as expected. I could also swear, but not certain that the next time it checked it would send the D4 ON when it was not supposed to, then the next time it would not, then it would alternate between just D4 OFF (which it should do-month check) and D4 OFF and D4 ON (which should not fire, temp check). Thus on every check, my flag would switch between on and off. I'll check this more thoroughly later today.
When you add more than one condition, it seems to do go nuts, now for sure alternating between (in my case D4 ON and OFF, turning my flag on, then off, on then off, regardless of the condition being met or not), as well as other strange behavior that I have not pinpointed as of yet. I have not checked the docs lately, but does it evaluate each condition in order? And is it supposed to fire the "else" if the condition is not met? What if I do not use an "else" and leave it blank? Anyway, have at it, I'll try again later today.
jjsalobird
-
I suspect it is your macros as I don't see anything in the code here. ???
I also think your trying to do something X10WeatherWatch wasn't designed to do. ???
In any case can you email me your WS_Settings file so I can test it here?
The else options were added to stop repeated x10 sends (flooding)
As well as to add a x10 send for when the conditions weren't met without having to use another paramiter.
Each will only fire once before the other leaving the else blank will not have any effect.
X10WeatherWatch has no x10 receive built into it it only sends.
I'll look into possibly adding a X10 trigger option for next release.
-
Tuicemen,
I ran through it all again and have duplicated this on numerous times. -:) I think I pinpointed the issue. My triggers are if temp is below 60 or if wind speed is above 20, or if current condition is rain, sleet, etc, then turn D4 ON. everything works, except the wind speed. As long as I set the value for windspeed as a single digit number, it works correctly, but as soon as I make it 10 or above, the greater than and less than signs work backwards.
For example, Right now it is 73 degrees and the wind is 7 MPH. So if I set up, if temp is less than 60, D4 ON or if wind speed is less than 9, D4 ON. In this scenario, all works as expected, D4 ON is triggered based on wind speed. If I change the wind speed to greater than 9, then no D4 ON is triggered at all. But if I change the wind speed to greater than 10 or any other 2 digit number, it triggers a D4 ON, which should not happen since actual wind speed is 7. If I reverse the sign to less than 10, or any other 2 digit number, it does not trigger the D4 ON even though it should since the actual wind speed is 7. This appears to be reversed for double digit numbers. Hope this helps, I ran through about 7 or 8 random double digit numbers as high as 50 to test this theory.
PuebloPete -:)
-
Ok I can recreate the problem here ???
B:( Code looks good . Guess I got some digging to do! ::) :'
I suspect the same may hold true for some other Paramiters
Man I'm going to see "< > =" in my sleep! rofl
>!
-
Tuicemen,
Just noticed some other odd behavior. Last night I left it running all night (usually do!) with only the month check and the temp check set, anyway the temp dropped below the trigger level and a D4 ON should have fired. Checked log and not once all night did anything fire. Had it set for every 5 minutes which should have fired a D4 OFF everytime, since that is checking whether the month is less than 13. Then when temp dropped below trigger it should have fired a D4 ON, everytime as well, but nothing.
Also noted 2 other things. I purposely changed the trigger value of my temp, to a value greater than the actual temp when I went to bed to see if my trigger would fire at all, since I suspected this. Temp at bed time was 56 and I set my trigger to fire at below 60. In the morning the window, inside WWL with all the data never refreshed all night, as all values were exactly the same as I left them. Only when I manually hit the reset timer button did the values change, temp went immediately to 50 degrees. Second, now everytime I hit the reset timer button I am getting alternating D4 OFF and D4 ON. It should be firing off both each time, leaving D4 ON, but it is not. One time it leaves it OFF, the next time I manually hit reset it turns if D4 ON. Not sure what is happening. As I said, my macros are doing nothing but setting a flag, no conditions any more. Sorry :'(
-
No Problem,
The program is set so once a paramiter and the conditions for it are set, It will fire the X10 trigger as soon as condition is met either with the reset, first startup or with actual condition. and not fire again until condition stops being met.
So if you have a temperature condition to fire off D3 on when it is <-3 it will fire off D# once and never fire it off again until temperature goes above -3. if it goes above-3 then drops back down it will fire.
It doesn't fire the D3 every cycle that it is -3.
I think I've found the issue with the < >
I've looked at the timer as the screen should have refreshed
:-[ Found the issue there too, seems I had commented out a key piece of code while testing and never undid it :-[
I should have a fix out this morring.
>!
-
OK Thanks Nice work :)%
-
Thanks, I only hope I didn't leave in any debug stuff this time arround! :-[ ::) :'
>!
-
Tuicemen,
:'( The plug in pack I downloaded last night still appears not to be working correctly, specifically the timer. Left it up all night and when I opened it the screen had not refreshed. Had to hit the reset timer button to get the window to refresh. Temp was 55 when I went to bed, showed 55 in AM until I hit reset, then changed to 44. None of the triggers fired overnight. Also, seems I have to hit reset twice before it actually fires the trigger. Cannot tell if the other things are fixed or not, since it did not trigger any macros. :'(
PuebloPete
-
Email me your WS_Settings file so I can test it here!
What version of X10WeatherWatch got installed? it should be 1.0.0.4.
What is generating the CSV file?
Does your PC hibernate/go to sleep or is it always running?
Are you minimizing X10WeatherWatch?
Sorry for the questions but I'm trying to duplicate here and can't.
I will make some minor changes today so if you can get your settings file to me I can test it here with any new adds I make.
>!
-
Can get them to you sometime around 3:30 PM eastern. I was using the version that had the time condition built into it and my PC is always on, no sleep, and I am using the csv file generated from the free weather exchange program. Temp is field 13 and it is set to less than 60 fire trigger. Will give more details when I get home.
PuebloPete
-
Cool.
I've made some minor changes to the way time triggers work as well as to the option selections, added a blank selection.
I just want to test your settings here in case I missed something.
>!
-
Tuicemen,
The CSV file I am using as well as the xml file are attached. Just rename the data.txt to data.csv an the other one to WS_Settings.xml. The basic idea is this. All triggered x10 commands fire off macros, all the macros do are set and clear flags. Since your program checks the triggers in order, I do not use your built in temperature trigger, instead I start with the month if it is less than 13 (it always is), then I trigger a D4 OFF which clears all flags - I need to make sure the first test is always true so that I can get all my flags turned off. This way at each check, I start fresh with flags off. Next I check the temp, if it is below 55, I fire a D4 ON which is a simple macro that sets flag 1. All the subsequent triggers then check and if the condition is met, fire the D4 ON which sets the flag. I use no else line. This way, if any one of my conditions is true, my flag is turned on, no matter where it is in the checking order. If none of them are true, then I assume the flag stays off, since D4 ON never fires. My logic is that each time it checks, every 10 minutes of whatever, it will always turn off the flag, because of the month condition, then it will check each of the other to see if they are true. If any are, it turns my flag on. Hope this makes sense.
PuebloPete
-
OK I see what your trying to do!
When I throw your setting into the mix it all screws up.
part of the issue is you have two paramiters for temperature and two for weather. That's messing with the logic in the program.
Also if you wish the month condition to fire first then it needs to be opposite the Programs Temperature Condition. And even then I'm not sure that that will be enough. I'm testing out a build that should force the timer to stay running.
I'll email you a copy so you can test on your end with the changes I've stated.
If the timer stops it should give me an idea where to look.
>!
-
Tuicemen,
I will try the things you sent my way and the instructions, but it seems that today, version 1.004? is working better. It seems to take 2-3 cycles of the timer for it to update, but eventually the window updates and it appears to work. Not sure why it was not before, but I am sure that it was on all night one night and no change in that window. But the last few hours it has worked fine. Again, I will still change my file structure and unzip the file to test it out.
PuebloPete
-
Tuicemen,
I cannot get the executable v 1.0.0.5 to open. Right after it opens it closes with one of those error messages that says it has encountered a problem, then asks if I want to send the error report to microsoft. It is the same type of message that one gets when internet explorer has a problem. So, I cannot test that file, as it will not open on my windows 2000 machine. Note, windows 2000 only uses IE version 6 something, nothing higher was ever developed for Win2000. I did note that the old version 1.0.0.4 "seems" to be working ok now, (have not tested all conditions) except for the fact that the timer settings do not seem to be correct. No matter what I set the timer interval for, it is running every 1 or 2 minutes, I have tried 9, 10 and 11 minutes and in the AHP activity log, it show the trigger firing off every 2 minutes. Any other ideas? Sorry I am having such a time with this.
PuebloPete
-
Back up your x10WeatherWatch.
Then place the file I sent in your existing x10WeatherWatch overwriting the existing one.
it needs the dlls in that folder.
If you still have the temperature and wind conditions named the same as the default ones or not using the default once that will cause delays as the program is sorting out the missmatch.
Fire times here corespond to the value from the slider.
-
My x10weather watcher executable is in the PC Companion directory. I overwrote the one inside with the new one in the zip file, but cannot get it to work, what happens is what I posted earlier. The older version I am still running seems to be working fine. I rearranged the setting, as in the jpg file you sent. Timer works, but no matter what the setting, it is checking every 9 minutes, but I can live with that. I may go back to the older version before you put in the temp, wind direction and wind speed. That one worked fine for me. Thanks for trying.
ThePuebloPete
PS if the version 1.0.0.5 executable ever works for me, I will let you know.
-
Sorry to hear the test file won't work for you! I should have a new version ready soon which fixes some things that may have been causing a stop in the timer.
One thing I noticed was when the program that was generating the file had control of it, X10weatherwatch would have a large delay maybe even stop completely.
Also if you clicked save it stopped the timer and failed to start it, so if you save make sure you restart .
You also are trying to do something that the program wasn't designed to do, but at least it is working for you.
>!
-
Thanks, that clicking "save" part was what I was doing, that is why the timer all of a sudden started working again! Didn't even realize I did that. anyway, cannot go back to the old version cause that was the version the wouldn't start minimized! -:) I'll use the current 1.0.0.4 for a while, as I said the 9 minute timer, I can live with. I'll try uninstalling the pluginpack then reinstalling and starting with a new config file to see if that helps. Keep up the good work! #:)
-
Tuicemen,
BTW, B:( how would I have ever know that I needed to put the "month" variable opposite your "temperature" variable? I have to admit, it works that way, but I was under the impression it checked the variables in order? so I just figured that the month would have to be first?
-
Tuicemen,
BTW, B:( how would I have ever know that I needed to put the "month" variable opposite your "temperature" variable? I have to admit, it works that way, but I was under the impression it checked the variables in order? so I just figured that the month would have to be first?
You wouldn't rofl
When I expanded the paramiter number I didn't want to change what previous users had configured/saved. Like I said your using x10WeatherWatch in a way I'd never thought of.
By the way the new Plugin pack update is posted. download button in x10WeatherWatch should get it. ;)
>!
-
Tuicemen,
I will try the new plug-in pack, but am happy to report that apparently uninstalling and reinstalling, corrected the timer issue. As of now, version 1.0.0.4 is working flawlessly, at least the things that I am using it for! FYI, the way I am using it relates to my garage door. Basically, setting a foul weather flag, which then indicates that my garage should automatically close when left open (Seems like everyone in the family cannot grasp the idea of closing the thing when they come inside, so I end up with snow in the garage, rain, and piles of leaves blown into it, or I was heating the outside in winter. So I needed a way to check lots of "foul" weather conditions.
If I do download the new pack, do I still leave everything the same in the config file? I mean, the month trigger still opposite the temp trigger? Also, is the month checked first? What is the exact order in which the conditions are checked? Thanks again.
-
Apparently I spoke too soon, for whatever reason, version 1.0.0.4 runs perfectly for a few hours, then it starts going haywire. I am back to the on/off/on/off scenario, where everytime the timer goes off, it alternates between sending a d4 ON and a d4 OFF. Also, the newest version will not run on my windows 2000 PC, must not be compatible with that OS. Any chance you could send me the version before you hardcoded the temp, wind speed, and wind direction, with the fix that made it start minimized? :angel:
-
Ah Windows 2000, seems I read somewhere it didn't work well with net 3.5
Ill check to see what net version it was built with and see if I can build a version using an earlier net.Framwork.
As for building a custom old version. I've discarded all that code. :(
-
Tuicemen,
:( I seem to be having weather watcher live issues again. It appears that although the program lists the time wwl starts and the time it updates, it is not actually updating, ie the weather inside the box does not change. I verified this by copying the weather info that WWL aquired at startup and comparing this to what it had listed after 3 consecutive updates. It was identical, even though the CSV file had changed. I have attached my xml file. I am using the latest version that give the time of the most recent update. As I said, this time changes, but it does not actually change the weather info. I noticed this recently due to the fact that the weather is getting warmer and my flags were not getting updated. Hoping you can look into this. In the meantime I will try and uninstall reinstall.
Thanks
-
Tuicemen.
8) My observations after watching this thing for about an hour one day. If you start WWL and do not touch it after that it works well. The moment you double click it to take a look at the interface itself, it will then fail after this. Does not matter if you change the settings, save it or not. Just looking at the window where all the weather info is captured causes the program to run a cycle or 2 more, then it fails (although it keeps saying in the interface that a check occured, no new info is captured in the window). I have verified this on numerous occasions since discovering this bug.
Also, a bug exists in the PC companion portion where one can set up, up to 4 temperature triggers. I am trying to get one thing to happen if the temp is above 55 and another if it is below 55. My first condition is the greater than one. If the temp is greater than 55 do A, the second one is if the temp is less than 55 do B. When you test the perameters the program will alternate between finding both conditions unmet, and finding the correct condition, subsequently firing the correct x10 PLC. For example, parameter check 1, both conditions do not meet the parameters (even though one does). Second check, the correct condition is acknowledged and the correct x10 code is fired, third check, again both do not meet the parameters, 4th check, as in 2nd check above. Seems PCC cannot keep track of the temperatures. rofl
FYI
-
Sorry for the slow reply, I was at the cottage and internet up there seemed to down every time I tried to get on! :'(
I'll look into these issues.
With the weather plug in I've found that it seems to stop checking info if it tries to access the file at the same time the file is being created.
I've fixed that issue (in my tests), perhaps the issue your seeing is related as I can't seem to recreate your issue.
Once you look at the interface are you just leaving it in normal view, minimizing or saving?
In PCC there was an issue with the conditions but I thought that had been resolved.
I guess this needs to be reexamined. ::) :'
-
Just reexamined PCC temperature triggers.
I had added a simple means to prevent a x10 command from being sent for each time the program checks the temperature which resets if no x10 signal is sent.
Not the best method but it does prevent x10 sends each time tempertature meets the paramiter.
I've made a note to explore a better option for the next release. I may even add a option to disable multiple send prevention.
In X10WeatherWatch I'm still unable to reproduce your issue even with the current release version.
I'm using VirtualWeatherStation to generate the CSV file that X10WeatherWatch uses.
I've tested with the WeatherExchange as well and unable to recreate your issue B:(
I'm unable to test with WeatherWatcherLive (WWL) as this is trialware and my trial expired.
Could this be a WWL issue? ???
I'll keep testing with what I have.
>!
-
Tuicemen,
I am using the CVS file created by weatherexchange. I have checked this numerous times and as long as I leave X10weatherwatch alone after it starts, it all works fine, but if I click on the icon in the tray to maximize it so that I can view it, then I minimize it again to the tray, it may check 1 or 2 times after that, but then it fails to actually check, even though the indicator says that it did indeed check. For instance, before I went to bed, it was about 45 degrees, I noted the temp, conditions, wind speed, etc., then maximized x10WW, then minimized. When I woke up next am, checked temp outside and it was 65. Went down and maximized, compared conditions and they were exactly the same as night before, temp in window said 45, etc. I noted that x10ww said last check about 3 min ago, so did a manual refresh and all paramiters immediately changed to 65 degrees and proper conditions and wind speed. So I sat and watched my AHP log one day, having it check every 2 minutes, again worked fine until I maximized and took a look at the conditions in the window, then minimized it. After this it checked once or twice, then nothing else in the log after that ( I would manually edit the CSV file in between checks). I will try to reproduce again, or I can send my XML file to you. But I am certain of this. For now, knowing it works as long as I don't touch it after it starts is fine with me.
As for the other issue, there is definitely something going on, as I had one x10 command firing if temp was above 55 and another firing if it was below 56. With the check box check so I could hear what paramiters were met, it would first get it correct, then the next time tell me both paremeters were not met, even when one should have been. Then the next time, correct again, then both incorrect. For now, I just quit using that part and set it up to work with the x10ww.
Hope that helps.
Jeff
-
I noticed you don't have the temperature being displayed as the icon maybe that is the issue.
I'm currently running with your settings XML file
I've change your time settings from 17 to 1 to test then i'll test with your time interval as that maybe the issue
How offen is WeatherExchange set to update?
Currently mine is set to 1 min.
As for the other issue, there is definitely something going on, as I had one x10 command firing if temp was above 55 and another firing if it was below 56. With the check box check so I could hear what paramiters were met, it would first get it correct, then the next time tell me both paremeters were not met, even when one should have been.
PCC reports paramiters not met if it doesn't fire off a X10 command (not the best wording so I'll change that fact)
>!
-
Right now it was set to update every 13 minutes, the csv file is update by weather exchange every 5 minutes. I don't have temp icon showing, just reg icon in tray, but I will try that.
-
I just can't recreate your issue here! ??? B:( B:(
I'm using all your settings both in X10WeatherWatch and WeatherExchange
How are you minimizing?
Are you double clicking on the system tray icon to minimize, clicking the minimize button at the top of the screen, or clicking the big red minimize button?
Maybe it's a Win 2000/.netframework issue. ??? ???
-
Maybe it is a win2000 thing. I just ran it last night again, started X10 WW, then from the minimized state, double clicked to open it. Viewed the info in the window, then selected it and CTRL - C copied it. Pasted it to a post-it, then closed X10 WW. Immediately restarted it, double clicked the minimized icon, looked at the weather info in the window, then clicked the minus sign to minimize it. Ran it all night without touching it. IN morning, double clicked the minimized icon, looked at the weather info in the window and it was identical to the info I pasted to the post-it note the night before. When I looked, it indicated it had been updated just 4 minutes before I opened it, but that was not the case as the info was the same as night before. At this point I hit restart timer, and the weather info in window immediately updates to current condition (temp was 20 degrees warmer than night before). I know it was not working since my flags were set according the previous night temps.
If I get time I will put X10 WW along with PC Companion on my windows XP machine and see if it works, if so, the we will know it is either a Windows 2000 issue or some program I run is interfering. Here is copy of my XML file in case the one you have is different.
-
I've posted a new plug-in build with with some minor changes to X10WeatherWatch.
The only time I had the program fail to read the CSV file was if WeatherExchange was creating the file at the same time. In that case XP threw a error screen, maybe 2000 doesn't do that.
In any case the program now waits 2 seconds if another program is accessing the CSV file then rechecks.
>!
-
:) Tuicemen
Fairly certain that that was the issue as your latest plug-in build does the trick. I say "fairly certain" since I made no other changes on my machine, only installed the updated plugin. Windows 2000 appears to not report an error if the files are being accessed at the same time, instead it just stopped working and updating. With the new build everything is cheesy :D once again!! Thanks again.
-
Thats good to know!
I've got my fingers crossed! rofl
>!
-
Hi
I have been reading this post because I have a Davis weather station and virtual weather station that is running 24/7 on a laptop.
I configured it to create a CSV file for PCC.
I setup PCC to read the file and it worked great
BUT...
When I save the configuration and close the X10 triggers window, when I reopen it all my settings are GONE!!!
I am using the trial version for now as I don't have my AHP and CM15a yet, but was wondering vats goink on!
Also, not related to the weather portion, when I open the layout, my system goes to a crawl, is jerky (in time with the nag message), and will not close.
All I get is the windows "ding" whenever I click on ANY of the buttons and I have to use task manager to kill the app. NOT GOOD.
Any Ideas???
BTW.... I am running on a win2K box.
-
Your weather settings issue is because your using the trial version.
The weather station setup merly shows the way the weather plug-in gets the info from your CVS file.
The weather station setup doesn't save it's settings as there is nothing it can do with that info.
Even with the full version you would still need the plug-in pack to make use of that.
I guess that needs a clearer message then the "Sample Showing CVS retrieval, No X10 Triggers! at the top of the screen!
???
The Floor plan display is probably also trial version related as there is a scrolling nag screen which makes setup very difficult!
It can make button presses hard to perform and even slow down the machine if memory is low in the machine though I suspect that isn't the issue.
I had played with settings for the scrolling nag for quite some time on a XP system.
If I make it scroll faster, setup is impossible.
Slowing it down more makes the screen seem to lag even more giving the appearance that your machine has come to a crawl.
I'll look at making changes to the trial version to improve this area as lots of users like this floor plan display of their x10 setup.
Possibly even remove this scrolling nag and replace it with a pop up!
>!