XMPP issue OH2

I have an issue which I have been trying to solve myself to no avail.

On OH1 I am using the XMPP action to communicate to Google Talk. It works without problems.

I moved the configuration to OH2 into a xmpp.cfg file which has the following contents:

########################## XMPP Action configuration ##################################
#
# The XMPP server to use, e.g. "jabber.org", "talk.google.com" or "talkx.l.google.com"
servername=talk.google.com

# The Security mode used for the XMPP connection. Can be either 'required', 'enabled'
# or 'disabled'. Defaults to 'disabled', which means that TLS will not be used.
# Warning: If you change this to non-disabled, then you must make sure that your
# TLS server certificate can be validated, otherwhise the connection will fail.
securitymode=required

# You need this "tlspin" if openhab cannot verify the certificate from the google server
tlspin=CERTSHA256:9e670d6624fc0c451d8d8e3efa81d4d8246ff9354800de09b549700e8d2a730a

# The XMPP Proxyserver to use, e.g. "gmail.com"
proxy=gmail.com

# the server port to use (optional, defaults to 5222)
#port=5222

# the username and password for the sending XMPP account
username=myusername@gmail.com
password=mynicepassword

# a comma separated list of users that are allowed to use the XMPP console
#consoleusers=

# the multi user chat to join, e.g. openhab@chat.example.com
#chatroom=

# the nickname used in the multi user chat (optional, defaults to openhab-bot)
#chatnickname=

# the password required to join the multi user chat
#chatpassword=

This configuration is similar to OH1 but it always gives me the following error:
[WARN ] [rg.openhab.action.xmpp.internal.XMPP] - Could not send XMPP message as connection is not correctly initialised!

I don’t get anymore information if I set the log:level to DEBUG. It must have something to do with improper handshaking or not reading the TLS PIN from the config file.

So who has a working configuration on OH2?
Or any ideas what might work?

Update. Did see the following error as well in the log:

[WARN ] [rg.jivesoftware.smack.XMPPConnection] - Connection closed with error
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate not pinned. Use 'CERTPLAIN:

Again, the xmpp.cfg does pin the tls cert needed to communicate with Google.

Nobody using XMPP these days?

I had to use CERTPLAIN for my tlspin

tlspin=CERTPLAIN:3082049d30820385a00302010202087d758e52031f53ce300d06092a864886f70d01010b05003049310b300906035504061302555331133011060355040a130a476f6f676c6520496e63312530230603550403131c476f6f676c6520496e7465726e657420417574686f72697479204732301e170d3136303931343038323631365a170d3136313230373038313930305a3063310b30090603550406130255533113301106035504080c0a43616c69666f726e69613116301406035504070c0d4d6f756e7461696e205669657731133011060355040a0c0a476f6f676c6520496e633112301006035504030c09676d61696c2e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100a8a29e432c4347ef34199b0d3f952e537ffbd9cdf398077007683f2b155999d32a11f9778404ec7c6ccbbceaec0e5f77aaa42dc720c6de88bb2f0252139c2c02df43e203304b4f0a0be7e6482d54df4fd76657915ab444af3a638aceac652bce88971920ed5ed3d6c8305ba8ecfb7abc44b5ad7120b10cac3d25daf81db3a97e12e1feee5f8f61f1af236ffe2713c8f7114fe3bc17f116c9e2a603641b4bd4933737ab56873127b90925b4bb84e340dbc1200700e32b161086f12af5ef5f96ce0cb2b35cde2eff917c2981594a01cf03ba3d2be6ec948a9fb784ea9b3742a0fe6cf3e743a3f22cea140d3fc28bc05dc5a9a67b05c932a9d5955ffe229f6417690203010001a382016d30820169301d0603551d250416301406082b0601050507030106082b06010505070302303b0603551d11043430328209676d61696c2e636f6d820b2a2e676d61696c2e636f6d8218706f6c6963792e6d74612d7374732e676d61696c2e636f6d306806082b06010505070101045c305a302b06082b06010505073002861f687474703a2f2f706b692e676f6f676c652e636f6d2f47494147322e637274302b06082b06010505073001861f687474703a2f2f636c69656e7473312e676f6f676c652e636f6d2f6f637370301d0603551d0e041604144bc49e4c83542f03c748cdf67a0c08abd86d5895300c0603551d130101ff04023000301f0603551d230418301680144add06161bbcf668b576f581b6bb621aba5a812f30210603551d20041a3018300c060a2b06010401d6790205013008060667810c01020230300603551d1f042930273025a023a021861f687474703a2f2f706b692e676f6f676c652e636f6d2f47494147322e63726c300d06092a864886f70d01010b050003820101005202a8a4af439a44fbb17c273d70218cb8695984fb403812bcf5e78828f5fce98ef004b378a2486ec0c7ea7ac256a5e829e822d4f09d351d66f06905db6c84c72f0ac56a010173d0d2322dff84b7cfb8b76eb355878a48c0801db7a8384ffc47de262ab43a52330574e7a3ebe06977907a9326380ad24008f220792cfa3ae5449445e56498d8137bd2b494c9a2f9ad6099c24b9e5a2ad0724c455b9dacac48e097b65bdaa74b677e2b8f9b95a829b3ce6fafc158f73056fef85bfd068ee97751c14b9294a0eaff9247d9c000759b657cb365514f03633d5dc83d82e68ce25c90e1fd79721f7ba59ceda00663afc63588d3e154bf42caf559dea401011b565459

Thank you! That worked.

How did you get the CERTPLAIN?

I think it came up in the logs when I tried a CERTSHA256.

ok, thanks again.