X10 senser stopped working

[jaminben]

Hi,

I've had an x10 setup working now for a few days using Girder 5 beta (demo) without any problems until today when a PIR senser stopped working. Nothing has changed and all other x10 devices still work fine with Girder.

I've tested the other devices and the senser with the default software (Harmony) and HAL which all work ok so I know for sure its not a hardware or a general windows/drivers problem.

I've uninstalled Girder and reinstalled but its still not picking up the senser like it used to. I've also tried changing the device address but that also didnt work.
I'm now at a loss as to why it will work with other software but not Girder.

Has anyone got any suggestions on how to fix this problem and does this sort of thing happen on a regular basis with Girder as I'm not too keen on purchasing a piece of software which then fails to work for no apparent reason.
Other than that I'm quite pleased with Girder and its other features like the volume OSD and Girder to Girder control.

Many Thanks

Ben

[jaminben]

Well I've just got it working again, the solution was to uninsatll Girder 5 and install Girder 4.
I then decided to return to Girder 5 and see if it would work with that and it did until I restarted Girder. Its now not working again so I guess I'm stuck with Girder 4 for the remainder of the trial period.

[Rob H]

Can you open the Lua console (press F7) and reset Girder (press F11) and see if there are any errors shown there.

[jaminben]

Can you open the Lua console (press F7) and reset Girder (press F11) and see if there are any errors shown there.

Reinstalled Girder 5 and below is the result of what you asked me to do, I think :eek:

Senser still continues to not work while all other devices are ok.


ScriptReset Start
LOG: Device Manager : 3 - Settings saved.
Component Manager Shutdown Time 46.556475753212
ScriptReset Done Calling ScriptReset Callbacks, Time: 79.080162422877
LOG: Device Manager : 1 - Initialized
Loaded LGTV Class
Loaded LGTV component
LOG: Device Manager : 1 - Provider: X10 Initialized
LOG: Device Manager : 2 - Provider: X10 Added Device M14 X10 M14
LOG: Device Manager : 2 - Provider: X10 Added Device G15 X10 G15
Welcome to Promixis Girder 5.0.0 build 523
LOG: Device Manager : 2 - DM Event: LocationList
LOG: Device Manager : 3 - Location List Update
LOG: Device Manager : 2 - DM Event: TypeList
LOG: Device Manager : 3 - Device Type List Update
LOG: Device Manager : 2 - DM Event: Add jaminbenpc\X10\G15 jaminbenpc\X10\M14


Girder 4 works ok so its not a big problem atm but I guess it will be once the trial runs out in a few weeks.

[Rob H]

And what house and unit code is the PIR sensor on?

[jaminben]

It was set to B_15 before it stopped working but I've tried A_1,A_2 & B_1 since.

[Rob H]

How are you adding the sensor device to Girder?

Any errors shown in the Lua console when you do?

[jaminben]

No errors in the console.

I add the senser by adding an event then setting the event device to Raw:X10.CM1X, click learn then make the device send an On/Off signal via the button on the device or breaking the beam. This method works well in Girder 4 but doesnt in version 5 beta.

The really strange thing is, the senser is now working in Girder 5 :) I havent changed anything except install version 5 with version 4 already installed.

I'm not sure what will happen if I uninstall version 4 so I'll leave it for a bit and see what happens.

[Rob H]

Try adding it using File|Component Manager - go to Lighting and Appliances|X10 and select the Device Manager tab.

[jaminben]

I've added the device the way you suggest above and it sems to be working. I'm going to assume that to triigger an event I have to use :-


Event
Event Device = Lua:X10
Event String = X10 B15:ON (from the drop down menu)

Now when I look at the log it shows two x10 devices clicking into action, but I have only the one connected.


Time Date Source Details Payloads
12:13:36:687 1/5/2008 xOSD xOSDnew2.gml:\New\xOSD
12:13:36:671 1/5/2008 X10 X10 B15:ON
12:13:36:671 1/5/2008 X10-CM1X B_15_On B15


Is the above log correct or should it only be listing one x10 device and the OSD Text?

Cheers

Ben

[Rob H]

The above is correct - one of them comes from the CM1X plugin and the other from the X10 device manager.

If you don't want to see the events from X10-CM1X then go to File|Settings - on the Event Log Settings tab you can uncheck the X10-CM1X device to hide the extra logged entries (any actions that are using the old style X10-CM1X events will still trigger, they just won't be logged).

[jaminben]

Cool,

Thankyou for your help :)

Ben