Joe Schubert

> (Which realistically isn't that bad. That's about twice a minute) Twice a minute is about right. The polling rate is supposed to be every 30 second for each device,...

@JoshuaMulliken I honestly haven't had many issues with it either way, to be honest. I only really use my lock through the integration anyway.... which broke a few months back...

@JoshuaMulliken I think some of it has to do with me closing the client after each request back in this [commit](https://github.com/JoshuaMulliken/wyzeapy/commit/c5e279f41840eb0a09fe6f312011529b523dcc9d), which killed the DNS caching on top of the...

> if you're asking... I'd prefer the connection be kept open so it can cache the DNS query. I've actually tried quite a few different ways, including reverting the change...

@SecKatie Looking at the output malamar posted there, I feel like they used to have "something.somethingelse.uuid" and they removed one of the somethings. however, I'm not sure if some versions...

Assuming that the token ends up being the same, why do you need to authenticate against the Roku server? Just use the normal auth token in whatever Roku functionally you...

> The Roku authentication server then returns two OAuth tokens: a Roku API token and a "partner" token for the Wyze API. Ok, and how is re-authentication handled then? Currently...

> Good point, I assumed the refresh token would work with the Wyze endpoint, but I will need to verify this by capturing mobile app traffic when it performs a...

> @JoeSchubert correct. Do you have any tips for triggering a token refresh while I'm intercepting traffic? Opening the app for the first time in weeks didn't seem to do...

My information may be outdated as I've been away from the project for a bit... but I don't think this would really make all that much sense to incorporate as...