Announcement

Collapse
No announcement yet.

Restart PI

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

    Restart PI

    Hi,

    Writing to let you know that for whatever reason the "restart plugin" plugin does not work for Spud's Chromecast PI. I tried both V1 and V2 (on HS3) and it doesn't work with either. Interestingly it works for other PIs.

    Here's what I see in the log:

    Code:
     
    Jul-02 7:46:06 PM Jon00Plugin Disabling Plugin: Chromecast
    Jul-02 7:46:06 PM Jon00_Plugin Error in Main Block 3: System.Net.WebException: The operation has timed out. at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in :0 at System.Net.HttpWebRequest.GetResponse () [0x00016] in :0 at scriptcode2.VBWrapper.Main (System.String Parm) [0x00fed] in <048effb2c7c34671ad1e829947b14bcc>:0
    Jul-02 7:45:48 PM Info Plugin EasyTrigger has connected. IP:127.0.0.1:48034
    Jul-02 7:45:46 PM Jon00Plugin Enabling Plugin: EasyTrigger
    Jul-02 7:45:25 PM Info Plugin EasyTrigger with instance: has disconnected
    Jul-02 7:45:25 PM Plug-In Shutting down Plug-In: EasyTrigger
    Jul-02 7:45:25 PM Jon00Plugin Disabling Plugin: EasyTrigger

    #2
    Odd. Are you on Linux? If you restart HS3 and then try to disable the Chromecast plugin first (i.e without disabling EasyTrigger) does that work?



    Jon

    Comment


      #3
      Hi,

      Yes, on linux. Also not running default port (not sure if that matters).

      Interestingly, restarting homeseer seems to make it work for a short period of time then it fails again.

      Comment


        #4
        Ok, it has nothing to do with Spud's Chromecast plugin. This issue has been around for some time with Linux builds. Provided you are on the latest version from my site, please try the suggestion in this thread: https://forums.homeseer.com/forum/3r...49#post1298349
        Jon

        Comment


          #5
          Thanks for the tip. Unfortunately neither of these settings fixed the problem although the error in the log no longer appears. (On v 1.0.6)

          Comment

          Working...
          X