I have a CM11a hooked to a dedicated system running XP. If the system is up for more than 2 days, the device triggered by the first ON event (5pm)will turn on, then right off. The rest of the sequences and events work fine. If I trigger it through HS manually, I get the same result. However, If I reboot the system then all is well. I have duplicated the problem with different modules in different locations so I am assuming it has to do with the CM11a or XP. I set the machine to auto-reboot once a day and everything works fine, but I would prefer to actually fix the issue instead of using a workaround. Any ideas? Thanks!
Announcement
Collapse
No announcement yet.
XP/CM11A going to sleep after idling too long?
Collapse
X
-
MarquiTags: None
-
Marqui
Ok, I turned on "Log raw communications" and saw that there was an external command sending the OFF command to that house code! I have no idea where it was coming from. I changed the code on that device so it should be fine. How do I track down what was doing it? I have the CM11a on the pc, and one wireless reciever in another room. There havent been any batteries in the CM11a, so where would that external command come from?
Comment
-
Marqui
It happened again, here is what the log is showing, I'm still a newbie and have no idea waht this means.
11/10/2003 4:59:18 PM~!~Event Trigger~!~External Trigger (Family Room Lamp OFF) F2 Off (Family Room Family Room Lamp)
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Sending: 4 9E Size: 2
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Got checksum: A2
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Sending: 6 93 Size: 2
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Got checksum: 99
11/10/2003 4:59:18 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:19 PM~!~Event Trigger~!~External Trigger (Family Room Lamp OFF) F2 Off (Family Room Family Room Lamp)
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Sending: 4 9E Size: 2
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Got checksum: A2
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Sending: 6 93 Size: 2
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Got checksum: 99
11/10/2003 4:59:19 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:20 PM~!~Event Trigger~!~External Trigger (Family Room Lamp OFF) F2 Off (Family Room Family Room Lamp)
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Sending: 4 9E Size: 2
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Got checksum: A2
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Sending: 6 93 Size: 2
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Got checksum: 99
11/10/2003 4:59:20 PM~!~DEBUG~!~CM11A Checksum OK, sending 0
11/10/2003 4:59:21 PM~!~DEBUG~!~CM11A Got ack of: 55
11/10/2003 4:59:21 PM~!~Event Trigger~!~External Trigger (Family Room Lamp OFF) F2 Off (Family Room Family Room Lamp)
Comment
-
Marqui
That one event had the force trigger of "off" in its run events list! It was the only event that had an entry, an per HS help- Be careful that you do not select the current event without checking its conditions. This would cause a loop where HomeSeer would be continuously triggering the same event.
BINGO!
Thanks for helping the Newbie! I'll let you know the next time I mess something up!!!
Comment
Comment