Announcement

Collapse
No announcement yet.

Weird Command Times

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weird Command Times

    I have an HSM100 sensor in our bedroom and at times it take a few extra, 20 or so, seconds for the light to come on that it is controlling. Then it will go back to turning it on almost instantly. Here is a log snip from this morning:

    12/4/2009 5:26:44 AM Device Update Device: 1st Floor Master Bedroom Multilevel Sensor 26 Motion Detector value set to 255 ()
    12/4/2009 5:27:00 AM Device Control Device: 1st Floor Master Bedroom Ceiling Fan Light (Q24) Dim 54%



    12/4/2009 5:31:04 AM Device Update Device: 1st Floor Master Bedroom Multilevel Sensor 26 Motion Detector value set to 255 ()
    12/4/2009 5:31:04 AM Device Control Device: 1st Floor Master Bedroom Ceiling Fan Light (Q24) Dim 54%

    In the first example the light command took 26 seconds to execute. In the second one it was right away. It seems like this happens after the sensor has been in a No Motion state for a little bit. Does anyone have any ideas what might be causing this? Has anyone else seen anything like this?

    Thanks.

  • #2
    I have seen similar symptoms.

    http://board.homeseer.com/showthread.php?t=135054

    I have my battery report once per day. I have disabled logging of temperature and light levels as one correspondent suggested. Qualitatively I'd say it's better, but I have no data to back it up.

    I am still running 2.3.0.19, I believe latter versions have a lot of Z-Wave updates. What version are you running?

    Mark

    Comment


    • #3
      Mark,

      I am on 2.4.0.1. I will take a look at my settings and see what the temp and light are doing and see if it helps.

      Thanks.

      Comment

      Working...
      X