Author |
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: October 28 2008 at 20:16 | IP Logged
|
|
|
One of the things I have in my system is an alarm clock and it has not worked for the last two days. My speakers (06.21.4D) are not turning on, and I think this is related as it happened at the right time.
Quote:
2008-10-28 06:00:08.750 TX 02 62 01 86 21 05 28 00
2008-10-28 06:00:10.421 RX CTLR NAK=02 62 01 86 21 05 28 00
2008-10-28 06:00:11.421 TX 02 62 01 86 21 05 28 00
2008-10-28 06:00:11.468 RX SENTINSTEON=0D FB AA 01 86 21 05 28 00 06
2008-10-28 06:00:11.656 RX RECEIVEINSTEONRAW=01 86 21 0D FB AA 21 28 00
2008-10-28 06:00:11.687 TX 02 62 06 21 4D 0F 11 FF
2008-10-28 06:00:11.703 TX 02 62 01 86 21 05 2B 22
2008-10-28 06:00:11.718 RX CTLR NAK=02 62 01 86 21 05 2B 22
2008-10-28 06:00:21.937 TX 02 62 01 86 21 05 2B 22
2008-10-28 06:00:21.953 TX 02 62 01 86 21 05 2B 22
2008-10-28 06:00:21.984 RX CTLR NAK=02 62 01 86 21 05 2B 22 |
|
|
Can anyone confirm this?
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: October 28 2008 at 20:34 | IP Logged
|
|
|
So what have you plugged into an outlet recently? I know the frustration as I do the same thing.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: October 29 2008 at 07:28 | IP Logged
|
|
|
Heh. This time, nothing.
Here is the line from the log. There are no Insteon commands in the area.
Oct 28 2008 06:00:05 Macro Macro REMOTE SPKRS ON executed.
This may be the Timed Event issue!
Here is the first portion that has the correct address.
Quote:
2008-10-28 06:03:39.375 TX &nbs p; 02 62 06 21 4D 0F 19 00
2008-10-28 06:03:39.406 RX SENTINSTEON=0D FB AA 06 21 4D 0F 19 00 06
2008-10-28 06:03:39.718 RX RECEIVEINSTEONRAW=06 21 4D 0D FB AA 2B 00 00
2008-10-28 06:03:39.781 TX 02 62 06 21 4D 05 28 00
2008-10-28 06:03:39.812 RX SENTINSTEON=0D FB AA 06 21 4D 05 28 00 06
2008-10-28 06:03:40.109 RX RECEIVEINSTEONRAW=06 21 4D 0D FB AA 21 28 00
2008-10-28 06:03:40.140 TX 02 62 06 21 4D 05 2B 30
2008-10-28 06:03:40.171 RX SENTINSTEON=0D FB AA 06 21 4D 05 2B 30 06
2008-10-28 06:03:40.437 RX RECEIVEINSTEONRAW=06 21 4D 0D FB AA 21 2B 20
2008-10-28 06:03:40.468 TX 02 62 06 21 4D 05 2B 31
2008-10-28 06:03:40.484 RX SENTINSTEON=0D FB AA 06 21 4D 05 2B 31 06
2008-10-28 06:03:40.750 RX RECEIVEINSTEONRAW=06 21 4D 0D FB AA 21 2B 00 |
|
|
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: October 29 2008 at 08:19 | IP Logged
|
|
|
They look like erroneous commands, some Direct, being sent to the PLM. It may be another Timed Event problem.
One other note, if the trigger fires at 06:00, why the PLM traffic at 06:03?
Edited by BeachBum - October 29 2008 at 08:27
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: October 29 2008 at 13:16 | IP Logged
|
|
|
Quote:
One other note, if the trigger fires at 06:00, why the PLM traffic at 06:03? |
|
|
A question for the ages!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: October 29 2008 at 16:06 | IP Logged
|
|
|
Tony,
In your first post you're getting CTLR NAK messages meaning that the PLM didnt accept the command for some reason. I checked the code and see two places where this can happen. Basically you try to send a command to the PLM and it rejects it because it's busy. You can see the first message is sent, a CTLR NAK, the message is retried, and it's successful. Then you have the command to turn on the speakers (11.687) immediately followed by a peek command to the device we addressed earlier at the top of your log (11.703). This command came in way to quick resulting in a CTLR NAK of that command and apparently obliterating the command to turn the speakers on. Bottom line, this is a problem that Ive got to get fixed because the direct processes (turn the speaker on) are not playing nice with the background processes (the peeks and pokes). Im in the middle of rewriting this portion of the PLM module to fix this problem.
The second set of logs are just coincidental and are the standard peek and poke background processes for that device. If the log is showing the Timed Event is firing but is not showing the macro as executing, this is most likely an error in the timed event formula. I was helping Craig with this the other day and this was his exact problem. I found it by going to the Timed Events, right clicking on the action formula and doing "Check Formula". Everyone of his timed event formulas was returning a "!" and so werent executing. Everything looked fine until we double-clicked the formula to bring up the formula editor and then it became apparent that the double quotes being used were not the standard type having copied/pasted from the forum and getting MS Word type double quotes. Probably not your problem, but maybe similar and the "Check Formula" might point us in the right direction.
Dave.
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: October 29 2008 at 19:55 | IP Logged
|
|
|
Thanks Dave. At least we caught something!
The Timed Event Type in this case is a macro, as is my other TE issue.
|
Back to Top |
|
|