Announcement

Collapse
No announcement yet.

Status on Google Groups sayings "buffering" on occasion..

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

    Status on Google Groups sayings "buffering" on occasion..

    I am triggering some simple speak events to my Google Speaker groups. Sometimes, it works fine. Other times, it says "buffering" and sits there for a long period of time. I noticed similar things with the GoogleCast plugin as well. Any ideas?
    HS3 Pro Edition 3.0.0.435 (Windows Server 8.1 on ESXi box)

    Plug-Ins Enabled:
    Z-Wave:,RaspberryIO:,AirplaySpeak:,Ecobee:,
    weatherXML:,JowiHue:,APCUPSD:,PHLocation:,Chromecast:,EasyTr igger:

    #2
    Originally posted by wpiman View Post

    Attached as file. I have a simple event to just speak something from each of the plugins to speaker group.

    It didn't work at one point, then I logged into the app and saw that group was casting-- so I stopped it. I then spoke and there was a long delay, but it worked.

    Your plugin gives a lot more feedback which makes it worth it.

    I was just typing this and another announcement came through from the test event. Maybe 2 minute delay, and the Google Home app didn't show anything being stuck casting. Odd.

    What does "changing media" mean? I bought some new Amazon TVs and I wonder if that is messing with Chromecast or something?

    castLog.txt

    castLog.txt

    I copied this from your HS3 thread, correct?

    Comment


      #3
      Yes. I am experiencing the issue on both plugins.....

      I followed up here as well with someone else seeing something similar...

      https://forums.homeseer.com/forum/hs...-changes-again

      I have strong wifi so I can ping the speakers just fine...
      HS3 Pro Edition 3.0.0.435 (Windows Server 8.1 on ESXi box)

      Plug-Ins Enabled:
      Z-Wave:,RaspberryIO:,AirplaySpeak:,Ecobee:,
      weatherXML:,JowiHue:,APCUPSD:,PHLocation:,Chromecast:,EasyTr igger:

      Comment


        #4
        Couple of updates.... I notice occasionally Google would change the whole house default IP address. My guess is it picks whatever one has had the best and most stable connection...

        11/4/2022 3:17:08 AM
        AK GoogleCast
        Warning
        [4182] 'wholeHouse': 'wholeHouse': IPEndPoint changed: 192.168.0.168:32011 (from 192.168.0.193:32011)​


        That may or may not lead to the errors. But I am seeing this in the log now.....
        11/5/2022 1:46:27 PM

        AK GoogleCast
        Warning
        [4182] 'wholeHouse': SendMedia: http://192.168.0.5:80/Wave/Cast/Goog...2351440-en.mp3 (audio/mpeg): Expected app: 'CC1AD845', but running: '' (wholeHouse): [HSPI_AKGoogleCast.CastDevice]
        11/5/2022 1:46:27 PM

        AK GoogleCast
        Warning
        [4182] 'wholeHouse': Not started application CC1AD845 timeout 10000 (wholeHouse): [HSPI_AKGoogleCast.CastDevice]
        11/5/2022 1:46:17 PM

        AK GoogleCast
        Info
        [4182] 'wholeHouse': SpeakText: The back door has been opened for 5 minutes. Turning off the downstairs air conditioning and heating. (True)

        HS3 Pro Edition 3.0.0.435 (Windows Server 8.1 on ESXi box)

        Plug-Ins Enabled:
        Z-Wave:,RaspberryIO:,AirplaySpeak:,Ecobee:,
        weatherXML:,JowiHue:,APCUPSD:,PHLocation:,Chromecast:,EasyTr igger:

        Comment


          #5
          https://forums.homeseer.com/forum/hs...31#post1595831

          Comment

          Working...
          X