-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unresponsive system and repeated chromecast log errors #3
Comments
This is either due to a missing removeThing at https://github.com/freaktechnik/chromecast-adapter/blob/master/adapter.js#L136 though in that case it should not lock up, or a continuous network problem with keeping the connection to the chromecast open. |
I think there may be a loop with closing and events, will put up a fix later today (which should also fix the first part I mentioned above). |
Version 0.3.4 s now available. If that doesn't fix the issue I'm a bit lost, since the error comes from the client library I use to talk with chromecasts. |
Thanks for your quick response to my issue. I've updated to latest adaptor now although I think you meant v0.3.3. I don't see that first device timeout error anymore so that seems fixed but I am still seeing the second error message. I've narrowed it down to when I try to add new devices. Every time I scan for new devices it adds one more error row per device to those chromecast device already exists messages. A reboot of the system resets the count back to just 1 error for each device but then the errors keep accumulating whenever I scan for new devices. So this extract is after reboot and 3 device scans. If I scan again I'll see 5 error messages for each chromecast device.
Removing and re-adding a chromecast device doesn't help. It picks up where it left off with repeated error rows. One other minor thing I noticed, when scanning for and adding a chromecast device, it initially shows the device type as On/Off Switch with the only other option being Custom Thing. Once it is added though it appears ok with the splat giving Mute:Play/Pause:App:Volume:Muted properties. |
This second error is not really relevant and shouldn't have any impact on responsiveness, it's possibly just a memory leak, if even.
Yes, there's no more specific device type yet, see WebThingsIO/schemas#34 |
Ok. I'm only just getting started with Things Gateway so still getting my head around it all. The first error is back - coincided with powering off the Chromecast.
System responsiveness is ok though - but I did also disable a few other devices so can't really say whether your update helped or not. Will keep an eye on how it behaves over time. |
You'll continue seeing these timeouts, those are an issue with the chromecasts and their network handling. I'll close this for now, feel free to re-open with additional details if you encounter this again and open other issues your come across :) |
Originally from WebThingsIO/gateway#1694 (via @clockbrain)
My whole system has become unresponsive with only a few of the devices working. Some will work for a short time after removing and adding again but some refuse to work at all. I have about 20 devices, some are wifi and some are zigbee.
One possible clue is my log file has 17 repeats of this error:
immediately followed by this in the log file:
The chromecast is turned off for most of each day but even so I wouldn't expect failed connections to clog up the gateway.
Any suggestions on how to reset or clear my system?
I'm on version 0.7 of the gateway.
The text was updated successfully, but these errors were encountered: