[Chromecast] Feature Request: Configurable timeouts and debug level

🧰 Built-In Apps and Drivers
1

My Hubitat logs this morning: :face_with_spiral_eyes:

image
image901×751 151 KB

The Google Mini "ccBüro" lost connection - this happens sometimes, nothing to worry about. :man_shrugging:

But:

Why is the Chromecast Driver trying to do this for such a long time (some attempts even take over 18 minutes!)?
The Device stats are showing, that this device is consuming "85 % of busy", and the utilization of my Hubitat is 37% (usual is 3%)!

That's why I have these requests:

  1. Please add an option to configure the max. timeout for such actions.
  2. Please add an option to configure the debug level for the logs.

Since these warnings occur frequently, they are rarely helpful - only in debug cases.

2

BTW: It would be also very helpful, when we could get an Custom Attribute that holds the last logged message. :sunglasses:
Often it's enough to do a speak " " to repair similar problems.

3

@Hubitat_Staff:
Who is the right contact person to get concret information about the Chromecast Integration (or even offer some free coding help)?

4

No one? :thinking:

5

@Hubitat_Staff it would be awesome to get some feedback on this Chromecast topic. @Jost has done a lot of work characterizing time timeout issue. See this other thread too:

I realize that adding configurable options is "real work," but perhaps you can try simply reducing the timeout in code as @Jost suggested in an upcoming release?

Any other Chromecast users able to put in their two cents and @ the staff for attention? @a.mcdear ?

2 Likes