Announcement

Collapse
No announcement yet.

Aborting poll issue

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

  • chewie
    replied
    One thing I have tried to do in my network is randomize my polling times for any non updating devices (I use a lot of Cooper switches so I do not have to poll those). This has resulted in my polls being fairly consistent and not having too many stomping issues.

    Example: If I want to poll every 5 minutes instead of using 300 seconds I use 286 or 308.

    Leave a comment:


  • luvatlast
    replied
    I seem to have been able to eliminate my problems with some adjustments to polling times and eliminating polling of some lighting devices. Not perfect but the errors have stopped except for some occasional ones.

    Leave a comment:


  • drozwood90
    replied
    The script is pretty simple:

    Code:
     
    Sub pollHVACDevices(ByVal par as object)
       Dim waitTime   = 25
       Dim myHighTemp = 78
       
       Dim pi As Object 
       Dim tempLoft As String
       Dim tempFurnace As String
       
       Dim acUnit        = hs.GetDeviceCode("HVAC Air Conditioner")
       Dim furnaceTherm  = hs.GetDeviceCode("HVAC Furnace Thermostat")
       Dim floaterTherm  = hs.GetDeviceCode("HVAC Floater Thermostat")
       Dim floater = 2
       Dim furnace = 1
       
       'open is 2; 3 is closed
       ' http://192.168.0.2:9000/Developer/We...or_Methods.htm
       ' Mode:
       ' 0=Off, 1=Heat, 2=Cool, 3=Auto
       ' GetCurrentMode heating right now
       ' GetModeSet set for which mode now
      
       hs.execx10("Main HVAC PollStatus","ON")
       hs.polldevice(floaterTherm) 
       hs.waitsecs(waitTime)
       hs.polldevice(furnaceTherm) 
       hs.execx10("Main HVAC PollStatus","OFF")
    ' removed for winter
    '   hs.waitsecs(waitTime)
    '   hs.polldevice(acUnit) 
       Try 
          pi = hs.Plugin("ZWave Thermostats") 
          tempFurnace = math.truncate(pi.GetTemp(1))
          tempLoft = math.truncate(pi.GetTemp(2))
     '     if(hs.devicestatus("[15") = 3) then
     '        if(tempLoft  > myHighTemp) then
     '        ' if the AC has been off for it's cooldown period (5 min) then
     '        ' turn it on if the loft's temp is greater than the set point of myTempHigh
     '           if(lastChangeGreaterThanMinutes(acUnit & "|5") and hs.isoff(acUnit)) then
    ''               hs.execx10(acUnit,"ON")
     '           end if
     '        end if
     '     end if
     '     if(hs.devicestatus("[15") = 2) then
     '        hs.execx10("Q20","OFF")
     '     end if
          'need to figure out better method to check this...
          ' 0=Off, 1=Heat, 2=Cool, 3=Auto
    '      if(hs.devicestatus("[15") = 3) then
          ''   'if(lastChangeGreaterThanMinutes(furnaceTherm & "|59")) then
          ''      'if(tempLoft > (tempFurnace + 1) AND tempFurnace > pi.GetHeatSet(furnace)) then
          ''         ' if mode off and not heating
          ''         if(pi.GetModeSet(furnace)=0 AND pi.GetOperating(furnace)=0) then
          ''            ' turn the blower ON
          ''            pi.CmdSetMode(furnace,2)
          ''            hs.writelog("HVAC","Turning Blower ON!")
          ''         else
          ''            ' otherwise turn the blower off
          ''            pi.CmdSetMode(furnace,0)
          ''            hs.writelog("HVAC","Turning Blower OFF!")
          ''         end if
          ''      'end if
          ''   'end if      
    '      end if
    ''''hs.WriteLog("debug", pi.GetHeatSet(furnace))
       Catch e As Exception
          hs.WriteLog("debug", e.Message)
       Finally
          pi = Nothing
       End Try   
    End Sub
    I disabled a lot of stuff in there, as it is mostly experimental at the moment.

    I just run that script once every 10 minutes.

    --Dan

    Leave a comment:


  • reidfo
    replied
    ok, here's a quick and dirty script I wrote to poll all ZWave devices with a 2 second delay in between. Unfortunately I still can't poll my stats, even if nothing else is being polled.

    Code:
    Sub Main
        Dim en
        Dim dv
    
        Set en = hs.GetDeviceEnumerator
        If IsObject(en) Then
        Else
            hs.WriteLog "reidfoZWavePoll","The device enumerator is invalid."
        End if
    
        Do While Not en.Finished
            If en.CountChanged Then
                hs.WriteLog "reidfoZWavePoll","----- The device count has changed -----"
            End if
            Set dv = en.GetNext
            'Check to see if this is a ZWave device and then poll
            If Not dv is Nothing And (dv.misc AND &h1000) Then
                hs.WriteLog "reidfoZWavePoll","Polling ZWave device " & dv.location & " " & dv.name
                hs.PollDevice(dv.hc & dv.dc)
                hs.WaitSecs(2)
            End if
            Loop
    
    End Sub

    Leave a comment:


  • luvatlast
    replied
    probably the issues

    Originally posted by Rupp View Post
    What version of HomeSeer are you guys running? I know Rich/Rick made some adjustments to the Z-Wave timeout in the most recent version but the issue is the devices that are exhibit this behavior typically do not stay awake long enough to get this information returned in the small timing window.
    Rupp,

    I changed to Standard Edition 2.5.0.23 last weekend and the problem appeared. I suspect you are right as i am having the same issues. How can I fix this one?

    PT

    Leave a comment:


  • msbreton
    replied
    I'd also love a copy of your script

    -Mike

    Leave a comment:


  • reidfo
    replied
    Dan, this sounds like it could be my problem as well. Now that you mention it the problems with my stats started again when I added more ZWave devices and started polling them. At the moment I can't poll any of my stats reliably. Would you mind sharing your script?

    Leave a comment:


  • drozwood90
    replied
    I found it has to do with the polling stomping on itself.

    Basically, if you poll two thermostats, or two "things" too close to a thermostat, the thermostat times out...

    So, to counter this, I started to poll my z-wave stuff using a script. I turned off ALL HS polling. By using this script, it coordinates polls to thermostats. It provides enough TIME to pass before and after a thermostat so that you can get good polls. Works very well.

    Polling other devices, you can poll as fast as you can (at least everything I own...not including the locks on the doors...which I do not poll).

    --Dan

    Leave a comment:


  • reidfo
    replied
    I'm getting the same errors with my 2gig thermostats. They had been working fine for a while and this morning started having issues.

    10/12/2011 12:41:47 PM ZWave Thermostats Aborting poll of this thermostat due to and error retrieving the temperature. Node: 3I reset them this morning and it cleared up for a little while but came back. I'm using the HS 2.5.0.20.

    I planned on adding more ZWave dimmers this week anyway, so I'll see if that makes a difference. I think Rupp is probably right that it's reception related, as the thermostat in my server room next to the Z-Troller doesn't seem to have any problem.

    Leave a comment:


  • Wadenut
    replied
    Originally posted by Rupp View Post
    What version of HomeSeer are you guys running? I know Rich/Rick made some adjustments to the Z-Wave timeout in the most recent version but the issue is the devices that are exhibit this behavior typically do not stay awake long enough to get this information returned in the small timing window.
    On version ..29 here. The devices I get these warnings from are not battery operated, so no wakeup issues. Recently switched from the Z-Stick back to the Z-Troller. Same problem. All this started with the more recent versions.
    Actual operation doesn't seem to be affected.
    More than 40 modules on the network.
    .
    Note for Rich/Rick: Many users seem to have lost faith in later versions of Homeseer 2 (see multiple threads) and have reverted to earlier versions where, while the response problems may have existed, they were not being logged so verbosly. Since this type of warning seems to be so common and in most cases is not apparantly affecting operation in any way, why can it not be made optional, or relegated to the "debugging trace functions". ie. "Z-Wave debug information (64)"? In that way, the warnings could be activated when necessary to provide detailed information in thoose rare cases where there actually may be a performance problem.

    Leave a comment:


  • Guest's Avatar
    Guest replied
    My 2Gig thermostats dont update Homeseer with temp changes automatically. My version is "Professional Edition 2.5.0.20", also using a Z-Troller.

    Leave a comment:


  • alphatech
    replied
    Thanks for your input. I currently have it already extended but I will try different locations, maybe it will help.

    Leave a comment:


  • ceesmf
    replied
    Hi, had the same problem with the 2GIG thermostat
    extending the usb, ie an extension usb cable between the stick and the computer solved the problem, probably a receiving problem

    Leave a comment:


  • alphatech
    replied
    Hi Rupp,
    HomeSeer Version: Standard Edition 2.5.0.20

    Leave a comment:


  • Rupp
    replied
    What version of HomeSeer are you guys running? I know Rich/Rick made some adjustments to the Z-Wave timeout in the most recent version but the issue is the devices that are exhibit this behavior typically do not stay awake long enough to get this information returned in the small timing window.

    Leave a comment:

Working...
X