Announcement

Collapse
No announcement yet.

Google Cast Group frequently disconnects

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

  • #16
    Originally posted by ServiceXp View Post
    Unfortunately, .20 has been far worst as there are now 3 problems.

    1) A complete disconnect across all devices which does not recover.
    2) Individual devices disconnecting which will not automatically reconnect, unless clicking on the 'connect' button.
    3) With this version I can no longer automatically shut the PI down using Jon's plug-in disabler.

    I don't have full logs as I started them after this mornings episode. Manually disabling and re enabling the PI corrects the problem.

    .
    I made some changes. Could you test version 3.0.0.21.
    Please delete your log file before starting the new version so that it's not too big.

    thanks

    Comment


    • #17
      Originally posted by spud View Post
      I made some changes. Could you test version 3.0.0.21.
      Please delete your log file before starting the new version so that it's not too big.

      thanks
      There doesn't seem to be any attachments on that post anymore?
      RJ_Make On YouTube

      Comment


      • #18
        Originally posted by ServiceXp View Post
        There doesn't seem to be any attachments on that post anymore?
        sorry about that, it's fixed now

        Comment


        • #19
          so were you able to test version 3.0.0.21? How is it going?

          Comment


          • #20
            Originally posted by spud View Post
            so were you able to test version 3.0.0.21? How is it going?
            Sorry for the delay. Still disconnects, but now recovers more gracefully, and doesn't take everything down with it. And when the PI doesn't re-connect on it's own (generally just one or two at a time), I'm able to shut the PI down and turn it back on via Jon's plug-in app.

            So much better IMO..
            RJ_Make On YouTube

            Comment


            • #21
              The behaviour on my system has changed.

              I am still getting disconnects every day around 3-5am (typically 430). Whereas in the past all devices have reconnected, now only the Chromecast devices reconnect and groups do not reconnect. Clicking the "connect" button on the root doesn't do anything and the only way I can reestablish the connection between Chromecast groups and this plugin is to restart the plugin.

              I am running beta version 19, will update to 21 today. I'll post logs tomorrow morning.

              Could this be related to a WiFi/router problem? I have a Netgear Orbi.

              Comment


              • #22
                Originally posted by benrjunk View Post
                The behaviour on my system has changed.

                I am still getting disconnects every day around 3-5am (typically 430). Whereas in the past all devices have reconnected, now only the Chromecast devices reconnect and groups do not reconnect. Clicking the "connect" button on the root doesn't do anything and the only way I can reestablish the connection between Chromecast groups and this plugin is to restart the plugin.

                I am running beta version 19, will update to 21 today. I'll post logs tomorrow morning.

                Could this be related to a WiFi/router problem? I have a Netgear Orbi.
                I'm seeing the same thing on completely different network gear. I think the root of the problem is the PI reliance on the Crapple service Bonjour.

                I've setup a fairly elaborate 'system' to first reconnect if any CCA device is disconnected for more then 5 min. If that fails and any device is disconnected for 20min, I then use Jon's PI disabler to shutdown and restart the plugin.

                So far that is working in build .21
                RJ_Make On YouTube

                Comment


                • #23
                  I've been testing this plugin for a day and while it works quite well, the log is filled with constant disconnects/reconnects. Sometimes devices connect and disconnect in as little as 5 minutes or so, sometimes more (there doesn't appear to be any consistency).

                  Additionally, previously removed Chromecasts (via the plugin's configuration page) are added back when devices are rediscovered and reconnected.

                  It would be very useful (for me anyway) to have an option on the configuration page that allows one to select utilizing auto-discovery/Bonjour, or just a manual device configuration. In my case, Bonjour is installed on the Homeseer machine for other purposes... I cannot remove it. I just don't want/need it for the plugin.

                  Comment


                  • #24
                    Ethernet connection

                    Hi,

                    Disconnects without reconnection became so frequent with this plugin that I purchased ethernet adapters for all my chromecast devices (5 of them). I'll post and let you know if this improves the situation.

                    https://store.google.com/product/eth...for_chromecast

                    Ben

                    Comment


                    • #25
                      With the Ethernet adapters for Chromecast, the plugin still disconnects daily around 430-5am from all the Chromecast devices but (at least over the past 48h) reconnects automatically to devices and CCA groups. These adapters seem to have improved the reliability of my system, but it is a relatively expensive fix.

                      Ben

                      Comment


                      • #26
                        I'm also experiencing this guess i should have tested more before purchasing... spud is hopefully still working on a solution? a manual setup and "connected" feature should be a good short term fix.

                        Mine disconnect a lot and the logs if flooded with "heartbeat" items.

                        83610 lines in debug log and only been running for a few hours.

                        Jan-04 10:33:27 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                        Jan-04 10:33:27 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }
                        Jan-04 10:33:28 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                        Jan-04 10:33:28 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }
                        Jan-04 10:33:28 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                        Jan-04 10:33:29 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }

                        Comment


                        • #27
                          Plug-In Version: 3.0.0.29
                          Platform: Windows
                          Issue: I too get lost/found posted non-stop in the log even though I do not have the group enabled in the plug-in. Below is a short example of what I see.
                          Jan-19 8:08:59 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:08:07 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:07:16 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:07:14 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:06:55 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:06:53 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:05:18 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:05:16 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:04:50 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:04:47 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:45 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:43 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:24 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:22 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:03 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:03:01 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:02:42 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:02:40 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:02:01 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:01:59 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:01:40 AM Chromecast INFO Lost Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc
                          Jan-19 8:01:38 AM Chromecast INFO Found Service: Google-Cast-Group-36146f03471a4540ae8c6ec286bb1efc

                          Comment


                          • #28
                            Originally posted by marcusone View Post

                            Mine disconnect a lot and the logs if flooded with "heartbeat" items.

                            83610 lines in debug log and only been running for a few hours.

                            Jan-04 10:33:27 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                            Jan-04 10:33:27 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }
                            Jan-04 10:33:28 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                            Jan-04 10:33:28 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }
                            Jan-04 10:33:28 DEBUG TX: { "sourceId": "sender-0", "destinationId": "receiver-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PING"}" }
                            Jan-04 10:33:29 DEBUG RX: { "sourceId": "receiver-0", "destinationId": "sender-0", "namespace": "urn:x-cast:com.google.cast.tp.heartbeat", "payloadUtf8": "{"type":"PONG"}" }
                            the hearbeat messages are expected in the debug logs. Set the log level to Debug, only when you try to debug a problem.

                            Comment


                            • #29
                              Originally posted by CElliott13@gmail.com View Post
                              Plug-In Version: 3.0.0.29
                              Platform: Windows
                              Issue: I too get lost/found posted non-stop in the log even though I do not have the group enabled in the plug-in. Below is a short example of what I see.
                              The lost/found messages are notifications from the Bonjour service. I don't know why on your system there are so many. But now in version 3.0.0.30 (available in Beta section of the updater) they are logged at debug level, so they will not flood your logs anymore.

                              Comment


                              • #30
                                Originally posted by spud View Post

                                The lost/found messages are notifications from the Bonjour service. I don't know why on your system there are so many. But now in version 3.0.0.30 (available in Beta section of the updater) they are logged at debug level, so they will not flood your logs anymore.
                                Thanks for the update - - very odd that Bonjour would cause it. I'm running the version you recommended for install on a Windows 7 x64 system if it makes any difference.

                                Comment

                                Working...
                                X