search

MrBearPresident / JBL_Soundbar

Home Assisstant custom integration to interact with a jbl soundbar based on the jbl one app
5 stars 0 forks source link

Cannot connect to host #2

Closed viziashkin closed 3 weeks ago

viziashkin commented 1 month ago

Hi.

Very appreciate your custom integration and was happy to control the soundbar from the HASS. Had it working for a week or so, but now EQ, power and other things except volume do not work.

Do you mind helping me to identify the issue? What tools have you used to debug requests?

Obviously it cannot connect to the soundbar, but I'm wondering what could change if it has been working. JBL One app works fine. Tried to reset the soundbar to factory settings, reconnect to network, restart HA, reinitialize the integration - no luck. And again, volume is working, so IP is correct.

Model: JBL Bar 1000 Software: OneOS 2.3 (24.33.31.80.00)

Getting in logs: jbl_integration/coordinator.py:104 Error getting device info:

jbl_integration/coordinator.py:212 Error fetching data: Error fetching data: Cannot connect to host 192.168.1.123:59152 ssl:default [Connect call failed ('192.168.1.123', 59152)]

jbl_integration/coordinator.py:261 Error getting EQ: Error getting EQ: Cannot connect to host 192.168.1.123:80 ssl:default [Connect call failed ('192.168.1.123', 80)]

MrBearPresident commented 1 month ago

Hi

I can confirm that I have the same issues. JBL pushed a firmware update and now some of the 'reverse Enginered'-api is not usable anymore.

You can dubbele check if this is the root of your problems through the app. (my previous firmware was 24.15.21.80.00)

My initial way of reverse engineering is not working on the new firmware so I already contacted jbl in the small hope they can give me some assistance.

I will try some different things coming weekend. So hopefully I can get it back working again.

viziashkin commented 1 month ago

That sucks. I thought updates are not automatic and I'd see some prompt, so also thought they already abandoned updating firmware. I guess if you manage to fix the problem it would be reasonable to check endpoints used for checking for updates and block them on router as I've done for my rooted WebOS TV.

viziashkin commented 1 month ago

Otherwise, I would buy some IR blaster to mimic remote signals. Opening the app each time I want to tune Low EQ at night is a pain in the ass.

MrBearPresident commented 1 month ago

I've found already something. So I used HTTP-Toolkit again (like I described here). I could see that all the commands that I use and not working anymore just switched to https. I am unable to get the certificate so the jbl bar accepts the https request.

But we are already making progress.

MrBearPresident commented 3 weeks ago

I have great news... after a long week reading trying, failing, and lots of frustration I cracked their client side key. Update comming up soon. Should all work again.

viziashkin commented 3 weeks ago

Great stuff!

MrBearPresident commented 3 weeks ago

Solved in https://github.com/MrBearPresident/JBL_Soundbar/releases/tag/V1.1.2