Announcement

Collapse
No announcement yet.

All Devices with ? (SOLVED)

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

    #16
    Originally posted by slbuck View Post
    I'll keep an eye on it and let you know what I see in the logs when it happens again. So far, the two devices that I usually cast two are still showing online, while the others have gone offline. I didn't see any error or warning messages in the logs for the other Chromecast Ultras indicating that they went offline.
    You can filter HS Log by the plugin and search

    Comment


      #17
      I'm not sure when the ultras went to question mark status, but I checked just now and they all were in that state. I tried casting to the Ultra and got this in the logs.
      Oct-22 10:49:13 AK GoogleCast ERROR [3308]: LoadMedia: not ready '', ''

      I didn't see any other error messages.

      Comment


        #18
        deleted

        Comment


          #19
          I think the error LoadMedia: not ready '', '' is secondary - the main problem is the error "The host failed to connect. Timeout occurred. 15000"

          Which explains why the plugin is "not ready". Question is - why?

          So, the plugin never recovers when this happens, until you restart the plugin?

          [EDIT]

          Ok, looking through the thread - the error is not on Chromecast side - it's connection to HomeSeer fails.

          The error in post #10 shows ConnectToHS Classroom TV: "The host failed to connect. Timeout occurred. 15000"

          It's important to provide more info for troubleshooting - otherwise it's just a waste of my time.
          And this error must be also present in HS Log.

          So, please disable all devices except for the one mis-behaving the most, make sure the Log is enabled for this device, restart the plugin.
          Please provide all log messages you find for this device which can assist troubleshooting connecting to HomeSeer (not to Google devices).

          Comment


            #20
            EDIT: All the Chromecast Ultras are hard-wired. The Minis and Hub are wireless. All the devices have DHCP reservations so the IP doesn't change. I've disabled discovery after all the devices were initially discovered.

            OK. I've disabled all the devices except for one.



            The red triangle is the load media error.

            I restarted the plugin and the one device comes back online.

            Click image for larger version  Name:	after plugin restart.png Views:	0 Size:	47.0 KB ID:	1428109

            Here are all the logs. When I notice the device with a red question mark, I'll send the logs.
            Code:
             
            Oct-23 12:37:46 AK GoogleCast Speakers: STEVE PHONE, STUDY TV
            Oct-23 12:37:41 AK GoogleCast [3308]: * PlayerState: Idle (Unknown) (Study TV)
            Oct-23 12:37:41 AK GoogleCast [3308]: * (4) Connected to Homeseer (hs_speech_client) HSPI_AKGoogleCast.SpeakerHS (Study TV) (state connected)...
            Oct-23 12:37:41 Speaker Speaker host added, Name: GOOGLECAST Instance: Study TV IP address: 192.168.22.11
            Oct-23 12:37:41 AK GoogleCast [3308]: * VolumeChanged: 1 (Study TV)
            Oct-23 12:37:41 AK GoogleCast Warning Zeroconf (mDNS) discovery is disabled
            Oct-23 12:37:41 AK GoogleCast [3308]: * Application started: Backdrop (E8C28D3C) (Study TV)
            Oct-23 12:37:41 AK GoogleCast [3308]: * Speaker Connected (hs_speech_client): Study TV
            Oct-23 12:37:41 AK GoogleCast [3308]: ConnectHSSpeechClient Study TV
            Oct-23 12:37:41 AK GoogleCast [3308]: * (3) Connecting to Homeseer (hs_speech_client) HSPI_AKGoogleCast.SpeakerHS (Study TV) (state retrying)...
            Oct-23 12:37:41 AK GoogleCast Warning Found Receiver [Chromecast Ultra] Nana's TV (192.168.22.13:8009): device is disabled!
            Oct-23 12:37:41 AK GoogleCast [3332]: * Set Receiver '[Chromecast Ultra] Nana's TV (192.168.22.13:8009)' (HSPI_AKGoogleCast.DeviceCastRoot)
            Oct-23 12:37:41 AK GoogleCast Warning [3332]: Device is disabled: [Chromecast Ultra] Nana's TV (192.168.22.13:8009)
            Oct-23 12:37:41 AK GoogleCast [3308]: * ChromeCastClient: Connected (Study TV)
            Oct-23 12:37:41 AK GoogleCast Warning Found Receiver [Google Home Mini] Dan (192.168.22.24:8009): device is disabled!
            Oct-23 12:37:41 AK GoogleCast Warning [3557]: Device is disabled: [Google Home Mini] Dan (192.168.22.24:8009)
            Oct-23 12:37:40 AK GoogleCast Warning Found Receiver [Google Home Mini] Upstairs (192.168.22.22:8009): device is disabled!
            Oct-23 12:37:40 AK GoogleCast Warning [3543]: Device is disabled: [Google Home Mini] Upstairs (192.168.22.22:8009)
            Oct-23 12:37:40 AK GoogleCast [3308]: * Set Receiver '[Chromecast Ultra] Study TV (192.168.22.63:8009)' (HSPI_AKGoogleCast.DeviceCastRoot)
            Oct-23 12:37:40 AK GoogleCast [3308]: * (2) SetReceiver HSPI_AKGoogleCast.SpeakerHS => ConnectAsync [Chromecast Ultra] Study TV (192.168.22.63:8009)... (Study TV)
            Oct-23 12:37:40 AK GoogleCast [3308]: * (1) Creating speaker HomeSeer ()...
            Oct-23 12:37:38 AK GoogleCast Warning Found Receiver [Google Nest Hub] Kitchen display (192.168.22.20:8009): device is disabled!
            Oct-23 12:37:38 AK GoogleCast [3356]: * Set Receiver '[Google Nest Hub] Kitchen display (192.168.22.20:8009)' (HSPI_AKGoogleCast.DeviceCastRoot)
            Oct-23 12:37:38 AK GoogleCast Warning [3356]: Device is disabled: [Google Nest Hub] Kitchen display (192.168.22.20:8009)
            Oct-23 12:37:38 AK GoogleCast Warning Found Receiver [Chromecast Ultra] Great room TV (192.168.22.60:8009): device is disabled!
            Oct-23 12:37:38 AK GoogleCast [3320]: * Set Receiver '[Chromecast Ultra] Great room TV (192.168.22.60:8009)' (HSPI_AKGoogleCast.DeviceCastRoot)
            Oct-23 12:37:38 AK GoogleCast Warning [3320]: Device is disabled: [Chromecast Ultra] Great room TV (192.168.22.60:8009)
            Oct-23 12:37:37 AK GoogleCast Warning Found Receiver [Chromecast Ultra] Classroom TV (192.168.22.21:8009): device is disabled!
            Oct-23 12:37:37 AK GoogleCast [3344]: * Set Receiver '[Chromecast Ultra] Classroom TV (192.168.22.21:8009)' (HSPI_AKGoogleCast.DeviceCastRoot)
            Oct-23 12:37:37 AK GoogleCast Warning [3344]: Device is disabled: [Chromecast Ultra] Classroom TV (192.168.22.21:8009)
            Oct-23 12:37:37 Plug-In Finished initializing plug-in AK GoogleCast
            Oct-23 12:37:37 Starting Plug-In AK GoogleCast loaded in 6358 milliseconds
            Oct-23 12:37:37 AK GoogleCast HS IP 192.168.22.11:80, HS_SPEAKER_IP 127.0.0.1:10401
            Oct-23 12:37:37 Starting Plug-In Plugin AK GoogleCast started successfully in 4121 milliseconds
            Oct-23 12:37:37 AK GoogleCast UpdateConfiguration: scheduled
            Oct-23 12:37:33 Starting Plug-In Initializing plugin AK GoogleCast ...
            Oct-23 12:37:33 Info Plugin AK GoogleCast has connected. IP:127.0.0.1:54345

            Comment


              #21
              Thank you, it all looks good. When you have the problem - filter the log by Study TV device id - [3308]

              As I said, the problem seems to be on HomeSeer side, not the Chromecasts - the error was in ConnectHSSpeechClient

              Comment


                #22
                Here you go. Everything filtered by "Study TV"
                Oct-24 02:22:58 AK GoogleCast [3308]: (Ref: 3308) Study TV (Unknown): Remove Receiver [Chromecast Ultra] Study TV (192.168.22.63:8009)
                Oct-24 02:22:58 AK GoogleCast [3308]: * PlayerState: Unknown (Idle) (Study TV)
                Oct-24 02:22:58 AK GoogleCast [3308]: Disconnected chromecast Study TV
                Oct-24 02:22:58 AK GoogleCast [3308]: * ChromeCastClient: DisConnected (Study TV)
                Oct-24 02:22:24 AK GoogleCast [3308]: * Application ended (Study TV)
                Oct-24 02:22:24 AK GoogleCast [3308]: * Media changed: (Study TV)
                Oct-24 02:22:24 AK GoogleCast [3308]: * PlayerState: Idle (Playing) (Study TV)
                Oct-24 02:21:08 AK GoogleCast [3308]: * Media changed: https://ccp-lh.googleusercontent.com...rLYEz1MtA4nc7K 1DSZvLBPNo0=s1280-w1280-h720-fcrop64=1 (Study TV)
                Oct-24 02:19:06 AK GoogleCast [3308]: * Media changed: https://ccp-lh.googleusercontent.com...hClA5cH96ShTjC aY80jyVsCkRoPdievL8qxKWUqMnltqBuhOf5R1q2IIEiUaD2l7AGGo7aIAHe sRDsO2_I1rEqFb2iAnt-NmQZHlPWYxEKiylb3oNliUM21j7zlMrsjk7Dp7tgJnhbvIKcKNL5lWPp-UzPyMLJmHyikm5b54AKTbv8PMZJa6WGWknnm8P4YFwNjTYvd03tKiHn3kNBb CugM0OgcdOnTx1iy6SiQfInOg=s1280-w1280-h720-fcrop64=1 (Study TV)
                Oct-24 02:17:04 AK GoogleCast [3308]: * Media changed: https://ccp-lh.googleusercontent.com...8zLvsv6GEH6d54 irHFgsYrFw=s1280-w1280-h720-fcrop64=1 (Study TV)

                Comment


                  #23
                  I see what's happening - Chromecasts do loose connection sometimes, so these messages are normal because mDNS finds them again and plugin re-connects.
                  Problem is - you disabled Zeroconf (mDNS) discovery - so they don't re-connect. Try enabling mDNS and see how it goes.
                  And I will see what I can do in the code.

                  Comment


                    #24
                    Once I re-enabled zeroconf autodiscover, then things started working again. Since I don't add any new devices, it would be great if you could automatically reconnect to disconnected devices that have already been discovered during an initial auto-discover when new devices were brought online.

                    Thanks for the help.

                    Comment


                      #25
                      Originally posted by slbuck View Post
                      Once I re-enabled zeroconf autodiscover, then things started working again. Since I don't add any new devices, it would be great if you could automatically reconnect to disconnected devices that have already been discovered during an initial auto-discover when new devices were brought online.

                      Thanks for the help.
                      I'l see what I can do.

                      It's just much cleaner using auto discovery - say you disconnect one of your Chromecasts. If discovery is enabled - when you connect the device back (even after a few days, even when DHCP IP lease expired) - mDNS will detect the device and re-connect.

                      Without mDNS I have to constantly poll the device to see if it's back on.

                      Comment


                        #26
                        Gotcha. Is there any overhead with leaving autodiscover turned on, or are you just passively listening do the mDNS broadcasts on the network to determine when the devices are online? If that's the case, then I'll just leave the autodiscover on and be done with it.

                        Comment


                          #27
                          Originally posted by slbuck View Post
                          Gotcha. Is there any overhead with leaving autodiscover turned on, or are you just passively listening do the mDNS broadcasts on the network to determine when the devices are online? If that's the case, then I'll just leave the autodiscover on and be done with it.
                          I will still try implementing polling when connection is lost - in case somebody does have legit problem with mDNS.

                          Regarding mDNS overhead - it does broadcasts requests, then listens for replies.
                          I support different mDNS libraries, original one is Zeroconf, newer TmDS, but I do recommend installing Apple Bonjour Print Services for Windows - it's oldest (I think it's original Zeroconf implementation) - the beauty is - it's doing optimised mDNS broadcasts in the background (from the service), then all clients (i.e. plugins) talk to the service. Instead of every plugin separately broadcasting requests.

                          When you install the service and restart the plugin - it should automatically select Mono.Zeroconf library - which is using Bonjour on Windows and Avahi on Linux. Assuming the "Auto" was selected.

                          Comment

                          Working...
                          X