Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jjsalobird]

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

[jjsalobird]

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

[Tuicemen]

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.

[jjsalobird]

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.

[Tuicemen]

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.
 

[jjsalobird]

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! 

[jjsalobird]

Tuicemen,

BTW,  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]

Tuicemen,

BTW,  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
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.
 

[jjsalobird]

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.

[jjsalobird]

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? 

[Tuicemen]

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.

[jjsalobird]

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

[jjsalobird]

Tuicemen.

  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.   

FYI

[Tuicemen]

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.

[Tuicemen]

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

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.