The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: xPLMediaNet Update Published


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: script problems...


  • Subject: Re: script problems...
  • From: Adrian <yahoo@xxxxxxxxxxxxxx>
  • Date: Thu, 25 Aug 2005 17:34:16 +0100
  • References: <20050825160000.AA8BB35AD06@mx1.nildram.co.uk>

I can see the hearbeats in the viewer (as the happen every 5 mins), the=20
other messagess only come at dawn and at dusk. Yes, it is the windows=20
service version. I tried deleting the

JOHNB_DAWNDUSK_DAWNDUSK.xpl file to see if would recreate it when a
message=
came in and it did.=20




Tony Tofts wrote:

>>have got the dawndusk module bit i cant get the scripts to=20
>>work for it, what i am doing wrong? I had some of tonyt's=20
>>code which i modified (as change the tonyt_dawn... to=20
>>johnb_dawn...) as my dawndusk module is set with johnb.  I=20
>>stripped the code so i could see what if any sub was being=20
>>hit (the heartbeat should be as you get one every 5 min) but=20
>>none of the global variables are being set suggesting this=20
>>script isnt being looked at. In the monitor, the heartbeat=20
>>comes through as "johnb-dawndusk.dawndusk", the script
below=20
>>is located in JOHNB_DAWNDUSK_DAWNDUSK.xpl, what am i missing
>>=20=20=20=20
>>
>
>Can you see the dawn/dusk messages in the viewer (i.e. not just the
>heartbeats)
>
>I believe we're talking the windows service version of dawndusk here?
If s=
o
>I don't know much about it, so you'll probably have to wait for John to
be
>around (or someone else who's using it)
>
>Regards
>Tony
>
>=20=20
>





xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.