I’m on openhabian 2.5 M1 running on 64 bit debian Linux 9 OS. The system has been stable but I started to receive many Chromecast log errors, especially at night, after I installed the Chromecast binding. Currently, I have added six Chromecast things but I haven’t linked them to items. Last night, for instance, I received errors over the span of 7 hours. I suspect the issue is with the chromecast audio since most of errors are attributed to the Chromecast audiogroup thing. The error is either “No route to host” or “Connection refused” The individual chromecast audio things are also displaying errors with occasional errors from the mini.
I changed the refresh rate from 10 to 60 but it didn’t seem to make a difference. I searched the community but didn’t see something similar. Also, I saw the problem on the my raspberry pi. I thought my system was corrupted so I restarted from scratch with a virtual appliance.
I had problems with the binding throwing warnings and spamming the logs so I uninstalled it. here is link to that thread
typing chromecast into the search reveals dozens of threads detailing problems. None of which ever seem to have a solution.
I see. The warning is the same but in your case the stacktrace of the exception is appended. Point is that these warnings are from an underlying thirdparty library. They do not hurt, because everything is working fine after they occurred, but they are visible in your log. The exception was removed some time ago (see https://github.com/openhab/openhab2-addons/issues/3770) but the warning will remain.
If you do not like them you can try to decrease logging on: su.litvak.chromecast.api.v2.
Thanks Chris for the explanation. In other words, it is an inherent feature of the Chromecast library – one that will continue to plague users. I searched for decreasing log levels in bindings and read “logging in Openhab.” I had a hard time trying to understand where to capture the logs. I know where to filter out messages but I don’t want to do that for the Chromecast binding. Somehow, I think I need to specify in the org.ops4j.pax.logging.cfg file to set the logging level to error for su.litvak.chromecast.api.v2. Can you point me to the appropriate post that illustrates changing the logging level for bindings in the openhab log?
A second option is to change it by running the log:set ERROR su.litvak.chromecast.api.v2 command from Karaf console. But this way it maybe is not persistent and you will have to repeat it after every restart.