Wrong API endpoint

[HSE83]

Hi,

I've been having problems with the adapter since late October. iobroker log shows endpoint id.eu.worx.com does not resolve to an IP anymore. The app is connecting to id.worx.com instead. Changed the address in the source code et voila - adapter is working again.

I am not sure if this is a change everybody would profit from since I have not seen any complaints about the worx API not working. For me it did the trick.

Best,
Tobi

[sqw534]

I am observing the same problem. Is anyone able to do the above mentioned workaround and build a test version for 3.4.x?
I can test it afterwards. Would be great to have the binding up and running again.

[berland]

I am also seeing the same problem. Tried a quick-fix by aliasing the hostnames in /etc/hosts, but that only leaves me with an SSL handshake problem, which probably makes sense.

[sihui62]

The latest 4.1.0 snapshot fixes that problem, it also works on 4.2.x:

https://community.openhab.org/t/worx-landroid-binding/95246/389

[sqw534]

I can confirm it is working. Thanks for your support. Von: sihui ***@***.***> Gesendet: Dienstag, 7. Mai 2024 10:24 An: nibi79/worxlandroid ***@***.***> Cc: sqw534 ***@***.***>; Comment ***@***.***> Betreff: Re: [nibi79/worxlandroid] Wrong API endpoint (Issue #102) The latest 4.1.0 snapshot fixes that problem, it also works on 4.2.x: https://community.openhab.org/t/worx-landroid-binding/95246/389 — Reply to this email directly, view it on GitHub <#102 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL5IULLZOXE5SJGZNSNHUTTZBCFTNAVCNFSM6AAAAAA7AEYBL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXG4ZTANBTGQ> . You are receiving this because you commented. <https://github.com/notifications/beacon/AL5IULM7N4TIVLM45G5B3YTZBCFTNA5CNFSM6AAAAAA7AEYBL2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT5BDJYE.gif> Message ID: ***@***.*** ***@***.***> >