Announcement

Collapse
No announcement yet.

Google Home Not Connecting

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Google Home Not Connecting

    I've been using Spud's Chromecast but have had issues with various devices disconnecting. Then the other day the Google Home would not stay connected. Out of frustration I disabled Chromecast and installed AK Google Cast. Same problem. I'm not pitting one PI against the other but I'm trying to figure out what is going on.
    an-27 19:43:00 AK GoogleCast [5756]: (Ref: 5756) Kitchen (Unknown): Remove Receiver [Google Home] Kitchen (192.168.1.44)
    Jan-27 19:43:00 AK GoogleCast Warning [5756]: Disconnected chromecast Kitchen
    Jan-27 19:43:00 AK GoogleCast [5756]: * ChromeCastClient: DisConnected (Kitchen)
    Jan-27 19:43:00 AK GoogleCast [5756]: * Disconnected from ChromeCastClient (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.44:8009) (Kitchen)
    Jan-27 19:42:44 AK GoogleCast ERROR [5756]: VerifyConnect timer fired - looks like connection chain failed, state retrying
    Jan-27 19:42:39 AK GoogleCast [5756]: * Set Receiver [Google Home] Kitchen (192.168.1.44) (HSPI_AKGoogleCast.DeviceCastRoot)
    Jan-27 19:42:39 AK GoogleCast [5756]: * (2) SetReceiver HSPI_AKGoogleCast.SpeakerGoogleTransl => ConnectAsync [Google Home] Kitchen (192.168.1.44)... (Kitchen)
    Jan-27 19:42:39 AK GoogleCast [5756]: * (1) Creating speaker GoogleTranslate...
    Jan-27 19:41:19 AK GoogleCast [5756]: (Ref: 5756) Kitchen (Unknown): Remove Receiver [Google Home] Kitchen (192.168.1.44)
    Jan-27 19:41:19 AK GoogleCast Warning [5756]: Disconnected chromecast Kitchen
    Jan-27 19:41:19 AK GoogleCast [5756]: * ChromeCastClient: DisConnected (Kitchen)
    Jan-27 19:41:19 AK GoogleCast [5756]: * Disconnected from ChromeCastClient (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.44:8009) (Kitchen)
    Jan-27 19:41:03 AK GoogleCast ERROR [5756]: VerifyConnect timer fired - looks like connection chain failed, state retrying
    Jan-27 19:40:58 AK GoogleCast [5756]: * Set Receiver [Google Home] Kitchen (192.168.1.44) (HSPI_AKGoogleCast.DeviceCastRoot)
    Jan-27 19:40:58 AK GoogleCast [5756]: * (2) SetReceiver HSPI_AKGoogleCast.SpeakerGoogleTransl => ConnectAsync [Google Home] Kitchen (192.168.1.44)... (Kitchen)
    Jan-27 19:40:58 AK GoogleCast [5756]: * (1) Creating speaker GoogleTranslate...
    Jan-27 19:39:39 AK GoogleCast [5756]: (Ref: 5756) Kitchen (Unknown): Remove Receiver [Google Home] Kitchen (192.168.1.44)
    Jan-27 19:39:39 AK GoogleCast Warning [5756]: Disconnected chromecast Kitchen
    Jan-27 19:39:39 AK GoogleCast [5756]: * ChromeCastClient: DisConnected (Kitchen)
    Jan-27 19:39:39 AK GoogleCast [5756]: * Disconnected from ChromeCastClient (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.44:8009) (Kitchen)
    Tags: None
    #2
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
    Other users reported similar issues caused by Firewall or network configuration.
    What kind of device it is - normal Google Home?
    Is your deviceon the same network?
    Any special security settings/apps?

    Comment

      #3
      I log the connection steps (it's not quite trivial...) i.e.

      * (1) Creating speaker GoogleTranslate...
      * (2) SetReceiver => ConnectAsync [Google Home] Kitchen

      So it looks like it never goes past step 2 - connecting to the device. It just times out.

      Comment

        #4
        Comparing to Spud's Chromecast my plugin should be more reliable and other users are switching to my plugin because of that

        Once we sort out you current issue...

        Comment

          #5
          I was able to resolve by removing the Google Home from my house (in the app) and then assigning it to a room. At that point it went through the entire setup process. I think it has something to do with the two Wi-fi bands. My Altice box has both regular and 5G. Somehow, connection with one was lost and it connected to the second one. In the process, the GH was still connected to the internet but couldn't be found in Homeseer.

          This might have been because of a firmware update by Altice, not sure.

          At this point, before I try any more plug-ins I'm going to wait until HS4 comes out and see how HS3 plugins work. That will be a slow process for sure.

          Comment

            #6
            Originally posted by racerfern View Post
            At this point, before I try any more plug-ins I'm going to wait until HS4 comes out and see how HS3 plugins work. That will be a slow process for sure.
            Yeah, this maybe a while. But I think HS4 Beta is available already? Or it may be for developers only...

            Comment

            Previous template Next
            Working...
            X