Unwanted effects of a required setting for another binding

A user of the tankerkoenig binding complained about a side effect caused by the rwe smarthome binding. Rwe requests this setting

Djdk.tls.client.protocols=TLSv1 \

Using this setting the web-request of the tankerkoenig binding doesn’t work anymore.

See discussion here:Tankerkoenig Binding now available on the marketplace

Could somebody assist?

Try -Djdk.tls.client.protocols="TLSv1,TLSv1.1,TLSv1.2" (or whatever TLS version tankerkoenig requires to work).

Thanks for the feedback.
Since Tankerkoenig worked without a setting, what does OHW use as a default?

PS: Sorry for the typos, typing on a small smartphone while sitting on the back of a Fiat 500 ian’t fun.

Dunno, probably nothing special, i.e. the java default.

After changing the line to:

-Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 \

is the RWE binding not working anymore. So I have to use again


So this way is not working at least for me :frowning:

I did read something about setting this TLS-version together with an argument like .
Found here in Box for “Use Case”: “Java Applets/WebStart”.

Would something like that be possible to set for differnet bindings?