-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wss test client #189
base: main
Are you sure you want to change the base?
Wss test client #189
Conversation
My connection was super flaky when I was testing this out earlier in the week. Even the iOS client was dropping the connection constantly. I couldn't tell if it was something screwed up with my account or if the PitBoss servers are just being wonky.
I've been using https://httptoolkit.com/ with an Android emulator to sniff traffic. There's a few different sites that publish APKs that you can side-load into the emulated device, and HTTP Toolkit is able to circumvent certificate pinning. |
BTW, I see the same flakiness from my IOS client as well; even when I've not tried connecting to the web socket via other means for days. And that could be on either the pitboss server sid or in the grill<-> cloud connection being formed. Thanks for the pointer on the httptoolkit not one I've used but it looks powerful. |
This is able as far as I can go without a more stable BLE from the grill. I did get the bluetooth stack going in the container. |
], | ||
"postStartCommand": "sudo service dbus start && sudo service bluetooth start", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll have to poke at it more when I have time, but I know the HomeAssistant devcontainer can pass-thru the bluetooth controller and it seems to work fine. I've never had to stop the bluetooth service on my laptop when developing integrations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, the ha dev container behaviour is beyond me at the moment. I've refactored the debug wrapper but need to check to see how it responds using the grill_id as opposed to the model. I've got more testing to do...
Client connects to the server but it doesn't seem to receive data from the the connection. Back to trying to capture and decode a wpa negotiation from my phone to the server...