search

cdpuk / ha-bestway

Home Assistant integration for Bestway / Lay-Z-Spa hot tubs
MIT License
74 stars 18 forks source link

spa found but wont connect #59

Closed russell1975 closed 4 months ago

russell1975 commented 6 months ago

fairly new to home assistant but have installed HACS and the bestway script and found my hottub but after logging in I cant control anything what am I doing wrong 


![Screenshot ha issue](https://github.com/cdpuk/ha-bestway/assets/171022724/d3ee9c32-33ae-4d34-b323-30b20a1e9f18)
![Screenshot ha issue](https://github.com/cdpuk/ha-bestway/assets/171022724/38c56534-f619-468d-9871-5b08badcaead)
cdpuk commented 6 months ago

This sounds a lot like #57, but sadly no further information was received on that issue.

Can you grab some debug logs from the integration to help work out what's happening? This looks like it thinks the device is offline.

cdpuk commented 6 months ago

I should also add that newly published v1.5.1 adds an additional log entry that will be useful for this issue.

thoj commented 5 months ago

I had the same issue. Deleting and readding the spa via the bestway app fixed it for me.

40pints commented 5 months ago

I am also having the same issue, getting the following errors in the logs: Error fetching Bestway API data: Error communicating with API: 502, message='Bad Gateway', url=URL('https://euapi.gizwits.com/app/bindings') Error fetching Bestway API data: Error communicating with API: Error fetching Bestway API data: Error communicating with API: 500, message='INTERNAL SERVER ERROR', url=URL('https://euapi.gizwits.com/app/devdata/xxxxxxxxxxxxxxxxxxxxxx/latest') Error fetching Bestway API data: Error communicating with API: Cannot connect to host euapi.gizwits.com:443 ssl:default [Connect call failed ('3.69.79.138', 443)] Error fetching Bestway API data: Error communicating with API: 502, message='Bad Gateway', url=URL('https://euapi.gizwits.com/app/devdata/xxxxxxxxxxxxxxxxxxxxxx/latest')

cdpuk commented 4 months ago

Closing due to inactivity. The 5xx errors are probably unrelated - there seemed to be a patch of these errors from the Bestway servers a few weeks ago.