Announcement

Collapse
No announcement yet.

408 Request Timeout Errors

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

    #16
    Originally posted by kevini View Post
    Yes, it has been solid, has not missed a beat and never had a timeout. I have the poll at 30 seconds too.

    I saw the same issue on my Legacy Eagle with the blinking cloud LED.
    Thanks! I think my utility has a $25 device rebate going now. Maybe I will pull the trigger on an upgrade.

    Comment


      #17
      Originally posted by Kitar View Post
      I am also noticing 408 timeouts on a Eagle Legacy-100

      The plugin itself does not give any indication that there is a problem. It would be nice if we could test for this in an event and create some kind of alert that the data has not been received for XXX seconds.

      Looking at the Plug-In management page everything looks good, no indication of any sort of failure. The PI management page should at least turn the icon amber if the PI is not receiving the data.

      Aside from these minor things I think the PI looks pretty good.


      spud, I've noticed that if my web browser is open and has one tab pointed at Rainforest's portal then there are no 408 errors. As soon as the browser is left to go idle and the PC sleeps the 408s return... Oddly my browser is not even on the same PC as the HS installation and plugins, but it is on the same subnet. Put another way: I get 408s every 100 seconds, which is what the timeout value is set to, but as soon as I open my browser with a background tab pointed at this URL the 408s disappear. It does not matter if the Rainforest tab is the active window.
      PI ver. 3.0.0.4

      Code:
      https://rainforestcloud.com/rainforest/user_portal/php/main.php?view=gateway_gui&cloud_id=xxxxxx
      I hope that helps somewhat. Aside from the 408 it seems to be a very tidy plug-in.
      Last edited by Kitar; October 12, 2018, 03:29 PM.

      Comment


        #18
        Originally posted by kevini View Post
        Yes, it has been solid, has not missed a beat and never had a timeout. I have the poll at 30 seconds too.

        I saw the same issue on my Legacy Eagle with the blinking cloud LED.
        I can confirm. I swapped out my Legacy Eagle for an Eagle 200 a couple of days ago, and so far - rock solid and no timeouts.

        One observation about the -200, the Zigbee radio doesn't seem as powerful. My -100 Eagle was installed about 80 feet from my meter, and connected without issue. The -200 would not work in the same location, and I had to move it to within about 30 feet of the meter in a spare bedroom. I don't have a LAN connection in that room, but fortunately the -200 has WiFi, so I am good to go. I will keep monitoring and report back if I encounter any issues.

        Edit: Just to update, I am seeing a couple of (504) Gateway Timeouts today with the -200 Eagle. No (408) Timeouts though.
        Last edited by automateme; October 15, 2018, 07:16 PM.

        Comment


          #19
          FYI, I implemented local polling for the Legacy Eagle, see this thread.

          Comment

          Working...
          X