use custom user-agent in websocket requests

[alexbilevskiy]

Summary

Fix user-agent in websocket requests (such as device controls tile in quick settings), use custom values insteadof okhttp/4.10.0
pretty much the same reason as in #1364 and #1418

Screenshots

Link to pull request in Documentation repository

Documentation: home-assistant/companion.home-assistant#

Any other notes

Sorry, I dont have development env, I hope github actions build will work

[home-assistant]

Hi alexbilevskiy

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[dshokouhi]

I thought we already handled this here for all of our network calls.

https://github.com/home-assistant/android/blob/master/common/src/main/java/io/homeassistant/companion/android/common/data/HomeAssistantApis.kt#L42

[jpelgrom]

I thought we already handled this here for all of our network calls.

Looks like interceptors don't work on websocket requests (also see this StackOverflow post). As we're only adding one header the suggested change should be OK in my opinion.

I hope github actions build will work

It currently doesn't because of actions/setup-java#422, but when that is fixed it still won't work because:

• you need to add an import statement for the added constants
• the USER_AGENT constant is currently private

I'd recommend editing with an IDE like Android Studio to help you catch errors like these.

[dshokouhi]

I thought we already handled this here for all of our network calls.

Looks like interceptors don't work on websocket requests (also see this StackOverflow post). As we're only adding one header the suggested change should be OK in my opinion.

In that case this PR is a good find!

[alexbilevskiy]

it still won't work because:

fixed

I'd recommend editing with an IDE like Android Studio to help you catch errors like these.

Did so. No more errors reported.

[dshokouhi]

Looks good to me! Nice catch.