The community member is unable to use routerQueryEngine with the chat engine, and it only works with the query engine. The comments suggest two potential solutions: wrapping the chat engine in a custom query engine, or using the lower-level selector API to route things themselves.
