TimeServer/X10 Plugin problem?

[Mikeydog]

I am pretty new at using Girder and have setup an HTPC. I currently use XLobby as a front end to my HTPC and am Using a USB-UIRT and a Philips Pronto TSU6000 Remote to control Xlobby. I am also using a Firecracker X10 module to control lights around the house. Anyway I have a couple lights that I want to turn on and off at certain times of the day. So I figured out by reading through these forums that I need the TimeServer Plugin and the X10 Firecracker plugin. The X10 now works fine no problems (when used by the Pronto). But when I create new commands that use the time server to trigger x10 events some interesting things happen. For one, everytime I open up Girder (from a minimized State) it resets the first X10 Event that I click on back to A1 House code. But this only happens to X10 events that use the Timeserver plugin. Second the time events don't always seem to fire off anyway. In fact most of the time nothing happens at all.. I am not sure if this is a problem with the Timeserver plugin or the X10 plugin or they just don't play nice together.

Question about the time server. If I just want an event to start do I turn off the "Time To Is Valid" check mark.. That way I am only giving an event a single time, since I will be setting up a seperate event to turn off the lights??

Anyway any suggestions or help would be greatly appreciated.

Thanks
Mike

[Mark F]

Get and install the Logger plugin to see what the event flow looks like. Make sure you have learned the correct TimeServer eventstring value(s) to the X10 command(s).

[Treetop]

For one, everytime I open up Girder (from a minimized State) it resets the first X10 Event that I click on back to A1 House code

Hmmm, I recently upgraded to the CM11A, so I don't use the Firecracker (ak CM17A) anymore, but I still have the plug-in loaded. So I attempted to test this portion of the problem. I set up an x10 command (A2 ON) and a timeserver event. It did appear to reset the house/unit code at first glance. The first time I clicked on it, the dialog box started at the default A1. The second time, in a row, that I clicked on it, it had the correct code A2. I don't think its really resetting it to A1, rather the dialog box is just starting at A1, by default, the first time it is open.

For the Cm11A/12U plug-in, it opens with the last command typed in. So if I made a bunch of x10 commands (A1 ON, A5 On), when I click back on A1, it will display A5 ON.


Second the time events don't always seem to fire off anyway. In fact most of the time nothing happens at all.. I am not sure if this is a problem with the Timeserver plugin or the X10 plugin or they just don't play nice together.


Well, they do play nice together on my end, so Im gonna bet that it is actually something related to the signal being passed from the CM17A to the transceiver (onto the powerline) to the lamp module. But just to make sure...

Do you get 100% accuracy when not using the timeserver plug-in (ie. you test the command)? Is the Lamp module and transceiver on the same power phase (most houses have two phases... 220v is split to 2 110v lines feeding different parts of the house... this is where an x10 coupler comes into play. So if the transceiver is on one phase, and the lamp module on another, the signal will not cross over to the other phase (unless you have a coupler). Not sure if that is clear or not.

To eliminate any problems between the Cm17A and the transceiver, put the lamp module on House code A / Unit code 1. This way when it is triggered, you will hear an audible click from the transceiver. If you get this far, the you know that the problem with the signal is on the powerline. Move the lamp module to an outlet in the same room (preferably on the same wall) and test again. Is the signal getting to the lamp? Every time?




Question about the time server. If I just want an event to start do I turn off the "Time To Is Valid" check mark.. That way I am only giving an event a single time, since I will be setting up a seperate event to turn off the lights??


I believe you can do this. I have reminders set-up, using the Say plug-in, which will be announced over my speakers (ie, Sunday night at 11pm..."did you remember to take the trash out?") The "time to is valid" doesn't come into play, as I have this set-up to run just once, every week. BUT, for holidays and birthdays, I wanted it to say "Happy birthday Treetop" every hour, on the hour (this way it wont go off,, during the middle of a tv show, just during commercials). So I have the start time set to 8am, and the end time set to 22:00:01. So for this, I have the date to/from set for that day, and the every hour box checked.

If your asking, does the time "to" will send an off command on its own... the answer is no. If you want a lamp to come on everyday at 5pm, you would check the "everyday" box, and have the start time as 5pm. I would also put the end time as 17:00:05, just to release it from its duty, since I dont want it to do anything again till tomorrow. Another thing I would do, is type in the time and days for the event in the comment box. This way you can easily tell what time and day the event is set for, without having to go back to the timeserver gui.

If your still not having any luck, post back. BUT, more importantly, if you find the fix... POST BACK the workaround, in case any others come across this problem too.

Good Luck,
Treetop